ACS 5.2 - Runtime process "not monitored"

[Matthew Knight]

(same both devices)

hostname/admin# show app ver acs

Cisco ACS VERSION INFORMATION
-----------------------------
Version : 5.2.0.26.8
Internal Build ID : B.3417
Patches :
5-2-0-26-1
5-2-0-26-2
5-2-0-26-3
5-2-0-26-4
5-2-0-26-5
5-2-0-26-6
5-2-0-26-7
5-2-0-26-8

hostname/admin# show app status acs

ACS role: PRIMARY

Process 'database'                  running
Process 'management'                running
Process 'runtime'                   not monitored
Process 'view-database'             running
Process 'view-jobmanager'           running
Process 'view-alertmanager'         running
Process 'view-collector'            running
Process 'view-logprocessor'         running

I am working on implementing ACS appliances.  All working ok, until I try to add an attribute to the Shell profile (priv-lvl = 15).  When I do this, the runtime process shutsdown (on both primary and secondary devices) and no further device authentications can be made.

Does anyone have any suggestions - I can reinitialise the database without issue at the moment, but I'd like to know what causes this and how to prevent from happening in the future - when the database will becoem much more critical.

Do I need to raise a TAC case?

Thanks all

[Sam Hertica]

Can you do this repeatedly? As in, every time you add an attribute to a shell profile, the runtime process shuts down and doesn't come back up?

Open a TAC case. Take a backup of your configuration to be safe. The runtime process shouldn't shut down after modifying shell profiles.

[antero]

Hi matthew

I had a simmilar problem, when doing a configuration of an invallid attribute for ASA, realised later that can´t be done inACS, and the ACS runtime stopped.

after several tryings to raise the process, without succes, cleared the configuration that i´ve made, restarted the services, and Runtime started.

hope this help

Antero vasconcelos

[camejia]

Hi All,

Issue seems to be the following known caveat:

http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?method=fetchBugDetails&bugId=CSCtl42972

The bug is listed as fixed in ACS 5.3.0.40.

http://www.cisco.com/en/US/partner/docs/net_mgmt/cisco_secure_access_control_system/5.3/release/notes/acs_53_rn.html#wp214169

NOTE: A valid Cisco CCOiD is needed in order to access the above links.

Hope this helps.

Regards.

[jai_chandra2001]

I experienced the same issue on 5.8.0.32 ACS cluster, no changes were made. Restarted the ACS services and the "runtime" status on now running.

[sholmes-telx]

Wouldn't you know I did the exact same thing with the same results.

I managed to fix it without having to blow out my configs.

I went into the web manager, removed the bad attribute dispite the runtime not running warning, saved it and restarted the acs from the cli (acs stop/acs start) and runtime finally started up.

-Stephen