Support

webizen · #11 10-08-2012, 10:36 PM

Quote:

Originally Posted by Jesse

...
Or alternatively a solution to the SuExec issue outlined in http://www.litespeedtech.com/support...ead.php?t=6299 so this issue can be resolved through deployment of 4.2?

We are currently working on a solution (code change) to resolve this (php.ini override in suEXEC daemon mode).

j1creative · #12 10-29-2012, 01:49 AM

Quote:

Originally Posted by webizen

We are currently working on a solution (code change) to resolve this (php.ini override in suEXEC daemon mode).

Hi, I am the client that they were having this issue with.

I was hoping you would be able to give me an ETA on this at all? I have just completed 2 websites for a rather large client that I would like to backup every week if possible.

It seems to have been dragged out to a couple of months to get this working on my hosting environment...

Any help that you could give Craig, Jesse or I would be great.

Thanks so much.

webizen · #13 10-29-2012, 11:48 PM

Quote:

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.

j1creative · #14 10-30-2012, 12:12 AM

I'm not really sure what this means, but hopefully Jesse or Craig will.

webizen · #15 11-14-2012, 01:45 PM

Quote:

Originally Posted by webizen

We are currently working on a solution (code change) to resolve this (php.ini override in suEXEC daemon mode).

This is in 4.2.1 (beta). Due to PHP internal handling, lsphp5 will turn off suEXEC daemon mode on custom php.ini.

kirkm · #16 11-25-2012, 06:10 PM

Hi,
I also have the same issue with BackupBuddy and LiteSpeed.
Transfer of the backups to Amazon S3 do not complete.
The only workaround for me is to switch back to Apache, manually send the backups, then switch back to LiteSpeed.

If you could update this thread with any progress on this issue, that would be great.
Thanks,
Kirk.

webizen · #17 11-26-2012, 10:49 AM

I am taking you need to php run as long as it can without timeout.

http://www.litespeedtech.com/support...ithout_timeout

kirkm · #18 11-27-2012, 02:50 AM

Thanks for your response.

I tried increasing the times on the first three options described on the link you provided.
1) LiteSpeed connection timeout override - Increased to 240
2) PHP execution time in php.ini - Increased to 120
3) LSAPI_MAX_PROCESS_TIME - Couldn't find this option in Litespeed v4.1.13, so I tried increasing lsphp5 Max Idle Time to 60.

Unfortunately, none of these timer increases worked for me.

Do you have any other suggestions that I could try?

mistwang · #19 11-27-2012, 09:10 AM

Please try 4.2.1

/usr/local/lsws/admin/misc/lsup.sh -f -v 4.2.1

kirkm · #20 11-27-2012, 03:43 PM

Hi,
Just letting you know that the update to LiteSpeed 4.2.1 appears to have fixed my problems with transferring BackupBuddy backup files to Amazon S3.

Currently the backups are only around 100MB. Maybe timeouts could be an issue with larger files, but the first few transfers I tried are working ok (with standard configuration).

Thanks for your help with this issue.
Kirk.