After a failed upgrade to PHP 5.4 (it caused out of memory errors), and rolling back to PHP 5.3 (still continued to get out of memory errors, till I raised PHP memory limit to around a 1GB), I am now seeing following errors in Litespeed Webserver log.
These seem to happen every 5-10 minutes or so and while I rarely get blank pages (I think I got it once in past week), I guess users of my forum are getting them regularly.
Does anyone has any idea why this is happening?
My host was a little hesitant to troubleshoot it, after failed PHP update and I too am hesitant to let them troubleshoot it, because that failed PHP update cost me around 3 hours of downtime, till I stepped in myself.
Code:
2014-01-12 09:54:45.162 INFO [54.***.***.***:26455-0#APVH_domain.com] connection to [/tmp/lshttpd/lsphp5.sock] on request #10, confirmed, 0, associated process: 15671, running: 1, error: Connection reset by peer!
2014-01-12 09:54:45.162 NOTICE [54.***.***.***:26455-0#APVH_domain.com] POST request in process stage, fail with 503
2014-01-12 09:54:45.162 NOTICE [54.***.***.***:26455-0#APVH_domain.com] oops! 503 Service Unavailable
2014-01-12 09:54:45.162 NOTICE [54.***.***.***:26455-0#APVH_domain.com] Content len: 0, Request line: 'HEAD /forum/photography-f17/threadname-t216 HTTP/1.1'
2014-01-12 09:54:45.162 INFO [54.***.***.***:26455-0#APVH_domain.com] Cookie len: 326, PHPSESSID=c1d42a944f52badd1d45c748dc188be2; __cfduid=d7f9de5453288cfd6ec15133fa39a4ac01389254029157; v2_lastactivity=0; v2_lastvisit=1389254028; v2_; v2_thread_lastview=16320915cc989b38b9570ca864f5d35d5fdbde04a-3-%7Bi-56699_i-1389338935_i-56698_i-1389338063_i-56709_i-1389409280_%7D
2014-01-12 09:54:45.162 NOTICE [54.***.***.***:26455-0#APVH_domain.com] Redirect: #1, URL: /forum/vbseo.php
2014-01-12 09:54:45.162 INFO [54.***.***.***:26455-0#APVH_domain.com] abort request..., code: 4
2014-01-12 09:54:45.162 INFO [54.***.***.***:26455-0#APVH_domain.com] File not found [/home/domain/public_html/503.shtml]
Does anyone has any idea why this is happening?
My host was a little hesitant to troubleshoot it, after failed PHP update and I too am hesitant to let them troubleshoot it, because that failed PHP update cost me around 3 hours of downtime, till I stepped in myself.
Last edited by a moderator: