[Resolved] Litespeed restarting automatically, HELP!

Status
Not open for further replies.
S

sahith

Well-Known Member
#1
#1
My litespeed is getting restarted automatically every3-4 hours. Following is grabbed from Server log viewer for one restart.

2014-02-18 00:03:30.991NOTICEServer Restart Request via Signal...
2014-02-18 00:03:30.991NOTICE[PID: 3059]: start cgid: 14199, /usr/local/lsws/bin/lscgid
2014-02-18 00:03:30.991NOTICE[Child: 3062] Start shutting down gracefully ...
2014-02-18 00:03:30.991NOTICE[Child: 3061] Start shutting down gracefully ...
2014-02-18 00:03:31.189NOTICEYour License key will expire in 18 days
2014-02-18 00:03:31.189NOTICELoading LiteSpeed/4.2.7 Enterprise ...
2014-02-18 00:03:31.190NOTICE[ADMIN] server socket: uds://usr/local/lsws/admin/tmp/admin.sock.7322
2014-02-18 00:03:31.190NOTICELoading configuration from /usr/local/lsws/conf/httpd_config.xml ...
2014-02-18 00:03:31.191NOTICERecovering server socket: [108.163.144.12:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [108.163.144.12:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [127.0.0.1:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [127.0.0.1:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.136:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.136:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.137:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.137:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.138:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.138:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.139:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [174.142.55.139:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.216:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.216:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.217:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.217:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.218:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.218:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.219:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [72.55.180.219:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [[::]:443]
2014-02-18 00:03:31.191NOTICERecovering server socket: [[::]:81]
2014-02-18 00:03:31.191NOTICERecovering server socket: [*:7080]
2014-02-18 00:03:31.191NOTICE[config] chroot is disabled.
2014-02-18 00:03:31.193NOTICE[PID: 14212]: start cgid: 14213, /usr/local/lsws/bin/httpd
2014-02-18 00:03:31.193NOTICEThe maximum number of file descriptor limit is set to 9000.
2014-02-18 00:03:31.193NOTICE[config:server:epsr:lsphp5]'Process Limit' probably is too low, adjust the limit to: 1300.
2014-02-18 00:03:31.194ERROR[config:server:epsr:lsphp55] invalid path - /usr/local/lsws/fcgi-bin/lsphp55, it cannot be started by Web server!
2014-02-18 00:03:31.194NOTICE[config:server:rails] Cannot find ruby interpreter, Rails easy configuration is turned off
2014-02-18 00:03:31.194ERROR[config:scripthandler] Can not find handler with type: 12, name: lsphp55.
2014-02-18 00:03:31.194ERROR[config:scripthandler] Can not find External Application: lsphp55, type: lsapi
2014-02-18 00:03:31.194ERROR[config:scripthandler] use static file handler for suffix [php55]
2014-02-18 00:03:31.194ERROR[ModSecurity] unknown server variable while parsing: MULTIPART_STRICT_ERROR
2014-02-18 00:03:31.236INFOProcessing config file: /usr/local/apache/conf/includes/pre_virtualhost_global.conf
2014-02-18 00:03:31.236INFOProcessing config file: /usr/local/apache/conf/includes/pre_virtualhost_2.conf
2014-02-18 00:03:31.236INFOProcessing config file: /usr/local/apache/conf/includes/post_virtualhost_global.conf
2014-02-18 00:03:31.236INFOProcessing config file: /usr/local/apache/conf/includes/post_virtualhost_2.conf
2014-02-18 00:03:31.239NOTICElitespeed (14212) is ready
2014-02-18 00:03:31.240NOTICE[AutoRestarter] new child process with pid=14214 is forked!
2014-02-18 00:03:31.240NOTICE[AutoRestarter] new child process with pid=14215 is forked!
2014-02-18 00:03:31.240NOTICE[Child: 14214] Setup swapping space...
2014-02-18 00:03:31.240NOTICE[child: 14214] Successfully change current user to nobody
2014-02-18 00:03:31.240NOTICE[Child: 14214] Core dump is enabled.
2014-02-18 00:03:31.240NOTICE[Child: 14215] Setup swapping space...
2014-02-18 00:03:31.240NOTICE[child: 14215] Successfully change current user to nobody
2014-02-18 00:03:31.240NOTICE[Child: 14215] Core dump is enabled.
2014-02-18 00:03:31.240NOTICE[Child: 14214] LiteSpeed/4.2.7 Enterprise starts successfully!
2014-02-18 00:03:31.240NOTICE[Child: 14215] LiteSpeed/4.2.7 Enterprise starts successfully!
2014-02-18 00:03:31.241NOTICENew litespeed process is ready, litespeed (3061) stops listeners
2014-02-18 00:03:31.281NOTICENew litespeed process is ready, litespeed (3062) stops listeners
2014-02-18 00:03:32.000NOTICE[AutoUpdate] Checking for new releases..., pid=14234
2014-02-18 00:03:32.035NOTICEStart to clean up cache directory, pid=14235
Click to expand...
I need help clearing this issue please. I would like to know about those bold lines especially.

Thank you.
 
S

sahith

Well-Known Member
#2
#2
N

NiteWave

Administrator
#3
#3
2014-02-18 00:03:30.991NOTICEServer Restart Request via Signal...
Click to expand...
please check your cron jobs, if there is one to restart web server.
can determine by check the time stamp of restarting, if it's almost in fixed time.

also check /usr/local/lsws/logs/lsrestart.log, see if any clue from it.

2014-02-18 00:03:31.194ERROR[config:server:epsr:lsphp55] invalid path - /usr/local/lsws/fcgi-bin/lsphp55, it cannot be started by Web server!
Click to expand...
because file /usr/local/lsws/fcgi-bin/lsphp55 not exist, can be ignored. or just bypass it by
Code: 
#cd /usr/local/lsws/fcgi-bin
#ln -s lsphp5 lsphp55
 
Last edited by a moderator:
S

sahith

Well-Known Member
#4
#4
grabbed following from the /usr/local/lsws/logs/lsrestart.log

Sun Feb 16 20:02:00 IST 2014
start, LSWS running: 0
Sun Feb 16 20:05:08 IST 2014
restart, LSWS running: 1
Sun Feb 16 20:05:57 IST 2014
restart, LSWS running: 1
Sun Feb 16 20:10:30 IST 2014
stophttpd, LSWS running: 1
Sun Feb 16 20:10:30 IST 2014
restart, LSWS running: 1
Sun Feb 16 20:10:42 IST 2014
stophttpd, LSWS running: 1
Sun Feb 16 20:10:42 IST 2014
restart, LSWS running: 1
Sun Feb 16 20:10:45 IST 2014
stophttpd, LSWS running: 1
Sun Feb 16 20:10:45 IST 2014
restart, LSWS running: 1
Sun Feb 16 20:11:03 IST 2014
restart, LSWS running: 1
Sun Feb 16 20:12:07 IST 2014
stop, LSWS running: 1
Sun Feb 16 23:35:56 IST 2014
start, LSWS running: 0
Sun Feb 16 23:36:57 IST 2014
stop, LSWS running: 1
Sun Feb 16 23:39:23 IST 2014
start, LSWS running: 0
Mon Feb 17 00:07:07 IST 2014
restart, LSWS running: 1
Mon Feb 17 00:13:32 IST 2014
restart, LSWS running: 1
Mon Feb 17 01:56:43 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 01:56:43 IST 2014
restart, LSWS running: 1
Mon Feb 17 07:11:11 IST 2014
restart, LSWS running: 1
Mon Feb 17 08:49:12 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 08:49:12 IST 2014
restart, LSWS running: 1
Mon Feb 17 08:49:22 IST 2014
restart, LSWS running: 1
Mon Feb 17 08:54:19 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 08:54:19 IST 2014
restart, LSWS running: 1
Mon Feb 17 08:54:25 IST 2014
restart, LSWS running: 1
Mon Feb 17 08:58:46 IST 2014
stop, LSWS running: 0
Mon Feb 17 09:00:42 IST 2014
restart, LSWS running: 0
Mon Feb 17 09:06:45 IST 2014
restart, LSWS running: 1
Mon Feb 17 09:06:54 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 09:06:54 IST 2014
restart, LSWS running: 1
Mon Feb 17 09:13:19 IST 2014
restart, LSWS running: 1
Mon Feb 17 09:13:28 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 09:13:28 IST 2014
restart, LSWS running: 1
Mon Feb 17 09:15:29 IST 2014
restart, LSWS running: 1
Mon Feb 17 09:15:37 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 09:15:37 IST 2014
restart, LSWS running: 1
Mon Feb 17 09:31:46 IST 2014
restart, LSWS running: 1
Mon Feb 17 09:31:50 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 09:31:50 IST 2014
restart, LSWS running: 1
Mon Feb 17 10:30:12 IST 2014
restart, LSWS running: 1
Mon Feb 17 10:38:37 IST 2014
restart, LSWS running: 1
Mon Feb 17 12:02:59 IST 2014
restart, LSWS running: 0
Mon Feb 17 12:03:02 IST 2014
start, LSWS running: 1
Mon Feb 17 12:08:39 IST 2014
restart, LSWS running: 1
Mon Feb 17 12:10:35 IST 2014
stop, LSWS running: 1
Mon Feb 17 12:25:25 IST 2014
start, LSWS running: 0
Mon Feb 17 12:33:57 IST 2014
restart, LSWS running: 1
Mon Feb 17 12:56:36 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 12:56:36 IST 2014
restart, LSWS running: 1
Mon Feb 17 12:56:37 IST 2014
stop, LSWS running: 1
Mon Feb 17 12:56:45 IST 2014
start, LSWS running: 0
Mon Feb 17 13:02:56 IST 2014
stop, LSWS running: 1
Mon Feb 17 13:18:28 IST 2014
start, LSWS running: 0
Mon Feb 17 13:18:41 IST 2014
restart, LSWS running: 1
Mon Feb 17 13:19:34 IST 2014
restart, LSWS running: 1
Mon Feb 17 14:43:51 IST 2014
restart, LSWS running: 1
Mon Feb 17 14:46:32 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 14:46:32 IST 2014
restart, LSWS running: 1
Mon Feb 17 15:04:05 IST 2014
stophttpd, LSWS running: 1
Mon Feb 17 15:04:05 IST 2014
restart, LSWS running: 1
Mon Feb 17 18:29:25 IST 2014
restart, LSWS running: 1
Mon Feb 17 21:16:28 IST 2014
restart, LSWS running: 1
Tue Feb 18 00:03:30 IST 2014
restart, LSWS running: 1
Tue Feb 18 03:40:34 IST 2014
restart, LSWS running: 1
Tue Feb 18 08:57:43 IST 2014
restart, LSWS running: 1
Tue Feb 18 13:24:50 IST 2014
restart, LSWS running: 1
Tue Feb 18 17:01:54 IST 2014
restart, LSWS running: 1
Tue Feb 18 20:05:37 IST 2014
restart, LSWS running: 1
Click to expand...
It seems more restarts happening in a single day. May i know how many cron jobs running in my server at which times?
 
S

sahith

Well-Known Member
#7
#7
I figured it out finally. While rotating logs cPanel restarts webserver. In this case cpanel restarting Litespeed whenever logs like access_log, domlogs reached their threshold. So i disabled those logs which solved my problem.
 
N

NiteWave

Administrator
#8
#8
Thanks for the update, I forgot about the log rotation by cPanel...
for your reference, I recalled some users use "piped log" in WHM/cPanel to avoid log rotation.
 
Status
Not open for further replies.
Top