LiteSpeed does not work when CageFs is enabled in Litepseed config.
Announcement
Collapse
No announcement yet.
cPanel+LiteSpeed+CageFs not working CL6
Collapse
X
-
LiteSpeed with Lve/no Lve works fine but as soon as i enable CageFs in LiteSpeed Admin it just does not work. LiteSpeed logs start filling up :-
Code:2012-08-02 00:59:03.979 INFO Remove pid: 858631, exitcode: 123 2012-08-02 00:59:03.984 INFO Remove pid: 858632, exitcode: 123 2012-08-02 00:59:03.988 INFO Remove pid: 858633, exitcode: 123 2012-08-02 00:59:03.993 INFO Remove pid: 858634, exitcode: 123 2012-08-02 00:59:03.998 INFO Remove pid: 858635, exitcode: 123 2012-08-02 00:59:04.008 INFO Remove pid: 858636, exitcode: 123 2012-08-02 00:59:13.086 NOTICE [APVH_*****ts_Suphp:] Increase effective max connections to 2. 2012-08-02 00:59:13.093 INFO Remove pid: 858638, exitcode: 123 2012-08-02 00:59:13.093 NOTICE [122.168.207.45:16407-0#APVH_******ts.com] LVE limit is reached, reduce max connections to: 1. 2012-08-02 00:58:55.813 INFO Remove pid: 858396, exitcode: 123 2012-08-02 00:58:55.813 NOTICE [96.47.224.42:53431-0#APVH_*********.info] LVE limit is reached, reduce max connections to: 0. 2012-08-02 00:58:58.071 NOTICE [APVH_patriot_Suphp:] stop worker processes 2012-08-02 00:58:58.074 NOTICE [APVH_deplscom_Suphp:] stop worker processes 2012-08-02 00:59:03.030 NOTICE [APVH_patriot_Suphp:] Increase effective max connections to 1. 2012-08-02 00:59:03.043 INFO Remove pid: 858409, exitcode: 123 2012-08-02 00:59:03.047 INFO Remove pid: 858410, exitcode: 123
-
Could you please increase "PHP suEXEC Max Conn" setting in LiteSpeed configuration ?
Also, could you please try to increase maxEntryProcs (Concurrent Connections) limit for that account (LVE)?
If this will not solve the issue, please post request to the CloudLinux support.
Comment
-
Did you try to increase "PHP suEXEC Max Conn" setting in LiteSpeed configuration (and then restart LiteSpeed) ?
I am not sure what might be causing the issue.
Please, contact our support at helpdesk.cloudlinux.com with server access info, so we could check.
Comment
Comment