Ad Widget

Collapse

Why isn't my autoregistration working? - I've read everything I can find on it

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • belfert
    Junior Member
    • Jan 2018
    • 8

    #1

    Why isn't my autoregistration working? - I've read everything I can find on it

    I recently installed Zabbix 7.0.10 on Ubuntu 24.04. I cannot get autoregistration to work no matter how many things I try. I have read the Zabbix documentation on autoregistration, plus looked at lots of web search results. I have a successful Zabbix 4.0x system running on an old version of CentOS with autoregistration working just fine. The old Zabbix server is just too much of a hassle to upgrade to 7.0.10 so we are starting over. I verified that DNS works for short and long names on the server. GWhat am I missing?

    I am using Zabbix Agent 2 on Windows Server 2025 in active mode. Firewall is turned off on the Windows server. I have tried multiple Windows 2025 servers. I have verified that ports are open on both server and agent. I created autoregistration discovery rules that match what are on our old Zabbix server. The logs on both sides indicate the agent and server are talking, but nothing works because the agent isn't registered in the Zabbix server. If I manually create a host in Zabbix then the agent works fine.

    Here are relevant snippets from my zabbix_agent2.conf file:

    Server=x.x.x.x
    ServerActive=x.x.x.x
    HostnameItem=system.hostname
    HostMetadata=system.uname

    Thanks for any help.
  • kyus
    Senior Member
    • Feb 2024
    • 172

    #2
    Hey!

    Have you setup an autoregistration action?
    If so, how is the configuration of this action?

    Comment

    • belfert
      Junior Member
      • Jan 2018
      • 8

      #3
      I have several auto registration actions configured the same as on my 4.0x system. Email is configured.

      Click image for larger version

Name:	{081F34EB-C370-41B8-AFB5-309F4BF48C92}.png
Views:	171
Size:	16.9 KB
ID:	500555
      Click image for larger version

Name:	{A7AB38D2-14F5-4D72-83CD-B140131F9406}.png
Views:	161
Size:	21.2 KB
ID:	500556

      Comment

      • belfert
        Junior Member
        • Jan 2018
        • 8

        #4
        This is fixed. I switched to using HostMetadataItem instead of HostMetadata in the config file.

        Comment

        Working...