Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot find PID file #1

Open
louwers opened this issue May 22, 2020 · 5 comments
Open

Cannot find PID file #1

louwers opened this issue May 22, 2020 · 5 comments

Comments

@louwers
Copy link

louwers commented May 22, 2020

[ERROR   ] Command 'systemctl status [email protected]' failed with return code: 3
[ERROR   ] output: * [email protected] - Atlassian Bamboo Agent (agent-1)
   Loaded: loaded (/etc/systemd/system/[email protected]; enabled; vendor preset: disabled)
   Active: activating (auto-restart) (Result: protocol) since Fri 2020-05-22 17:11:50 CEST; 6s ago
  Process: 18622 ExecStart=/opt/atlassian/bamboo-agent/run-agent.sh %i start (code=exited, status=0/SUCCESS)

May 22 17:11:50 redacted.nl systemd[1]: Can't open PID file /opt/atlassian/bamboo-agent/home/agent-1/bin/bamboo-agent.pid (yet?) after start: No such file or directory
May 22 17:11:50 redacted.nl systemd[1]: Failed to start Atlassian Bamboo Agent (agent-1).
May 22 17:11:50 redacted.nl systemd[1]: Unit [email protected] entered failed state.
May 22 17:11:50 systemd[1]: [email protected] failed.
@corux
Copy link
Member

corux commented May 22, 2020

Hi @louwers,

please check the logs from journalctl -u atlassian-bamboo-agent@agent-1 and /opt/atlassian/bamboo-agent/home/agent-1/logs/atlassian-bamboo.log as well.
The output from systemctl does not contain enough info to debug the issue.

@louwers
Copy link
Author

louwers commented May 25, 2020

Thanks for your response @corux!

The logs from [email protected] don't seem very helpful either...

mei 25 11:27:15 redacted run-agent.sh[12470]: Starting Bamboo Agent...
mei 25 11:27:16 redacted systemd[1]: Can't open PID file /opt/atlassian/bamboo-agent/home/agent-1/bin/bamboo-agent.pid (yet?) after start: No such file or directory
mei 25 11:27:16 redacted systemd[1]: Failed to start Atlassian Bamboo Agent (agent-1).
mei 25 11:27:16 redacted systemd[1]: Unit [email protected] entered failed state.
mei 25 11:27:16 redacted systemd[1]: [email protected] failed.

No logs directory exists in /opt/atlassian/bamboo-agent/home/agent-1/.

@louwers
Copy link
Author

louwers commented May 25, 2020

I think this might be the issue:

# IMPORTANT - Make sure that the user has the required privileges to write
#  the PID file and wrapper.log files.  Failure to be able to write the log
#  file will cause the Wrapper to exit without any way to write out an error
#  message.

Edit: I had to chown -R bamboo:bamboo /opt/atlassian/bamboo-agent/home.
Can you make sure that Salt sets up the right permissions?

@corux
Copy link
Member

corux commented May 25, 2020

The permissions are now set on the Bamboo agent's home directory. See commit 65e1808. I've verified the change on a CentOS 7 machine.

Please test again with this fix and close this issue if it is working for you. Thanks!

@louwers
Copy link
Author

louwers commented Jun 3, 2020

Haven't had the time yet to test. I'll get back to you. 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants