Cumulus Support

Caused MX to have problems seconds after the 0900 rollover this morning - although it appeared to keep running. Diags file (truncated to show output from 0700 this morning) and program stdout/stderr attached. MX restarted around 0943 to clear up remaining problems.
NB: MX is the only user program running on this box.

It could just be that you need to increase the max number of file handles (note that this isn't just for disk files) if yours is still at the default of 1024; Google found this for me - http://stackoverflow.com/questions/8988 ... -on-ubuntu

It could be that there's a leak somewhere - perhaps the FTP component leaves files and/or TCP connections open when it gets timeouts.

steve wrote:It could just be that you need to increase the max number of file handles

I'm reluctant to do that, as I have had MX running for 12 months now without this error occurring. I will keep my eye on it for the moment, and may take action if there is a recurrence.

steve wrote:It could be that there's a leak somewhere - perhaps the FTP component leaves files and/or TCP connections open when it gets timeouts.

You would certainly hope this isn't the case!

Thanks for taking a look.

Apparently 'lsof' (may need installing) is good for investigating what files are open by what. It produces rather a lot of output, though, so you really need to be quite good at sed and awk and things like that, although lsof does have some useful options itself to limit the output.