Hi,

Have you tried looking in http://<HOST>/pollerlog/view=devices/ - This will show each device stats and which is taking the longest

Have you also tried looking in http://<HOST>/device/device=<ID>/tab=perf/ - That will show what module is taking the longest on that device

Is might help you narrow down if its network related...

Regards

Simon - Hestor

On 28 Aug 2018, at 13:39, Adam Armstrong <adama@memetic.org> wrote:

This is very strange. I can't imagine what would cause all modules to gain 10 seconds.

Can you run one module with -dd to see why this is happening?

Thanks,
Adam.

Sent from BlueMail
On 28 Aug 2018, at 13:31, Silvio del Val Hinojal <silvio.delval@pandasecurity.com> wrote:

Hi Denis,




 

Thanks for your answer. I have seen that all devices and all modules in those devices are impacted.



For example, this is a Ubuntu 14 machine. Polling times raised from about 7 or 8 seconds to about 80 or 90 seconds…




 




 

The installation is CentOS 7.5, I’m trying to update operating system and see any difference.



These are my versions:




 

#####  Software versions  #####




 

o OS                   Linux 3.10.0-862.3.2.el7.x86_64 [amd64] (CentOS 7)



o Apache               2.4.6



o PHP                  7.2.8 (OPcache: ENABLED)



o Python               2.7.5



o MySQL                5.5.60-MariaDB (extension: mysqli 5.5.60-MariaDB)



o SNMP                 NET-SNMP 5.7.2



o RRDtool              1.6.0 (rrdcached remote: eseuskpmariadb01.linux.local)



o Fping                3.10 (IPv4 only)




 

Thank you




 

cid:image001.png@01D03B1C.E8E96F80






Silvio del Val



Systems Engineer - Panda Security



 


+34 944 343 728






silvio.delval@pandasecurity.com



pandasecurity.com




 

This e-mail contains confidential information owned by Panda Security. Any such copy, or use, or distribution or disclosure of its contents is strictly forbidden. Please notify us immediately at our phone number (+34 94 425 11 00) if you receive this e-mail and are not its consignee, and then delete this message from your system without copying it, distributing it, or disclosing its contents



 


P Before printing this message, please make sure it is really necessary




 

De: observium [mailto:observium-bounces@observium.org] En nombre de Klimek, Denis
Enviado el: martes, 28 de agosto de 2018 14:15
Para: 'Observium' <observium@observium.org>
Asunto: Re: [Observium] Polling times grew a lot upgrading to 18.8.9403 from 18.7.9337




 

Hi Silvio,



 


try to determine which devices and which poller module increased the polling time. You can view it https://yourdomain/device/device=<id>/tab=perf/ and pollerlog/view=devices/



 


Mit freundlichem Gruß



Stadtwerke Norderstedt



 


Denis Klimek



 


Professional Network Engineer



IP-Systemtechnik



 


Tel:        040 / 521 04 – 1049



Mobil:    0151 / 652 219 06



 


dklimek@stadtwerke-norderstedt.de



www.stadtwerke-norderstedt.de



 


Von: observium [mailto:observium-bounces@observium.org] Im Auftrag von Silvio del Val Hinojal
Gesendet: Dienstag, 28. August 2018 13:55
An: Observium
Betreff: [Observium] Polling times grew a lot upgrading to 18.8.9403 from 18.7.9337



 


Hello,



 


This morning I upgraded our Observium Pro machines from prior version 18.7.9337 to last 18.8.9403 and, since then, polling times growed by almost 3 or 4 times:



 




 


I upgraded using “svn update” in our polling machines and “discovery.php –u” to upgrade DB schema.



I even tried to activate “$config['snmp']['max-rep']    = TRUE;” with no luck.



 


What should I change to fix this times?



 


Regards,



Silvio



 


cid:image001.png@01D03B1C.E8E96F80


Silvio del Val


Systems Engineer - Panda Security


 

+34 944 343 728


silvio.delval@pandasecurity.com


pandasecurity.com


 


This e-mail contains confidential information owned by Panda Security. Any such copy, or use, or distribution or disclosure of its contents is strictly forbidden. Please notify us immediately at our phone number (+34 94 425 11 00) if you receive this e-mail and are not its consignee, and then delete this message from your system without copying it, distributing it, or disclosing its contents



 



P Before printing this message, please make sure it is really necessary



 




observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium