FlashFXP Forums - View Single Post

Yil · 08-05-2010, 01:33 AM

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.

08-05-2010, 01:33 AM
Yil Too much time... Join Date: May 2005 Posts: 1,194	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.