Forum Discussion

Khoa_53278's avatar
Khoa_53278
Icon for Nimbostratus rankNimbostratus
Jun 04, 2009

Standby F5 processes restart when synchronising with active unit?

Hi all,

 

 

We have 2 F5 LTM units running active/standby. When we add some config in the active unit and perform sysching between 2 units, our SNMP Monitoring tool indicated that the standby unit rebooted. From uptime of the standby unit, it said that it up for more than 50 days and the messages liog show that some processes restarted at the same time of synchronization:

 

In the log of ltm:

 

Jun 3 15:54:28 SGDC2SS1LB02 bigpipe: Begin config install operation: /var/local/ucs/__sync_remote__.ucs

 

Jun 3 15:54:28 SGDC2SS1LB02 mcpd[1117]: 01070410:5: Removed subscription with subscriber id Subsnmpd_Subscriber

 

Jun 3 15:54:30 SGDC2SS1LB02 mcpd[1117]: 01070465:4: DB changed: failover.nettimeoutsec, configsync needed

 

Jun 3 15:54:30 SGDC2SS1LB02 mcpd[1117]: 01070465:4: DB changed: failover.netretrylimit, configsync needed

 

 

In the boot log:

 

Jun 3 15:54:30 SGDC2SS1LB02 ntpd: ntpd shutdown succeeded

 

Jun 3 15:54:30 SGDC2SS1LB02 ntpd: ntpd startup succeeded

 

 

And daemon log:

 

Jun 3 15:54:30 SGDC2SS1LB02 ntpd[5400]: ntpd exiting on signal 15

 

Jun 3 15:54:30 SGDC2SS1LB02 ntpd[17717]: ntpd 4.1.2@1.892 Mon Oct 15 12:16:59 PDT 2007 (1)

 

Jun 3 15:54:30 SGDC2SS1LB02 ntpd[17717]: kernel time discipline status 0040

 

Jun 3 15:54:33 SGDC2SS1LB02 named[17818]: starting BIND 9.3.5-P1 -f -t /var/named -u named -c /config/named.conf

 

Jun 3 15:54:33 SGDC2SS1LB02 named[17818]: the working directory is not writable

 

Jun 3 15:54:33 SGDC2SS1LB02 named[17818]: command channel listening on 127.0.0.1953

 

Jun 3 15:54:39 SGDC2SS1LB02 subsnmpd[17845]: Connect to master agent successfully.

 

Jun 3 15:54:42 SGDC2SS1LB02 rmonsnmpd[17852]: Connect to master agent successfully.

 

 

Is this normal when sysnching the configuration and the standby box restart the processes?

 

 

Thanks,

 

Khoa
  • Hi Khoa.

     

     

    The logs look normal during a active to standby unit. However, if the SNMP Uptime that you are monitoring is coming back to zero then it's possible you are running a version with a bug in it or you are monitoring the wrong Uptime element. What version are you running?

     

     

    Thanks,

     

    CB