188 jobs in the queue - not counting down!

Discussion in 'General' started by Indieben, Feb 28, 2018.

  1. Indieben

    Indieben Member

    Hi there,
    My job queue in entirely stuck. A reset of the webserver did not clear it. Does anybody have any ideas please. I'm running the latest ispconfig version.

    Many thanks.

  2. till

    till Super Moderator Staff Member ISPConfig Developer

  3. Indieben

    Indieben Member

    When I went into crontab -e I noticed:

    * * * * * /usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done
    * * * * * /usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done
    Is having the two jobs, as standard, correct - I notice that there is a small difference in the two above....

    Upon disabling both cronjobs and running the script manually:
    02.03.2018-20:50 - WARNING - There is already an instance of server.php running with pid 1494.
    This is all I can see :) Hopefully you can point me in the right direction to sort it out, with great gratitude.

    Thanks :)
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    If you still get that errr now when you run
    /usr/local/ispconfig/server/server.sh, then kill the job with that pid with the kill command and try to run server.sh again.
  5. Indieben

    Indieben Member

    Hi Till,

    Thanks as usual for saving my bacon!

    I'm pretty sure that this issue has happened before, killing the PID (In my case 2564 if that's relevant) has sorted out the issue and it's now clearing the jobs (having run the above command manually). Is the repeated occurrence of this problem indicative of any particular wider issue that you can think of? I'm keen to try and nip it in the bud for good, if possible.

    I'm starting to think that, because I am hosting on Proxmox 3.4 and we are now on 4.x, with totally different (LXC) containers, that there maybe more and more compatibility issues cropping up as updates for my various servers (including ISPConfig) are released - is this a valid theory?

    Thanks again Till,

    indieben :)

Share This Page