Forum Discussion
TJ_Vreugdenhil
Cirrus
Cirrusconfigsync issue with 10.1.0 Build 3402.0 Hotfix HF2
[admin@ed2lb2-pro:Standby] ~ csTest.pl --v
Status of daemons:
Warning: BigDB daemon (bigdbd) is not running.
Configsync configuration:
Failover address (Self): 10.1.1.2
Peer IP address: 10.1.1.1
Configsync port: 443
Configsync username: admin
Acceptable time difference: 600 seconds
Configsync auto detect status:
0 - Synchronized
Last change (Self): 12/27/2010 09:08:14 (1293469694)
Peer state is: known
Last change (Peer): 12/27/2010 09:08:44 (1293469724)
Last configsync: 12/27/2010 09:08:44 (1293469724)
Peer update interval: 30 (seconds)
Network connection status:
Local system is listening on configsync port (443).
Ping test to peer 10.1.1.1 succeeded.
Error: SOAP query failed. Ensure the user ID and password are
correct and the Allow Protocol TCP/443 is allowed on the
primary failover address 10.1.1.1.
[admin@ed2lb1-pro:Active] ~ csTest.pl --v
Status of daemons:
Warning: BigDB daemon (bigdbd) is not running.
Configsync configuration:
Failover address (Self): 10.1.1.1
Peer IP address: 10.1.1.2
Configsync port: 443
Configsync username: admin
Acceptable time difference: 600 seconds
Configsync auto detect status:
3 - Config modified on both systems, manual intervention required
Last change (Self): 12/27/2010 08:48:17 (1293468497)
Peer state is: known
Last change (Peer): 12/27/2010 09:08:44 (1293469724)
Last configsync: 12/16/2010 00:22:17 (1292487737)
Peer update interval: 30 (seconds)
Network connection status:
Local system is listening on configsync port (443).
Ping test to peer 10.1.1.2 succeeded.
SOAP connection test to peer 10.1.1.2 succeeded.
SOAP time difference check:
Within the acceptable range.
Product version test:
Major and minor product versions are identical. The maintenance
versions are different.
The configsync tests completed successfully. You can run this
diagnostic tool on the peer 10.1.1.2 for further information.
------------------
[admin@ed2lb2-pro:Standby] ~ bigstart status bigdbd
Service bigdbd has not been added to bigstart.
[admin@ed2lb2-pro:Standby] ~ bigstart start bigbdb
Couldn't find service: bigbdb
[admin@ed2lb2-pro:Standby] ~ bigstart status
big3d run (pid 3116) 35 days
bigd run (pid 3105) 35 days
-- same output on Active member --
Items that have been ruled out:
- disk space
- versions match
- Port Lockdown settings
- both LTM's run through a 'b load' just fine.
The syncing seems to be working. But from the EM there is alerts of the configsync status.
[admin@ed2lb1-pro:Active] ~ b config sync show
CONFIG SYNC STATUS --
Status 3 - Config modified on both systems, manual intervention required
Last change (Self) 2010-12-27 08:48:17
Last change (Peer) 2010-12-27 09:08:44
Last Configsync 2010-12-16 00:22:17
[admin@ed2lb1-pro:Active] ~ b config sync all
Checking configuration on local system and peer system...
Peer's IP address: 10.1.1.2
Synchronizing Master Keys...
Saving active configuration...
Configsync Mode: Push
Transferring UCS to peer...
Installing UCS on peer...
Obtaining results of remote configuration installation...
Saving active configuration...
Current configuration backed up to /var/local/ucs/cs_backup.ucs.
Product : BIG-IP
Version : 10.1.0
Hostname: UCS : ed2lb1-prodecomm.ns.dstcorp.net
System: ed2lb2-prodecomm.ns.dstcorp.net
Installing --shared-- configuration on host ed2lb2-prodecomm.ns.dstcorp.net
Installing configuration...
Post-processing...
Reading configuration from /config/low_profile_base.conf.
Reading configuration from /defaults/config_base.conf.
Reading configuration from /config/bigip_sys.conf.
Reading configuration from /config/bigip_base.conf.
Reading configuration from /usr/share/monitors/base_monitors.conf.
Reading configuration from /config/profile_base.conf.
Reading configuration from /config/daemon.conf.
Reading configuration from /config/bigip.conf.
Reading configuration from /config/bigip_local.conf.
Loading the configuration ...
Any Ideas?
Thanks!!!
8 Replies
TJ_VreugdenhilLooking into the following solution...
http://support.f5.com/kb/en-us/solutions/public/10000/600/sol10675.html- TJ_VreugdenhilI tried the following on both members:
bigstart enable bigdbd
bigstart add bigdbd
bigstart start bigdbd
bigstart status bigdbd
but the 'bigdbd' daemon keeps on restarting.
Dec 28 11:49:34 local/ed2lb1-pro emerg logger: Re-starting bigdbd
Dec 28 11:49:38 local/ed2lb1-pro emerg logger: Re-starting bigdbd
Dec 28 11:49:40 local/ed2lb1-pro emerg logger: Re-starting bigdbd
Ideas? 
hoolioCirrostratus
What is the actual message you're seeing on EM about the config sync status for this pair? If you do a config sync and then run 'b config sync show' what do you see for the status compared with what EM says?
I don't think bigdbd is used in 10.1.0+:
SOL11488: Overview of the daemons that are monitored and restarted by the runsv utility in BIG-IP version 10.x
http://support.f5.com/kb/en-us/solutions/public/11000/400/sol11488.html
The csTest.pl script should probably be updated to handle this more gracefully on current LTM versions.
Aaron- TJ_VreugdenhilYour'e right; the perl script was most likely not updated.
-----------
'b config sync' was run and then when the periodic 30 sec interval for a configsync we get the following:
EM Alert:
Status 3 - Config modified on both systems, manual intervention required
Standby:
Configsync auto detect status:
Status 0 - Synchronized
Last change (Self): 12/27/2010 09:08:14 (1293469694)
Peer state is: known
Last change (Peer): 12/27/2010 09:08:44 (1293469724)
Last configsync: 12/27/2010 09:08:44
Active:
Configsync auto detect status:
Status 3 - Config modified on both systems, manual intervention required
Last change (Self): 12/27/2010 08:48:17 (1293468497)
Peer state is: known
Last change (Peer): 12/27/2010 09:08:44 (1293469724)
Last configsync: 12/16/2010 00:22:17
--
(nothing to crazy in /var/log/ltm before the last configsync either):
Dec 16 00:22:14 local/ed2lb1-pro info bigpipe: Completed config sync all operation
--
The last things I would think of is to manually synchronize using the link below or reboot both members one at a time. (slated for 1/9/11)
http://support.f5.com/kb/en-us/solutions/public/10000/100/sol10181.html
Thanks Aaron,
-Tj - TJ_VreugdenhilConfig sync error:
Peer's IP address: 10.1.1.1
Caught SOAP exception: Error negotiating secure connection :
Connection reset by peer
Error: There is a problem accessing the peer system.
BIGpipe parsing error:
01110034:3: The configuration for running config-sync is incorrect. - TJ_VreugdenhilYou can change .ext to .cap.
I see full handshakes between both members. So I know connectivity and port lockdown are working correctly. - TJ_VreugdenhilAaron,
A 'full_box_reboot' on each member corrected this issue.
Thanks!
-Tj - hoolioThat's an odd one. Glad you figured out something that got it working...
Aaron
