We’re installing the bigfix client on a handful of Linux machines (BESAgent-10.0.7.52) and while 99% of them are fine, I’m running into an issue with 2 machines where the service just fails to start and there is no reason as to why. We have all the folders in place:
/etc/opt/BESClient
/var/opt
and have the actionsite.afxm placed under /etc/opt/BESClient
When trying to start the service via systemd with systemctl start besclient we instantly get a failure message:
“Job for besclient.service failed because the control process exited with error code. See “systemctl status besclient.service” and “journalctl -xe” for details.”
when digging into both the status of service:
besclient.service - BESClient daemon
Loaded: loaded (/usr/lib/systemd/system/besclient.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2023-05-04 15:49:11 IDT; 1min 3s ago
Process: 212949 ExecStart=/usr/local/bin/besclient start (code=exited, status=1/FAILURE)
When digging into the journalctl we see this, pretty much the same:
May 04 15:49:11 systemd[1]: Starting BESClient daemon…
– Subject: Unit besclient.service has begun start-up
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit besclient.service has begun starting up.
May 04 15:49:11 systemd[1]: besclient.service: control process exited, code=exited status=1
May 04 15:49:11 systemd[1]: Failed to start BESClient daemon.
– Subject: Unit besclient.service has failed
– Defined-By: systemd
– Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
– Unit besclient.service has failed.
– The result is failed.
May 04 15:49:11 systemd[1]: Unit besclient.service entered failed state.
May 04 15:49:11 systemd[1]: besclient.service failed.
Has anyone seen this odd behavior before? Any input is greatly appreciated.
Thanks!