-
Pandora Agent not starting
Hi guys,
New to Pandora here.
Pandora Server installation went fine, but we are having issues with installing an agent on another server. It’s an Almalinux 8.
The installation itself (running the command given from the web console… curl -Ls https: //pfms.me/agent-deploy | bash, etc.) was completing without errors, but it cannot start the agent.
No logs in /var/log/pandora/, but in the /var/log/messages I see:
Dec 20 12:04:46 servername systemd[1]: Started Pandora FMS agent daemon.
Dec 20 12:04:46 servername pandora_agent[1374971]: /tmp/par-726f6f74/cache-81708fd539634d98ff546f81b38c5a20e0362194/pandora_agent: exec of /tmp/par-726f6f74/cache-81708fd539634d98ff546f81b38c5a20e0362194/pandora_agent (custom Perl interpreter) failed (errno=13)
Dec 20 12:04:46 servername systemd[1]: pandora_agent_daemon.service: Main process exited, code=exited, status=255/n/a
Dec 20 12:04:46 servername systemd[1]: pandora_agent_daemon.service: Failed with result ‘exit-code’.
Dec 20 12:04:46 servername systemd[1]: pandora_agent_daemon.service: Service RestartSec=100ms expired, scheduling restart.
Dec 20 12:04:46 servername systemd[1]: pandora_agent_daemon.service: Scheduled restart job, restart counter is at 3.
Dec 20 12:04:46 servername systemd[1]: Stopped Pandora FMS agent daemon.
The problem is most likely that we have secured the /tmp/ directory so you cannot run applications from it. Is it possible to configure the agent to use another working directory?
I tried changing the temporal line in the configuration file (it’s /tmp by default) – but that didn’t change anything.
Any hints? 🙂
-
This discussion was modified 1 week, 3 days ago by
Michael.
-
This discussion was modified 1 week, 3 days ago by
-
1 Reply
