The follwing article describes the steps that can be taken to debug the ISPConfig 3 server scripts.

Enable the debug Loglevel in ISPConfig

Login to the ISPConfig intterface and set the log level to Debug under System > System > Server Config (see also chapter 4.9.2.2 of the ISPConfig 3 manual) for the affected server. After one or two minutes, there should be more detailed messages in ISPConfig's system log (Monitor > System State (All Servers) > Show System-Log).

Disable the server.sh cronjob

Go to the command line of the server on which the error happens (on multiserver systems, it is often the slave and not the master) and run (as root):

crontab -e

Comment out the server.sh cron job:

#* * * * * /usr/local/ispconfig/server/server.sh > /dev/null >> /var/log/ispconfig/cron.log

Run the server script manually to get detailed debug output

Then run the command:

/usr/local/ispconfig/server/server.sh

This will display any errors directly on the command line which should help you to fix the error. When you have fixed the error, please don't forget to uncomment the server.sh cron job again.

Facebooktwittergoogle_plusredditlinkedinmail
Tagged on:             

One thought on “Debugging of ISPConfig 3 server actions in case of a failure

  • February 9, 2016 at 8:53 pm
    Permalink

    I get no errors when I run the server.sh script manually, but still have numerous jobs in the jobqueue and nothing being written to disk. Please help?

    I also ran the htf script and don’t see any errors there either.
    This was a working production server prior to whatever has happened.

    TIA!

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *