ZABBIX BUGS AND ISSUES
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-8152

missing explanation in server log of optional DB patching

    Details

      Description

      See first comment.

        Activity

        Hide
        Oleksiy Zagorskyi added a comment - - edited

        When start zabbix server 2.2.3 first time after 2.2.1-2 we can see these lines:

        42771:20140422:145007.735 Starting Zabbix Server. Zabbix 2.2.3 (revision 44105).
        42771:20140422:145007.735 ****** Enabled features ******
        42771:20140422:145007.735 SNMP monitoring:           YES
        42771:20140422:145007.735 IPMI monitoring:           YES
        42771:20140422:145007.735 WEB monitoring:            YES
        42771:20140422:145007.735 VMware monitoring:         YES
        42771:20140422:145007.735 Jabber notifications:      YES
        42771:20140422:145007.735 Ez Texting notifications:  YES
        42771:20140422:145007.735 ODBC:                       NO
        42771:20140422:145007.735 SSH2 support:              YES
        42771:20140422:145007.736 IPv6 support:               NO
        42771:20140422:145007.736 ******************************
        42771:20140422:145007.736 using configuration file: /etc/zabbix/zabbix_server.conf
        42771:20140422:145007.748 current database version (mandatory/optional): 02020000/02020000
        42771:20140422:145007.748 required mandatory version: 02020000
        42771:20140422:145007.748 starting automatic database upgrade
        42771:20140422:145007.762 completed 100% of database upgrade
        42771:20140422:145007.762 database upgrade fully completed
        

        Next 2.2.3 runs will show:

        42973:20140422:145138.315 Starting Zabbix Server. Zabbix 2.2.3 (revision 44105).
        42973:20140422:145138.315 ****** Enabled features ******
        42973:20140422:145138.316 SNMP monitoring:           YES
        42973:20140422:145138.316 IPMI monitoring:           YES
        42973:20140422:145138.316 WEB monitoring:            YES
        42973:20140422:145138.316 VMware monitoring:         YES
        42973:20140422:145138.316 Jabber notifications:      YES
        42973:20140422:145138.316 Ez Texting notifications:  YES
        42973:20140422:145138.316 ODBC:                       NO
        42973:20140422:145138.316 SSH2 support:              YES
        42973:20140422:145138.316 IPv6 support:               NO
        42973:20140422:145138.316 ******************************
        42973:20140422:145138.316 using configuration file: /etc/zabbix/zabbix_server.conf
        42973:20140422:145138.347 current database version (mandatory/optional): 02020000/02020001
        42973:20140422:145138.347 required mandatory version: 02020000
        

        It's not clear why required mandatory version matches with current DB version but some automatic DB upgrade being performed.
        If investigate it appear to be an optional 2020001 patch.

        Suggestion: to be more user friendly would be good to mention that there available optional patch(es). Log something like:

        required mandatory version: 02020000
        available optional version: 02020001
        

        p.s. the patch introduced in ZBX-7849 for 2.2.3

        Show
        Oleksiy Zagorskyi added a comment - - edited When start zabbix server 2.2.3 first time after 2.2.1-2 we can see these lines: 42771:20140422:145007.735 Starting Zabbix Server. Zabbix 2.2.3 (revision 44105). 42771:20140422:145007.735 ****** Enabled features ****** 42771:20140422:145007.735 SNMP monitoring: YES 42771:20140422:145007.735 IPMI monitoring: YES 42771:20140422:145007.735 WEB monitoring: YES 42771:20140422:145007.735 VMware monitoring: YES 42771:20140422:145007.735 Jabber notifications: YES 42771:20140422:145007.735 Ez Texting notifications: YES 42771:20140422:145007.735 ODBC: NO 42771:20140422:145007.735 SSH2 support: YES 42771:20140422:145007.736 IPv6 support: NO 42771:20140422:145007.736 ****************************** 42771:20140422:145007.736 using configuration file: /etc/zabbix/zabbix_server.conf 42771:20140422:145007.748 current database version (mandatory/optional): 02020000/02020000 42771:20140422:145007.748 required mandatory version: 02020000 42771:20140422:145007.748 starting automatic database upgrade 42771:20140422:145007.762 completed 100% of database upgrade 42771:20140422:145007.762 database upgrade fully completed Next 2.2.3 runs will show: 42973:20140422:145138.315 Starting Zabbix Server. Zabbix 2.2.3 (revision 44105). 42973:20140422:145138.315 ****** Enabled features ****** 42973:20140422:145138.316 SNMP monitoring: YES 42973:20140422:145138.316 IPMI monitoring: YES 42973:20140422:145138.316 WEB monitoring: YES 42973:20140422:145138.316 VMware monitoring: YES 42973:20140422:145138.316 Jabber notifications: YES 42973:20140422:145138.316 Ez Texting notifications: YES 42973:20140422:145138.316 ODBC: NO 42973:20140422:145138.316 SSH2 support: YES 42973:20140422:145138.316 IPv6 support: NO 42973:20140422:145138.316 ****************************** 42973:20140422:145138.316 using configuration file: /etc/zabbix/zabbix_server.conf 42973:20140422:145138.347 current database version (mandatory/optional): 02020000/02020001 42973:20140422:145138.347 required mandatory version: 02020000 It's not clear why required mandatory version matches with current DB version but some automatic DB upgrade being performed. If investigate it appear to be an optional 2020001 patch. Suggestion: to be more user friendly would be good to mention that there available optional patch(es). Log something like: required mandatory version: 02020000 available optional version: 02020001 p.s. the patch introduced in ZBX-7849 for 2.2.3
        Hide
        Juris Miščenko (Inactive) added a comment -

        Fixes implemented in svn://svn.zabbix.com/branches/dev/ZBX-8152-2_2 for 2.2 and svn://svn.zabbix.com/branches/dev/ZBX-8152 for trunk.

        Show
        Juris Miščenko (Inactive) added a comment - Fixes implemented in svn://svn.zabbix.com/branches/dev/ZBX-8152-2_2 for 2.2 and svn://svn.zabbix.com/branches/dev/ZBX-8152 for trunk.
        Hide
        Oleksiy Zagorskyi added a comment - - edited

        I see new log message:
        "%d optional patch(es) were found"

        Just wanted to say that I'd replace it with:
        "%d optional patches were found"

        Alexander Vladishev I think it is not important how many patches are found. I vote for:

        "optional patches were found" without number of patches.

        42771:20140422:145007.748 current database version (mandatory/optional): 02020000/02020000
        42771:20140422:145007.748 required mandatory version: 02020000
        42771:20140422:145007.748 optional patches were found                      <-- new line
        42771:20140422:145007.748 starting automatic database upgrade
        42771:20140422:145007.762 completed 100% of database upgrade
        42771:20140422:145007.762 database upgrade fully completed
        
        Show
        Oleksiy Zagorskyi added a comment - - edited I see new log message: "%d optional patch(es) were found" Just wanted to say that I'd replace it with: "%d optional patches were found" Alexander Vladishev I think it is not important how many patches are found. I vote for: "optional patches were found" without number of patches. 42771:20140422:145007.748 current database version (mandatory/optional): 02020000/02020000 42771:20140422:145007.748 required mandatory version: 02020000 42771:20140422:145007.748 optional patches were found <-- new line 42771:20140422:145007.748 starting automatic database upgrade 42771:20140422:145007.762 completed 100% of database upgrade 42771:20140422:145007.762 database upgrade fully completed
        Hide
        Juris Miščenko (Inactive) added a comment -

        Implemented in 2.2.4rc1 r45505, 2.3.0 (trunk) r45511

        Show
        Juris Miščenko (Inactive) added a comment - Implemented in 2.2.4rc1 r45505, 2.3.0 (trunk) r45511

          People

          • Assignee:
            Unassigned
            Reporter:
            Oleksiy Zagorskyi
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: