quic crashing

M

m00ster

New Member
#1
#1
Hello,

I have been experiencing QUIC related crashes for LSWS:

====
2017-07-16 06:19:42.801 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets of process with pid=25487 !
2017-07-16 06:19:42.802 [NOTICE] [AutoRestarter] child process with pid=25487 received signal=11, a core file has been created!
2017-07-16 06:19:43.113 [NOTICE] [AutoRestarter] new child process with pid=25520 is forked!
2017-07-16 06:19:45.422 [NOTICE] [AutoRestarter] cleanup children processes and unix sockets of process with pid=25520 !
2017-07-16 06:19:45.422 [NOTICE] [AutoRestarter] child process with pid=25520 received signal=11, a core file has been created!
2017-07-16 06:19:45.736 [NOTICE] [AutoRestarter] new child process with pid=25587 is forked!
2017-07-16 06:19:45.736 [NOTICE] [Child: 25587] Setup swapping space...
2017-07-16 06:19:45.736 [NOTICE] [child: 25587] Successfully change current user to nobody
2017-07-16 06:19:45.736 [NOTICE] [Child: 25587] Core dump is enabled.
2017-07-16 06:19:45.736 [NOTICE] [Child: 25587] LiteSpeed/5.2 Enterprise starts successfully!
2017-07-16 06:19:45.739 [INFO] [PID 25587] [QuicShm::cleanupOldShmData]: cleaning up dead process SHM (pid: 25520)
====

The configuration is pretty generic - standard cPanel/CloudLinux install.

I would be more than happy toi let you access the server to check out the core dumps if needed.

Thanks!
 
M

mistwang

LiteSpeed Staff
#2
#2
Please update the latest build of 5.2, currently build 4, with command
/usr/local/lsws/admin/misc/lsup.sh -f -v 5.2
Please install gdb: yum install gdb
If the crash continues, we may need to login to your server to figure out the root cause.
 
M

m00ster

New Member
#3
#3
Hello,

Thanks for the reply.

This is happening with build 4 and I have gdb installed. If you give me your ssh public key I can add it for you.

Thanks!
 
Hedloff

Hedloff

Well-Known Member
#5
#5
Did you get it to work?
I have issues with 5.2 build 8 and cPanel version 64 (build 36). Quic is not working anymore.
I also tried to disable CSF completely, but still no QUIC!

Tested with Google Chrome 59.0.3071.115
 
N

NiteWave

Administrator
#6
#6
please check if this is also your case:
mistwang said:
Looks like google is doing something to the chrome. my chrome's QUIC was disabled all of sudden.
You can go to chrome://flags/, change "Experimental QUIC protocol" from "Default" to "On" .
If you use different IP, you need to check "netstat -anp" to make litespeed is listen on UDP <IP>:443 .
Click to expand...
 
You must log in or register to reply here.
Top