Jobqueue stuck, create database user

Discussion in 'ISPConfig 3 Priority Support' started by Taleman, Sep 9, 2024.

Tags:
  1. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Creating new database user, got stuck in jobqueue and red ball with number 1 at top of window.
    Popup says "Create database user for database: 1".
    Code:
    ##### SERVER #####
IP-address (as per hostname): ***.***.***.***
[WARN] could not determine server's ip address by ifconfig
[INFO] OS version is Debian GNU/Linux 10 (buster)

[INFO] uptime:  12:22:34 up 10 min,  1 user,  load average: 1,21, 1,20, 0,71

[INFO] memory:
              total        used        free      shared  buff/cache   available
Mem:           31Gi       3,0Gi        21Gi       911Mi       6,5Gi        27Gi
Swap:         3,7Gi          0B       3,7Gi

[INFO] systemd failed services status:
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

[INFO] ISPConfig is installed.

##### ISPCONFIG #####
ISPConfig version is 3.2.11p2


##### VERSION CHECK #####

[INFO] php (cli) version is 7.3.33-19+0~20240606.119+debian10~1.gbp87e0d7
[INFO] php-cgi (used for cgi php in default vhost!) is version 7.3.33

##### PORT CHECK #####


##### MAIL SERVER CHECK #####


##### RUNNING SERVER PROCESSES #####

[INFO] I found the following web server(s):
        Apache 2 (PID 12408)
[INFO] I found the following mail server(s):
        Postfix (PID 1266)
[INFO] I found the following pop3 server(s):
        Dovecot (PID 688)
[INFO] I found the following imap server(s):
        Dovecot (PID 688)
[INFO] I found the following ftp server(s):
        PureFTP (PID 1361)

##### LISTENING PORTS #####
(only           ()
Local           (Address)
[anywhere]:587          (1266/master)
[localhost]:11211               (710/memcached)
[anywhere]:110          (688/dovecot)
[anywhere]:143          (688/dovecot)
[anywhere]:465          (1266/master)
[localhost]:9012                (695/php-fpm:)
[anywhere]:21           (1361/pure-ftpd)
[anywhere]:22           (717/sshd)
[anywhere]:25           (1266/master)
[anywhere]:993          (688/dovecot)
[anywhere]:995          (688/dovecot)
[localhost]:10023               (756/postgrey)
*:*:*:*::*:3306         (887/mysqld)
*:*:*:*::*:587          (1266/master)
[localhost]10           (688/dovecot)
[localhost]43           (688/dovecot)
*:*:*:*::*:8080         (12408/apache2)
*:*:*:*::*:80           (12408/apache2)
*:*:*:*::*:8081         (12408/apache2)
*:*:*:*::*:465          (1266/master)
*:*:*:*::*:21           (1361/pure-ftpd)
*:*:*:*::*:22           (717/sshd)
*:*:*:*::*:25           (1266/master)
*:*:*:*::*:443          (12408/apache2)
*:*:*:*::*:993          (688/dovecot)
*:*:*:*::*:995          (688/dovecot)
*:*:*:*::*:10023                (756/postgrey)




##### IPTABLES #####
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         
f2b-sshd   tcp  --  [anywhere]/0            [anywhere]/0            multiport dports 22
f2b-recidive  tcp  --  [anywhere]/0            [anywhere]/0           

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain f2b-recidive (1 references)
target     prot opt source               destination         
REJECT     all  --  ***.***.***.***         [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***         [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
...
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***         [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***         [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***      [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***         [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***          [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***         [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***           [anywhere]/0            reject-with icmp-port-unreachable
RETURN     all  --  [anywhere]/0            [anywhere]/0           

Chain f2b-sshd (1 references)
target     prot opt source               destination         
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***        [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***       [anywhere]/0            reject-with icmp-port-unreachable
REJECT     all  --  ***.***.***.***          [anywhere]/0            reject-with icmp-port-unreachable
RETURN     all  --  [anywhere]/0            [anywhere]/0           




##### LET'S ENCRYPT #####
Certbot is installed in /usr/bin/letsencrypt
    Datalog history shows one line with text
    Code:
    2024-09-09 11:37        Insert    web_database_user    admin
    where server column is empty. This may be the culprit, ISPConfig can not create this user since there is no server to create it on? But this line does not have the "Undo action" -button.
    Line with timestamp a minute later does have entry in the server column:
    Code:
    2024-09-09 11:38    web.myserver.tld    Update    web_database_user    admin
    and this line does have the "Undo action" -button.
    I managed to set Debug mode on for ISPConfig, but it may not be useful here. No error in cron.log or ispconfig.log when cron starts the server script. Should I remove it from cron, create a database user and run server.sh manually to see what happens?
    Or should I press the Undo Action?
    Work is underway to move this installation to a new system, so I might manage by not creating anything on this host anymore. But it would be nice if it worked.
     
    Taleman, Sep 9, 2024
    #1
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Database users never have a server_id, so they must show up with empty server column in the datalog history and they do not get created in MySQL when you add it in ISPConfig, so that's all fine. A database user gets added to mysql when you create a database for it. So your issue is likely related to something else. Is this a single or multiserver setup?
     
    till, Sep 9, 2024
    #2
  3. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Multiserver. Two web servers, e-mail server and three dns-servers.
     
    Taleman, Sep 9, 2024
    #3
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Ok, so one of these must not have picked up the update then. As datalog records with server_id = 0 are basically a broadcast records intended for all systems to be picked up. Do you maybe have deactivated one of the servers but it is still listed under system > server services?
     
    till, Sep 9, 2024
    #4
  5. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    No to my knowledge. All servers should be running. Except third dns server, it has died.
     
    Taleman, Sep 9, 2024
    #5
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    The third DNS server causes this. These records are broadcast to all nodes; if one node does not pick them up, they will remain in the job queue as pending for that node.
     
    till, Sep 9, 2024
    #6
    Taleman likes this.
  7. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    Taleman, Sep 9, 2024
    #7
  8. till

    till Super Moderator Staff Member ISPConfig Developer

    What you can do to fix this temporarily is that you set the value of the updated column for the ns3 server in the dbispconfig master database to the highest value (maximum) of the datalog_id column from sys_datalog table. This will make the blinking dot disappear.
     
    till, Sep 9, 2024
    #8

Share This Page