Description of problem: The agent service cannot create the PID file during startup due to inssuficient file permissions to write to /var/run. The agent is started under a non-root username (created during the installation process). How reproducible: Everytime Steps to Reproduce: 1. Install JON Agent RPM 2. Try to start the service Actual results: The agent gets started but cannot create the PID file and is reporting an error. Expected results: The agent gets started and the PID file gets created. Additional info: The solution is to create a subfolder under /var/run that has write permissions for the agent user. The problem applies issue applies to both EC2 and non-EC2 agent RPMs.
Created bug 817100 to track EC2 specific work.
This has now been resolved for the non-EC2 JON agent RPM. The solution only required changes to the RPM template spec file. The pid files will be stored in /var/run/jboss-on/agent. JON agent user has full access to the folder.
reopened. Agent starts correctly but the pid file is not being created under /var/run/jboss-on/agent. Please get screenshot attached.attached
Created attachment 599756 [details] ec2_pid
Created attachment 599814 [details] varRun ownership
Applied a couple of fixes to separate regular and ec2 pid folders. Please retest this in conjunction with regular RPMs (non-EC2).
Hi Stefan, PID still is not being created for ec2. for regular jon service is is being created correctly.
sorry. non-ec2 PID was being created correctly. marking bug as verified. Thank you Stefan.
Bulk closing of old issues in VERIFIED state.