Close problem in ioFTPD (no crash)

[BoNeZz]

Hi

i have a problem because i found my ioftpd closed

from ioFTPD.log i can see it:

07-28-2010 04:43:05 STOP: "PID=5208"
07-28-2010 10:17:53 SSL: "Found certificate" "name=ioFTPD" "Service=FTP_Service" "(Certificate_name)"
07-28-2010 10:17:53 START: "PID=7160" "CmdLine="
07-28-2010 10:17:53 PRELOAD: "begin" "..\etc\default.vfs"
07-28-2010 10:17:54 PRELOAD: "points=18" "..\etc\default.vfs"

07-29-2010 04:00:32 STOP: "PID=7160"
07-29-2010 12:52:01 SSL: "Found certificate" "name=ioFTPD" "Service=FTP_Service" "(Certificate_name)"
07-29-2010 12:52:01 START: "PID=5208" "CmdLine="
07-29-2010 12:52:01 PRELOAD: "begin" "..\etc\default.vfs"
07-29-2010 12:52:02 PRELOAD: "points=18" "..\etc\default.vfs"

i have ioftpd 7.5.7r + nxtools 1.2.1 + ioprecheck.

i not installed serviceinstaller because ioftpd don't crash, but only close the service, and i don't know if there is an option in ioftpd.ini.

thanks for the support and sorry for another thread.

[Yil]

You'll have to be a bit more specific. Does it stop responding? Report the site is closed when trying to login? Is the process still running? If it appears to not respond but it should be, try enabling the 'Restart_On_Deadlock' feature which will kill it if it gets locked up... Just set it up as a service to auto-restart if it happens.

[BoNeZz]

Originally Posted by Yil

You'll have to be a bit more specific. Does it stop responding? Report the site is closed when trying to login? Is the process still running? If it appears to not respond but it should be, try enabling the 'Restart_On_Deadlock' feature which will kill it if it gets locked up... Just set it up as a service to auto-restart if it happens.

no ioftpd.exe in task manager, if i try to log in in ftp, seems down.

[Yil]

Shy of some new unknown behavior ioFTPD has 3 "exit" paths.

1) Graceful shutdown via site shutdown which you'll see a log message for.

2) The lockup detector or no connectivity detector which you'll see a log message for.

3) A crash which won't generate a log message but will generate a CrashLog.txt file and a TINY/MINI dump file.

Which best fits what you're seeing?

[BoNeZz]

Originally Posted by Yil

Shy of some new unknown behavior ioFTPD has 3 "exit" paths.

1) Graceful shutdown via site shutdown which you'll see a log message for.

2) The lockup detector or no connectivity detector which you'll see a log message for.

3) A crash which won't generate a log message but will generate a CrashLog.txt file and a TINY/MINI dump file.

Which best fits what you're seeing?

1) i don't make site shutdown

2) from log i can see only STOP PID. anyway are two times that happen. when re-happen i check logs one more time, and i paste you.

3) crash log not create. because i think that isn't crash.

thanks always for the support Yil.

[BoNeZz]

Originally Posted by Yil

Shy of some new unknown behavior ioFTPD has 3 "exit" paths.

1) Graceful shutdown via site shutdown which you'll see a log message for.

2) The lockup detector or no connectivity detector which you'll see a log message for.

3) A crash which won't generate a log message but will generate a CrashLog.txt file and a TINY/MINI dump file.

Which best fits what you're seeing?

in error.log i found a problem.

in attachment logs from it, i hope that you know how to fix it.

07-27-2010 00:55:41 AcceptEx() failed with error: 64
07-27-2010 00:56:41 No services appear to be online! Defined=1, Active=1, Online=0, Failed=0.  Exiting!
07-28-2010 04:42:04 AcceptEx() failed with error: 64
07-28-2010 04:43:04 No services appear to be online! Defined=1, Active=1, Online=0, Failed=0.  Exiting!
07-29-2010 03:59:32 AcceptEx() failed with error: 64
07-29-2010 04:00:32 No services appear to be online! Defined=1, Active=1, Online=0, Failed=0.  Exiting!

[ArtX]

try updating ioFTPD to 7.5.9 to see if the problem goes away, if not i would disable any scripts you have running, if that still doesn't fix it then its definitely an ioFTPD bug

[BoNeZz]

Originally Posted by Carpo

try updating ioFTPD to 7.5.9 to see if the problem goes away, if not i would disable any scripts you have running, if that still doesn't fix it then its definitely an ioFTPD bug

ok i try to update, for update need only that i change ioftpd.exe old with new ioftpd.exe in system folder, or needed replace other\more stuff?

[Yil]

Hmm... 7.5.7? Yes, please update to 7.5.9 as this will almost certainly solve the problem. You'll note that the Changelog entry for 7.5.8 modifies the behavior of the server when it detects a service is offline which is exactly the error message that you are seeing:
"No services appear to be online! Defined=1, Active=1, Online=0, Failed=0. Exiting!"

Offline means the local connection attempt to the service failed. It's possible for this to fail in rare situations and thus the problem of shutting down. On the other hand, the new 7.5.8+ behavior is it must be "offline" 3 times in a row and thus promoted to "failed" state which probably means something is wrong and restarting the best option...

There is one downside to this "feature". Someone can denial of service the server and trick it into shutting down. If you find people doing this to you there is a simple solution. Just setup a 2nd service on a different port that isn't exposed to the outside world. The server will now only shutdown if ALL services report they have failed and the 2nd local-only service will never be unless the server actually locks up...

NOTE: To update from one release to the next walk through the first few lines of the Changelog for EACH release between yours and the one you are updating to and apply all the changes listed. It's actually pretty simple for point releases with just the .exe/pdb usually needing to be changed.