Ad Widget

Collapse

agentd log volume after server upgrade

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • LenR
    Senior Member
    • Sep 2009
    • 1005

    #1

    agentd log volume after server upgrade

    I'm testing our upgrade from 1.6.7 to 1.8.1. I updated the server and proxy but now downlevel agentd logs have lots more traffic. Looks like this:

    19242:20100219:153956 Sleeping for 1 seconds
    19240:20100219:153957 Processing request.
    19240:20100219:153957 In check_security()
    19240:20100219:153957 Requested [net.if.out[eth0,bytes]]
    19240:20100219:153957 Sending back [1524178745]
    19242:20100219:153957 In send_buffer('128.206.0.149','10051')

    On my server and proxy, the new agent is in /usr/local/sbin, the old agent is in /usr/sbin, so switching between the two is pretty easy. Switiching to the new agent returns the log to silence after startup:

    16781:20100219:152859 Requested [vfs.fs.size[/home,free]]
    16781:20100219:152859 Sending back [9664556]
    16782:20100219:152900 Got signal. Exiting ...
    16776:20100219:152900 One child process died. Exiting ...
    16779:20100219:152900 Got signal. Exiting ...
    16780:20100219:152900 Got signal. Exiting ...
    16781:20100219:152900 Got signal. Exiting ...
    16776:20100219:152900 zbx_on_exit() called.
    16778:20100219:152900 Got signal. Exiting ...
    16776:20100219:152900 Got signal. Exiting ...
    16776:20100219:152900 zbx_on_exit() called.
    16776:20100219:152900 Cannot remove PID file [/tmp/zabbix_agentd.pid] [No such file or directory]
    16776:20100219:152902 ZABBIX Agent stopped. ZABBIX 1.6.7 (revision 8252).
    8410:20100219:152904.570 zabbix_agentd started. Zabbix 1.8.1 (revision 9702).
    8412:20100219:152904.571 zabbix_agentd collector started
    8413:20100219:152904.574 zabbix_agentd listener started
    8414:20100219:152904.575 zabbix_agentd listener started
    8415:20100219:152904.576 zabbix_agentd listener started
    8416:20100219:152904.577 zabbix_agentd active check started [127.0.0.1:10051]

    Not a big issue, but I could see filling some disks with all this log traffic. I can probably deploy updated agents to all hosts in about 30 minutes, but I'd rather not be rushed. (Puppet rules!)
Working...