Ad Widget

Collapse

Proble in stop zabbix-agent service

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • aria
    Junior Member
    • May 2020
    • 8
    #1

    Proble in stop zabbix-agent service

    Hello friends. I have Debian 8 and the Zabbix-Agent service was running well on it. Today, the Zbbix service suddenly stopped and I can't understand why???

    When I check the status of the service with the following command, the following error is displayed :
    PHP Code:
    # service zabbix-agent status
    ● zabbix-agent.service - Zabbix Agent
    Loaded    : loaded (/lib/systemd/system/zabbix-agent.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Sun 2020-10-04 12:36:47 ; 10min ago
    Docs    : man:zabbix_agentd
    Process    : 17388 ExecStart=/usr/sbin/zabbix_agentd --foreground (code=exited, status=127)
    Main PID: 17388 (code=exited, status=127)

    Oct 04 12:36:47 Sip systemd[1]: Started Zabbix Agent.
    Oct 04 12:36:47 Sip systemd[1]: zabbix-agent.service: Main process exited, code=exited, status=127/n/a
    Oct 04 12    :36:47 Sip systemd[1]: zabbix-agent.service: Unit entered failed state.
    Oct 04 12:36:47 Sip systemd[1]: zabbix-agent.service: Failed with result 'exit-code'. 
    It also returns the following code to me when I run the journalctl command :
    PHP Code:
    # journalctl -u zabbix-agent
    -- Logs begin at Sat 2020-10-03 14:45:30 +0330, end at Sun 2020-10-04 12:48:44 +0330. --
    Oct 04 06:25:07 Sip systemd[1]: Stopping Zabbix Agent...
    Oct 04 06:25:07 Sip systemd[1]: Stopped Zabbix Agent.
    Oct 04 06:25:07 Sip systemd[1]: Started Zabbix Agent.
    Oct 04 06:25:07 Sip systemd[1]: zabbix-agent.service: Main process exited, code=exited, status=127/n/a
    Oct 04 06    :25:07 Sip systemd[1]: zabbix-agent.service: Unit entered failed state.
    Oct 04 06:25:07 Sip systemd[1]: zabbix-agent.service: Failed with result 'exit-code'.
    Oct 04 11:24:15 Sip systemd[1]: Started Zabbix Agent.
    Oct 04 11:24:15 Sip systemd[1]: zabbix-agent.service: Main process exited, code=exited, status=127/n/a
    Oct 04 11    :24:15 Sip systemd[1]: zabbix-agent.service: Unit entered failed state.
    Oct 04 11:24:15 Sip systemd[1]: zabbix-agent.service: Failed with result 'exit-code'.
    Oct 04 11:24:28 Sip systemd[1]: Started Zabbix Agent. 
    Even the zabbix agent service even starts and stops successfully, but It is not running when I check the status of the service.

    Where can the problem come from? please Help me
    Tags: None
    • tim.mooney
      Senior Member
      • Dec 2012
      • 1427
      #2
      The 'status=127' part likely means exited because of a signal. Since your system is using 'systemd' for services under the hood, you should probably move away from the 'service' command and get used to using 'systemctl', including

      Code:
      systemctl status -l zabbix-server.service
      The '-l' is long output, it might provide more details.

      However, the best place to look for more information is the zabbix_serverd.log file, which is probably under /var/log/zabbix/. Check there to see if there's more information on what the problem might be.

      Also, to make it easier for other people to potentially help you, it's useful to provide what version of Zabbix you're using and what database backend (MySQL, Postgres, etc.) and what its version is, in addition to the Linux distro and version that you already provided.

        Comment

        • aria
          Junior Member
          • May 2020
          • 8
          #3
          Thank you for your support. My problem was solved, but I still do not understand the reason for this problem??? I once removed the zabbix-agent service and reinstalled it, which fixed the problem.

          Today again, a number of my other servers that have the old version of agent-zabbix installed have a problem and the zabbix-agent service has stopped on them, and to solve the problem, I have to uninstall the zabbix-agent service and reinstall it.

          The only thing I can guess is that this problem occurs because my zabbix server is on the latest version (5) but the zabbix-agent is much older.
          PHP Code:
          # zabbix_agentd -V
          zabbix_agentd (daemon) (Zabbix) 3.0.7
          Revision 64609 21 December 2016          , compilation time: Jun 4 2017 07:14:06

          Copyright           (C) 2016 Zabbix SIA
          License GPLv2          +: GNU GPL version 2 or later <http://gnu.org/licenses/gpl.html>.
          This is free software: you are free to change and redistribute it according to
          the license          . There is NO WARRANTY, to the extent permitted by law. 

          Specifications of servers and clients:
          zabbix server version 5
          zabbix agent version 3
          DB => MariaDB
          OS in agents => Debian 8

            Comment

            Previous template Next
            Working...