Troubleshooting a site that goes down

  • Over the past month or so a test site of mine has gone down a few times.

    It is hosted with reputable hosting company who have, to be frank, to-date provided wonderful support whenever it was needed.

    Essentially what happens is the “container” shuts down and i have to restart it.

    Apparently this could indicate that the fault could be at my end.

    What type of site and what type of hosting ?

    The site is a test site and gets very little traffic. The “site” is a wordpress/buddypress/multinetwork and is now the only site on this hosting plan.

    The hosting package that i am on is a VPS (with cPanel + vz; CPU: 1.13ghz; Ram: 768mb; Disk Space: 30gb Bandwidth: 500gb)

    The would be at most 5 networks (subdomains) in the set-up. and about 10 sites (say 2 per network) in all with very very little traffic.

    Recent changes ?

    Have begun testing sliders.
    Have Slidedeck and Recent Post Sliders active at the moment

    Errors

    I attach below the most frequent error pattern (literally repeated thousands upon thousands of times)
    However it may not be related?? As a result of googling i also attach the end of the php.ini Floundering around here. i just suspect there may be a connection !
    There are other errors (as well as errors collected by debug.log) but this is the one that sticks out.

    Other info

    Have a local install kind of mirror site with no observable problems.
    I can follow instructions, copy & paste etc though frankly have no great understanding.

    I would really appreciate it to hear from anyone with any ideas about this and about how to troubleshoot the problem ?

    and also who could point me to a good troubleshooting resource.

    The most frequent error (a series of four)

    [30-Nov-2012 13:49:44] PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/extensions/no-debug-non-zts-20060613/magickwand.so’ – /usr/local/lib/php/extensions/no-debug-non-zts-20060613/magickwand.so: cannot
    open shared object file: No such file or directory in Unknown on line 0
    [30-Nov-2012 13:49:44] PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/extensions/no-debug-non-zts-20060613/imagick.so’ – /usr/local/lib/php/extensions/no-debug-non-zts-20060613/imagick.so: cannot open shared object file: No such file or directory in Unknown on line 0
    [30-Nov-2012 13:49:44] PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/extensions/no-debug-non-zts-20060613/mailparse.so’ – /usr/local/lib/php/extensions/no-debug-non-zts-20060613/mailparse.so: cannot open shared object file: No such file or directory in Unknown on line 0
    [30-Nov-2012 13:49:44] PHP Warning: PHP Startup: Unable to load dynamic library ‘/usr/local/lib/php/extensions/no-debug-non-zts-20060613/phar.so’ – /usr/local/lib/php/extensions/no-debug-non-zts-20060613/phar.so: cannot open shared object file: No such file or directory in Unknown on line 0

    Towards the end of php.ini file

    extension=magickwand.so
    extension=imagick.so
    ;extension=mailparse.so

    extension=pdo.so
    extension=pdo_sqlite.so
    extension=sqlite.so
    extension=pdo_mysql.so
    ;extension=uploadprogress.so
    ;extension=gnupg.so
    extension=mailparse.so
    ;extension=fileinfo.so

    ;extension=mongo.so
    ;extension=http.so
    extension=phar.so
    extension=timezonedb.so
    extension=”ixed.5.2.lin”
    zend_extension=”/usr/local/Zend/lib/Optimizer-3.3.9/php-5.2.x/ZendOptimizer.so”

Viewing 2 replies - 1 through 2 (of 2 total)

  • This is on PHP startup,

    extension=magickwand.so Not Found
    /usr/local/lib/php/extensions/no-debug-non-zts-20060613/magickwand.so: cannot
    open shared object file: No such file or directory in Unknown on line 0

    It is the same with imagick.so, mailparse.so and phar.so. These should not cause the server to crash.

    If the server VPS container is crashing, then you need to find out why,

    If you have root access to the server and the OS is supported, new relic is a great little monitoring tool which should give you an indication if it is the RAM / CPU usage causing the crash.

    Also, have a look for a paniclog in the server logs, that should hold clues on system crashes.

    Thread Starter valuser

    (@valuser)

    Thanks Ben,

    “Also, have a look for a paniclog in the server logs”

    forgive my ignorance —– server logs are located where ?

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Troubleshooting a site that goes down’ is closed to new replies.