This community is for technical, feature, configuration and deployment questions.
For production deployment issues, please contact the TAC! We will not comment or assist with your TAC case in these forums.
Please see How to Ask the Community for Help for other best practices.
Looks like the Bug CSCum28910 - Runtime fails due to an empty AD Group is back !
Just update some of or ACS platforms - 2 updated no problem but the 3rd refused to start.
When issuing the "show application status acs" command the Runtime process was in "restarting" state and never came up.
Had to back off the 18.104.22.168.3 Patch.
Heads up !
No, had no issues with the 22.214.171.124.2 Patch the problem only showed up when moving from Patch 2 to Patch 3 (126.96.36.199.3) and again only one of three deployments.
Two deployments are identical in server structure - Primary ACS (Log Collector) is a VM host and the Secondary is an 1121 appliance. Both have Active Directory configured. One system upgraded to 188.8.131.52.3 fine and the other failed ?
I can confirm same issue. In my case runtime process got stucked "not monitored" state.
Service and whole appliance restart didn't helped. Solved by returning to 184.108.40.206.2.
Hi Josef, the system that you tried to update from Patch 2 to Patch 3 (220.127.116.11.3) were you running the Large Deployment License ??
That is the only difference between our 3 deployments.
Wow, I didn't get away with that easy an upgrade !
Tried to upgrade to 5.7 from 18.104.22.168.2 upgrade progressed up until reboot and then hit the dread Grub - unable to mount volume .....
Had to back off and recover from 5.6 iso
Was able to get the system back and running, full replication but my cli is clobbered ! I am unable to SSH into the cli.
Login accepts userid and password and then I get this crap:
Could not chdir to home directory /home/ACSadmin: permission denied
unable to launch ADE-OS shell. Disk Full.
I'm thinking it is related to the recovery during setup when it requests the cli administration account(admin) but we change this to ACSadmin due to some issues we discovered during Nessus vulnerability testing that can render the admin account useless.
What a PAIN !