Ad Widget

Collapse

zabbix active checks started to fail

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • nobre255
    Junior Member
    • Dec 2018
    • 2

    #16
    I have same problem.


    24525:20190629:234812.080 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    24533:20190629:234812.080 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    24534:20190629:234812.081 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    24532:20190629:234812.081 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    24531:20190629:234812.081 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    24536:20190629:234812.082 Got signal [signal:15(SIGTERM),sender_pid:1,sender_uid:0,reaso n:0]. Exiting ...
    24525:20190629:234812.083 Zabbix Agent stopped. Zabbix 3.0.17 (revision 80549).
    25585:20190629:234812.097 Starting Zabbix Agent [Zabbix server]. Zabbix 3.0.17 (revision 80549).
    25585:20190629:234812.097 **** Enabled features ****
    25585:20190629:234812.097 IPv6 support: YES
    25585:20190629:234812.097 TLS support: YES
    25585:20190629:234812.097 **************************
    25585:20190629:234812.097 using configuration file: /etc/zabbix/zabbix_agentd.conf
    25585:20190629:234812.098 agent #0 started [main process]
    25590:20190629:234812.098 agent #1 started [collector]
    25592:20190629:234812.099 agent #3 started[listener #2]
    25591:20190629:234812.099 agent #2 started[listener #1]
    25593:20190629:234812.100 agent #4 started[listener #3]
    25595:20190629:234812.100 agent #5 started [active checks #1]
    25595:20190629:234815.100 active check configuration update from [127.0.0.1:10051] started to fail (cannot connect to [[127.0.0.1]:10051]: [4] Interrupted system call)

    Comment

    • emz
      Junior Member
      • Mar 2014
      • 20

      #17
      Same here, I receive the same error - Zabbix Server, Proxy and agent v3.0.28.
      Any ideas?

      Comment

      • emz
        Junior Member
        • Mar 2014
        • 20

        #18
        Found it! It was the Linux firewall! Once I allowed communications to TCP port 10051 the issue disappeared!

        Comment

        Working...