Jobqueue backed up

Discussion in 'General' started by ra3don, Apr 3, 2009.

  1. falko

    falko Super Moderator ISPConfig Developer

    This is nothing to worry about. This happens if you did not configure any accounts under Fetchmail in ISPConfig.
  2. beryl

    beryl New Member

    Dear Falko,

    EDIT: To put it simple, even though there are fetchmails configured, they do not get created on the server.

    See nothing in the logs about any errors.

    Does permission errors get logged?
    EDIT: not a permission problem, the reinstalled working server have the same permissions on folders and files.

    How is the getmail configs created? what files can i check?
    Last edited: Jul 17, 2009
  3. Gimly

    Gimly Member

    Hi All,

    I've the same problem job doesn't work, there are no errors in jobqueue, ispconfig database user's permission is OK.

    This is the result for command "/usr/local/ispconfig/server/":

    If you have an idea ?

    Thank you in advance for your help :)
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    The debug output shows that everything is ok, at least on the server where you executed it.

    1) Is this a multiserver system?
    2) If yes, how did you add the slave servers?
  5. Gimly

    Gimly Member

    Yes, it's multiserver system. But it worked fine during 1 month and since 1 week, it bug :(.

    There are no package updated before the problem.
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Then you had run the script /usr/local/ispconfig/server/ on the wrong server. You have to run it on the slave that does not work and not the master.
  7. Gimly

    Gimly Member

    Ok thanks Till, this is the result for the command on my sql server :

    I can view my sql serer can't access to my master server. If I uninstall ispconfig on my sql server and then I reinstall it, I don't miss any data ?

    Maybe there are an other resolution ?

    Thank you :)
  8. crazylamp

    crazylamp New Member


    I just delete /usr/local/ispconfig/server/temp/.ispconfig_lock
    and everything is ok now...
  9. crazylamp

    crazylamp New Member


    kill all other ispconfig related thread:
    $ ps aux | grep ispconfig
    root 28043 0.0 0.0 9144 1032 ? Ss 13:52 0:00 /bin/sh -c /usr/local/ispconfig/server/ &> /var/log/ispconfig/cron.log
    root 28045 0.0 0.0 106008 1336 ? S 13:52 0:00 /bin/sh /usr/local/ispconfig/server/
    root 28061 0.0 0.1 393708 20144 ? S 13:52 0:00 /usr/bin/php -q /usr/local/ispconfig/server/server.php
    root 28654 0.0 0.0 103152 832 pts/1 S+ 13:53 0:00 grep ispconfig

    $ kill -9 28061

Share This Page