zabbix-agent

  • If someone submits the add-on code to our repo along with a pledge to maintain it over time we're happy to build and publish - otherwise I'd see it as an über-niche requirement; AFAIK you're the first person to ask for zabbix in the ~6 years I've been hanging around the LE/OE team.

    zabbix-agent might be an easier option. Probably not as efficient in terms of "small light agent" if it requires a nice big fat OS image to run the agent, but functionally it'll do the job.

  • I know it's quite old, but I managed zabbix agent on my libreelec to work. Without docker, just few megabytes. If anyone still interested, please let me know here.

  • It's pretty easy, but I don't know how to package it.

    1) Just downloaded the agent (I'm using x86_64, so need to use an old one for linux 3.0 but it works)

    https://cdn.zabbix.com/zabbix/binarie…4-static.tar.gz
    2) Unpacked it into /storage/.kodi/userdata/zabbix_agent

    3) Now it's time to zabbix config - in /storage/.kodi/userdata/zabbix_agent/conf/zabbix_agentd.conf need to set at least option Server; I have also ServerActive and hostname and...

    4) User. User must be set in above config file to nobody. We cannot add new user to LE, so it's the only way to lest zabbix_agent work. Well, not only - is it also possible to set AllowRoot as 1, but it's better to not use root.
    5) Last step is to add /storage/.kodi/userdata/zabbix_agent/sbin/zabbix_agentd --config /storage/.kodi/userdata/zabbix_agent/conf/zabbix_agentd.conf to autostart (/storage/.config/autostart.sh)

    That's all. Only restart needed.

  • Hi,
    Sorry for digging this up, but I think the information might be useful to more people.

    following your advice andrkac i stopped at the last point. I just can't start the service. I get Segmentation fault error. Thus, adding it to autostart won't do anything.

    The same happens when I run with ./zabbix_agentd -c /storage/.kodi/userdata/zabbix_agent/conf/zabbix_agentd.conf but it's logical.