ispconfig jobs stopped working

Discussion in 'ISPConfig 3 Priority Support' started by budgierless, Aug 4, 2022.

  1. budgierless

    budgierless Member HowtoForge Supporter

    hi,
    I need help to fix an issue with ispconfig, Its work fine, until i had internet problems soi got a new set of static ips, i added them to the server without problem then using resync in the panel for all services, but i still mad more internet issues and was given i next pair if static ip, but after i added them to the server, the ispconfig jobs queue is stuck (update server settings & update server ip), even a reboot dose not get rid of this, i even reinstilled ispconfig update but this dis fix anything, the cron still works because if i use resync+all services it dose what it is ment to do, but its leave the stuck jobs uncompleted.
    how can i clear the ispconfig job queue to get rid of the stuck jobs, so i can start again with new jobs?
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Clearing the queue will not solve your problem. Instead of clearing the queue, fix the underlying issue and the queue will clear itself.

    Use debug mode to find out why jobs can not be processed anymore:

    https://www.faqforge.com/linux/debugging-ispconfig-3-server-actions-in-case-of-a-failure/

    and if this is a multiserver system, then ensure to debug the right node (the one which fails) and not the master. Just as an explanation, ISPConfig processes jobs always in order, so resync can not work for a server with queued jobs as ISPConfig will always wait until the older jobs are processed. This means that either resync does not work, or the stuck jobs are targeted to another server, so resync works for one server but you have another server which is not processing his jobs.
     
    Last edited: Aug 4, 2022
  3. budgierless

    budgierless Member HowtoForge Supporter

    Ok, so i found this in the lets.. log file

    Code:
    2022-08-20 03:00:44,638:DEBUG:certbot.cli:Var post_hook=echo '1' > /usr/local/ispconfig/server/le.restart (set by user).
    2022-08-20 03:00:44,643:INFO:certbot.renewal:Cert not yet due for renewal
    2022-08-20 03:00:44,645:DEBUG:certbot.plugins.selection:Requested authenticator webroot and installer None
    2022-08-20 03:00:44,650:INFO:certbot.renewal:Cert not yet due for renewal
    2022-08-20 03:00:44,652:DEBUG:certbot.plugins.selection:Requested authenticator webroot and installer None
    2022-08-20 03:00:44,653:DEBUG:certbot.cli:Var post_hook=echo '1' > /usr/local/ispconfig/server/le.restart (set by user).
    2022-08-20 03:00:44,658:DEBUG:certbot.storage:Should renew, less than 30 days before certificate expiry 2021-08-10 01:00:41 UTC.
    2022-08-20 03:00:44,658:INFO:certbot.renewal:Cert is due for renewal, auto-renewing...
    2022-08-20 03:00:44,659:DEBUG:certbot.plugins.selection:Requested authenticator webroot and installer None
    2022-08-20 03:00:44,659:DEBUG:certbot.plugins.selection:Single candidate plugin: * webroot
    Description: Place files in webroot directory
    Interfaces: IAuthenticator, IPlugin
    Entry point: webroot = certbot.plugins.webroot:Authenticator
    Initialized: <certbot.plugins.webroot.Authenticator object at 0x7f36511fc630>
    Prep: True
    2022-08-20 03:00:44,660:DEBUG:certbot.plugins.selection:Selected authenticator <certbot.plugins.webroot.Authenticator object at 0x7f36511fc630> and installer None
    2022-08-20 03:00:44,660:INFO:certbot.plugins.selection:Plugins selected: Authenticator webroot, Installer None
    2022-08-20 03:00:44,660:WARNING:certbot.renewal:Attempting to renew cert (example.com) from /etc/letsencrypt/renewal/example.com.conf produced an unexpected error: Account at /etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/619364c290bbf70797a4f50e39731642 does not exist. Skipping.
    2022-08-20 03:00:44,661:DEBUG:certbot.renewal:Traceback was:
    Traceback (most recent call last):
      File "/usr/lib/python3/dist-packages/certbot/renewal.py", line 443, in handle_renewal_request
        main.renew_cert(lineage_config, plugins, renewal_candidate)
      File "/usr/lib/python3/dist-packages/certbot/main.py", line 1195, in renew_cert
        le_client = _init_le_client(config, auth, installer)
      File "/usr/lib/python3/dist-packages/certbot/main.py", line 641, in _init_le_client
        acc, acme = _determine_account(config)
      File "/usr/lib/python3/dist-packages/certbot/main.py", line 508, in _determine_account
        acc = account_storage.load(config.account)
      File "/usr/lib/python3/dist-packages/certbot/account.py", line 245, in load
        return self._load_for_server_path(account_id, self.config.server_path)
      File "/usr/lib/python3/dist-packages/certbot/account.py", line 214, in _load_for_server_path
        prev_loaded_account = self._load_for_server_path(account_id, prev_server_path)
      File "/usr/lib/python3/dist-packages/certbot/account.py", line 225, in _load_for_server_path
        "Account at %s does not exist" % account_dir_path)
    certbot.errors.AccountNotFound: Account at /etc/letsencrypt/accounts/acme-v01.api.letsencrypt.org/directory/619364c290bbf70797a4f50e39731642 does not exist
    
     
    Last edited: Aug 21, 2022
  4. budgierless

    budgierless Member HowtoForge Supporter

    UPDATE, I think i found and fixed the issue, the domain was not pointing to the server dns, i already changed it, but for some reason it did not update but when i did it again, it worked.
     
    till likes this.

Share This Page