Hello.
After the upgrade (4.0.4 from 3.2.11) in the zabbix_server.log I found many of these rows:
Message from 127.0.0.1 is missing header. Message ignored.
In a few milliseconds 10-40 lines go out, then nothing for 2-8 minutes, then another bit of lines and so on.
Debug level 3, nothing in the agent log. With debug level 4 o 5, I do not find anything relevant but I do not know what to look for.
This behavior occurred in the first days after the migration:
1256 lines on 20190215 (partial), first day
3856 rows on 20190216
844 rows on 20190217
then 0 on all other days to date (20190221): 4088 lines (partial).
What can you depend on? The agent on the server is 4.0.4 installed simultaneously with the server, from sources.
I have seen that some speak of agents that are newer than the proxy or server, this is not the case, if anything the opposite: older agents (3.2.x). I have a couple of older proxies (3.2.3) even though I know that this configuration is not supported: I'm updating them anyway.
After the upgrade (4.0.4 from 3.2.11) in the zabbix_server.log I found many of these rows:
Message from 127.0.0.1 is missing header. Message ignored.
In a few milliseconds 10-40 lines go out, then nothing for 2-8 minutes, then another bit of lines and so on.
Debug level 3, nothing in the agent log. With debug level 4 o 5, I do not find anything relevant but I do not know what to look for.
This behavior occurred in the first days after the migration:
1256 lines on 20190215 (partial), first day
3856 rows on 20190216
844 rows on 20190217
then 0 on all other days to date (20190221): 4088 lines (partial).
What can you depend on? The agent on the server is 4.0.4 installed simultaneously with the server, from sources.
I have seen that some speak of agents that are newer than the proxy or server, this is not the case, if anything the opposite: older agents (3.2.x). I have a couple of older proxies (3.2.3) even though I know that this configuration is not supported: I'm updating them anyway.
Comment