Ad Widget

Collapse

Timeout while answering request

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cjwallace
    Senior Member
    • Sep 2008
    • 126

    #1

    Timeout while answering request

    Guys

    In /tmp/Zabbix_Server.log i have alot of the following Timeout while answering request

    Is this anything that i should be worrying about?


    4236:20081102:131834 Starting zabbix_server. ZABBIX 1.6.
    4236:20081102:131834 **** Enabled features ****
    4236:20081102:131834 SNMP monitoring: YES
    4236:20081102:131834 WEB monitoring: YES
    4236:20081102:131834 Jabber notifications: NO
    4236:20081102:131834 ODBC: NO
    4236:20081102:131834 IPv6 support: NO
    4236:20081102:131834 **************************
    4236:20081102:131838 ZABBIX semaphores already exist, trying to recreate.
    4337:20081102:131838 server #6 started [Trapper]
    4338:20081102:131838 server #7 started [Trapper]
    4339:20081102:131838 server #8 started [Trapper]
    4343:20081102:131838 server #11 started [ICMP pinger]
    4344:20081102:131838 server #12 started [Alerter]
    4345:20081102:131838 server #13 started [Housekeeper]
    4345:20081102:131838 Executing housekeeper
    4348:20081102:131838 server #14 started [Timer]
    4340:20081102:131838 server #9 started [Trapper]
    4341:20081102:131838 server #10 started [Trapper]
    4352:20081102:131838 server #16 started [Node watcher. Node ID:0]
    4353:20081102:131838 server #17 started [HTTP Poller]
    4354:20081102:131838 server #18 started [HTTP Poller]
    4336:20081102:131838 server #5 started [Poller. SNMP:YES]
    4332:20081102:131838 server #1 started [Poller. SNMP:YES]
    4359:20081102:131838 server #19 started [HTTP Poller]
    4334:20081102:131838 server #3 started [Poller. SNMP:YES]
    4363:20081102:131838 server #20 started [HTTP Poller]
    4333:20081102:131838 server #2 started [Poller. SNMP:YES]
    4335:20081102:131838 server #4 started [Poller. SNMP:YES]
    4367:20081102:131838 server #21 started [HTTP Poller]
    4349:20081102:131838 server #15 started [Poller for unreachable hosts. SNMP:YES]
    4371:20081102:131838 server #23 started [Escalator]
    4236:20081102:131838 server #0 started [Watchdog]
    4236:20081102:131838 In main_watchdog_loop()
    4369:20081102:131838 server #22 started [Discoverer. SNMP:YES]
    4345:20081102:131846 Deleted 0 records from history and trends
    4369:20081102:131851 Timeout while answering request
    4369:20081102:131904 Timeout while answering request
    4369:20081102:131916 Timeout while answering request
    4369:20081102:131929 Timeout while answering request
    4369:20081102:131941 Timeout while answering request
    4369:20081102:131954 Timeout while answering request
    4369:20081102:132006 Timeout while answering request
    4369:20081102:132019 Timeout while answering request
    4369:20081102:132031 Timeout while answering request
    4369:20081102:132044 Timeout while answering request
    4369:20081102:132056 Timeout while answering request
    4369:20081102:132109 Timeout while answering request
    4369:20081102:132121 Timeout while answering request
    4369:20081102:132134 Timeout while answering request
    4369:20081102:132146 Timeout while answering request
    4369:20081102:132159 Timeout while answering request
    4369:20081102:132211 Timeout while answering request
    4369:20081102:132224 Timeout while answering request
    4369:20081102:132237 Timeout while answering request
    4369:20081102:132249 Timeout while answering request
    4369:20081102:132302 Timeout while answering request
    4369:20081102:132314 Timeout while answering request
    4369:20081102:132327 Timeout while answering request
    4369:20081102:132339 Timeout while answering request
    4369:20081102:132352 Timeout while answering request
  • velosprinter
    Junior Member
    • Jul 2008
    • 19

    #2
    Same here

    I don't know why but I get the same thing in my log.

    repeats this patten:
    6489:20081206:200811 Timeout while answering request
    6487:20081206:200813 Timeout while answering request
    6488:20081206:200814 Timeout while answering request
    6489:20081206:200815 Timeout while answering request
    6490:20081206:200817 Timeout while answering request
    6487:20081206:200819 Timeout while answering request
    6488:20081206:200820 Timeout while answering request
    6490:20081206:200822 Timeout while answering request
    6491:20081206:200823 Timeout while answering request
    6487:20081206:200824 Timeout while answering request
    6488:20081206:200825 Timeout while answering request
    6489:20081206:200827 Timeout while answering request

    and sometimes

    6489:20081206:200902 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6491:20081206:200902 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6491:20081206:200902 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6488:20081206:200903 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6491:20081206:200903 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6491:20081206:200903 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6489:20081206:200904 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6488:20081206:200904 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6490:20081206:200906 SNMP error [(noSuchName) There is no such variable name in this MIB.]
    6490:20081206:200906 SNMP error [(noSuchName) There is no such variable name in this MIB.]


    There was something about changing a file to add more info in 1.4 but that file is not in 1.6

    On the monitor everything is gren and reporting fine so I just don't know where to start.

    Comment

    • alexdaoust
      Junior Member
      • May 2009
      • 6

      #3
      Same here its the only error i have in my log now but i do get a lot of it
      so what exactly does it mean?

      Comment

      • velosprinter
        Junior Member
        • Jul 2008
        • 19

        #4
        This was long ago and I don't know that I fixed it.

        Try increasing the logging value in the config to see what is writing to log.

        Comment

        Working...