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

do-agent does not start on CentOS v7 #257

Open
sdwru opened this issue Oct 20, 2021 · 6 comments
Open

do-agent does not start on CentOS v7 #257

sdwru opened this issue Oct 20, 2021 · 6 comments

Comments

@sdwru
Copy link

sdwru commented Oct 20, 2021

To Reproduce

Install the latest do-agent from yum repository. Run journalctl -f to watch systemd logging in real time. From another shell run systemctl restart do-agent

You will see the following error in the journalctl shell:

Failed at step EXEC spawning /opt/digitalocean/bin/do-agent --syslog: Permission denied

To Fix

chmod 755 /opt/digitalocean
chmod 755 /opt/digitalocean/bin

Run systemctl restart do-agent again and it should work now

@bsnyder788
Copy link
Contributor

Hi @sdwru, I just tried re-producing this with a CentOS v7 droplet and was unable too. Are you using the actual DO image for this distro or a custom image?

@sdwru
Copy link
Author

sdwru commented Oct 21, 2021

Hello,

This may have been due to a change to the RPM, which used to set the file and folder permissions to user:nobody, group:do-agent, and permissions 750. Or perhaps the droplet-agent did that? When the RPM was updated it appears it did not update the previous file and folder permissions on my server. After I completely uninstalled do-agent and droplet-agent and removed the /opt/digitalocean folder and tried re-installed both RPMs individually they both set the permissions correctly.

So it seems to be working now for new installs. However, I think it would still be advisable to have the RPM update folder/file permissions on updates, for anyone who may still be running older versions of the RPM and have not updated yet.

@stale
Copy link

stale bot commented Jan 8, 2022

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Jan 8, 2022
@bsnyder788
Copy link
Contributor

still valid

@stale stale bot removed the stale label Jan 10, 2022
@stale
Copy link

stale bot commented Apr 16, 2022

This issue has been automatically marked as stale because it has not had any recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale label Apr 16, 2022
@bsnyder788
Copy link
Contributor

still valid

@stale stale bot removed the stale label Apr 16, 2022
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