Forum Discussion
NimbostratusError on LTM restart, configuration process failed
Hi.
Issue after restarting standby node. Get a configuration error: The object (some SSL profile) is owned by a non-existent application (an application). Unexpected error: loading configraion process failed.
Web gui is stuck in configuration utility restarting..
The application I recall was created, deleted and recreated with a different iapps version but with the same name. Might have created a conflict perhaps. Not very familiar with the CLI and can't find any good info about how to troubleshoot this issue.
9 Replies
vineyard_166933See an old issue, 409303, but this was fixed and we're at 11.6.
antienho_01_141not sure which TMOS version you have.. but may be also try "restart sys service all" at the TMOS shell- vineyard_166933We're at 11.6.0. Tried to reboot again but still the same. "Restart sys service all" will that interfere with online node? Guess the services if local was restarted during reboot.
- vineyard_166933
Still have this issue, config won't load because of the SSL profile belonging to a non-existent application.
- JG
Cumulonimbus
You can try the reload method detailed in solution article SOL13030: Forcing the mcpd process to reload the BIG-IP configuration .
- vineyard_166933
Working with support technician regarding this.
- vineyard_166933
Got good help and was guided trough CLI.
The final solution was make a backup of bigip.conf then edit it with nano.
For the client ssl profile in question, set "appservervice none" Then, tmsh load sys config verify showed no errors.
Rebooted and it started ok again. Checked online device if it had the same misconfiguration, it didnt so synced with overwrite from online to standby.
- JGThanks for sharing the solution. I wonder what caused this to happen. Obviously you did not edit the bigip.conf file in anyway prior to the problem?
- vineyard_166933
We had synchronizing issues with the application service before.
Hard to say exactly what triggered it because a number of things was done before manually synchronizing. Created, deleted, recreated, added more.
To make GUI sync work again the application service was deleted and recreated after a successfull sync. In GUI Sync seemed OK - but in fact it didn't synchronize completely over to device 2, the application service wasn't deleted. We noticed when rebooting device 2.
