Broken - Server Down! - After Upgrade

XN-Matt

Well-Known Member
#1
Upgraded to 4.2.3 - since then LS will not start.

Downgraded back to 4.2.2 still won't start.

2013-05-31 21:12:27.797 [WARN] [AutoRestarter] forking too frequently, suspend for a while!
2013-05-31 21:12:57.006 [NOTICE] [AutoRestarter] new child process with pid=6480 is forked!
2013-05-31 21:12:57.017 [NOTICE] [Child: 6480] Setup swapping space...
2013-05-31 21:12:57.017 [NOTICE] [child: 6480] Successfully change current user to nobody
2013-05-31 21:12:57.017 [NOTICE] [Child: 6480] Core dump is enabled.
2013-05-31 21:12:57.018 [NOTICE] [Child: 6480] LiteSpeed/4.2.3 Enterprise starts successfully!
2013-05-31 21:12:57.327 [NOTICE] [AutoRestarter] child process with pid=6480 received signal=11, a core file has been created!
2013-05-31 21:12:57.378 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets of process with pid=6480 !
2013-05-31 21:12:57.383 [NOTICE] [AutoRestarter] new child process with pid=6494 is forked!
2013-05-31 21:12:57.393 [NOTICE] [Child: 6494] Setup swapping space...
2013-05-31 21:12:57.394 [NOTICE] [child: 6494] Successfully change current user to nobody
2013-05-31 21:12:57.394 [NOTICE] [Child: 6494] Core dump is enabled.
2013-05-31 21:12:57.394 [NOTICE] [Child: 6494] LiteSpeed/4.2.3 Enterprise starts successfully!
2013-05-31 21:12:57.412 [INFO] [APVH_traditio_Suphp:] PID: 6494, add child process pid: 6498, procinfo: 0x9bc6920
2013-05-31 21:12:57.973 [NOTICE] [AutoRestarter] child process with pid=6494 received signal=11, a core file has been created!
2013-05-31 21:12:58.021 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets of process with pid=6494 !
2013-05-31 21:12:58.021 [INFO] [CLEANUP] kill pid: 6498, error: Invalid argument
2013-05-31 21:12:58.025 [NOTICE] [AutoRestarter] new child process with pid=6515 is forked!
2013-05-31 21:12:58.038 [NOTICE] [Child: 6515] Setup swapping space...
2013-05-31 21:12:58.038 [NOTICE] [child: 6515] Successfully change current user to nobody
2013-05-31 21:12:58.038 [NOTICE] [Child: 6515] Core dump is enabled.
2013-05-31 21:12:58.039 [NOTICE] [Child: 6515] LiteSpeed/4.2.3 Enterprise starts successfully!
2013-05-31 21:12:58.055 [INFO] [APVH_maestrot_Suphp:] PID: 6515, add child process pid: 6518, procinfo: 0x9bc7e48
2013-05-31 21:12:58.304 [INFO] [APVH_tienocom_Suphp:] PID: 6515, add child process pid: 6522, procinfo: 0x9bcc208
2013-05-31 21:12:58.316 [INFO] [APVH_ivaooco_Suphp:] PID: 6515, add child process pid: 6523, procinfo: 0x9bc7fc0
2013-05-31 21:12:58.327 [INFO] [APVH_ivaooco_Suphp:] PID: 6515, add child process pid: 6524, procinfo: 0x9bda4a0
2013-05-31 21:13:00.437 [NOTICE] [AutoRestarter] child process with pid=6515 received signal=11, a core file has been created!
2013-05-31 21:13:00.489 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets of process with pid=6515 !
2013-05-31 21:13:00.489 [INFO] [CLEANUP] kill pid: 6524, error: Invalid argument
2013-05-31 21:13:00.489 [INFO] [CLEANUP] kill pid: 6523, error: Invalid argument
2013-05-31 21:13:00.489 [INFO] [CLEANUP] kill pid: 6522, error: Invalid argument
2013-05-31 21:13:00.493 [NOTICE] [AutoRestarter] new child process with pid=6542 is forked!
2013-05-31 21:13:00.504 [NOTICE] [Child: 6542] Setup swapping space...
2013-05-31 21:13:00.504 [NOTICE] [child: 6542] Successfully change current user to nobody
2013-05-31 21:13:00.504 [NOTICE] [Child: 6542] Core dump is enabled.
2013-05-31 21:13:00.505 [NOTICE] [Child: 6542] LiteSpeed/4.2.3 Enterprise starts successfully!
2013-05-31 21:13:00.916 [NOTICE] [AutoRestarter] child process with pid=6542 received signal=11, a core file has been created!

Any ideas on this?
 

mistwang

LiteSpeed Staff
#5
You can revert back to earlier release from command line

/usr/local/lsws/admin/misc/mgr_ver.sh 4.x.x

4.x.x is the release used previously.

then "service lsws restart"
 

Monarobase

Well-Known Member
#6
Any news XN-Matt ?

We're holding back the latest litespeed upgrade and would like to know if you managed to roll back and get the previous version running again :)

Hope all went well for you and as you have not posted and answer to say it isn't I presume you managed to get the server back up again :)
 
Top