Somer Error?

[k3oni]

Hi, we seem to have same issue here and the wraper script seems to not work.. just installed litespeed with cpanel 2 days ago:

2008-04-02 13:20:01.414 NOTICE [AutoRestarter] child process with pid=23710 received signal=9, no core file is created!
2008-04-02 13:20:01.418 NOTICE [AutoRestarter] cleanup children processes and unix sockets belong to process 23710 !
2008-04-02 13:20:01.418 INFO [AutoRestater] Clean up child process with pid: 23787
2008-04-02 13:20:01.420 NOTICE [AutoRestarter] child process with pid=23708 received signal=9, no core file is created!
2008-04-02 13:20:01.423 NOTICE [AutoRestarter] cleanup children processes and unix sockets belong to process 23708 !
2008-04-02 13:20:01.423 INFO [AutoRestater] Clean up child process with pid: 23709
2008-04-02 13:20:01.423 INFO [AutoRestater] Clean up child process with pid: 23845

This is happening every 1 minute.

[mistwang]

Maybe you need to uncheck "monitor httpd" under service manager page.

[k3oni]

Originally Posted by mistwang

Maybe you need to uncheck "monitor httpd" under service manager page.

I hav already did that, also disabled Auto Restart and LFD on the server, but this is still happening.

Any ideas?

[mistwang]

check if there is any cron job that tries to stop lshttpd process, there are some security scripts doing that.

[k3oni]

Thanks for trying to help here, seems that there is no cron job.

2008-04-03 09:30:01.297 NOTICE [AutoRestarter] child process with pid=12438 received signal=9, no core file is created!
2008-04-03 09:30:01.300 NOTICE [AutoRestarter] cleanup children processes and unix sockets belong to process 12438 !
2008-04-03 09:30:01.301 INFO [AutoRestater] Clean up child process with pid: 12464
2008-04-03 09:30:01.304 NOTICE [AutoRestarter] child process with pid=12436 received signal=9, no core file is created!
2008-04-03 09:30:01.309 NOTICE [AutoRestarter] cleanup children processes and unix sockets belong to process 12436 !
2008-04-03 09:30:01.309 INFO [AutoRestater] Clean up child process with pid: 12439
2008-04-03 09:30:01.412 INFO Stop listener x.x.x.x:443.
2008-04-03 09:30:01.412 INFO Stop listener x.x.x.x:80.
2008-04-03 09:30:01.412 INFO Stop listener x.x.x.x:443.
2008-04-03 09:30:01.412 INFO Stop listener x.x.x.x:80.
2008-04-03 09:30:01.412 INFO Stop listener x.x.x.x:443.
2008-04-03 09:30:01.412 INFO Stop listener x.x.x.x:80.
2008-04-03 09:30:01.412 NOTICE [child: 12755] Successfully change current user to nobody
2008-04-03 09:30:01.412 NOTICE [Child: 12755] Core dump is enabled.
2008-04-03 09:30:01.412 NOTICE [Child: 12755] Setup swapping space...
2008-04-03 09:30:01.412 NOTICE [Child: 12755] LiteSpeed/3.3.9 Enterprise starts successfully!
2008-04-03 09:30:01.413 NOTICE [AutoRestarter] new child process with pid=12755 is forked!

Interesting part is that once is stoping the listeners on a few IP's, next time on others, another time my them up, so it does not do a restart on all the IP's every time.

[k3oni]

We would really like a solution to this, i can provide whatever logs needed. This restarts are making the sites show as down and need a refresh to bring the sites back up, not best solution when the client is a hosting company.

Please advise, any help would be appreciated, thank you!

[mistwang]

You need to find out which process want to kill lshttpd.
PM me your server login, I can take a look if you want.

[mistwang]

Originally Posted by k3oni

We would really like a solution to this, i can provide whatever logs needed. This restarts are making the sites show as down and need a refresh to bring the sites back up, not best solution when the client is a hosting company.

Please advise, any help would be appreciated, thank you!

A cron job added by root user is killing all processes running as nobody every minutes. the script is /root/sks.pl

[k3oni]

Thanks for that.. seems that i missed exactly teh script that was put in place by us.. great . Will have to modify that as it is working correctly only on Cpanel with apache.

Thanks again George!

[mistwang]

Originally Posted by mistwang

check if there is any cron job that tries to stop lshttpd process, there are some security scripts doing that.

Next time, please look harder along what I have suggested.