ZABBIX Forums  
  #1  
Old 30-10-2017, 21:52
Starko Starko is offline
Member
Zabbix certified professionalZabbix certified specialist
 
Join Date: Aug 2012
Location: Germany
Posts: 51
Default Zabbix Server 3.2.9 - Action Auto Registration Message Flood

Hello,
since I updated to Zabbix Server 3.2.9 on 2017-10-27 09:42:34 exactly, two things happened:

1. First of all, I started receiving Auto Registration Messages via SMTP and via Telegram API Script once again. I was very happy about that, because that stopped working months ago, but I was to lazy to search for it. Sadly I can't remember on which version it stopped working.

2. Second, it never stopped working since then! I literally get flooded with Auto Registration Notifications! I have a screenshot of my Telegram History for you, as a brief example, but this is only two servers, as I get over 5-8000 messages per day.
https://i.imgur.com/blyxHCW.png
The Action log looks similar:
https://i.imgur.com/QTcDCZq.png

Any ideas, or should I open a bug report?
Reply With Quote
  #2  
Old 06-11-2017, 23:34
Starko Starko is offline
Member
Zabbix certified professionalZabbix certified specialist
 
Join Date: Aug 2012
Location: Germany
Posts: 51
Default

Someone has any idea whats going on? This is driving me nuts.
https://i.imgur.com/t80dw69.png
Reply With Quote
  #3  
Old 07-11-2017, 03:23
LenR LenR is offline
Senior Member
 
Join Date: Sep 2009
Posts: 357
Default

Autoregistration actions can send messages yet fail to register the host. If they do that, it keeps firing because the host doesn't exist.

Are the hosts being enrolled? Are they hitting the same server or proxy that is discovering them?
Reply With Quote
  #4  
Old 07-11-2017, 11:02
Starko Starko is offline
Member
Zabbix certified professionalZabbix certified specialist
 
Join Date: Aug 2012
Location: Germany
Posts: 51
Default

Quote:
Autoregistration actions can send messages yet fail to register the host.
That is an interesting point, but I don't see a correlation just yet.
Where can I see if it fails?

Quote:
If they do that, it keeps firing because the host doesn't exist.
That doesn't fit, because all of that hosts already exist.

Quote:
Are the hosts being enrolled?
No, it happens in a productive Environment where all Hosts/agents are already working for years. It started with the update to 3.2.9.

Quote:
Are they hitting the same server or proxy that is discovering them?
We are not working with discovery, but with the Agent Auto Registration via HostMetaData https://www.zabbix.com/documentation...o_registration
Reply With Quote
  #5  
Old 07-11-2017, 16:50
LenR LenR is offline
Senior Member
 
Join Date: Sep 2009
Posts: 357
Default

Sorry, my last question should have been autoreg, not discovery.

How many proxies do you have? Are these hosts monitored by server or proxy? Do these hosts have more than one entry in ServerActive?

Post your autoregistration action that is generating the messages.

We just had a message flood issue similar, but self induced. We have actions to add systems based on metadata, but different naming patterns hit different actions. One action that matched on just metadata sent the message. A new naming pattern was created and we weren't told, so no action that enrolled the host matched, but the notification action still matched.
Reply With Quote
  #6  
Old 07-11-2017, 17:29
Starko Starko is offline
Member
Zabbix certified professionalZabbix certified specialist
 
Join Date: Aug 2012
Location: Germany
Posts: 51
Default

No problem :-D

>How many proxies do you have?
~25

>Are these hosts monitored by server or proxy?
Proxy

>Do these hosts have more than one entry in ServerActive?
No

>Post your autoregistration action that is generating the messages.
https://i.imgur.com/htxZcBy.png

But I think I found the issue. But I stick to my opinion that Zabbix 3.2.8 or 3.2.9 changed something.
The Hostname in the "zabbix_agentd.win.conf" of the affected Hosts is different then the Hostname used in the Frontend. Example:
zabbix_agentd.win.conf -> SERVER01.domain.local
Frontend -> server01.domain.local

This leads to your suggestion "Autoregistration actions can send messages yet fail to register the host."
Reply With Quote
  #7  
Old 07-11-2017, 17:36
LenR LenR is offline
Senior Member
 
Join Date: Sep 2009
Posts: 357
Default

Yea, bet they are windows systems aren't they?

We tried to use hostname.item and our windows systems would change the case of their hostname when patched and rebooted.
Reply With Quote
  #8  
Old 04-12-2017, 12:30
Starko Starko is offline
Member
Zabbix certified professionalZabbix certified specialist
 
Join Date: Aug 2012
Location: Germany
Posts: 51
Default

Yes, the affected systems are Windows OS hosts.

We don't use the hostname item, we use a BAT script which generated the hostname. But the BAT generated the hostname UPPER case and in the Frontend we have the hosts lowercase.
That must be the problem.
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 06:29.