Ad Widget

Collapse

Service not Starting after update

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Martin Romer
    Junior Member
    • May 2022
    • 1

    #1

    Service not Starting after update

    Hi together,

    I updatet the Zabbix Server from Version 5.0.2 to 6.0.1
    After the update i tried to start the service.
    But still get an error that the service ist not starting.

    In the service logs i only see following errors:
    Mai 09 10:31:05 Zabbix zabbix_server[1426645]: /usr/sbin/zabbix_server: symbol lookup error: /usr/sbin/zabbix_server: undefined symbol: usmHMAC192SHA256AuthProtocol
    -- The process' exit code is 'exited' and its exit status is 127.


    The database is cause of that also not updating
  • Greg101
    Junior Member
    • Sep 2022
    • 3

    #2
    I am seeing the same issue after the upgrade from 6.0 to 6.2.
    I have no relating errors in zabbix_server.log.
    I see the below in the journalctl
    journalctl -r
    Code:
    Sep 09 09:28:29 stjvzab-lab-02 systemd[1]: Failed to start Zabbix Server.
    Sep 09 09:28:29 stjvzab-lab-02 systemd[1]: zabbix-server.service: Failed with result 'exit-code'.
    Sep 09 09:28:29 stjvzab-lab-02 systemd[1]: zabbix-server.service: Control process exited, code=exited, status=127/n/a
    Sep 09 09:28:29 stjvzab-lab-02 zabbix_server[1210]: /usr/sbin/zabbix_server: symbol lookup error: /usr/sbin/zabbix_server: undefined symbol: usmHMAC192SHA256AuthProtocol
    Sep 09 09:28:29 stjvzab-lab-02 systemd[1]: Starting Zabbix Server...
    ​

    Comment

    • tim.mooney
      Senior Member
      • Dec 2012
      • 1427

      #3
      What Linux distro and version are you using?

      Are there any pending updates for packages from your distro, especially SNMP-related packages?

      I can explain in more detail what's happening if you need, but the basic issue is that Zabbix is trying to use something that one of your system libraries should be providing, but for some reason the version of the library installed on your distro doesn't have the symbol (most likely a function, but there are other types of symbols that can be provided by shared libraries) available.

      This can happen when the distro (like RHEL or CentOS) changes what symbols are part of a later version of a package, but you've kept your system using an older version of the distro. Linux distros try to keep the public interface of libraries stable between distro point releases, but they're not always successful and sometimes they have to change what symbols a library provides. I suspect that's what's happened here, but without more info I can't be certain.



      Comment

      Working...