Ad Widget

Collapse

Zabbix stable client exits on Debian stable (Etch).

Collapse
X
Collapse
 
  • Page of 1
  • Time
  • Show
Clear All
new posts
Previous template Next
  • kanour
    Senior Member
    • May 2006
    • 105
    #1

    Zabbix stable client exits on Debian stable (Etch).

    Hi I installed agent only on debian Etch from packages. Configured zabbix_agentd.conf. When I start zabbix agent it Exits in about 10 seconds.

    Can you help.

    002504:20070413:112642 zabbix_agentd started. ZABBIX 1.1.4.
    002505:20070413:112642 zabbix_agentd 2505 started
    002506:20070413:112642 zabbix_agentd 2506 started
    002507:20070413:112642 zabbix_agentd 2507 started
    002508:20070413:112642 zabbix_agentd 2508 started
    002509:20070413:112642 zabbix_agentd 2509 started
    002504:20070413:112652 One child process died. Exiting ...
    002505:20070413:112652 Got signal. Exiting ...
    002506:20070413:112652 Got signal. Exiting ...
    002507:20070413:112652 Got signal. Exiting ...
    002508:20070413:112652 Got signal. Exiting ...
    002568:20070413:113107 zabbix_agentd started. ZABBIX 1.1.4.
    002569:20070413:113107 zabbix_agentd 2569 started
    002570:20070413:113107 zabbix_agentd 2570 started
    002571:20070413:113107 zabbix_agentd 2571 started
    002572:20070413:113107 zabbix_agentd 2572 started
    002573:20070413:113107 zabbix_agentd 2573 started
    002568:20070413:113117 One child process died. Exiting ...
    002569:20070413:113117 Got signal. Exiting ...
    002570:20070413:113117 Got signal. Exiting ...
    002571:20070413:113117 Got signal. Exiting ...
    002572:20070413:113117 Got signal. Exiting ...
    Tags: None
    • kanour
      Senior Member
      • May 2006
      • 105
      #2
      Can anyone help with this. I am looking for easy way to install zabbix agents on machines which I want to monitor.
      Does anyone have problems with debian package on Etch?

        Comment

        • glut0r
          Member
          • Mar 2007
          • 38
          #3
          Originally posted by kanour
          Can anyone help with this. I am looking for easy way to install zabbix agents on machines which I want to monitor.
          Does anyone have problems with debian package on Etch?
          I've run at the same issue today, zabbix agents died without notice.
          So i run gdb to check WTF.

          Code:
          ~# gdb /usr/sbin/zabbix_agentd

... (unimportant lines removed)

Using host libthread_db library "/lib/tls/libthread_db.so.1".

(gdb) r

Starting program: /usr/sbin/zabbix_agentd
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1211039072 (LWP 23553)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
Missing mandatory parameter [Server]

Program exited normally.
(gdb) q
          yeah. Forgot Server= in zabbix_agentd.conf.
          Simple check to make sure:

          Code:
          ~# cat /etc/zabbix/zabbix_agentd.conf | grep -i server
# List of comma delimited IP addresses (or hostnames) of ZABBIX servers.
#Server
~#:
          yeah. Anyway, while trying to debug this, I've came across funny thing/bug:
          If I set DebugLevel=4, zabbix agent actually starts, but dies immediately after (undefined) server talks to it:

          Code:
          023588:20070415:233706 In refresh_metrics()
