This is an error we would likely expect when attempting to install Release Automation as a non-root user, or a user that lacks write access to /etc/init.d, as well as /etc/rc*.d in Linux distributions utilizing the SysV init process, the most common being RHEL/CentOS 6.x. Thankfully this does not break our installation or Release Automation, all that we need to do is run a command as root(or a user with write access to the aforementioned paths).To correct this and install the init scripts correctly, as well as starting the Nolio/Release Automation services properly as the intended user please take the following steps:
1. Switch directories to the directory you installed Release Automation to, typically /opt/ReleaseAutomationServer which we will use as the example in this scenario.
2. Make sure you are root, then execute the following from the (cwd) install directory: ./nolio_server.sh install
3. You will receive a SUCCESS or FAILURE as to whether or not the init scripts were installed, assuming successful next we will need to update one, possibly two configuration files depending on the options selected during installation.
a. First, use a text editor and open $install_dir/nolio_server.sh -- yes, this is the script we just ran to install the init scripts.
b. At or around line 14 of this file, there should be a variable 'RUN_AS_USER=' not defined. Simply insert the user this component will be running as and then save the file.
c. Ensure that all files and directories within the CA Release Automation installation directory are owned by the user defined with RUN_AS_USER.
d. Now, you should be ready to start the server running as the intended/defined user by simply executing './nolio_server.sh start' from the install directory as 'root' user. (note: it is imperative to execute as root for user impersonation to properly work).
The procedures we just performed should ensure that the server starts on boot, as well as guarantee the server will run as the desired user when launched by root.