03-09-2015 01:06 AM - edited 03-10-2019 10:31 PM
I have an ACS ver 5.4.0.46.7 running on an applicance, ACS-1121-K9. After rebooting a Win2008-controller it stopped working and someone in my Department rebooted the ACS. It looks like the authentications are working now, but I can't Access the web gui. It responds to ping and ssh. I did a show acs-config-web-Interface and the view-Interface was disabled, I enabled it but still it isn't working:
TBGACS02/admin# show acs-config-web-interface
migration interface is disabled
ucp interface is disabled
view interface is enabled
rest interface is disabled
TBGACS02/admin# show application status acs
ACS role: PRIMARY
Process 'database' running
Process 'management' running (HTTP is nonresponsive)
Process 'runtime' not monitored
Process 'adclient' running
Process 'ntpd' running
Process 'view-database' running
Process 'view-jobmanager' Execution failed
Process 'view-alertmanager' running
Process 'view-collector' running
Process 'view-logprocessor' running
I could try to reboot again but I'd prefer not if possible..
Solved! Go to Solution.
03-09-2015 05:14 AM
Hi,
Can you try "application acs stop" and then application acs start and see if that resolves the issue?
If not, then i would suggest to take a show tech and support bundle and open a case with TAC.
Regards,
Kanwal
Note: Please mark answers if they are helpful.
03-09-2015 05:14 AM
Hi,
Can you try "application acs stop" and then application acs start and see if that resolves the issue?
If not, then i would suggest to take a show tech and support bundle and open a case with TAC.
Regards,
Kanwal
Note: Please mark answers if they are helpful.
03-10-2015 12:01 AM
acs stop and acs start solved it. I suspect that my co-workers restarted the ACS by taking the Power instead of issuing the reload-command in the CLI.
08-26-2019 02:17 PM
03-09-2015 10:13 AM
As a basic troubleshooting we can restart the services or server completely. However if that doesn't help, then we can also review the size of /opt to ensure accumulation of view database is not causing this issue. From the logging perspective we can look at management and ade/ADE logs.
In Majority of cases customer reset the application configuration and restore the last good backup. This always help them resolve the issue quickly without going through the troubleshooting process.
HTH
-Jatin
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide