Hi Michael (et al.),
I don't want to be annoying, but does anyone have any other ideas how to
further track this issue down? I could try to set up a minimised environment
that still shows the problem, but I'd rather wait with that effort until I know
that there isn't a bug somewhere in the code that's already known.
Cheers,
Peter.
> On 7 Dec 2015, at 11:19, Peter Eckel wrote:
>
> Hi Michael,
>
> thanks for your quick reply!
>
[...]
06/12/2015 15:35:08 :: wrote 441 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.num_services_ok.value
in 0.00660 seconds
06/12/2015 15:35:08 :: wrote 442 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.min_execution_time.value
in 0.00105 seconds
06/12/2015 15:35:08 :: wrote 442 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.num_hosts_flapping.value
in 0.00077 seconds
06/12/2015 15:35:08 :: wrote 442 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.num_hosts_up.value
in 0.00419 seconds
06/12/2015 15:35:08 :: wrote 443 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.num_services_unknown.value
in 0.00075 seconds
06/12/2015 15:35:08 :: wrote 443 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.avg_latency.value
in 0.00070 seconds
06/12/2015 15:35:08 :: wrote 443 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.max_execution_time.value
in 0.00063 seconds
06/12/2015 15:35:08 :: wrote 443 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.num_services_pending.value
in 0.00075 seconds
06/12/2015 15:35:08 :: wrote 443 datapoints for
icinga2.icinga2-satellite1_vm_hindenburgring_com.services.icinga.icinga.perfdata.num_services_warning.value
in 0.00066 seconds
[...]
>>>
>>> The extreme load drops to normal values immediately once I shut down either
>>> of the satellites - it doesn't have to be the one that's doing the extreme
>>> amount of perfdata writing.
>>
>> Does that pattern repeat?
>
> Hundreds of time per second, as long as the second satellite is in operation.
> And it's not only the 'icinga' check, (probably) all other checks are showing
> the same behaviour as well ('disk', for instance):
>
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._mnt_hgfs.value
>> 321149468672 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._vagrant.value
>> 321149468672 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._.value
>> 1170210816 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._boot.value
>> 30408704 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._mnt_hgfs.value
>> 321149468672 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._vagrant.value
>> 321149468672 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._.value
>> 1170210816 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._boot.value
>> 30408704 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._mnt_hgfs.value
>> 321149468672 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._vagrant.value
>> 321149468672 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._.value
>> 1170210816 1449421237'.
>> [2015-12-06 17:00:47 +] debug/GraphiteWriter: Add to metric
>> list:'icinga2.icinga2-satellite1_vm_hindenburgring_com.services.disk.disk.perfdata._boot.value
>> 30408704 1449421237'.
>> [2015-12-06 17:00:47 +] debug/Gr