| 1 |
>>> I've attached a PNG from Munin showing the TCP timeout errors on my |
| 2 |
>>> Gentoo server over the past month. The data is expressed in timeouts |
| 3 |
>>> per second and that rate is shown to be steadily increasing over the |
| 4 |
>>> past month. That seems strange to me. Munin doesn't show any other |
| 5 |
>>> data point increasing like this over the time period. Any ideas? |
| 6 |
>>> |
| 7 |
>>> - Grant |
| 8 |
>>> |
| 9 |
>> |
| 10 |
>> weird - does it reset on an interface restart or reboot? |
| 11 |
> |
| 12 |
> this would be my test #1 |
| 13 |
|
| 14 |
|
| 15 |
I rebooted and the rate of errors has dropped off to almost nothing. |
| 16 |
|
| 17 |
|
| 18 |
>> Can you verify its not an artefact within munin (how?) |
| 19 |
> |
| 20 |
> In theory, a misconfigured graph can do this. Munin can draw many |
| 21 |
> different types of graph, including cumulative values. Even for a data |
| 22 |
> type like this which is X events per unit time, if you tell munin to add |
| 23 |
> them all up, it will do so and graph it. |
| 24 |
> |
| 25 |
> Qucik test is to look at the graph config. |
| 26 |
|
| 27 |
|
| 28 |
This graph lives in the "network" section of the munin web interface. |
| 29 |
There is no matching section in /etc/munin/plugin-conf.d/munin-node so |
| 30 |
it should be be using the default config. |
| 31 |
|
| 32 |
Any ideas based on this new info? |
| 33 |
|
| 34 |
- Grant |
Archives