error 503 concrete 5 CMS cache

Discussion in 'General' started by DoM, Dec 12, 2011.

  1. DoM

    DoM Well-Known Member

    Hello,
    a customer complains that when he enabled cache of concrete 5 CMS that use Zend Cache he obtains following error:

    2011-12-12 11:11:09.736 [INFO] [x.x.x.x:21772-0#APVH_xxx.xxx] connection to [/tmp/lshttpd/APVH_xxx.xxx_Suphp.sock.814] on request #0, confirmed, 1, associated process: 580133, running: 1, error: Connection reset by peer!
    2011-12-12 11:11:09.736 [NOTICE] [x.x.x.x:21772-0#APVH_xxx.xxx] Max retries has been reached, 503!
    2011-12-12 11:11:09.736 [NOTICE] [x.x.x.x:21772-0#APVH_xxx.xxx] oops! 503 Service Unavailable
    2011-12-12 11:11:09.736 [NOTICE] [x.x.x.x:21772-0#APVH_xxx.xxx] Content len: 0, Request line: 'GET /demo/bramante32/it/eventi/evento-azzurro HTTP/1.1'
    2011-12-12 11:11:09.736 [INFO] [x.x.x.x:21772-0#APVH_xxx.xxx] Cookie len: 276, CONCRETE5=6ae2d3f57b0bc25c7d23a4f04adcf97a; __utma=153858858.164218206.1323684636.1323684636.1323684636.1; __utmb=153858858.1.10.1323684636; __u
    tmc=153858858; __utmz=153858858.1323684636.1.1.utmcsr=xxx.xxx|utmccn=(referral)|utmcmd=referral|utmcct=/admin/xxx.php
    2011-12-12 11:11:09.736 [NOTICE] [x.x.x.x:21772-0#APVH_xxx.xxx] Redirect: #1, URL: /demo/bramante32/index.php/it/eventi/evento-azzurro
    2011-12-12 11:11:09.736 [INFO] [x.x.x.x:21772-0#APVH_xxx.xxx] File not found [/home/xxxxxxxx/public_html/503.shtml]


    Waiting for your reply

    Regards
     
  2. NiteWave

    NiteWave Administrator

    please try manually install 4.1.9 first, to see if 503 still exist.
     
  3. DoM

    DoM Well-Known Member

    Ok from where i can download it ?


    Waiting for your reply

    Regards
     
  4. NiteWave

    NiteWave Administrator

    get 4.1.8 download url, then just change 4.1.8 to 4.1.9 in the url
     
  5. DoM

    DoM Well-Known Member

    Hello,
    we installed 4.1.9 but same error appears.


    Waiting for your reply

    Regards
     
  6. webizen

    webizen Well-Known Member

    if possible, switch to Apache and see if problem persists.

    Or enable debug logging in LSWS and see if more context of 503 error shows up in error_log.
     
  7. DoM

    DoM Well-Known Member

    No error if we switch to apache and also if we execute it from command line.


    Waiting for your reply

    Regards
     
  8. webizen

    webizen Well-Known Member

    DoM,

    is this the same server with gallery3 issue? if not, paste here the output of
     

Share This Page