Start a new topic script in Linux

jvamos @ Mon Apr 21 08:25:00 EEST 2014

I am having difficulty running Crushftp7 with the new script provided. I can't reach the http GUI. Running the jar command does launch the server and creating an administer both work. Is this something suited for systemd?



spinkb @ Mon Apr 21 08:58:11 EEST 2014
What jar command?

What does the script do when you run it?

What shows in the nohup.out file?

What shows in the CrushFTP.log when you use the script?

spinkb @ Mon Apr 21 11:57:04 EEST 2014
Please check again.

That error is a one time error and just means it didn't find a registration code and is going to use default settings. Its normal, expected, and not an issue.

The other line you gave is the line that is logged when eh server is started...but there are other lines too...

Delete the CrushFTP.log and nohup.log. Then start the server with:

./ start

Paste here was gets logged in both of those.

Let me know,
jvamos @ Mon Apr 21 12:11:40 EEST 2014
The Crushftp.LOG is here

The nohup.out file is blank this time.

spinkb @ Mon Apr 21 14:09:38 EEST 2014
This isn't a normal config, you have already made changes.

Delete your prefs.XML file, and your backup folder.

kill all "java" processes running in the background.

Then start CrushFTP again using the script.

Let me know what the log has then.

jvamos @ Mon Apr 21 14:26:25 EEST 2014
I used pidof to find all instances java and close them.

I then deleted all the folders and pasted the log here

and output of nohup.out

The ports all seem wrong...

I noticed it is binding to a strange port so I tried to connect on that port instead.

---Server Started--- LAN IP= WAN IP=**.***.***.***(edited by JV) PORT=9090
04/21/2014 03:23:54 PM|:
04/21/2014 03:23:54 PM|There is now 1 active connections
04/21/2014 03:23:54 PM|:
04/21/2014 03:23:54 PM|Remote client reported an invalid protocol version!
04/21/2014 03:23:54 PM|There are now 0 active connections
04/21/2014 03:23:56 PM|:
04/21/2014 03:23:56 PM|There is now 1 active connections
04/21/2014 03:23:56 PM|:
04/21/2014 03:23:56 PM|Remote client reported an invalid protocol version!
04/21/2014 03:23:56 PM|There are now 0 active connections
spinkb @ Mon Apr 21 14:28:06 EEST 2014
The ports are all correct and default...good.

If you follow the quick start guide, everything is working identical to what the video is showing you... You could login using a web browser at this point using port 8080 or 9090 and HTTP.

jvamos @ Mon Apr 21 14:33:07 EEST 2014
I found that port 8080 will work as it is listed in the log. Port 21 says it's taken in previous logs. This is a fresh installation of Suse 13.1 which has been out for a few months.
I can't see why port 80 isn't binding to the correct port but port 21 seems to be assigned by java.
jvamos @ Mon Apr 21 14:34:13 EEST 2014
I am sorry Ben, didn't realize 80 wasn't a default port.
spinkb @ Mon Apr 21 14:49:47 EEST 2014
Port 21 is use by some other OS FTP server that is installed in your distro.

Port 80 was never supposed to work...default is port 80to avoid conflicting with a server that is already using 80. If your not, login on 8080, go to the admin, prefs, and change the 8080 to be 80 and click save.

Then start using port 80.

jvamos @ Mon Apr 21 15:06:33 EEST 2014
I must have messed something up with my original config trying to get this init script to startup properly and got off track.

Thanks for sorting it out.

jvamos @ Thu Apr 24 16:02:47 EEST 2014
Hey all,

I got some real help making this script work in Suse 13.1. They switched everything over to systemd which required a service for systemd specifically to be functional as an always up server.

There is a link to a rpm that will install crush as a service.

[code]zypper in /download/location/systemd-crushftp-service-0.0-1.1.noarch.rpm
systemctl start crushftp.service
systemctl status crushftp.service
systemctl enable crushftp.service[/code]

The thread where the creator can be thanked is here.

spinkb @ Thu Apr 24 16:28:19 EEST 2014
Its fine for reference...not sure i can do anything with it. The github is GPL, so I can't touch it with the CrushFTP software distribution without the virus that GPL is towards closed things.
But beyond long until this changes? Or this RPM stops working, etc. I hope its making its call to the startup script in some way...
jvamos @ Thu Apr 24 16:46:13 EEST 2014
There may be an edit soon, it's not a good idea to add the repository as it isn't solely for crush's systemd service.

The service does call the init script that comes with Crush7 from the path that is recommended. /var/opt/CrushFTP7_PC/

systemd is something I am just learning how to use and so I had difficulty setting up a service.
jvamos @ Fri Apr 25 09:44:00 EEST 2014
Would it be contrary to GPL to host the systemd service files here or roll them into crush? Or is it due to whom authored it?

Login to post a comment