Search results

It's not something you can change in a shared environment. They will need to do that for you.

There is no support ticket option in the client area. I really wish you would not expect paying customers to use a forum. It is simply not good enough for a support mechanism and has frankly taken far too long.

Yes it is. Litespeed is crashing (which we can confirm it is), cPanel may be starting Apache but still the issue remains, why is LiteSpeed crashing?

Nope. This is LiteSpeed. It is happening on ALL our LS servers - new installs with CentOS 7 and old installations with CentOS 6 root@[~]# ps aux | grep litespeed root 819211 5.9 0.5 112364 90104 ? SN 14:00 0:02 litespeed (lshttpd) nobody 819258 1.7 0.5 296240 90940 ...

No response in over 2 days. C'mon guys. We expect SOME support here for your software which just keeps dying on us.

We might have correlated this to mod_security. We are using the CWAF rules but have not updated automatically. User memory increase is seen a bit before the crash and our mod_sec logs have timestamps like. [14/Apr/2017:04:23:28 +0100] - 217.182.132.65 49084 xx:80 80 [14/Apr/2017:04:23:31 +0100]...

Well that made no difference. Crashed again. [Sat Apr 15 05:07:08.034194 2017] [:notice] [pid 585649:tid 140077775644640] [host xxx] mod_lsapi: Selfstarter 585649 stopped [Sat Apr 15 05:07:08.536042 2017] [cgid:error] [pid 585650:tid 140077329999616] (111)Connection refused: [client...

OK, what is the significance in that date? I can't see any changes in the release log between when we might have first downloaded it and now.

Even if already running 5.1.15 do we need to force a re-install?

Server 2 [Fri Apr 14 08:12:59.684280 2017] [core:error] [pid 569847:tid 140266308560640] (104)Connection reset by peer: [client 87.127.112.191:62876] AH00574: ap_content_length_filter: apr_bucket_read() failed [Fri Apr 14 08:12:59.772203 2017] [core:error] [pid 569875:tid 140266400880384]...

In the recent versions, we're seeing LS die completely with varying errors. Last log entry is immediately before it stopped responding. [Fri Apr 14 04:59:28.747400 2017] [:notice] [pid 173875:tid 139935212316640] [host xxxxxx] mod_lsapi: Selfstarter 173875 started [Fri Apr 14 04:59:57.623652...

Will play with that. I note that in the docs it states that Deamon mode does not work with CloudLinux PHP selector. What about cPanel native PHP version control?

Daemon mode has helped overall. First connection is lower, where as others are little higher. Is there any benefit of having more Instances or increasing Max Idle Time in such mode?

It does appear to be PHP related but having compared Nginx with PHP-FPM and Litespeed, we only see the issue with the latter. I think I have correlated it to the PHP process having to start up and although have tried altering the settings to keep this "alive", it appears this does not work that...

Hi, We're seeing some really poor initial connect times. Have tried all methods of PHP (using lsapi/PHP via cPanels repo and Easy Apache 4). Subsequent loads are good, just the initial. Have unrestricted the user in CL giving all CPU/Memory as needed but no change there either. Any initial...

Not that helpful really. How do we determine why. It's near immediate.

2014-08-21 15:08:32.219 [DEBUG] [193.238.80.115:80] New connection from 1.2.3.4:28022. 2014-08-21 15:08:32.219 [DEBUG] [1.2.3.4:28022-0] concurrent conn: 1 2014-08-21 15:08:32.219 [DEBUG] [1.2.3.4:28022-0] HttpIOLink::handleEvents() events=1! 2014-08-21 15:08:32.219 [DEBUG] [1.2.3.4:28022-0]...

Only on one page in a Joomla install are we seeing this. Anything obvious as we can only see "add ENV: 'HTTP_AUTHORIZATION:'" but unsure if that is related. Logs below in two posts.

Following on from the previous thread. Assuming the latest build fixes what was discussed there. We're now seeing the below error which did not occur in 4.2.3. Message: [client x] mod_security: Access denied with code 403, [Rule: 'REQUEST_COOKIES'...

Not specific, - the exact same fault.