ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

CARA Execution not starting properly after OS reboot

book

Article ID: 225591

calendar_today

Updated On:

Products

CA Release Automation - Release Operations Center (Nolio)

Issue/Introduction

After OS patch we tried restarting the CARA NES but its not starting and permissions keep changing to root across logs and catalina.PID
Services are starting with root.

 

Cause

Usually, the reason why those files get changed to root after a reboot is because the server was reboot without the Nolio Server is not configured with an appropriate RUN_AS_USER value (as described in the product docs below). When a server is reboot without these settings, Nolio is started by root because Nolio creates startup scripts in /etc/init.d and the appropriate rc.d directories (and services in /etc/systemd/system). During a reboot, root is the user that executes those startup scripts. 

Documentation outlining setup/install for non-root users:

 

 

 

Environment

Release : 6.x

Component : CA RELEASE AUTOMATION EXECUTION SERVER

 

Resolution

To resolve the problem you will need to:

  1. stop nolio services (cd /path/to/ReleaseAutomationServer; ./nolio_server.sh stop)
  2. chmod -R <your non-root user>:<your non-root users group> /path/to/ReleaseAutomationServer
  3. update the /path/to/ReleaseAutomationServer/nolio_server.sh script's RUN_AS_USER line to reflect: RUN_AS_USER=<your non-root user>
  4. clean files outlined here: CA Release Automation Clean up and Troubleshooting best practices
  5. start nolio services (cd /path/to/ReleaseAutomationServer; ./nolio_server.sh start)

 

Powered by Wolken Software