Error starting ESET Management on AlmaLinux 9

[tschertel 0]

Hi guys,

 

just installed ESET Management on two Alma Linux machines using the client installation script created on my ESET Protect Dashboard.

But the agent doesn't start using the systemd unit. I get this error:

 

[user@server-01 ~]$ sudo systemctl status eraagent
× eraagent.service - ESET Management Agent
     Loaded: loaded (/etc/systemd/system/eraagent.service; enabled; preset: disabled)
     Active: failed (Result: exit-code) since Wed 2024-06-26 10:46:36 CEST; 2s ago
   Duration: 57ms
    Process: 12516 ExecStart=/opt/eset/RemoteAdministrator/Agent/ERAAgent --daemon --pidfile /var/run/eraagent.pid (code=exited, status=0/SUCCESS)
   Main PID: 12517 (code=exited, status=70)
        CPU: 59ms

Jun 26 10:46:36 server-01 systemd[1]: Starting ESET Management Agent...
Jun 26 10:46:36 server-01 systemd[1]: Started ESET Management Agent.
Jun 26 10:46:36 server-01 systemd[1]: eraagent.service: Main process exited, code=exited, status=70/SOFTWARE
Jun 26 10:46:36 server-01 systemd[1]: eraagent.service: Failed with result 'exit-code'.

How can I solve this?

 

Thank you!

[MartinK 383]

Could you please temporarily switch SELinux protection to "permissive" mode in order to verify issues is not triggered by SELinux? Enabling permissive mode can be done from root terminal using command:

setenforce 0

and re-enabled enforcing mode using command:

setenforce 1

or it will be re-enabled after reboot.

Once SELinux is in permissive mode, please just try to start eraagent service and check whether it starts and connects to the PROTECT.

In case service will work as expected, please run command:
 

/opt/eset/RemoteAdministrator/Agent/setup/selinux/eraagent.sh --update

and provide us it's output -> it will list SELinux permissions, that are actually missing in AGENT's policy. Also note that this command will offer you also to add those missing permissions into the AGENT's policy, but be aware that those will be lost upon next AGENT upgrade. But might help to temporarily resolve issues, until we verify what is the problem and whether it might have been fixed in the meantime and prepared for upcoming releases.