I have to wait more than 10 minutes for ISPConfig to create a website?

Discussion in 'General' started by todx, Jul 26, 2012.

  1. todx

    todx Member

    Ok, having problems again, I have to wait too long again (20 minutes now). I'll post the output of "server.sh" to show you the debug and if no one has a solution I will try to remove APC and see how it goes than.

    Code:
    root@cp:~# /usr/local/ispconfig/server/server.sh
    26.08.2012-09:38 - DEBUG - Set Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    26.08.2012-09:38 - DEBUG - Found 2 changes, starting update process.
    26.08.2012-09:38 - DEBUG - Calling function 'update' from plugin 'apps_vhost_plugin' raised by event 'server_update'.
    26.08.2012-09:38 - DEBUG - Calling function 'update' from plugin 'network_settings_plugin' raised by event 'server_update'.
    26.08.2012-09:38 - DEBUG - Network configuration disabled in server settings.
    26.08.2012-09:38 - DEBUG - Calling function 'update' from plugin 'postfix_server_plugin' raised by event 'server_update'.
    26.08.2012-09:38 - DEBUG - Processed datalog_id 1996
    26.08.2012-09:38 - DEBUG - Calling function 'update' from plugin 'apps_vhost_plugin' raised by event 'server_update'.
    26.08.2012-09:38 - DEBUG - Calling function 'update' from plugin 'network_settings_plugin' raised by event 'server_update'.
    26.08.2012-09:38 - DEBUG - Network configuration disabled in server settings.
    26.08.2012-09:38 - DEBUG - Calling function 'update' from plugin 'postfix_server_plugin' raised by event 'server_update'.
    26.08.2012-09:38 - DEBUG - Processed datalog_id 1997
    26.08.2012-09:38 - DEBUG - Calling function 'restartHttpd' from module 'web_module'.
    26.08.2012-09:38 - DEBUG - Remove Lock: /usr/local/ispconfig/server/temp/.ispconfig_lock
    finished.
    
     
    Last edited: Aug 26, 2012
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    The output is fine and the changes have been processed correctly. As there was no lock file, there is no problem fom ispconfig dide. Maybe your cron is not running thevwcript once a minute as it should.
     
  3. cfoe

    cfoe Member

    what helped my was not to install APC via pecl install apc but via the package manager. in my case yum install php-pecl-apc. For centos it seems that the pecl apc package is not working properly
     
  4. todx

    todx Member

    Ok so I don't know much about cron jobs so I went on the google and looked around a bit. It seems people suggest: "*/1 * * * *" instead of "* * * *". Dunno if this will make any difference, I will post again in a day or so to tell you if that changed anything... If that won't work I'll start fixing APC.

    Thanks to both of you for fast reply.
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    The way ispconfig creates the cronjob is absolutely fine, dont change it or you may get problems after the next update. I'am talking about a issue that your cron daemon is not running.
     
  6. todx

    todx Member

    Well I'm 100% sure that my cron daemon is running.

    Code:
    root@cp:~# pgrep cron
    2300
    Also I'm running debian and since debian stores cron messages to: "/var/log/messages", I tailed it right after that minute when ispconfigs cronjob executes shell script and everything seems fine to me.

    Any other way I can debug/check if my daemon is working properly?
     
  7. till

    till Super Moderator Staff Member ISPConfig Developer

    Leave debugging on and if you experience the problem again, then check the ispconfig cron.log for errors or messages that look unusual.
     

Share This Page