Multiserver setup => monitor wrongly shows 2 servers having mismatched version

Discussion in 'Installation/Configuration' started by dfumagalli, Jan 1, 2023.

  1. dfumagalli

    dfumagalli Member

    Hello,
    I have just upgraded my servers. They are a multiserver setup (I used the ISPConfig 3.1 PDF manual).
    I upgraded both Ubuntu and ISPConfig.
    The two DNS servers were upgraded from Ubuntu LTS 18.04 to 22.04, the others did not yet.

    Before upgrading Ubuntu on the DNS servers I upgraded ISPConfig first on all servers. I upgraded the master server first, then every other server including the two DNS servers. I read I had to upgrade the master server first on several threads in this forum.

    After I upgraded everything, all the servers work. I tried adding and removing databases, DNS zones and so on and everything works.
    Looking in the ISPConfig database, there is a field stating the database version on every server and it matches for all.

    However, the ISPConfig monitor, on the master (and web) server, reports the two DNS servers as:
    • still having Ubuntu 18.04. I refreshed the page, rebooted every server... nothing fixes this.
    • still having the previous ISPConfig version. This is false. Both the database field reports the database version is up to date. Checking the version string inside the ISPConfig files present on the two DNS servers (using SSH) it reports 3.2.9 as it should.
    • If I expand the "More information...", both DNS servers tell me they need several Ubuntu Packages updates. I quadruple-checked, packages are updated.
    I even ran the ispconfig_update --force script on both master and DNS servers to see if it could fix something but it didn't.

    Any way I can fix this? Or to find out what's going wrong?



    2023-01-01_001.png
     
  2. Taleman

    Taleman Well-Known Member HowtoForge Supporter

    It might be you just need to wait until Monitor tab updates its view of the status.
    Does the problem still persist today?
     
    dfumagalli likes this.
  3. dfumagalli

    dfumagalli Member

    Yes, today it shows all OK. I thought it'd take some minutes or even 1 hour. It took days instead :eek:
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    It usually takes just a few minutes. Something must have blocked communication between the nodes or the cronjob did not run. But the issue seems to be resolved now as you see the updated data.
     

Share This Page