Ad Widget

Collapse

Simple upgrade questions

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Maxburn
    Member
    • Sep 2019
    • 48

    #1

    Simple upgrade questions

    What should I expect to have to do when upgrading from one LTS release to the next? I'm not finding these upgrades quick and painless at all, what am I doing wrong?

    Specifically #3 and #4 bother me, should I be going through and updating all of these templates?

    I started out with docs on this page and I'm finding it very far from complete. Our original server was 4 LTS I think and every LTS release I've struggled with it a couple days until everything was working again. Going from 6 to 7 this week was no exception, lots of problems.
    1. DB we've been using for ages suddenly didn't have enough permission, You do not have the SUPER privilege. ~database upgrade failed on patch 06010049, exiting fix that.
    2. Bunch of agent ping items broken after doing the recommended agent upgrades, had to fix that.
    3. I just found our pushover integration was broken "Pushover notification failed: ReferenceError: identifier 'CurlHttpRequest' undefined" I had to import the v7 template and then re-enter the info to fix it.
    4. Logs are currently filled with this, have not researched this one yet; 1093:20250305:114552.146 error reason for "hostname:vfs.dev.read.rate[DiskReadsPersec.1]" changed: Preprocessing failed for: [{"AvgDiskBytesPerRead":"57344","AvgDiskBytesPer Tra nsfer":"8192","AvgDiskBytesPerWrite":"5300","A...
      1. Failed: cannot extract value from json by path "$[?(@.Name == "1")].DiskReadsPersec.first()": no data matches the specified path
    5. System info has Global scripts on Zabbix server Disabled. Seems like a new security thing, I haven't researched it yet. Potentially related to #4?

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

    #2
    1. going from 4 to 7... first thing on upgrade notes for v7 https://www.zabbix.com/documentation.../debian_ubuntu
    Upgrade process
    To complete a successful Zabbix server upgrade on MySQL/MariaDB, you may require to set GLOBAL log_bin_trust_function_creators = 1 in MySQL if binary logging is enabled, there are no superuser privileges and log_bin_trust_function_creators = 1 is not set in MySQL configuration file.
    2. Userparameter is "ping.host" and then you allowkey for system.run ? That does not compute... Maybe you chose to overwrite existing config? Thats why those lines disappeared?
    3. might be something specific to your integration...
    4. Please check, what your item returns and is that preprocessing matching .. From error I would assume that preprocessing just does not match...
    5. not related to 4...
    EnableGlobalScripts

    Enable global scripts on Zabbix server.
    Note: Global script execution is enabled by default. However, for new installations starting with Zabbix 7.0, EnableGlobalScripts is explicitly set to 0 (disabled).

    Default: 1
    Values: 0 - disable; 1 - enable

    Comment

    • Maxburn
      Member
      • Sep 2019
      • 48

      #3
      Originally posted by cyber
      1. going from 4 to 7... first thing on upgrade notes for v7 https://www.zabbix.com/documentation.../debian_ubuntu

      2. Userparameter is "ping.host" and then you allowkey for system.run ? That does not compute... Maybe you chose to overwrite existing config? Thats why those lines disappeared?
      3. might be something specific to your integration...
      4. Please check, what your item returns and is that preprocessing matching .. From error I would assume that preprocessing just does not match...
      5. not related to 4...
      1. Strings "GLOBAL" or "log_bin_trust_function_creators" are not found on that page that my browser can find. But yes, that sounds like what was needed for that external article I linked.
      2. Allow the system to run ping.host was the way I interpreted that, and it started to work so I didn't look further. I could easily be wrong there. I don't know that the agent upgrade gives the option to keep existing config, it seems to lift the name and key etc and replace it. I can't seem to replicate it as I didn't keep the old configs and it won't allow a upgrade workflow on same versions. The messaging in CLI on linux server config files is superior here, lets you know there's changes there and offers keep,replace,inspect etc...
      3. Fix was to upgrade the template and repopulate the config that that blew away. You can find "CurlHttpRequest" in the old template but not the new one. Seems this does not get updated between versions. This makes me wonder how many other things are like that, what do I need to look for?
      4. This looks like it is an improvement in v7, UI has this message too "The item is not discovered anymore and will not be disabled, will be deleted in 24d 21h 14m". What I think happened is a change in config in the machines dropped some things off and we still had a autodiscovered item there. This has probably been a problem for a long time and I never realized it, and v7 is offering to clean it up for me?
      5. I understand now. I left it disabled, I don't think I'm using any. I'll do a little more research to make sure not using any.
      Last edited by Maxburn; 06-03-2025, 18:27.

      Comment

      Working...