jobs stuck after ip reset

Discussion in 'ISPConfig 3 Priority Support' started by chief, Nov 19, 2024.

  1. chief

    chief Member HowtoForge Supporter

    Hey, debian 12 - ispc 3.2.12-p1
    Thanks in advance

    I have after replacing the IP's need to get out the emails from the server to replacement.
    Renamed all the IP in the control panel, updated the username via phpmyadmin user editor changing
    Code:
    ispcsrv3 IP
    root(IP)
    I tried the password i have and it didnt work, so i also updated the password for the above users. I then ran an
    Code:
    ispconfig-update.sh -- force and it connected and did its thing, but still the jobs wont go down.
    There are 726 jobs in the queue.
    How do i find out where the jobs are headed to?
    Can i clear them and try again?
    Or which bit of the queue is causing me grief..
    All this to replace a email password
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    You must change the IP address in the ispcsrv* users in mysql on the master server. best is to use the phpmyadmin user editor for that as manually editing them will likely fail. There is no ISPConfig update needed for that.
     
  3. chief

    chief Member HowtoForge Supporter

    I went to https:xx.xx.xx.xx./phpmyadmin and logged in. then i went into "User accounts", clicked "show all" and clicked into old IP and changed it to new IP and clicked save.
    It shows the correct IP

    I also updated the root IP as well there.
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    It might be nescessary that you select flush privileges in phpmyadmin to apply the changes.
     
  5. chief

    chief Member HowtoForge Supporter

    Thats in "User accounts" and the link at the bottom to "reload the priviliges"?
    If it is i have already done that and it is the same, the "Jobqueue" still shows 727
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Then one of your nodes does not pick up changes. You can use the ispconfig debug mode to run server.sh on each node to see which one fails.
     
  7. chief

    chief Member HowtoForge Supporter

  8. chief

    chief Member HowtoForge Supporter

    got it
    Code:
    root@mx1:~# crontab -e
    crontab: installing new crontab
    root@mx1:~# /usr/local/ispconfig/server/server.sh
    19.11.2024-20:18 - WARNING - There is already a lockfile set, but no process running with this pid (320322). Continuing.
    Database connection failed Database connection failed Database connection failed Database connection failed Database connection failed Zugriff auf Datenbankserver fehlgeschlagen! / Database server not accessible! PHP Fatal error:  Uncaught Error: Call to a member function testConnection() on bool in /usr/local/ispconfig/server/server.php:67
    Stack trace:
    #0 {main}
      thrown in /usr/local/ispconfig/server/server.php on line 67
    Database connection failed Database connection failed Database connection failed Database connection failed Database connection failed Zugriff auf Datenbankserver
     

Share This Page