Forum Discussion

Anthony's avatar
Anthony
Icon for Nimbostratus rankNimbostratus
Aug 15, 2013

config-sync fail - Can't load monitor instance for /Common/http:359

I've had to roll back out test loadbalancers from 11.4 to 11.2.1 HF3.

I've manaually updated the config on the first box and this is working just fine.

Doing this for the second one and running the: tmsh load /sys config command once I've uploaded the bigip.conf gives the following error:

Loading system configuration...
  /defaults/app_template_base.conf
  /defaults/config_base.conf
  /config/low_profile_base.conf
  /defaults/wam_base.conf
  /usr/share/monitors/base_monitors.conf
  /config/daemon.conf
  /config/profile_base.conf
  /defaults/fullarmor_gpo_base.conf
  /defaults/classification_base.conf
Loading configuration...
  /config/bigip_base.conf
  /config/bigip_user.conf
  /config/bigip.conf
01070712:3: Caught configuration exception (0), Can't load monitor instance for /Common/http:359 - ltm/validation/MonitorRule.cpp, line 1606.
Unexpected Error: Loading configuration process failed.

When I try and just config-sync over it gives the following:

Aug 15 10:19:17 LTM2 notice mcpd[6112]: 01071038:5: 4a:47:49:fe:50:7c:a7:26:35:6c:9e:49:44:46:43:f7:46:ca:23:83
Aug 15 10:19:17 LTM2 notice mcpd[6112]: 01071038:5: 4a:47:49:fe:50:7c:a7:26:35:6c:9e:49:44:46:43:f7:46:ca:23:83
Aug 15 10:19:17 LTM2 notice mcpd[6112]: 01071038:5: Unit key read from the hardware.
Aug 15 10:19:17 LTM2 notice mcpd[6112]: 01071038:5: Loading keys from the file.
Aug 15 10:19:19 LTM2 info mcpd[6112]: 010712e9:6: Resuming log processing at this invocation; held 1 messages.
Aug 15 10:19:19 LTM2 warning mcpd[6112]: 010712e9:4: gtm.checkpendingmonitor is not in BigDB.dat.
Aug 15 10:19:19 LTM2 warning mcpd[6112]: 010712e9:4: tmm.lb.weightedratioenable is not in BigDB.dat.
Aug 15 10:19:19 LTM2 warning mcpd[6112]: 010712e9:4: lacpd.refport.stick is not in BigDB.dat.
Aug 15 10:19:19 LTM2 warning mcpd[6112]: 010712e9:4: systemauth.radiusservicetype is not in BigDB.dat.
Aug 15 10:19:19 LTM2 warning mcpd[6112]: 010712e9:4: dag.tcp.hash is not in BigDB.dat.
Aug 15 10:19:19 LTM2 info mcpd[6112]: 010712e9:6: Per-invocation log rate exceeded; throttling.
Aug 15 10:19:20 LTM2 notice mcpd[6112]: 01070727:5: Pool /Common/PartnerHub_UAT_Func_SSH member /Common/chlorine:22 monitor status up. [ was up for 0hr:0min:1sec ]
Aug 15 10:19:20 LTM2 notice mcpd[6112]: 01070727:5: Pool /Common/PartnerHub_UAT_Func_SSH member /Common/scandium:22 monitor status up. [ was up for 0hr:0min:1sec ]
Aug 15 10:19:20 LTM2 notice mcpd[6112]: 01070638:5: Pool /Common/Zone_Map_pool member /Common/argon9:9101 monitor status forced down. [ was forced down for 0hr:0min:1sec ]
Aug 15 10:19:20 LTM2 notice mcpd[6112]: 01070639:5: Pool /Common/Zone_Map_pool member /Common/helium5:91 session status forced disabled.
Aug 15 10:19:20 LTM2 notice mcpd[6112]: 01070638:5: Pool /Common/Zone_Map_pool member /Common/helium5:91 monitor status forced down. [ was forced down for 0hr:0min:1sec ]
Aug 15 10:19:20 LTM2 err mcpd[6112]: 01070712:3: Caught configuration exception (0), Can't load monitor instance for /Common/http:359 - ltm/validation/MonitorRule.cpp, line 1606.
Aug 15 10:19:21 LTM2 err mcpd[6112]: 01071488:3: Remote transaction for device group /Common/device-group-failover-584c50b71dcd to commit id 118 5912273116538870559 /Common/LTM1.domain.co.uk failed with error 01070712:3: Caught configuration exception (0), Can't load monitor instance for /Common/http:359 - ltm/validation/MonitorRule.cpp, line 1606..
Aug 15 10:19:21 LTM2 notice mcpd[6112]: 01071038:5: 4a:47:49:fe:50:7c:a7:26:35:6c:9e:49:44:46:43:f7:46:ca:23:83
Aug 15 10:19:22 LTM2 notice mcpd[6112]: 01071038:5: 4a:47:49:fe:50:7c:a7:26:35:6c:9e:49:44:46:43:f7:46:ca:23:83
Aug 15 10:19:22 LTM2 notice mcpd[6112]: 01071038:5: Unit key read from the hardware.
Aug 15 10:19:22 LTM2 notice mcpd[6112]: 01071038:5: Loading keys from the file.
Aug 15 10:19:22 LTM2 notice mcpd[6112]: 010714a0:5: Sync of device group /Common/device_trust_group to commit id 118 5912273116547139026 /Common/LTM1.domain.co.uk from device /Common/LTM1.domain.co.uk complete.

