Forum Discussion

amandeep_gupta_'s avatar
amandeep_gupta_
Icon for Nimbostratus rankNimbostratus
Jan 31, 2017

emerg logger: Re-starting mcpd

i am installing a new F5 LTM big ip 4000 but i am not able to see nay option to configure management ip.

 

moreover after connecting the console i observed following errors:

 

localhost emerg logger: Re-starting mcpd

 

i have tried rebooting the LB and getting below logs:

 

tail -f Jan 30 05:02:40 localhost emerg logger: Re-starting mcpd ltm Jan 30 05:00:27 localhost warning chmand[7124]: 012a0004:4: getLopSensorData: LopDev: sendLopCmd: Lopd status: 1 packet: action=1 obj_id=16d sub_obj=0 slot_id=ff result=1 len=0 crc=9050 payload= (error code:0x1) Jan 30 05:00:27 localhost warning chmand[7124]: 012a0004:4: getLopSensorData: LopDev: sendLopCmd: Lopd status: 1 packet: action=1 obj_id=16e sub_obj=0 slot_id=ff result=1 len=0 crc=383e payload= (error code:0x1) Jan 30 05:00:27 localhost warning chmand[7124]: 012a0004:4: getLopSensorData: LopHlprDev: sensor data reply too short, objId: 16f size: 39 Jan 30 05:00:27 localhost warning chmand[7124]: 012a0004:4: Per-invocation log rate exceeded; throttling. Jan 30 05:00:27 localhost notice chmand[7124]: 012a0005:5: initialize tmstat sensors (num sensors:11) Jan 30 05:00:27 localhost notice chmand[7124]: 012a0017:5: Chassis power module 1 turned on. Jan 30 05:00:27 localhost warning chmand[7124]: 012a0019:4: Chassis power module 2 absent. Jan 30 05:00:27 localhost info chmand[7124]: 012a0006:6: Power Supply 2 removed Jan 30 05:00:28 localhost err chmand[7124]: 012a0003:3: Error sending MCP system_information (err:1020003) Jan 30 05:01:01 localhost warning diskmonitor: 011d0002: Can not access the database because mcpd is not running. Jan 30 05:02:42 localhost emerg logger: Re-starting mcpd

 

i need help on how to recover this mcpd process.

 

2 Replies

  • what version of code are you running?

     

    some tmsh commands to get the MGT IP and default route configure:

     

    (bigip01)(cfg-sync Changes Pending)(Active)(/Common)(tmos) create sys ma Components: management-dhcp management-ip management-route (tmos) create sys management-ip ? Identifier: [object identifier] [ip_address/netmask] (-bigip01)(cfg-sync Changes Pending)(Active)(/Common)(tmos) create sys management-ip

     

    some article on initial setup via cmd line :

     

    link text

     

  • mcpd handles the device configuration. If is restarting, the majority of the device functions will not work, including change the management configuration.

     

    Try to create USB thumb drive with the software you want to use. Perform the clean install.

     

    If you still have mcpd restarting after the clean install, open a support case with F5 support. At this stage is possible that you may have a fault unit or disk.

     

    https://support.f5.com/csp/article/K13164