[ZBXNEXT-1405] The logentry "Message size *** exceeds the maximum size 67108864 bytes. Message ignored." Doesn't give source info, would like to know the IP for instance or any other info that lets me find it Created: 2012 Sep 06 Updated: 2013 Nov 04 Resolved: 2013 Aug 06 |
|
Status: | Closed |
Project: | ZABBIX FEATURE REQUESTS |
Component/s: | Server (S) |
Affects Version/s: | 2.1.0, 2.2.0 |
Fix Version/s: | 2.0.8, 2.1.2 |
Type: | New Feature Request | Priority: | Trivial |
Reporter: | Frater | Assignee: | Unassigned |
Resolution: | Fixed | Votes: | 3 |
Labels: | debugging, limits, trivial | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Linux |
Issue Links: |
|
Description |
All of a sudden (since a trunk upgrade), I'm getting warning messages "Message size *** exceeds the maximum size 67108864 bytes. Message ignored." I would like to know the culprit. |
Comments |
Comment by Oleksii Zagorskyi [ 2012 Sep 07 ] |
it is from forum thread I suppose http://www.zabbix.com/forum/showthread.php?t=28931 |
Comment by Frater [ 2013 Mar 01 ] |
Can you take a look at it... |
Comment by Stanislav Antic [ 2013 Jun 17 ] |
Is there a way to put id of item that's responsible? |
Comment by Andris Zeila [ 2013 Aug 06 ] |
Fixed in development branch svn://svn.zabbix.com/branches/dev/ZBXNEXT-1405 |
Comment by Alexander Vladishev [ 2013 Aug 06 ] |
Successfully tested! |
Comment by Andris Zeila [ 2013 Aug 06 ] |
Released in: |
Comment by richlv [ 2013 Aug 06 ] |
(1) whatsnew (with before/after examples) wiper added to whatsnew, please review: https://www.zabbix.com/documentation/2.0/manual/introduction/whatsnew208?&#improved_warnings_for_messages_exceeding_size_limits <richlv> thanks, i only slightly changed formatting, CLOSED |
Comment by Riaan Olivier [ 2013 Oct 17 ] |
After the change to show the IP I got this error, but no IP was shown: |
Comment by Andris Zeila [ 2013 Oct 17 ] |
The size is obviously wrong so this is not a simple problem of client sending larger data packet to server. The empty IP field indicates that there was a problem obtaining IP address from socket which together with |
Comment by Pavel [ 2013 Oct 29 ] |
How I could debug reason why connection has been dropped in the beginning of data exchange? |
Comment by Andris Zeila [ 2013 Nov 04 ] |
Now it should write real reason (TCP error description) why the connection was dropped instead of bogus message about message size. |