023588:20070415:233706 get_active_checks: host[(null)] port[10051]
023584:20070415:233805 In check_security()
023584:20070415:233805 Connection from [87.....]. Allowed servers [(null)]
023583:20070415:233805 One child process died. Exiting ...
023585:20070415:233805 Got signal. Exiting ...
023587:20070415:233805 Got signal. Exiting ...
023586:20070415:233805 Got signal. Exiting ...
          Anyway, you may use my way to find out what's wrong.

            Comment

            • kanour
              Senior Member
              • May 2006
              • 105
              #4
              The package does not work.

              I purged the package. I installed the package again. I configured just the server for trial. I could run the the agent. When I stoped the agent I could not start it again.

              zabbix_agentd started. ZABBIX 1.1.4.
              002199:20070416:100714 zabbix_agentd 2199 started
              002200:20070416:100714 zabbix_agentd 2200 started
              002201:20070416:100714 zabbix_agentd 2201 started
              002202:20070416:100714 zabbix_agentd 2202 started
              002203:20070416:100714 zabbix_agentd 2203 started
              002203:20070416:100714 Cannot connect to [localhost:10051] [Connection refused]
              002203:20070416:100714 Getting list of active checks failed. Will retry after 60 seconds
              002203:20070416:100814 Cannot connect to [localhost:10051] [Connection refused]
              002203:20070416:100814 Getting list of active checks failed. Will retry after 60 seconds
              002199:20070416:100822 Connection from [172.31.1.31] rejected. Allowed server is [localhost]
              002211:20070416:100832 zabbix_agentd started. ZABBIX 1.1.4.
              002211:20070416:100832 Cannot bind to port 10050. Error [Address already in use]. Another zabbix_agentd already running ?
              002203:20070416:100914 Cannot connect to [localhost:10051] [Connection refused]
              002203:20070416:100914 Getting list of active checks failed. Will retry after 60 seconds
              002200:20070416:100923 Connection from [172.31.1.31] rejected. Allowed server is [localhost]
              002203:20070416:101014 Cannot connect to [localhost:10051] [Connection refused]
              002203:20070416:101014 Getting list of active checks failed. Will retry after 60 seconds
              002201:20070416:101023 Connection from [172.31.1.31] rejected. Allowed server is [localhost]
              002203:20070416:101035 Got signal. Exiting ...
              002202:20070416:101035 Got signal. Exiting ...
              002201:20070416:101035 Got signal. Exiting ...
              002200:20070416:101035 Got signal. Exiting ...
              002199:20070416:101035 Got signal. Exiting ...
              002198:20070416:101035 One child process died. Exiting ...
              002226:20070416:101058 zabbix_agentd started. ZABBIX 1.1.4.
              002227:20070416:101058 zabbix_agentd 2227 started
              002228:20070416:101058 zabbix_agentd 2228 started
              002229:20070416:101058 zabbix_agentd 2229 started
              002230:20070416:101058 zabbix_agentd 2230 started
              002231:20070416:101058 zabbix_agentd 2231 started
              002226:20070416:101058 One child process died. Exiting ...
              002227:20070416:101058 Got signal. Exiting ...
              002228:20070416:101058 Got signal. Exiting ...
              002229:20070416:101058 Got signal. Exiting ...
              002230:20070416:101058 Got signal. Exiting ...
              002237:20070416:101119 zabbix_agentd started. ZABBIX 1.1.4.
              002238:20070416:101119 zabbix_agentd 2238 started
              002239:20070416:101119 zabbix_agentd 2239 started
              002240:20070416:101119 zabbix_agentd 2240 started
              002241:20070416:101119 zabbix_agentd 2241 started
              002242:20070416:101119 zabbix_agentd 2242 started
              002237:20070416:101119 One child process died. Exiting ...
              002238:20070416:101119 Got signal. Exiting ...
              002239:20070416:101119 Got signal. Exiting ...
              002240:20070416:101119 Got signal. Exiting ...
              002241:20070416:101119 Got signal. Exiting ...
              002252:20070416:101336 zabbix_agentd started. ZABBIX 1.1.4.
              002253:20070416:101336 zabbix_agentd 2253 started
              002254:20070416:101336 zabbix_agentd 2254 started
              002255:20070416:101336 zabbix_agentd 2255 started
              002256:20070416:101336 zabbix_agentd 2256 started
              002257:20070416:101336 zabbix_agentd 2257 started
              002252:20070416:101336 One child process died. Exiting ...
              002253:20070416:101336 Got signal. Exiting ...
              002254:20070416:101336 Got signal. Exiting ...
              002255:20070416:101336 Got signal. Exiting ...
              002256:20070416:101336 Got signal. Exiting ...

                Comment

                • kanour
                  Senior Member
                  • May 2006
                  • 105
                  #5
                  I compiled agent myself and it runs no problem.

                    Comment

                    • kanour
                      Senior Member
                      • May 2006
                      • 105
                      #6
                      Any agent zabbix_agentd does not work in debian stable. I tried all agents from debian repositories, also agent from zabbix web site.
                      Ane here is what I get


                      012278:20070416:163719 zabbix_agentd started. ZABBIX 1.1.
                      012279:20070416:163719 zabbix_agentd 12279 started
                      012280:20070416:163719 zabbix_agentd 12280 started
                      012281:20070416:163719 zabbix_agentd 12281 started
                      012282:20070416:163719 zabbix_agentd 12282 started
                      012283:20070416:163719 zabbix_agentd 12283 started
                      012283:20070416:163719 In init_list()
                      012283:20070416:163719 In refresh_metrics()
                      012283:20070416:163719 get_active_checks: host[172.31.1.31] port[10051]
                      012283:20070416:163719 Sending [ZBX_GET_ACTIVE_CHECKS
                      proxy01.ad.netstrategy.com.au
                      ]
                      012283:20070416:163719 Before read
                      012283:20070416:163719 In delete_all_metrics()
                      012283:20070416:163719 Parsed [ZBX]
                      012283:20070416:163719 Key [ZBX]
                      012283:20070416:163719 Refresh [(null)]
                      012283:20070416:163719 Lastlogsize [(null)]
                      012278:20070416:163719 One child process died. Exiting ...
                      012279:20070416:163719 Got signal. Exiting ...
                      012280:20070416:163719 Got signal. Exiting ...
                      012281:20070416:163719 Got signal. Exiting ...
                      012282:20070416:163719 Got signal. Exiting ...

                        Comment

                        • glut0r
                          Member
                          • Mar 2007
                          • 38
                          #7
                          Originally posted by kanour

                          002211:20070416:100832 zabbix_agentd started. ZABBIX 1.1.4.
                          002211:20070416:100832 Cannot bind to port 10050. Error [Address already in use]. Another zabbix_agentd already running ?
                          this one seems like a debian bug #374758 more info here. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=374758
                          If you restart agent or server too fast, it seems to hang waiting for socket to close.

                          You messed up with your setup dude, I work with agent and servers from version 1.1.4 until today, and it works fine. Nothing die (well, not without a cause anyway). I've run zabbix suite on sarge and on etch. No problems you fight with. Check forum, and active debian bugs.
                          Good luck!

                            Comment

                            Previous template Next
                            Working...