Ad Widget

Collapse

Zabbix 7.0.17 to 7.2

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Kevin_Merritt
    Junior Member
    • Nov 2023
    • 2

    #1

    Zabbix 7.0.17 to 7.2

    I hope someone can help.
    I have run through the upgrade from 7.0.17 (which was working fine) to 7.2, I am getting the

    "Manual intervention is required to complete upgrade!

    Starting with Zabbix 7.2 official packages, frontend PHP files were moved from /usr/share/zabbix to /usr/share/zabbix/ui."

    I have gone through this and I have also checked the

    apache.conf and it shows the correct Directory <Directory "/usr/share/zabbix/ui">

    But I still cannot get past the Manual Intervention. I am running Ubuntu 24.04.3 LTS
    Can anyone help me get the server back up and running.
    Its a PostgreSQL Backend (In case this is needed).
  • Kevin_Merritt
    Junior Member
    • Nov 2023
    • 2

    #2
    I have now managed to get the PHP frontend working.
    By changing /etc/apache2/sites-available/000-default.conf
    But I am now getting a

    Click image for larger version

Name:	{67456E0A-FA8E-4E90-AE5D-DDFBD5F28CD0}.png
Views:	104
Size:	12.0 KB
ID:	506241

    Looking at the Log I have
    114902:20250815:081549.104 database is down: reconnecting in 10 seconds
    114902:20250815:081559.108 [Z3001] connection to database 'zabbix' failed: [0] connection to server at "localhost" (127.0.0.1), port 5432 failed: fe_sendauth: no password supplied

    But looking at the /etc/zabbix/web/zabbix.conf.php
    ​I can see the Database info in there, Username and password is still there.
    Can someone help?

    Comment

    • cyber
      Senior Member
      Zabbix Certified SpecialistZabbix Certified Professional
      • Dec 2006
      • 4807

      #3
      Originally posted by Donkey
      In zabbix_server.conf
      change AllowUnsupportedDBVersions=1
      and restart Zabbix server
      It does not mean you can use unknown schema... it means you can use unsupported DB engine (ie too old old or too new version)

      As OP says, they managed to get webUI working. That error message kind of confirms, that 7.2 webUI is trying to connect to DB, but sees older version of DB schema there... The error from log is not from webUI, it is from server log. Your server has not managed to start properly to do all the upgrade taks. As it complains about password, check your server conf file, if everything is present... Can you make that connection from command line with same user etc..

      Comment

      Working...