NimbostratusHi,
I have upgraded 3600 ltm from BIG-IP 11.5.1 Build 4.0.128 to BIG-IP 11.6.0 Build 0.0.401, after the upgrade is completed and the device restarted it is stuck in Configuration Utility restarting... although I still access the device via ssh.
any ideas how to fix this issues ?
Thanks Sahir
NimbostratusWhile in CLI, you should examine "/var/log/ltm" - that should provide you more information about what is stuck. "bigstart status" can also show you what processes aren't starting or are constantly restarting.
If this is a production system, I highly recommend opening an F5 support case.
I should have stated that you will also see this when the configuration has not completed loading, most commonly seen during upgrades or reboot of a device.
Nimbostratusthanks guys, solved the problem 2 yrs ago :)
CumulonimbusWhile in CLI, you should examine "/var/log/ltm" - that should provide you more information about what is stuck. "bigstart status" can also show you what processes aren't starting or are constantly restarting.
If this is a production system, I highly recommend opening an F5 support case.
I should have stated that you will also see this when the configuration has not completed loading, most commonly seen during upgrades or reboot of a device.
Nimbostratusthanks guys, solved the problem 2 yrs ago :)
NimbostratusUsually when I have a problem like this after an upgrade it is because of a licensing issue that is hanging the box.
Can you ssh into the device? If so, run tmsh show sys mcp-state and make sure mcp is running. Also what is the status of the device in the bash banner? Does it say INOPERATIVE?
Do a tmsh show /sys license and make sure your license is ok. You may need to reapply it.
NimbostratusNimbostratusShaggy & Brian, thanks for your response.
The device I am working at is a lab device, and yes the issue with licencing, after reading through F5 site I managed to licence the device again and brought back to life.
Thanks Sahir
NimbostratusI have faced the same issue while I was upgrading the F5 LTM 2000Series.
And I followed the following steps and it's work.
01- access via ssh and login with root ID
02- go to tmsh
03- stop sys service all
04- start sys service all
05- load sys ucs Base_Config.ucs no-license
06- save sys config
07- reboot
This is a pretty common issue and is typically caused by a failure of httpd or tomcat in relation to tomcat java services. Running the following, non-traffic impacting command will remedy this in most cases. This may also be seen when too many admins logon and do not logout, releasing the consumed resources.
tmsh restart /sys service httpd tomcat
Nimbostratusyeah I have used tmsh restart /sys service httpd tomcat and restarted server and it no longer hanged
NimbostratusI didn't upgrade but my F5 has been up for past 313 days and was hung going to redirected, then configuration utility restarted. Running the command tmsh restart /sys service httpd tomcat fixed the issue and web login no longer hung.
NimbostratusI am still stuck in this process and when I login via CLI, I am just seeing this messages and do not have time and possibility to write something. It is virtual F5 BIG-IP
Are you able to help me? Thank you in advance.
2018 Nov 12 07:57:22 degio9010lb003p logger: Re-starting restnoded
2018 Nov 12 07:57:22 degio9010lb003p logger: Re-starting mcpd
2018 Nov 12 07:57:23 degio9010lb003p logger: Re-starting evrouted
2018 Nov 12 07:57:23 degio9010lb003p logger: Re-starting lind
2018 Nov 12 07:57:23 degio9010lb003p logger: Re-starting csyncd
2018 Nov 12 07:57:23 degio9010lb003p logger: Re-starting restnoded
2018 Nov 12 07:57:24 degio9010lb003p logger: Re-starting lind
2018 Nov 12 07:57:24 degio9010lb003p logger: Re-starting evrouted
2018 Nov 12 07:57:24 degio9010lb003p logger: Re-starting csyncd
2018 Nov 12 07:57:24 degio9010lb003p logger: Re-starting restnoded
2018 Nov 12 07:57:24 degio9010lb003p logger: Re-starting mcpd
2018 Nov 12 07:57:25 degio9010lb003p logger: Re-starting lind
NimbostratusThe solution of restarting the tomcat service worked for me. Thanks Chris Byrne.
tmsh restart /sys service httpd tomcat