Ryan, Thank you. No way to save the device and alert setup?
Helmut
------ Original Message ------ From "Ryan, Spencer J. via observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> To "Observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> Cc "Ryan, Spencer J." <Ryan@millercanfield.commailto:Ryan@millercanfield.com> Date 1/17/2023 5:39:50 PM Subject [EXTERNAL] [Observium] Re: dbquery failure
If you don’t care about historical data, config.php is really all that matters, you could blow it away and re-add all the devices and start fresh in an hour or so.
________________________________ Spencer J. Ryan| Manager, Technology and Infrastructure Miller Canfield T +1.313.496.7979 | F +1.313.496.7500 ________________________________
From: Helmut Fritz via observium <observium@lists.observium.orgmailto:observium@lists.observium.org> Sent: Tuesday, January 17, 2023 8:21 PM To: Observium <observium@lists.observium.orgmailto:observium@lists.observium.org> Cc: Helmut Fritz <helmut.fritz@cirrascale.commailto:helmut.fritz@cirrascale.com> Subject: [Observium] Re: dbquery failure
Caution: This is an external email. Do not open attachments or click links from unknown or unexpected emails.
actually, after digging into my history i may have found the cause: our hard drive filled up (seemingly database logs) and jammed up the database. i have set them to be circular (I believe, will follow up on that) but that is likely the timing of the start of those messages. is there a method to check the health of the database?
is there a method to reinstall and save the setup that is currently there? that might just be faster/easier than anything else!
thx!
Helmut
------ Original Message ------ From "Helmut Fritz" <helmut.fritz@cirrascale.commailto:helmut.fritz@cirrascale.com> To "Observium" <observium@lists.observium.orgmailto:observium@lists.observium.org> Date 1/17/2023 5:02:18 PM Subject dbquery failure
Hello! Subscriber here... One of our Observium instances has stopped alerting on the port down alert/checker. Specifically, it will still alert in ports we had configured already when this instance of Observium was installed, but it will not alert on any new ports we configure/add to the infrastructure. I.e. switch1 port1 was set up right after install, tested, good, and still alerts if it goes down. switch1 port2 was added to observium at a later date due to a new server install, and if it goes down it will not alert. We had 8 switches at the time, and this behavior seems to be equal across all 8 (not had time for thorough testing, which I would normally do except for the discovery of the below error).
It has been going on for a few months that we know of, but this has not yet bubbled to the top of our list of things to tackle. But we are now adding new infrastructure to that particular datacenter, and while I am mucking about there I thought I would take a look.
I found the observium and housekeeping logs seemingly normal, but the db log is full of the below error (and nothing else):
[2023/01/17 22:53:56 +0000] index.php(40131): Failed dbQuery (#1064 - You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'AND 0 GROUP BY `group_id`' at line 1), Query: SELECT COUNT(*) AS `count`, `group_id` FROM `group_table` WHERE AND 0 GROUP BY `group_id`
I thought this may have started when I did an update several months ago, but it is possible it has been doing this since inception. I did do an update today, thinking perhaps I missed running discovery.php -u when I did that update, but alas that did not help.
Help please. 😀
Helmut Fritz Director, Programs Cirrascale Cloud Services
You have received a message from the law firm Miller Canfield. The information contained in or attached to this electronic mail may be privileged and/or confidential. If you received this transmission and are not the intended recipient, you should not read this message and are hereby notified that any dissemination, distribution or copying of this communication and/or its attachments is strictly prohibited. If you have received this communication in error or are not sure whether it is privileged, please immediately notify us by return e-mail and delete or destroy the original and any copies, electronic, paper or otherwise, that you may have of this communication and any attachments.