[webizen]

Originally Posted by craigles

Tried setting the max idle time to zero, but it didn't make any difference from what I could see.

I did however install 4.2 and set it to suEXEC PHP Daemon mode and that worked perfect and let backupbuddy complete the send without it stopping and being killed, but there is another issue with 4.2 and the suEXEC PHP Daemon mode which is preventing us from using it.

When max idle set to -1, it will be overridden with 30 seconds (per developer). For the example shown in pm, after 36 seconds, ext app process is removed by parent. However, leave more idle process running will eat up your system resources which is a bad. Therefore, that "Max idle time reached, stop external application." message isn't an indication of problem. It just means these vhosts are not that busy. On the other hand, if you do _not_ care the resource issue, you can leave max idle time long enough to see if message show up less frequently.