Agents on AlmaLinux 9.5 unable to install agent

[AlexVanSteenhoven]

Description

I’ve attempted to install the agent on multiple servers running AlmaLinux. However, on each server I’ve tested, the agent service fails to start, and I receive an error indicating that the service could not be launched.

These servers are also running Plesk. While I don’t believe this should cause any issues, I can’t rule it out entirely.

OS / Architecture

AlmaLinux 9.5

Beszel version

0.10.2

Installation method

Binary

Configuration

No response

Hub Logs

No response

Agent Logs

Mar 25 13:48:05 server-domain.xyz systemd[1]: Started Beszel Agent Service.
Mar 25 13:48:05 server-domain.xyz systemd[381781]: beszel-agent.service: Failed to locate executable /opt/beszel-agent/beszel-agent: Permission denied
Mar 25 13:48:05 server-domain.xyz systemd[381781]: beszel-agent.service: Failed at step EXEC spawning /opt/beszel-agent/beszel-agent: Permission denied
Mar 25 13:48:05 server-domain.xyz systemd[1]: beszel-agent.service: Main process exited, code=exited, status=203/EXEC
Mar 25 13:48:05 server-domain.xyz systemd[1]: beszel-agent.service: Failed with result 'exit-code'.
Mar 25 13:48:10 server-domain.xyz systemd[1]: beszel-agent.service: Scheduled restart job, restart counter is at 1.
Mar 25 13:48:10 server-domain.xyz systemd[1]: Stopped Beszel Agent Service.
Mar 25 13:48:10 server-domain.xyz systemd[1]: Started Beszel Agent Service.
Mar 25 13:48:10 server-domain.xyz systemd[381853]: beszel-agent.service: Failed to locate executable /opt/beszel-agent/beszel-agent: Permission denied
Mar 25 13:48:10 server-domain.xyz systemd[381853]: beszel-agent.service: Failed at step EXEC spawning /opt/beszel-agent/beszel-agent: Permission denied
Mar 25 13:48:10 server-domain.xyz systemd[1]: beszel-agent.service: Main process exited, code=exited, status=203/EXEC
Mar 25 13:48:10 server-domain.xyz systemd[1]: beszel-agent.service: Failed with result 'exit-code'.
Mar 25 13:48:15 server-domain.xyz systemd[1]: beszel-agent.service: Scheduled restart job, restart counter is at 2.
Mar 25 13:48:15 server-domain.xyz systemd[1]: Stopped Beszel Agent Service.
Mar 25 13:48:15 server-domain.xyz systemd[1]: Started Beszel Agent Service.
Mar 25 13:48:15 server-domain.xyz systemd[381858]: beszel-agent.service: Failed to locate executable /opt/beszel-agent/beszel-agent: Permission denied

[henrygd]

Thanks for letting me know. Are you able to run the binary directly? This should show the help menu.

/opt/beszel-agent/beszel-agent -h

And as the beszel user:

sudo su -s /bin/sh beszel -c "/opt/beszel-agent/beszel-agent -h"

[henrygd]

It's probably an issue with the service config and/or SELinux settings.

Try modifying /etc/systemd/system/beszel-agent.service. Remove the block with the security/sandboxing options, and maybe the StateDirectory line. If that fixes it, you can try narrowing it down to the specific rule that causes the problem.

If that doesn't work, try changing the user from beszel to root.

Remember to reload / restart the service after changing settings:

sudo systemctl daemon-reload
sudo systemctl restart beszel-agent

[henrygd]

It could also be an issue with the binary being located in /opt.

You could try sudo ln -s /opt/beszel-agent/beszel-agent /usr/local/bin/beszel-agent then changing ExecStart in the unit file to point to /usr/local/bin/beszel-agent.

[AlexVanSteenhoven]

I've tried all possible options one at the time and even combined, but nothing seems to be working.
It still shows code=exited, status-203/EXEC

This is how the service looks like at the moment:

[AlexVanSteenhoven]

I've got it working running 2 commands:

chcon -t bin_t /opt/beszel-agent/beszel-agent
restorecon -v /opt/beszel-agent/beszel-agent

After that reloading the deamon and starting the agent:

systemctl daemon-reload
systemctl restart beszel-agent

Now it is running, but it still says that the server is down

[AlexVanSteenhoven]

Also fixed that the server is down. This was a firewall issue, opened the port and it worked!

[henrygd]

Awesome, thanks for the update! I made a note to mention this on the troubleshooting page next time I update the docs.