Any advice that could be give on this would be hugely appreciated.

Many thanks Anthony

management

7 Replies

Sort By
  • Anthony's avatar
    Anthony
    Icon for Nimbostratus rankNimbostratus
    Aug 15, 2013

    Thanks for the links. I have looked at both of them before posting and tried the IP address one, but made no difference.

     

    I really don't understand how a config that is exactly the same will load on one machine, but not the other. So frustrating!

     

    I need to do a clean install, but seems that when I install to another partition it still has the config from the other one.

     

  • BinaryCanary_19's avatar
    BinaryCanary_19
    Historic F5 Account
    Aug 16, 2013

    Boneyard is actually right. It's a known issue fixed in Hotfix 8 of 11.2.1.

     

    If you fancy it, you can open a support case and ask them to confirm if this is ID 396261.

     

    The workaround is to copy the bigip.conf file from the peer to the affected unit and manually load it with "tmsh load sys config".

     

    Then you just make the unit without an issue the one with the highest commit ID (just open a configuration object and click update), then syncing should work.

     

    Probably good to upgrade to the latest hotfix too.

     

  • Anthony's avatar
    Anthony
    Icon for Nimbostratus rankNimbostratus
    Aug 16, 2013

    I will be continuing the upgrade on Hotfixes once I have them back where they were on HF3.

     

    I have been using the bigip.conf from each machine and using beyond compare to make sure they are the same, so I will try a physical copy from the working to the none working and see if that makes a difference.

     

    Will feed back when I have carried this out.

     

    Thanks Ant

     

  • Anthony's avatar
    Anthony
    Icon for Nimbostratus rankNimbostratus
    Aug 16, 2013

    Ok I've just copied the config from the working LTM to the other, run tmsh load /sys config and it has failed still with the above error.

     

    I think I will do a HF8 install on one of the spare partitions and see what happens there.

     

  • Anthony's avatar
    Anthony
    Icon for Nimbostratus rankNimbostratus
    Aug 27, 2013

    I rolled forward to HF8 and thankfully managed to get passed the error from above! Both test LTMs are now happily running v11.2.1 HF8 after rolling back from 11.4!

     

    Thanks to all for your help and suggestions.

     

    Regards, Anthony

     

  • RiverFish's avatar
    RiverFish
    Icon for Altostratus rankAltostratus
    Apr 05, 2014

    All I did was recreate the monitor in the gui and then tried to reapply it back to the pool member (got some other error message) then: tmsh load sys config verify tmsh load sys config tmsh save sys config

     

    When all that worked I went back to the gui and did a sync to-group and it worked.