[collectd] about memory graph

Israel Garcia igalvarez at gmail.com
Wed Oct 21 15:44:18 CEST 2009


Hi Florian,

Since we increase to 512Mb the memory of this server, all graphs are normal. :-)
Thanks tons

regards,
Israel.

here you have rrdtool info:
filename = "memory-free.rrd"
rrd_version = "0003"
step = 30
last_update = 1256132347
ds[value].type = "GAUGE"
ds[value].minimal_heartbeat = 60
ds[value].min = 0.0000000000e+00
ds[value].max = 2.8147497671e+14
ds[value].last_ds = "154951680.000000"
ds[value].value = 1.0846617600e+09
ds[value].unknown_sec = 0
rra[0].cf = "AVERAGE"
rra[0].rows = 1200
rra[0].cur_row = 837
rra[0].pdp_per_row = 1
rra[0].xff = 1.0000000000e-01
rra[0].cdp_prep[0].value = NaN
rra[0].cdp_prep[0].unknown_datapoints = 0
rra[1].cf = "MIN"
rra[1].rows = 1200
rra[1].cur_row = 1110
rra[1].pdp_per_row = 1
rra[1].xff = 1.0000000000e-01
rra[1].cdp_prep[0].value = NaN
rra[1].cdp_prep[0].unknown_datapoints = 0
rra[2].cf = "MAX"
rra[2].rows = 1200
rra[2].cur_row = 658
rra[2].pdp_per_row = 1
rra[2].xff = 1.0000000000e-01
rra[2].cdp_prep[0].value = NaN
rra[2].cdp_prep[0].unknown_datapoints = 0
rra[3].cf = "AVERAGE"
rra[3].rows = 1440
rra[3].cur_row = 1273
rra[3].pdp_per_row = 2
rra[3].xff = 1.0000000000e-01
rra[3].cdp_prep[0].value = 0.0000000000e+00
rra[3].cdp_prep[0].unknown_datapoints = 0
rra[4].cf = "MIN"
rra[4].rows = 1440
rra[4].cur_row = 359
rra[4].pdp_per_row = 2
rra[4].xff = 1.0000000000e-01
rra[4].cdp_prep[0].value = 1.5503148373e+08
rra[4].cdp_prep[0].unknown_datapoints = 0
rra[5].cf = "MAX"
rra[5].rows = 1440
rra[5].cur_row = 1311
rra[5].pdp_per_row = 2
rra[5].xff = 1.0000000000e-01
rra[5].cdp_prep[0].value = 1.5503148373e+08
rra[5].cdp_prep[0].unknown_datapoints = 0
rra[6].cf = "AVERAGE"
rra[6].rows = 1260
rra[6].cur_row = 574
rra[6].pdp_per_row = 16
rra[6].xff = 1.0000000000e-01
rra[6].cdp_prep[0].value = 9.3424011947e+08
rra[6].cdp_prep[0].unknown_datapoints = 0
rra[7].cf = "MIN"
rra[7].rows = 1260
rra[7].cur_row = 712
rra[7].pdp_per_row = 16
rra[7].xff = 1.0000000000e-01
rra[7].cdp_prep[0].value = 1.5503148373e+08
rra[7].cdp_prep[0].unknown_datapoints = 0
rra[8].cf = "MAX"
rra[8].rows = 1260
rra[8].cur_row = 1018
rra[8].pdp_per_row = 16
rra[8].xff = 1.0000000000e-01
rra[8].cdp_prep[0].value = 1.5634916693e+08
rra[8].cdp_prep[0].unknown_datapoints = 0
rra[9].cf = "AVERAGE"
rra[9].rows = 1207
rra[9].cur_row = 606
rra[9].pdp_per_row = 74
rra[9].xff = 1.0000000000e-01
rra[9].cdp_prep[0].value = 4.3730122069e+09
rra[9].cdp_prep[0].unknown_datapoints = 0
rra[10].cf = "MIN"
rra[10].rows = 1207
rra[10].cur_row = 970
rra[10].pdp_per_row = 74
rra[10].xff = 1.0000000000e-01
rra[10].cdp_prep[0].value = 1.5503148373e+08
rra[10].cdp_prep[0].unknown_datapoints = 0
rra[11].cf = "MAX"
rra[11].rows = 1207
rra[11].cur_row = 637
rra[11].pdp_per_row = 74
rra[11].xff = 1.0000000000e-01
rra[11].cdp_prep[0].value = 1.5767292587e+08
rra[11].cdp_prep[0].unknown_datapoints = 0
rra[12].cf = "AVERAGE"
rra[12].rows = 1201
rra[12].cur_row = 63
rra[12].pdp_per_row = 878
rra[12].xff = 1.0000000000e-01
rra[12].cdp_prep[0].value = 1.8465624610e+10
rra[12].cdp_prep[0].unknown_datapoints = 0
rra[13].cf = "MIN"
rra[13].rows = 1201
rra[13].cur_row = 1165
rra[13].pdp_per_row = 878
rra[13].xff = 1.0000000000e-01
rra[13].cdp_prep[0].value = 1.0789157547e+08
rra[13].cdp_prep[0].unknown_datapoints = 0
rra[14].cf = "MAX"
rra[14].rows = 1201
rra[14].cur_row = 1014
rra[14].pdp_per_row = 878
rra[14].xff = 1.0000000000e-01
rra[14].cdp_prep[0].value = 1.5953783467e+08
rra[14].cdp_prep[0].unknown_datapoints = 0


On 10/21/09, Florian Forster <octo at verplant.org> wrote:
> Hi Israel,
>
> On Mon, Oct 19, 2009 at 03:56:46PM -0500, Israel Garcia wrote:
>> That's right, it's only on the memory graph. As I told you this server
>> is always swapping to disk. So, there's nothing I can do?
>
> are you positive that's only the memory graphs? Can you send us any
> other graph of the same server and time window which doesn't have this
> problem, for example the swap graph?
>
> As Mariusz already pointed out this behavior is usually caused by an
> overloaded system or network, so it usually happends to *all* graphs of
> a specific host.
>
> Another possibility is that the RRD-files for the memory graph were
> created and the interval in which data is collected was increased
> afterwards. Can you post your collectd config file and the output of
>
>   rrdtool info /path/to/host/memory/memory-used.rrd
>
> Regards,
> —octo
> --
> Florian octo Forster
> Hacker in training
> GnuPG: 0x91523C3D
> http://verplant.org/
>


-- 
Regards;
Israel Garcia



More information about the collectd mailing list