Ad Widget

Collapse

Agent autoregistration with PSK via Proxy is not working

Collapse
This topic has been answered.
X
X
 
  • Time
  • Show
Clear All
new posts
  • zbx2020
    Junior Member
    • Oct 2022
    • 4

    #1

    Agent autoregistration with PSK via Proxy is not working

    Newbie here. I have been playing with Zabbix 6.2 on RHEL7 for 2 days. It worked OK so far, but got stuck when trying to set autoregistration + PSK + Proxy. Perhaps a bit ambitious compared to my Zabbix exposure, but hey, that's the job.

    I was hoping for some assistance with these two issues:
    1. Unencrypted autoregistration via the proxy works OK, but now I'd like to set autoreg up with a pre-shared key. I followed this page to set it up: https://www.zabbix.com/documentation...o_registration and had a look at this one https://www.zabbix.com/documentation...re_shared_keys as well. Created the PSK in Administration > General > Autoregistration, Put the TLS* parameters with the same psk id in the Agent's config and the PSK file in the /etc/zabbix/zabbix_agentd.psk ; Agent does not show up in Config > Hosts .
      What am I missing?
    2. Agent produces absolutely no logs. Set DebugLevel=5 in agent config (restarted agent), still, no logs what so ever. Neither the journal nor any files in /var/log/zabbix. Documentation says journald should be overflowing with "5 - extended debugging (produces even more information)" (see https://www.zabbix.com/documentation.../zabbix_agentd)
      Not gonna lie, this bugs the hell out of me. What should I do get some decent loggin going? I'd like to see what the agent is doing and whether or it can connect to the Proxy. And if not, why not?
    Thanks.
  • Answer selected by zbx2020 at 06-10-2022, 15:31.
    zbx2020
    Junior Member
    • Oct 2022
    • 4

    So, managed to find my own solution to the problem. A few rookie mistakes in the agent's config and a typo in the autoregister rule on the server were easy to fix, once I found out why the logs on the agent side didn't contain **any** logging info. Well, log messages went to `syslog` (to the main log `/var/log/messages`) instead of the journal. Obviously not a major malfunction but I was expecting stuff to show up in the journal. An annoying side effect of RHEL7.

    Comment

    • zbx2020
      Junior Member
      • Oct 2022
      • 4

      #2
      So, managed to find my own solution to the problem. A few rookie mistakes in the agent's config and a typo in the autoregister rule on the server were easy to fix, once I found out why the logs on the agent side didn't contain **any** logging info. Well, log messages went to `syslog` (to the main log `/var/log/messages`) instead of the journal. Obviously not a major malfunction but I was expecting stuff to show up in the journal. An annoying side effect of RHEL7.

      Comment

      Working...