Forum Discussion

Heiko_Engemann_'s avatar
Heiko_Engemann_
Icon for Nimbostratus rankNimbostratus
Jan 29, 2009

restart the snmp daemon with cron

Hello,

 

 

we had some trouble witht he snmp daemon on our bigip LB's.

 

It didnt answer any snmp queries, after restartign the snmp service everything run fine again.

 

 

What is the exact command I have to put into the crontab?

 

 

im thinking about something like "bigstart restart snmpd".

 

 

thx

 

 

.h

7 Replies

  • Putting "bigstart restart snmpd" into crontab should work for periodically bouncing the snmp service, but that configuration may not survive an upgrade or hotfix (plus it shouldn't be dying in the first place). I would open a support case with F5 to see if they can tell what may be causing the snmp service to hang up.

     

     

    Denny
  • Hello,

     

     

    we dont have any support left on our bigips.

     

    In a active/passive Setup, do I have to only create the conrjob on the active bigip?

     

     

    greetings
  • Hi,

     

     

    i did put the below line into the crontab, but thre service didnt got restarted:

     

     

    1 1 * * * * bigstart restart snmpd

     

     

     

    I can see there are more than one snmpd, do I have to restart all of them?

     

     

    bigstart status

     

    alertd run (pid 808) 186 days

     

    bcm56xxd run (pid 814) 186 days

     

    big3d run (pid 810) 186 days

     

    big3dshim run (pid 811) 186 days

     

    bigd run (pid 30817) 51 minutes, 1771 restarts

     

    bigdbd run (pid 816) 186 days

     

    bigsnmpd run (pid 19535) 5 minutes, 4 starts

     

    chmand run (pid 817) 186 days

     

    cssd run (pid 832) 186 days

     

    eventd run (pid 827) 186 days

     

    fpdd run (pid 818) 186 days

     

    lacpd run (pid 819) 186 days

     

    mcpd run (pid 820) 186 days

     

    nokiasnmpd down 4 minutes

     

    radvd down 186 days

     

    rmonsnmpd run (pid 19543) 5 minutes, 4 starts

     

    snmpd run (pid 19476) 5 minutes, 4 starts

     

    sod run (pid 831) 186 days

     

    statsd run (pid 821) 186 days

     

    stpd run (pid 822) 186 days

     

    syscalld run (pid 823) 186 days

     

    tamd run (pid 1273) 186 days, 1 start

     

    tmm run (pid 807) 186 days

     

    tmrouted run (pid 824) 186 days

     

    tmsnmpd run (pid 19553) 5 minutes, 4 starts

     

    tomcat4 run (pid 25662) 9 hours, 186 starts

     

    zebosd down 186 days

     

     

    cheers

     

     

    Heiko
  • Hello,

     

    did I edit the wrong file?

     

    I do a "crontab -e".

     

    when I do a "crontab -l" i get:

     

    DO NOT EDIT THIS FILE - edit the master and reinstall.

     

    (/tmp/crontab.23492 installed on Mon Feb 9 13:57:45 2009)

     

    (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $)

     

    1 1 * * * * /usr/bin/bigstart restart snmpd

     

    1-59/30 * * * * /usr/bin/diskmonitor

     

     

    what is meant by "edit the master"?

     

    I ask because the snmpd hasnt got restarted, but it should been at 1.10h tonight

     

    thx

     

    Heiko
  • Deb_Allen_18's avatar
    Deb_Allen_18
    Historic F5 Account
    use -l flag to view current entries, -e flag to edit the master (root crontab file) in vi
  • ah, ic.

     

    thats what I did, "crontab -e".

     

     

    now the question remains why the snmpd didnt got restarted