Litespeed Ent. Keeps duplicate logging when restarting the server.

G

gotroot

New Member
#1
#1
Any ideas on why i keep see LS duplicate logging issue a graceful restart from SSH or from the console? Iv looked everywhere for the reason why. I still have not found the reason in 3 months and i am getting sick of seeing it. I suspect it maybe because /usr/local/lsws/logs/error.log gets quite large and has an issues being read on restart? 10M size restriction is too small. I can fill that mutiple times in a day. So mine is set to 2000M. Is LS having the problem as the size of error.log gets bigger? I never used to see this. Now all i get are these entries. The more times i restart LS in a day the more entries show up. And this was only for a restart. A STOP or START does the same thing.

Code: 
2026-07-26 06:26:22.417481    NOTICE    [45715] [T0] New litespeed process is ready, stops listeners
2026-07-26 06:26:22.417481    NOTICE    [45709] [T0] New litespeed process is ready, stops listeners
2026-07-26 06:26:22.417484    NOTICE    [45708] [T0] New litespeed process is ready, stops listeners
2026-07-26 06:26:22.417521    INFO    [45715] [T0] Stop all listeners.
2026-07-26 06:26:22.417525    INFO    [45709] [T0] Stop all listeners.
2026-07-26 06:26:22.417534    INFO    [45708] [T0] Stop all listeners.
2026-07-26 06:26:22.417543    INFO    [45715] [T0] Stop listener *:443.
2026-07-26 06:26:22.417641    INFO    [45715] [T0] Stop listener *:80.
2026-07-26 06:26:22.417652    INFO    [45715] [T0] Stop listener 127.0.0.1:8765.
2026-07-26 06:26:22.417668    NOTICE    [45715] [T0] QuicEngine::startCoolDown(), active connections: 0
2026-07-26 06:26:22.417673    NOTICE    [45715] [T0] Event-loop lingering done.
2026-07-26 06:26:22.417682    NOTICE    [45715] [T0] Shut down successfully!
2026-07-26 06:26:22.417550    INFO    [45709] [T0] Stop listener *:443.
2026-07-26 06:26:22.417731    INFO    [45709] [T0] Stop listener *:80.
2026-07-26 06:26:22.417557    INFO    [45708] [T0] Stop listener *:443.
2026-07-26 06:26:22.417739    INFO    [45709] [T0] Stop listener 127.0.0.1:8765.
2026-07-26 06:26:22.417752    INFO    [45708] [T0] Stop listener *:80.
2026-07-26 06:26:22.417768    INFO    [45708] [T0] Stop listener 127.0.0.1:8765.
 
Last edited:
G

gotroot

New Member
#3
#3
Im waiting for LS to chime in here. Surely they have an explanation as to whats going on here. If not, thats a huge problem cause this does not make any sense. Its not a corrupt xml. Iv reinstalled LS 3 times now. The issues is still evident.
 
abk

abk

Administrator
Staff member
#4
#4
Can you please open a support ticket? I tried on one of my test servers and couldn't reproduce this. Would like to check if there is something particular about your setup.
 
R

rustytrout

New Member
#5
#5
gotroot said:
Im waiting for LS to chime in here. Surely they have an explanation as to whats going on here. If not, thats a huge problem cause this does not make any sense. Its not a corrupt xml. Iv reinstalled LS 3 times now. The issues is still evident.
Click to expand...
Three reinstalls pointing at the same behavior makes it feel more like a restart/log handling quirk than a busted install. Waiting on an LS explanation is pretty much all that's left here.
 
hardy_hammer865

hardy_hammer865

New Member
#6
#6
gotroot said:
Any ideas on why i keep see LS duplicate logging issue a graceful restart from SSH or from the console? Iv looked everywhere for the reason why. I still have not found the reason in 3 months and i am getting sick of seeing it. I suspect it maybe because /usr/local/lsws/logs/error.log gets quite large and has an issues being read on restart? 10M size restriction is too small. I can fill that mutiple times in a day. So mine is set to 2000M. Is LS having the problem as the size of error.log gets bigger? I never used to see this. Now all i get are these entries. The more times i restart LS in a day the more entries show up. And this was only for a restart. A STOP or START does the same thing.

Code:
2026-07-26 06:26:22.417481 NOTICE [45715] [T0] New litespeed process is ready, stops listeners
2026-07-26 06:26:22.417481 NOTICE [45709] [T0] New litespeed process is ready, stops listeners
2026-07-26 06:26:22.417484 NOTICE [45708] [T0] New litespeed process is ready, stops listeners
2026-07-26 06:26:22.417521 INFO [45715] [T0] Stop all listeners.
2026-07-26 06:26:22.417525 INFO [45709] [T0] Stop all listeners.
2026-07-26 06:26:22.417534 INFO [45708] [T0] Stop all listeners.
2026-07-26 06:26:22.417543 INFO [45715] [T0] Stop listener *:443.
2026-07-26 06:26:22.417641 INFO [45715] [T0] Stop listener *:80.
2026-07-26 06:26:22.417652 INFO [45715] [T0] Stop listener 127.0.0.1:8765.
2026-07-26 06:26:22.417668 NOTICE [45715] [T0] QuicEngine::startCoolDown, active connections: 0
2026-07-26 06:26:22.417673 NOTICE [45715] [T0] Event-loop lingering done.
2026-07-26 06:26:22.417682 NOTICE [45715] [T0] Shut down successfully!
2026-07-26 06:26:22.417550 INFO [45709] [T0] Stop listener *:443.
2026-07-26 06:26:22.417731 INFO [45709] [T0] Stop listener *:80.
2026-07-26 06:26:22.417557 INFO [45708] [T0] Stop listener *:443.
2026-07-26 06:26:22.417739 INFO [45709] [T0] Stop listener 127.0.0.1:8765.
2026-07-26 06:26:22.417752 INFO [45708] [T0] Stop listener *:80.
2026-07-26 06:26:22.417768 INFO [45708] [T0] Stop listener 127.0.0.1:8765.
Click to expand...
Those look like separate worker PIDs all writing their own shutdown lines, not the same old log being reread. The timestamps lining up makes it especially noisy, but the 2GB error log setting probably isn't the cause.
 
You must log in or register to reply here.
Top