Forum Discussion
NimbostratusBigip Reboot
BIGIP 6900 system version 10.2.3
Here is the messages in ltm.log
Mar 12 03:57:54 PM boot_marker: ---===[ MD1.3 - BIG-IP 10.2.3 Build 123.0 ]===---
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: Invoked as: /usr/bin/mprov.pl (pid=2918) --boot --quiet
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/gtm
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/tmm
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/wom
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/psm
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/ui
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/lc
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/woml
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/apm
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/wam
Mar 12 15:57:59 local/PEKDC2-BR-SVC-LB5 info mprov: /bin/mkdir -p /dev/mprov/asm
Mar 12 15:58:00 local/PEKDC2-BR-SVC-LB5 info mprov: No mountpoints existed, likely first boot after upgrade.
Mar 12 15:58:00 local/PEKDC2-BR-SVC-LB5 info mprov: Created mountpoints, but this is not first boot after install (ignoring)...
We did not change anything about the network,Was this a bug in this version?
Thanks~~
8 Replies
- nitass
Employee
the log you posted is after the reboot. to find a root cause, i think you have to check log before the reboot.
additionally, you may open a support case to get assistance from engineer.
airman525_19311Anywhere else the log messages was saved ？Except that，only this two words int the ltm.log 's beginning which didn’t match the reboot time： Mar 12 09:08:21 local/tmm1 warning tmm1[6449]: 011e0001:4: Limiting open port RST response from 251 to 250 packets/sec Mar 12 11:36:10 local/tmm1 warning tmm1[6449]: 011e0001:4: Limiting open port RST response from 251 to 250 packets/sec The one above is the whole contents in the ltm.log before the "boot_marker" Thank you very much!- boneyard
MVP
those don't really indicate any issue. might be wise to configure syslog or such so the next time you have those logs somewhere else.
nitass_89166Noctilucent
the log you posted is after the reboot. to find a root cause, i think you have to check log before the reboot.
additionally, you may open a support case to get assistance from engineer.
- airman525_19311Anywhere else the log messages was saved ？Except that，only this two words int the ltm.log 's beginning which didn’t match the reboot time： Mar 12 09:08:21 local/tmm1 warning tmm1[6449]: 011e0001:4: Limiting open port RST response from 251 to 250 packets/sec Mar 12 11:36:10 local/tmm1 warning tmm1[6449]: 011e0001:4: Limiting open port RST response from 251 to 250 packets/sec The one above is the whole contents in the ltm.log before the "boot_marker" Thank you very much!
- boneyardthose don't really indicate any issue. might be wise to configure syslog or such so the next time you have those logs somewhere else.
SynACk_128568Cirrostratus
if system rebooting frequently enable console logging to capture the logs and see later ...
Ed_SummersCheck the TMM logs in /var/log as well. We found those useful in sniffing out a BigIP bug, though that was during a system upgrade.
kern.log and messages (in /var/log) could also be useful. We experienced a memory leak issue (believed to have been AVR) that was apparent when reviewing /var/log/messages.
Good luck!
