Monitoring agent on arm


(Mark Verlinde) #21

Installed it on aarch64 and it works. :grinning:

To be accuracte it did need a manual stop and start of the zabbix-server.service.
This is most likely my fault by over doing it, just to many services are installed / running.

.. systemd[1]: Starting Zabbix Server...
.. systemd[1]: zabbix-server.service: Supervising process 3659 which is not our child. We'll most likely not notice when it exits.
.. systemd[1]: Started Zabbix Server.
.. systemd[1]: zabbix-server.service: main process exited, code=exited, status=1/FAILURE
.. kill[3663]: Usage:
.. kill[3663]: kill [options] <pid|name> [...]
.. kill[3663]: Options:
.. systemd[1]: zabbix-server.service: control process exited, code=exited status=1
.. kill[3663]: -a, --all              do not restrict the name-to-pid conversion to processes
.. kill[3663]: with the same uid as the present process
.. kill[3663]: -s, --signal <sig>     send specified signal
.. kill[3663]: -q, --queue <sig>      use sigqueue(2) rather than kill(2)
.. kill[3663]: -p, --pid              print pids without signaling them
.. kill[3663]: -l, --list [=<signal>] list signal names, or convert one to a name
.. kill[3663]: -L, --table            list signal names and numbers
.. kill[3663]: -h, --help     display this help and exit
.. kill[3663]: -V, --version  output version information and exit
.. kill[3663]: For more details see kill(1).
.. systemd[1]: Unit zabbix-server.service entered failed state.
.. systemd[1]: zabbix-server.service failed.
.. systemd[1]: zabbix-server.service holdoff time over, scheduling restart.

(Markus Neuberger) #22

I had the same log entries but services were restarted during the update so it worked without manual restart.