Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:image001.jpg@01D5617C.C2F25CC0]
Pozdrawiam
Jacek Dąbrowski
Looking at the process list on the system might give clues as to why the MySQL server has run out of connections.
Likely you'll find a lot of some sort of process holding a lot of connections open.
Adam.
From: observium observium-bounces@observium.org On Behalf Of Jacek Dabrowski via observium Sent: 02 September 2019 09:54 To: observium@observium.org Cc: Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
Pozdrawiam
Jacek Dąbrowski
Login as root user to your MySQLd and run this statement: show variables like "max_connections"; Result would look something like this: +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 100 | +-----------------+-------+ Increase that number to allow more concurrent connections, for example run this statement: set global max_connections = 200;
To make this change permanent, locate your my.cnf file (often in /etc or /etc/mysql) and add this under the [mysqld] section: max_connections = 200 After a restart of the mysqld service this setting will be the new default.
Or maybe try a tool like mysqltuner.pl to find the optimised advised configuration setting for the max_connection limit: https://github.com/major/MySQLTuner-perl
Jacek Dąbrowski via observium wrote at 2019-09-02 10:54:
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
Pozdrawiam
Jacek Dąbrowski
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
It did not help but I see that even RRDtool does not work properly.
[cid:image001.jpg@01D56277.EA372350]
Pozdrawiam
Jacek Dąbrowski
From: Michiel Klaver michiel@klaver.it Sent: Tuesday, September 3, 2019 9:28 AM To: Observium observium@observium.org Cc: Dąbrowski Jacek Jacek.Dabrowski@selgros.pl Subject: Re: [Observium] DB Error
Login as root user to your MySQLd and run this statement: show variables like "max_connections"; Result would look something like this: +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 100 | +-----------------+-------+ Increase that number to allow more concurrent connections, for example run this statement: set global max_connections = 200;
To make this change permanent, locate your my.cnf file (often in /etc or /etc/mysql) and add this under the [mysqld] section: max_connections = 200 After a restart of the mysqld service this setting will be the new default.
Or maybe try a tool like mysqltuner.pl to find the optimised advised configuration setting for the max_connection limit: https://github.com/major/MySQLTuner-perl
Jacek Dąbrowski via observium wrote at 2019-09-02 10:54: Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:15674956685d6e15f471539819603908@klaver.it]
Pozdrawiam
Jacek Dąbrowski
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
It also checked the performance of the machine itself, it has not changed (SSD DISK)
[root@observium2 ~]# sudo hdparm -Tt /dev/sda
/dev/sda: Timing cached reads: 12828 MB in 1.99 seconds = 6442.45 MB/sec Timing buffered disk reads: 3478 MB in 3.00 seconds = 1159.04 MB/sec [root@observium2 ~]# ^C [root@observium2 ~]# ^C [root@observium2 ~]#
Pozdrawiam
Jacek Dąbrowski Koordynator Administratorów IT
[cid:image003.png@01D5627A.D3830950]http://transgourmet.pl/ Transgourmet Polska Sp. z o.o. Zamenhofa 133, 61-131, Poznań, Polska tel.: +48 61 874 20 17 kom.: +48 604 069 933 E-mail: Jacek.Dabrowski@selgros.pl www.selgros.plhttp://selgros.pl www.selgros24.plhttp://selgros24.pl www.transgourmet.plhttp://transgourmet.pl
Transgourmet Polska Sp. z o.o. jest zarejestrowana w Sądzie Rejonowym Poznań-Nowe Miasto i Wilda w Poznaniu, Wydział VIII Gospodarczy Krajowego Rejestru Sądowego pod nr KRS: 0000045597. NIP: PL 781-10-11-998, REGON 630375413. Wysokość kapitału zakładowego: 310.000.000,00 złotych. Zapraszamy do korzystania z aplikacji HELPDESKhttp://helpdesk-it... From: observium observium-bounces@observium.org On Behalf Of Jacek Dąbrowski via observium Sent: Tuesday, September 3, 2019 4:52 PM To: michiel@klaver.it; observium@observium.org Cc: Dąbrowski Jacek Jacek.Dabrowski@selgros.pl Subject: Re: [Observium] DB Error
It did not help but I see that even RRDtool does not work properly.
[cid:image001.jpg@01D56277.EA372350]
Pozdrawiam
Jacek Dąbrowski From: Michiel Klaver <michiel@klaver.itmailto:michiel@klaver.it> Sent: Tuesday, September 3, 2019 9:28 AM To: Observium <observium@observium.orgmailto:observium@observium.org> Cc: Dąbrowski Jacek <Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl> Subject: Re: [Observium] DB Error
Login as root user to your MySQLd and run this statement: show variables like "max_connections"; Result would look something like this: +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 100 | +-----------------+-------+ Increase that number to allow more concurrent connections, for example run this statement: set global max_connections = 200;
To make this change permanent, locate your my.cnf file (often in /etc or /etc/mysql) and add this under the [mysqld] section: max_connections = 200 After a restart of the mysqld service this setting will be the new default.
Or maybe try a tool like mysqltuner.pl to find the optimised advised configuration setting for the max_connection limit: https://github.com/major/MySQLTuner-perl
Jacek Dąbrowski via observium wrote at 2019-09-02 10:54: Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:15674956685d6e15f471539819603908@klaver.it]
Pozdrawiam
Jacek Dąbrowski
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
There will be no stats collected if your MySQL server is not functioning properly - Observium would have no idea what hosts or metrics to poll.
On 9/3/2019 4:52 PM, Jacek Dąbrowski via observium wrote:
It did not help but I see that even RRDtool does not work properly.
Pozdrawiam
Jacek Dąbrowski
*From:*Michiel Klaver michiel@klaver.it *Sent:* Tuesday, September 3, 2019 9:28 AM *To:* Observium observium@observium.org *Cc:* Dąbrowski Jacek Jacek.Dabrowski@selgros.pl *Subject:* Re: [Observium] DB Error
Login as root user to your MySQLd and run this statement: show variables like "max_connections"; Result would look something like this: +-----------------+-------+ | Variable_name | Value | +-----------------+-------+ | max_connections | 100 | +-----------------+-------+ Increase that number to allow more concurrent connections, for example run this statement: set global max_connections = 200;
To make this change permanent, locate your my.cnf file (often in /etc or /etc/mysql) and add this under the [mysqld] section: max_connections = 200 After a restart of the mysqld service this setting will be the new default.
Or maybe try a tool like mysqltuner.pl to find the optimised advised configuration setting for the max_connection limit: https://github.com/major/MySQLTuner-perl
Jacek Dąbrowski via observium wrote at 2019-09-02 10:54:
Hello, Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ??? cid:15674956685d6e15f471539819603908@klaver.it Pozdrawiam Jacek Dąbrowski _______________________________________________ observium mailing list observium@observium.org <mailto: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
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.org Cc: Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:image001.jpg@01D5617C.C2F25CC0]
Pozdrawiam
Jacek Dąbrowski
I have these times in my log:
[2019/09/04 15:21:30 +0000] poller.php(16243): /opt/observium/poller.php: p121-rt - 1 devices polled in 387.1 secs [2019/09/04 15:21:30 +0000] poller.php(19578): /opt/observium/poller.php: p112-sw-35-poe - 1 devices polled in 281.3 secs [2019/09/04 15:21:30 +0000] poller.php(19623): /opt/observium/poller.php: p126-sw-33-poe - 1 devices polled in 280.4 secs [2019/09/04 15:21:30 +0000] poller.php(16212): /opt/observium/poller.php: p117-sw-core-pt - 1 devices polled in 387.9 secs [2019/09/04 15:21:33 +0000] poller.php(19689): /opt/observium/poller.php: p124-sw-36 - 1 devices polled in 281.1 secs [2019/09/04 15:21:36 +0000] poller.php(16209): /opt/observium/poller.php: p113-sw-core-pt - 1 devices polled in 394.0 secs [2019/09/04 15:21:40 +0000] poller.php(16203): /opt/observium/poller.php: p101-rt-d - 1 devices polled in 397.6 secs [2019/09/04 15:21:41 +0000] poller.php(16200): /opt/observium/poller.php: p101-sw-05-rack5 - 1 devices polled in 398.4 secs [2019/09/04 15:21:41 +0000] poller.php(19877): /opt/observium/poller.php: p127-sw-37-poe - 1 devices polled in 282.0 secs [2019/09/04 15:21:42 +0000] poller.php(16194): /opt/observium/poller.php: p170-rt-2 - 1 devices polled in 400.0 secs [2019/09/04 15:21:43 +0000] poller.php(16196): /opt/observium/poller.php: p102-rt-b - 1 devices polled in 400.7 secs [2019/09/04 15:21:44 +0000] poller.php(19953): /opt/observium/poller.php: p123-sw-36 - 1 devices polled in 281.5 secs [2019/09/04 15:21:46 +0000] poller.php(22490): /opt/observium/poller.php: p116-etykiety2 - 1 devices polled in 182.6 secs [2019/09/04 15:21:47 +0000] poller.php(20083): /opt/observium/poller.php: p114-sw-34-kasyn - 1 devices polled in 280.1 secs [2019/09/04 15:21:47 +0000] poller.php(22543): /opt/observium/poller.php: p127-etykiety1 - 1 devices polled in 182.8 secs [2019/09/04 15:21:47 +0000] poller.php(16191): /opt/observium/poller.php: p102-rt - 1 devices polled in 405.2 secs [2019/09/04 15:21:49 +0000] poller.php(16185): /opt/observium/poller.php: p170-rt-1 - 1 devices polled in 406.4 secs [2019/09/04 15:21:51 +0000] poller.php(16179): /opt/observium/poller.php: p121-sw-core - 1 devices polled in 408.5 secs [2019/09/04 15:21:51 +0000] poller.php(21905): /opt/observium/poller.php: p124-dc1 - 1 devices polled in 210.1 secs [2019/09/04 15:21:56 +0000] poller.php(22638): /opt/observium/poller.php: p121-netbotz - 1 devices polled in 190.4 secs [2019/09/04 15:21:57 +0000] poller.php(22679): /opt/observium/poller.php: p128-netbotz - 1 devices polled in 189.8 secs [2019/09/04 15:21:57 +0000] poller.php(22672): /opt/observium/poller.php: p120-netbotz - 1 devices polled in 190.1 secs [2019/09/04 15:21:57 +0000] poller.php(22633): /opt/observium/poller.php: p101-ups-symetra - 1 devices polled in 190.7 secs [2019/09/04 15:21:58 +0000] poller.php(16175): /opt/observium/poller.php: p101-sw-09-rack2 - 1 devices polled in 415.6 secs [2019/09/04 15:21:58 +0000] poller.php(22564): /opt/observium/poller.php: p114-sts - 1 devices polled in 193.7 secs [2019/09/04 15:21:59 +0000] poller.php(22611): /opt/observium/poller.php: p101-rac-vela - 1 devices polled in 193.2 secs [2019/09/04 15:21:59 +0000] poller.php(22733): /opt/observium/poller.php: p117-netbotz - 1 devices polled in 190.1 secs [2019/09/04 15:21:59 +0000] poller.php(22731): /opt/observium/poller.php: p113-netbotz - 1 devices polled in 190.6 secs [2019/09/04 15:22:02 +0000] poller.php(22576): /opt/observium/poller.php: p113-sts - 1 devices polled in 196.7 secs [2019/09/04 15:22:02 +0000] poller.php(22545): /opt/observium/poller.php: p111-sts - 1 devices polled in 197.8 secs [2019/09/04 15:22:03 +0000] poller.php(16172): /opt/observium/poller.php: p122-rt - 1 devices polled in 420.7 secs [2019/09/04 15:22:04 +0000] poller.php(22886): /opt/observium/poller.php: p114-netbotz - 1 devices polled in 189.7 secs [2019/09/04 15:22:05 +0000] poller.php(22572): /opt/observium/poller.php: p112-sts - 1 devices polled in 199.8 secs [2019/09/04 15:22:05 +0000] poller.php(22927): /opt/observium/poller.php: p123-netbotz - 1 devices polled in 189.8 secs [2019/09/04 15:22:06 +0000] poller.php(22327): /opt/observium/poller.php: p111-dc1 - 1 devices polled in 207.9 secs [2019/09/04 15:22:06 +0000] poller.php(16168): /opt/observium/poller.php: p102-sw-core - 1 devices polled in 423.9 secs [2019/09/04 15:22:09 +0000] poller.php(22417): /opt/observium/poller.php: pl-sdc01 - 1 devices polled in 207.6 secs [2019/09/04 15:22:09 +0000] poller.php(22499): /opt/observium/poller.php: p101-wifi-guest - 1 devices polled in 205.6 secs [2019/09/04 15:22:09 +0000] poller.php(22404): /opt/observium/poller.php: p111-ms1 - 1 devices polled in 208.3 secs [2019/09/04 15:22:10 +0000] poller.php(22443): /opt/observium/poller.php: pl-sapp08 - 1 devices polled in 208.2 secs
Pozdrawiam
Jacek Dąbrowski
From: observium observium-bounces@observium.org On Behalf Of Greg Peterson via observium Sent: Wednesday, September 4, 2019 5:20 PM To: Observium observium@observium.org Cc: Greg Peterson gpeterson@nescmn.net Subject: Re: [Observium] DB Error
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.orgmailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:image001.jpg@01D5617C.C2F25CC0]
Pozdrawiam
Jacek Dąbrowski
Why did you turn Observium off and back on again? What other things were you doing at the same time which required that?
There's not really anything about restarting a server which would cause what you're seeing, which is probably massive poller backlogs and huge numbers of poller processes.
Adam.
From: observium observium-bounces@observium.org On Behalf Of Jacek Dabrowski via observium Sent: 04 September 2019 16:24 To: observium@observium.org Cc: Jacek.Dabrowski@selgros.pl Subject: Re: [Observium] DB Error
I have these times in my log:
[2019/09/04 15:21:30 +0000] poller.php(16243): /opt/observium/poller.php: p121-rt - 1 devices polled in 387.1 secs
[2019/09/04 15:21:30 +0000] poller.php(19578): /opt/observium/poller.php: p112-sw-35-poe - 1 devices polled in 281.3 secs
[2019/09/04 15:21:30 +0000] poller.php(19623): /opt/observium/poller.php: p126-sw-33-poe - 1 devices polled in 280.4 secs
[2019/09/04 15:21:30 +0000] poller.php(16212): /opt/observium/poller.php: p117-sw-core-pt - 1 devices polled in 387.9 secs
[2019/09/04 15:21:33 +0000] poller.php(19689): /opt/observium/poller.php: p124-sw-36 - 1 devices polled in 281.1 secs
[2019/09/04 15:21:36 +0000] poller.php(16209): /opt/observium/poller.php: p113-sw-core-pt - 1 devices polled in 394.0 secs
[2019/09/04 15:21:40 +0000] poller.php(16203): /opt/observium/poller.php: p101-rt-d - 1 devices polled in 397.6 secs
[2019/09/04 15:21:41 +0000] poller.php(16200): /opt/observium/poller.php: p101-sw-05-rack5 - 1 devices polled in 398.4 secs
[2019/09/04 15:21:41 +0000] poller.php(19877): /opt/observium/poller.php: p127-sw-37-poe - 1 devices polled in 282.0 secs
[2019/09/04 15:21:42 +0000] poller.php(16194): /opt/observium/poller.php: p170-rt-2 - 1 devices polled in 400.0 secs
[2019/09/04 15:21:43 +0000] poller.php(16196): /opt/observium/poller.php: p102-rt-b - 1 devices polled in 400.7 secs
[2019/09/04 15:21:44 +0000] poller.php(19953): /opt/observium/poller.php: p123-sw-36 - 1 devices polled in 281.5 secs
[2019/09/04 15:21:46 +0000] poller.php(22490): /opt/observium/poller.php: p116-etykiety2 - 1 devices polled in 182.6 secs
[2019/09/04 15:21:47 +0000] poller.php(20083): /opt/observium/poller.php: p114-sw-34-kasyn - 1 devices polled in 280.1 secs
[2019/09/04 15:21:47 +0000] poller.php(22543): /opt/observium/poller.php: p127-etykiety1 - 1 devices polled in 182.8 secs
[2019/09/04 15:21:47 +0000] poller.php(16191): /opt/observium/poller.php: p102-rt - 1 devices polled in 405.2 secs
[2019/09/04 15:21:49 +0000] poller.php(16185): /opt/observium/poller.php: p170-rt-1 - 1 devices polled in 406.4 secs
[2019/09/04 15:21:51 +0000] poller.php(16179): /opt/observium/poller.php: p121-sw-core - 1 devices polled in 408.5 secs
[2019/09/04 15:21:51 +0000] poller.php(21905): /opt/observium/poller.php: p124-dc1 - 1 devices polled in 210.1 secs
[2019/09/04 15:21:56 +0000] poller.php(22638): /opt/observium/poller.php: p121-netbotz - 1 devices polled in 190.4 secs
[2019/09/04 15:21:57 +0000] poller.php(22679): /opt/observium/poller.php: p128-netbotz - 1 devices polled in 189.8 secs
[2019/09/04 15:21:57 +0000] poller.php(22672): /opt/observium/poller.php: p120-netbotz - 1 devices polled in 190.1 secs
[2019/09/04 15:21:57 +0000] poller.php(22633): /opt/observium/poller.php: p101-ups-symetra - 1 devices polled in 190.7 secs
[2019/09/04 15:21:58 +0000] poller.php(16175): /opt/observium/poller.php: p101-sw-09-rack2 - 1 devices polled in 415.6 secs
[2019/09/04 15:21:58 +0000] poller.php(22564): /opt/observium/poller.php: p114-sts - 1 devices polled in 193.7 secs
[2019/09/04 15:21:59 +0000] poller.php(22611): /opt/observium/poller.php: p101-rac-vela - 1 devices polled in 193.2 secs
[2019/09/04 15:21:59 +0000] poller.php(22733): /opt/observium/poller.php: p117-netbotz - 1 devices polled in 190.1 secs
[2019/09/04 15:21:59 +0000] poller.php(22731): /opt/observium/poller.php: p113-netbotz - 1 devices polled in 190.6 secs
[2019/09/04 15:22:02 +0000] poller.php(22576): /opt/observium/poller.php: p113-sts - 1 devices polled in 196.7 secs
[2019/09/04 15:22:02 +0000] poller.php(22545): /opt/observium/poller.php: p111-sts - 1 devices polled in 197.8 secs
[2019/09/04 15:22:03 +0000] poller.php(16172): /opt/observium/poller.php: p122-rt - 1 devices polled in 420.7 secs
[2019/09/04 15:22:04 +0000] poller.php(22886): /opt/observium/poller.php: p114-netbotz - 1 devices polled in 189.7 secs
[2019/09/04 15:22:05 +0000] poller.php(22572): /opt/observium/poller.php: p112-sts - 1 devices polled in 199.8 secs
[2019/09/04 15:22:05 +0000] poller.php(22927): /opt/observium/poller.php: p123-netbotz - 1 devices polled in 189.8 secs
[2019/09/04 15:22:06 +0000] poller.php(22327): /opt/observium/poller.php: p111-dc1 - 1 devices polled in 207.9 secs
[2019/09/04 15:22:06 +0000] poller.php(16168): /opt/observium/poller.php: p102-sw-core - 1 devices polled in 423.9 secs
[2019/09/04 15:22:09 +0000] poller.php(22417): /opt/observium/poller.php: pl-sdc01 - 1 devices polled in 207.6 secs
[2019/09/04 15:22:09 +0000] poller.php(22499): /opt/observium/poller.php: p101-wifi-guest - 1 devices polled in 205.6 secs
[2019/09/04 15:22:09 +0000] poller.php(22404): /opt/observium/poller.php: p111-ms1 - 1 devices polled in 208.3 secs
[2019/09/04 15:22:10 +0000] poller.php(22443): /opt/observium/poller.php: pl-sapp08 - 1 devices polled in 208.2 secs
Pozdrawiam
Jacek Dąbrowski
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Greg Peterson via observium Sent: Wednesday, September 4, 2019 5:20 PM To: Observium <observium@observium.org mailto:observium@observium.org > Cc: Greg Peterson <gpeterson@nescmn.net mailto:gpeterson@nescmn.net > Subject: Re: [Observium] DB Error
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.org mailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.pl mailto:Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
Pozdrawiam
Jacek Dąbrowski
We had a power system upgrade in the server room to two UPS , I did not change anything and earlier the server has not been restarted for a long time, I am looking for other possible reasons but ping to devices and server performance is the same.
Pozdrawiam
Jacek Dąbrowski
From: observium observium-bounces@observium.org On Behalf Of Adam Armstrong via observium Sent: Wednesday, September 4, 2019 5:49 PM To: 'Observium' observium@observium.org Cc: adama@memetic.org Subject: Re: [Observium] DB Error
Why did you turn Observium off and back on again? What other things were you doing at the same time which required that?
There's not really anything about restarting a server which would cause what you're seeing, which is probably massive poller backlogs and huge numbers of poller processes.
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Jacek Dabrowski via observium Sent: 04 September 2019 16:24 To: observium@observium.orgmailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl Subject: Re: [Observium] DB Error
I have these times in my log:
[2019/09/04 15:21:30 +0000] poller.php(16243): /opt/observium/poller.php: p121-rt - 1 devices polled in 387.1 secs [2019/09/04 15:21:30 +0000] poller.php(19578): /opt/observium/poller.php: p112-sw-35-poe - 1 devices polled in 281.3 secs [2019/09/04 15:21:30 +0000] poller.php(19623): /opt/observium/poller.php: p126-sw-33-poe - 1 devices polled in 280.4 secs [2019/09/04 15:21:30 +0000] poller.php(16212): /opt/observium/poller.php: p117-sw-core-pt - 1 devices polled in 387.9 secs [2019/09/04 15:21:33 +0000] poller.php(19689): /opt/observium/poller.php: p124-sw-36 - 1 devices polled in 281.1 secs [2019/09/04 15:21:36 +0000] poller.php(16209): /opt/observium/poller.php: p113-sw-core-pt - 1 devices polled in 394.0 secs [2019/09/04 15:21:40 +0000] poller.php(16203): /opt/observium/poller.php: p101-rt-d - 1 devices polled in 397.6 secs [2019/09/04 15:21:41 +0000] poller.php(16200): /opt/observium/poller.php: p101-sw-05-rack5 - 1 devices polled in 398.4 secs [2019/09/04 15:21:41 +0000] poller.php(19877): /opt/observium/poller.php: p127-sw-37-poe - 1 devices polled in 282.0 secs [2019/09/04 15:21:42 +0000] poller.php(16194): /opt/observium/poller.php: p170-rt-2 - 1 devices polled in 400.0 secs [2019/09/04 15:21:43 +0000] poller.php(16196): /opt/observium/poller.php: p102-rt-b - 1 devices polled in 400.7 secs [2019/09/04 15:21:44 +0000] poller.php(19953): /opt/observium/poller.php: p123-sw-36 - 1 devices polled in 281.5 secs [2019/09/04 15:21:46 +0000] poller.php(22490): /opt/observium/poller.php: p116-etykiety2 - 1 devices polled in 182.6 secs [2019/09/04 15:21:47 +0000] poller.php(20083): /opt/observium/poller.php: p114-sw-34-kasyn - 1 devices polled in 280.1 secs [2019/09/04 15:21:47 +0000] poller.php(22543): /opt/observium/poller.php: p127-etykiety1 - 1 devices polled in 182.8 secs [2019/09/04 15:21:47 +0000] poller.php(16191): /opt/observium/poller.php: p102-rt - 1 devices polled in 405.2 secs [2019/09/04 15:21:49 +0000] poller.php(16185): /opt/observium/poller.php: p170-rt-1 - 1 devices polled in 406.4 secs [2019/09/04 15:21:51 +0000] poller.php(16179): /opt/observium/poller.php: p121-sw-core - 1 devices polled in 408.5 secs [2019/09/04 15:21:51 +0000] poller.php(21905): /opt/observium/poller.php: p124-dc1 - 1 devices polled in 210.1 secs [2019/09/04 15:21:56 +0000] poller.php(22638): /opt/observium/poller.php: p121-netbotz - 1 devices polled in 190.4 secs [2019/09/04 15:21:57 +0000] poller.php(22679): /opt/observium/poller.php: p128-netbotz - 1 devices polled in 189.8 secs [2019/09/04 15:21:57 +0000] poller.php(22672): /opt/observium/poller.php: p120-netbotz - 1 devices polled in 190.1 secs [2019/09/04 15:21:57 +0000] poller.php(22633): /opt/observium/poller.php: p101-ups-symetra - 1 devices polled in 190.7 secs [2019/09/04 15:21:58 +0000] poller.php(16175): /opt/observium/poller.php: p101-sw-09-rack2 - 1 devices polled in 415.6 secs [2019/09/04 15:21:58 +0000] poller.php(22564): /opt/observium/poller.php: p114-sts - 1 devices polled in 193.7 secs [2019/09/04 15:21:59 +0000] poller.php(22611): /opt/observium/poller.php: p101-rac-vela - 1 devices polled in 193.2 secs [2019/09/04 15:21:59 +0000] poller.php(22733): /opt/observium/poller.php: p117-netbotz - 1 devices polled in 190.1 secs [2019/09/04 15:21:59 +0000] poller.php(22731): /opt/observium/poller.php: p113-netbotz - 1 devices polled in 190.6 secs [2019/09/04 15:22:02 +0000] poller.php(22576): /opt/observium/poller.php: p113-sts - 1 devices polled in 196.7 secs [2019/09/04 15:22:02 +0000] poller.php(22545): /opt/observium/poller.php: p111-sts - 1 devices polled in 197.8 secs [2019/09/04 15:22:03 +0000] poller.php(16172): /opt/observium/poller.php: p122-rt - 1 devices polled in 420.7 secs [2019/09/04 15:22:04 +0000] poller.php(22886): /opt/observium/poller.php: p114-netbotz - 1 devices polled in 189.7 secs [2019/09/04 15:22:05 +0000] poller.php(22572): /opt/observium/poller.php: p112-sts - 1 devices polled in 199.8 secs [2019/09/04 15:22:05 +0000] poller.php(22927): /opt/observium/poller.php: p123-netbotz - 1 devices polled in 189.8 secs [2019/09/04 15:22:06 +0000] poller.php(22327): /opt/observium/poller.php: p111-dc1 - 1 devices polled in 207.9 secs [2019/09/04 15:22:06 +0000] poller.php(16168): /opt/observium/poller.php: p102-sw-core - 1 devices polled in 423.9 secs [2019/09/04 15:22:09 +0000] poller.php(22417): /opt/observium/poller.php: pl-sdc01 - 1 devices polled in 207.6 secs [2019/09/04 15:22:09 +0000] poller.php(22499): /opt/observium/poller.php: p101-wifi-guest - 1 devices polled in 205.6 secs [2019/09/04 15:22:09 +0000] poller.php(22404): /opt/observium/poller.php: p111-ms1 - 1 devices polled in 208.3 secs [2019/09/04 15:22:10 +0000] poller.php(22443): /opt/observium/poller.php: pl-sapp08 - 1 devices polled in 208.2 secs
Pozdrawiam
Jacek Dąbrowski From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Greg Peterson via observium Sent: Wednesday, September 4, 2019 5:20 PM To: Observium <observium@observium.orgmailto:observium@observium.org> Cc: Greg Peterson <gpeterson@nescmn.netmailto:gpeterson@nescmn.net> Subject: Re: [Observium] DB Error
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.orgmailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:image001.jpg@01D5617C.C2F25CC0]
Pozdrawiam
Jacek Dąbrowski
Do you monitor the Observium machine with Observium? Added localhost as a device? /Markus
Den ons 4 sep. 2019 17:55Jacek Dąbrowski via observium < observium@observium.org> skrev:
We had a power system upgrade in the server room to two UPS , I did not change anything and earlier the server has not been restarted for a long time, I am looking for other possible reasons but ping to devices and server performance is the same.
Pozdrawiam
Jacek Dąbrowski
*From:* observium observium-bounces@observium.org *On Behalf Of *Adam Armstrong via observium *Sent:* Wednesday, September 4, 2019 5:49 PM *To:* 'Observium' observium@observium.org *Cc:* adama@memetic.org *Subject:* Re: [Observium] DB Error
Why did you turn Observium off and back on again? What other things were you doing at the same time which required that?
There’s not really anything about restarting a server which would cause what you’re seeing, which is probably massive poller backlogs and huge numbers of poller processes.
Adam.
*From:* observium observium-bounces@observium.org *On Behalf Of *Jacek Dabrowski via observium *Sent:* 04 September 2019 16:24 *To:* observium@observium.org *Cc:* Jacek.Dabrowski@selgros.pl *Subject:* Re: [Observium] DB Error
I have these times in my log:
[2019/09/04 15:21:30 +0000] poller.php(16243): /opt/observium/poller.php: p121-rt - 1 devices polled in 387.1 secs
[2019/09/04 15:21:30 +0000] poller.php(19578): /opt/observium/poller.php: p112-sw-35-poe - 1 devices polled in 281.3 secs
[2019/09/04 15:21:30 +0000] poller.php(19623): /opt/observium/poller.php: p126-sw-33-poe - 1 devices polled in 280.4 secs
[2019/09/04 15:21:30 +0000] poller.php(16212): /opt/observium/poller.php: p117-sw-core-pt - 1 devices polled in 387.9 secs
[2019/09/04 15:21:33 +0000] poller.php(19689): /opt/observium/poller.php: p124-sw-36 - 1 devices polled in 281.1 secs
[2019/09/04 15:21:36 +0000] poller.php(16209): /opt/observium/poller.php: p113-sw-core-pt - 1 devices polled in 394.0 secs
[2019/09/04 15:21:40 +0000] poller.php(16203): /opt/observium/poller.php: p101-rt-d - 1 devices polled in 397.6 secs
[2019/09/04 15:21:41 +0000] poller.php(16200): /opt/observium/poller.php: p101-sw-05-rack5 - 1 devices polled in 398.4 secs
[2019/09/04 15:21:41 +0000] poller.php(19877): /opt/observium/poller.php: p127-sw-37-poe - 1 devices polled in 282.0 secs
[2019/09/04 15:21:42 +0000] poller.php(16194): /opt/observium/poller.php: p170-rt-2 - 1 devices polled in 400.0 secs
[2019/09/04 15:21:43 +0000] poller.php(16196): /opt/observium/poller.php: p102-rt-b - 1 devices polled in 400.7 secs
[2019/09/04 15:21:44 +0000] poller.php(19953): /opt/observium/poller.php: p123-sw-36 - 1 devices polled in 281.5 secs
[2019/09/04 15:21:46 +0000] poller.php(22490): /opt/observium/poller.php: p116-etykiety2 - 1 devices polled in 182.6 secs
[2019/09/04 15:21:47 +0000] poller.php(20083): /opt/observium/poller.php: p114-sw-34-kasyn - 1 devices polled in 280.1 secs
[2019/09/04 15:21:47 +0000] poller.php(22543): /opt/observium/poller.php: p127-etykiety1 - 1 devices polled in 182.8 secs
[2019/09/04 15:21:47 +0000] poller.php(16191): /opt/observium/poller.php: p102-rt - 1 devices polled in 405.2 secs
[2019/09/04 15:21:49 +0000] poller.php(16185): /opt/observium/poller.php: p170-rt-1 - 1 devices polled in 406.4 secs
[2019/09/04 15:21:51 +0000] poller.php(16179): /opt/observium/poller.php: p121-sw-core - 1 devices polled in 408.5 secs
[2019/09/04 15:21:51 +0000] poller.php(21905): /opt/observium/poller.php: p124-dc1 - 1 devices polled in 210.1 secs
[2019/09/04 15:21:56 +0000] poller.php(22638): /opt/observium/poller.php: p121-netbotz - 1 devices polled in 190.4 secs
[2019/09/04 15:21:57 +0000] poller.php(22679): /opt/observium/poller.php: p128-netbotz - 1 devices polled in 189.8 secs
[2019/09/04 15:21:57 +0000] poller.php(22672): /opt/observium/poller.php: p120-netbotz - 1 devices polled in 190.1 secs
[2019/09/04 15:21:57 +0000] poller.php(22633): /opt/observium/poller.php: p101-ups-symetra - 1 devices polled in 190.7 secs
[2019/09/04 15:21:58 +0000] poller.php(16175): /opt/observium/poller.php: p101-sw-09-rack2 - 1 devices polled in 415.6 secs
[2019/09/04 15:21:58 +0000] poller.php(22564): /opt/observium/poller.php: p114-sts - 1 devices polled in 193.7 secs
[2019/09/04 15:21:59 +0000] poller.php(22611): /opt/observium/poller.php: p101-rac-vela - 1 devices polled in 193.2 secs
[2019/09/04 15:21:59 +0000] poller.php(22733): /opt/observium/poller.php: p117-netbotz - 1 devices polled in 190.1 secs
[2019/09/04 15:21:59 +0000] poller.php(22731): /opt/observium/poller.php: p113-netbotz - 1 devices polled in 190.6 secs
[2019/09/04 15:22:02 +0000] poller.php(22576): /opt/observium/poller.php: p113-sts - 1 devices polled in 196.7 secs
[2019/09/04 15:22:02 +0000] poller.php(22545): /opt/observium/poller.php: p111-sts - 1 devices polled in 197.8 secs
[2019/09/04 15:22:03 +0000] poller.php(16172): /opt/observium/poller.php: p122-rt - 1 devices polled in 420.7 secs
[2019/09/04 15:22:04 +0000] poller.php(22886): /opt/observium/poller.php: p114-netbotz - 1 devices polled in 189.7 secs
[2019/09/04 15:22:05 +0000] poller.php(22572): /opt/observium/poller.php: p112-sts - 1 devices polled in 199.8 secs
[2019/09/04 15:22:05 +0000] poller.php(22927): /opt/observium/poller.php: p123-netbotz - 1 devices polled in 189.8 secs
[2019/09/04 15:22:06 +0000] poller.php(22327): /opt/observium/poller.php: p111-dc1 - 1 devices polled in 207.9 secs
[2019/09/04 15:22:06 +0000] poller.php(16168): /opt/observium/poller.php: p102-sw-core - 1 devices polled in 423.9 secs
[2019/09/04 15:22:09 +0000] poller.php(22417): /opt/observium/poller.php: pl-sdc01 - 1 devices polled in 207.6 secs
[2019/09/04 15:22:09 +0000] poller.php(22499): /opt/observium/poller.php: p101-wifi-guest - 1 devices polled in 205.6 secs
[2019/09/04 15:22:09 +0000] poller.php(22404): /opt/observium/poller.php: p111-ms1 - 1 devices polled in 208.3 secs
[2019/09/04 15:22:10 +0000] poller.php(22443): /opt/observium/poller.php: pl-sapp08 - 1 devices polled in 208.2 secs
Pozdrawiam
Jacek Dąbrowski
*From:* observium observium-bounces@observium.org *On Behalf Of *Greg Peterson via observium *Sent:* Wednesday, September 4, 2019 5:20 PM *To:* Observium observium@observium.org *Cc:* Greg Peterson gpeterson@nescmn.net *Subject:* Re: [Observium] DB Error
I was getting this message when I had devices that didn’t finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
*From:* observium [mailto:observium-bounces@observium.org observium-bounces@observium.org] *On Behalf Of *Jacek Dabrowski via observium *Sent:* Monday, September 02, 2019 3:54 AM *To:* observium@observium.org *Cc:* Jacek.Dabrowski@selgros.pl *Subject:* [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[image: cid:image001.jpg@01D5617C.C2F25CC0]
Pozdrawiam
Jacek Dąbrowski _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Discovery time is very big, top does not show that the server is heavily loaded
[cid:image001.jpg@01D56349.0F0A66C0]
[cid:image002.jpg@01D56349.0F0A66C0]
Pozdrawiam
Jacek Dąbrowski Koordynator Administratorów IT
[cid:image004.png@01D56349.0F0A66C0]http://transgourmet.pl/ Transgourmet Polska Sp. z o.o. Zamenhofa 133, 61-131, Poznań, Polska tel.: +48 61 874 20 17 kom.: +48 604 069 933 E-mail: Jacek.Dabrowski@selgros.pl www.selgros.plhttp://selgros.pl www.selgros24.plhttp://selgros24.pl www.transgourmet.plhttp://transgourmet.pl
Transgourmet Polska Sp. z o.o. jest zarejestrowana w Sądzie Rejonowym Poznań-Nowe Miasto i Wilda w Poznaniu, Wydział VIII Gospodarczy Krajowego Rejestru Sądowego pod nr KRS: 0000045597. NIP: PL 781-10-11-998, REGON 630375413. Wysokość kapitału zakładowego: 310.000.000,00 złotych. Zapraszamy do korzystania z aplikacji HELPDESKhttp://helpdesk-it... From: observium observium-bounces@observium.org On Behalf Of Greg Peterson via observium Sent: Wednesday, September 4, 2019 5:20 PM To: Observium observium@observium.org Cc: Greg Peterson gpeterson@nescmn.net Subject: Re: [Observium] DB Error
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.orgmailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:image001.jpg@01D5617C.C2F25CC0]
Pozdrawiam
Jacek Dąbrowski
There are 28 snmpbulkwalk/snmpget processes on that screenshot, which suggests that there are at least 26 pollers running, which is probably causing the problem.
I also see a number of python processes, which suggests there are a lot of poller-wrappers running.
The system is at 100% load, which would explain the problems, because it'll just spawn more and more processes.
Kill all of this off and it might go back to normal. If it doesn't, you need to find out which devices are polling slowly, or why everything is polling slowly.
Have you changed the setting that limits poller-wrapper processes in the config?
Adam.
From: observium observium-bounces@observium.org On Behalf Of Jacek Dabrowski via observium Sent: 04 September 2019 16:49 To: observium@observium.org Cc: Jacek.Dabrowski@selgros.pl Subject: Re: [Observium] DB Error
Discovery time is very big, top does not show that the server is heavily loaded
Pozdrawiam
Jacek Dąbrowski Koordynator Administratorów IT
http://transgourmet.pl/ Transgourmet Polska Sp. z o.o. Zamenhofa 133, 61-131, Poznań, Polska tel.: +48 61 874 20 17 kom.: +48 604 069 933 E-mail: Jacek.Dabrowski@selgros.pl mailto:Jacek.Dabrowski@selgros.pl http://selgros.pl www.selgros.pl http://selgros24.pl www.selgros24.pl http://transgourmet.pl www.transgourmet.pl
Transgourmet Polska Sp. z o.o. jest zarejestrowana w Sądzie Rejonowym Poznań-Nowe Miasto i Wilda w Poznaniu, Wydział VIII Gospodarczy Krajowego Rejestru Sądowego pod nr KRS: 0000045597. NIP: PL 781-10-11-998, REGON 630375413. Wysokość kapitału zakładowego: 310.000.000,00 złotych. Zapraszamy do korzystania z aplikacji http://helpdesk-it HELPDESK...
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Greg Peterson via observium Sent: Wednesday, September 4, 2019 5:20 PM To: Observium <observium@observium.org mailto:observium@observium.org > Cc: Greg Peterson <gpeterson@nescmn.net mailto:gpeterson@nescmn.net > Subject: Re: [Observium] DB Error
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.org mailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.pl mailto:Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
Pozdrawiam
Jacek Dąbrowski
The tips didn't help. limiting processes helps so that the database does not scream. However, rrdtool does not work properly (no graphics) how can you transfer the whole configuration to the new server?
Pozdrawiam
Jacek Dąbrowski
From: observium observium-bounces@observium.org On Behalf Of Adam Armstrong via observium Sent: Wednesday, September 4, 2019 6:13 PM To: 'Observium' observium@observium.org Cc: adama@memetic.org Subject: Re: [Observium] DB Error
There are 28 snmpbulkwalk/snmpget processes on that screenshot, which suggests that there are at least 26 pollers running, which is probably causing the problem.
I also see a number of python processes, which suggests there are a lot of poller-wrappers running.
The system is at 100% load, which would explain the problems, because it'll just spawn more and more processes.
Kill all of this off and it might go back to normal. If it doesn't, you need to find out which devices are polling slowly, or why everything is polling slowly.
Have you changed the setting that limits poller-wrapper processes in the config?
Adam.
From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Jacek Dabrowski via observium Sent: 04 September 2019 16:49 To: observium@observium.orgmailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl Subject: Re: [Observium] DB Error
Discovery time is very big, top does not show that the server is heavily loaded
[cid:image001.jpg@01D5657D.EFFA18C0]
[cid:image002.jpg@01D5657D.EFFA18C0]
Pozdrawiam
Jacek Dąbrowski Koordynator Administratorów IT
[cid:image003.png@01D5657D.EFFA18C0]http://transgourmet.pl/ Transgourmet Polska Sp. z o.o. Zamenhofa 133, 61-131, Poznań, Polska tel.: +48 61 874 20 17 kom.: +48 604 069 933 E-mail: Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl www.selgros.plhttp://selgros.pl www.selgros24.plhttp://selgros24.pl www.transgourmet.plhttp://transgourmet.pl
Transgourmet Polska Sp. z o.o. jest zarejestrowana w Sądzie Rejonowym Poznań-Nowe Miasto i Wilda w Poznaniu, Wydział VIII Gospodarczy Krajowego Rejestru Sądowego pod nr KRS: 0000045597. NIP: PL 781-10-11-998, REGON 630375413. Wysokość kapitału zakładowego: 310.000.000,00 złotych. Zapraszamy do korzystania z aplikacji HELPDESKhttp://helpdesk-it... From: observium <observium-bounces@observium.orgmailto:observium-bounces@observium.org> On Behalf Of Greg Peterson via observium Sent: Wednesday, September 4, 2019 5:20 PM To: Observium <observium@observium.orgmailto:observium@observium.org> Cc: Greg Peterson <gpeterson@nescmn.netmailto:gpeterson@nescmn.net> Subject: Re: [Observium] DB Error
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.orgmailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.plmailto:Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
[cid:image001.jpg@01D5617C.C2F25CC0]
Pozdrawiam
Jacek Dąbrowski
Graph data is stored in the rrds folder, you can copy this to a new install and ./device_add.php all of the devices, and it'll pick up graphing data.
You can also transfer the MySQL database, this will keep any settings you've changed in the web UI, alerting, etc. This might not be the best idea, if you're not sure what's set in the database that might be causing issues.
Then config.php is things you've changed. I'd recommend not copying this, but reading through it and manually transferring settings you KNOW you need. Less is more.
Reinstall onto a clean server using the install script, then copy rrd folder across and ./device_add.php everything (you could shell script this pretty easily).
Adam.
From: observium observium-bounces@observium.org On Behalf Of Jacek Dabrowski via observium Sent: 07 September 2019 12:13 To: observium@observium.org Cc: Jacek.Dabrowski@selgros.pl; adama@memetic.org Subject: Re: [Observium] DB Error
The tips didn't help. limiting processes helps so that the database does not scream. However, rrdtool does not work properly (no graphics) how can you transfer the whole configuration to the new server?
Pozdrawiam
Jacek Dąbrowski
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Adam Armstrong via observium Sent: Wednesday, September 4, 2019 6:13 PM To: 'Observium' <observium@observium.org mailto:observium@observium.org > Cc: adama@memetic.org mailto:adama@memetic.org Subject: Re: [Observium] DB Error
There are 28 snmpbulkwalk/snmpget processes on that screenshot, which suggests that there are at least 26 pollers running, which is probably causing the problem.
I also see a number of python processes, which suggests there are a lot of poller-wrappers running.
The system is at 100% load, which would explain the problems, because it'll just spawn more and more processes.
Kill all of this off and it might go back to normal. If it doesn't, you need to find out which devices are polling slowly, or why everything is polling slowly.
Have you changed the setting that limits poller-wrapper processes in the config?
Adam.
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Jacek Dabrowski via observium Sent: 04 September 2019 16:49 To: observium@observium.org mailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.pl mailto:Jacek.Dabrowski@selgros.pl Subject: Re: [Observium] DB Error
Discovery time is very big, top does not show that the server is heavily loaded
Pozdrawiam
Jacek Dąbrowski Koordynator Administratorów IT
http://transgourmet.pl/ Transgourmet Polska Sp. z o.o. Zamenhofa 133, 61-131, Poznań, Polska tel.: +48 61 874 20 17 kom.: +48 604 069 933 E-mail: Jacek.Dabrowski@selgros.pl mailto:Jacek.Dabrowski@selgros.pl http://selgros.pl www.selgros.pl http://selgros24.pl www.selgros24.pl http://transgourmet.pl www.transgourmet.pl
Transgourmet Polska Sp. z o.o. jest zarejestrowana w Sądzie Rejonowym Poznań-Nowe Miasto i Wilda w Poznaniu, Wydział VIII Gospodarczy Krajowego Rejestru Sądowego pod nr KRS: 0000045597. NIP: PL 781-10-11-998, REGON 630375413. Wysokość kapitału zakładowego: 310.000.000,00 złotych. Zapraszamy do korzystania z aplikacji http://helpdesk-it HELPDESK...
From: observium <observium-bounces@observium.org mailto:observium-bounces@observium.org > On Behalf Of Greg Peterson via observium Sent: Wednesday, September 4, 2019 5:20 PM To: Observium <observium@observium.org mailto:observium@observium.org > Cc: Greg Peterson <gpeterson@nescmn.net mailto:gpeterson@nescmn.net > Subject: Re: [Observium] DB Error
I was getting this message when I had devices that didn't finish polling in five minutes (300s). you can check this by looking at polling information/Per Device
From: observium [mailto:observium-bounces@observium.org] On Behalf Of Jacek Dabrowski via observium Sent: Monday, September 02, 2019 3:54 AM To: observium@observium.org mailto:observium@observium.org Cc: Jacek.Dabrowski@selgros.pl mailto:Jacek.Dabrowski@selgros.pl Subject: [Observium] DB Error
Hello,
Yesterday I turned off Observium after turning on the message DB Error 1040 appears, which I can do with it ???
Pozdrawiam
Jacek Dąbrowski
participants (6)
-
adama＠memetic.org -
Greg Peterson -
Jacek.Dabrowski＠selgros.pl -
Markus Klock -
Michiel Klaver -
Tom Laermans