LiteSpeed is changing the configuration

J

justAndre

Member
#1
#1
Hi,

I have a strange problem with litespeed.

If I let LS to use Cloudlinux with LVE in 5 days the configuration is changing to CageFS. I want to mention that nobody is accesing the server to change the configuration, I dont know why LS is making this change in the configuration file without a request from an administrator.

I have exactly the same configuration on another server and there nothing happens with the settings.

I dont want to use CageFS because all the sites are offline with this error on the admin panel:

2014-03-20 08:03:46.415 ERROR [APVH_nexdddsr_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-03-20 08:03:46.416 ERROR [APVH_komparrts_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-03-20 08:03:46.417 ERROR [APVH_nexdddsr_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-03-20 08:03:46.417 ERROR [APVH_komparrts_Suphp:]: Failed to start one instance. Resouce limit reached!
 
M

mistwang

LiteSpeed Staff
#2
#2
LS wont change configuration by itself. you should check file time stamp and admin console access log.
Resouce limit is part of LVE, not CageFS, I guess you need to look into what and why resource limit has been reached.
 
J

justAndre

Member
#3
#3
mistwang said:
LS wont change configuration by itself. you should check file time stamp and admin console access log.
Resouce limit is part of LVE, not CageFS, I guess you need to look into what and why resource limit has been reached.
Click to expand...
I'm not kidding, the configuration is changing without my intervention(i'm the only one who has the acces to LS admin interface). Today the configuration is with LVE and tomorow morning the configuration is on CageFS and all the sites are down due to the "Resouce limit reached" error.
 
J

justAndre

Member
#4
#4
Hi again,

Today litespeed crashed again, the error I see is this.

2014-04-16 05:39:16.130ERROR[config:server:epsr:lsphp55] invalid path - /usr/local/lsws/fcgi-bin/lsphp55, it cannot be started by Web server!
2014-04-16 05:39:16.130ERROR[config:scripthandler] Can not find handler with type: 12, name: lsphp55.
2014-04-16 05:39:16.130ERROR[config:scripthandler] Can not find External Application: lsphp55, type: lsapi
2014-04-16 05:39:16.130ERROR[config:scripthandler] use static file handler for suffix [php55]
2014-04-16 05:39:16.132ERROR[ModSecurity] unknown server variable while parsing: MULTIPART_STRICT_ERROR
2014-04-16 05:39:16.177ERROR[ModSecurity] unknown server variable while parsing: WWW-Authenticate
2014-04-16 05:39:16.196ERROR[ModSecurity] unknown server variable while parsing: FILES_NAMES
2014-04-16 05:39:16.959ERROR[APVH_kompacts_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:18.258ERROR[APVH_devester_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:19.884ERROR[APVH_beius_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:20.166ERROR[APVH_mfinansc_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:20.623ERROR[APVH_cybeero1_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:23.654ERROR[APVH_glass_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:25.310ERROR[APVH_ejanteco_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:31.485ERROR[APVH_calatoro_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:33.392ERROR[APVH_azsmrro_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:34.594ERROR[APVH_bacaoro1_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:36.100ERROR[APVH_cybeero1_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:36.102ERROR[APVH_beius_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:36.104ERROR[APVH_kompacts_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:37.369ERROR[APVH_ejanteco_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:38.070ERROR[APVH_devester_Suphp:]: Failed to start one instance. Resouce limit reached!
2014-04-16 05:39:39.283ERROR[APVH_beius_Suphp:]: Failed to start one instance. Resouce limit reached!
Click to expand...
Any idea what to do ?
 
M

mistwang

LiteSpeed Staff
#5
#5
You need to raise LVE limit to allow two running instance of litespeed during a server graceful restart.
If the limit has been reached by PHP processes started by the previous instance of litespeed, the newly started litespeed instance could not start any PHP process.

Raise LVE limit to give some head room.
 
J

justAndre

Member
#6
#6
mistwang said:
You need to raise LVE limit to allow two running instance of litespeed during a server graceful restart.
If the limit has been reached by PHP processes started by the previous instance of litespeed, the newly started litespeed instance could not start any PHP process.

Raise LVE limit to give some head room.
Click to expand...

Where do I need to change LVE limit? in cloudlinux or litespeed ?
 
N

NiteWave

Administrator
#11
#11
I think EP is too low for a busy user.
a lsphp5 process may fork more sub processes, for example, a simple php code
exec("sh ls -l | head")
will fork 2 additional sub processes

anyway you can try to increase it to see if those errors disappear.
 
S

sahostking

Well-Known Member
#12
#12
Did you solve this by any chance? We had 1 client report this today. Was watching apache logs then suddenly noticed all sites have this issue. When I disable CageFS all is good though but would like to have cagefs on again. Any ideaS?

Note: Can't be setup issue as it hasn't changed in months. This is like magic :/
 
N

NiteWave

Administrator
#13
#13
you mean apache logs filled with
"Failed to start one instance. Resouce limit reached!" ?

per discussion above, it's likely a configuration issue : LVE limit too low.
if the issue happened only once, it's hard to find out the root cause. maybe just a restart fix it.
if it happens repeatedly, try to raise LVE limit as suggested, see if any improvement.

also, you can try latest 4.2.19. to be sure to run tests against latest version.
 
You must log in or register to reply here.
Top