Consecutive actions running with impersonation fails intermittently
search cancel

Consecutive actions running with impersonation fails intermittently


Article ID: 115325


Updated On:


CA Release Automation - Release Operations Center (Nolio) CA Release Automation - DataManagement Server (Nolio)


Consecutive actions running with impersonation hangs and fails intermittently.

Sample simulation steps

i) Set the entry in sudoer file as no password, also do the configuration in agent as per the details mentioned in the CA Documentation.
ii) Then in action, under set credentials give the user name.
iii) Now execute the action, it will work. Which is as expected because in the sudoer we set as no Password, even if we give incorrect password, sudo wont consider this, which is correct
iv) Create a complex process with some more actions and most of them run with impersonation.
v) The actions start hanging and failing intermittently when the agent is restarted the process resume finex.

Some common error been observed during above scenario in agents logs are listed below.
  • <<user>> will now span a new process with the user id=<another  user> Sorry, user <another  user> is not allowed to execute '/usr/bin/sh -c /CARA/LISAReleaseAutomationAgent/ 41441 35026 <another  user>' as <another  user>on <server-name>.
  • SLF4J: Class path contains multiple SLF4J bindings.SLF4J: Found binding in [jar:file:/CARA/LISAReleaseAutomationAgent/lib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]SLF4J: Found binding in [jar:file:/CARA/LISAReleaseAutomationAgent/actionslib/slf4j-log4j12-1.7.5.jar!/org/slf4j/impl/StaticLoggerBinder.class]SLF4J: See for an explanation.SLF4J: Actual binding is of type [org.slf4j.impl.Log4jLoggerFactory]NolioSocketAppender is not ready yet!17:07:47,571 [main] WARN ( - cannot load remote process execution properties. use conf/ (Permission denied) at Method) at<init>(Unknown Source) at<init>(Unknown Source) at<init>(Unknown Source) at com.nolio.platform.shared.datamodel.execution.conf.ProcessesConfig.<clinit>(


CA Release Automation 6.4,6.5,6.6 and higher


In configuration the configuration "" ii.e. 300 seconds equivalent to 5 minutes, which implies that even though the action is finished the session waits for 5 minutes even being idle before closing the connection.


Suggested change in the configuration to set “ to 5” from earlier of 300 seconds in /conf/