Hi all,
I just setup a new Cacti 1.2.23 and ready to promote it to internal usage. Before promote Cacti I do some test for the system and I found some problems with Cacti. May I ask if someone can help me?
After I add a device with monitoring HTTP port and stop the service in the related device, I got an email that Poller Output Table not empty for poller id 1. Even I start HTTP service and got the notification that it is online, the email was still sent every 5 minutes. I tried restarting the server and the email do not send out until I trigger the server that I closed the service. May I ask if anyone knows how to fix the problem?
I assume that an email would be sent to notify me that a server is down when I close the HTTP service. I found the log that the related server is down but I cannot get any email about the problem. What should I do about the problem?
After I turn on the service, I got the message that the device is on with the wrong "Last Date Checked UP" date and time (the last 2 show 1970-01-01 (got the message on 2023-02-07 at 1220 UTC-5) and 1969-12-31 (got the message on 2023-02-07 at 1310 UTC-5)). May I ask if it is normal?
Problem with Email Setting
Moderators: Developers, Moderators
-
- Posts: 10
- Joined: Mon Jan 09, 2023 11:31 am
Problem with Email Setting
- Attachments
-
- Combined SCSI Disk Bytes Graph
- Combined SCSI Disk Bytes Graph.jpg (83.27 KiB) Viewed 703 times
-
- Combined SCSI Disk Bytes Setting
- Combined SCSI Disk Bytes Setting.jpg (49.55 KiB) Viewed 703 times
-
- Error Log
- Error Log.jpg (100.69 KiB) Viewed 703 times
-
- Device Up and Down Log
- Device Up and Down Log.jpg (179.27 KiB) Viewed 703 times
-
- Warning Log
- Warning Log.jpg (501.3 KiB) Viewed 703 times
-
- Posts: 10
- Joined: Mon Jan 09, 2023 11:31 am
Re: Problem with Email Setting
Tried to upload more than 5 attachments but failed. Just upload the attachments left.
- Attachments
-
- Recover Email
- Recover Email.jpg (137.5 KiB) Viewed 702 times
-
- Device Threshold Setting
- Device Threshold Setting 01.jpg (148.78 KiB) Viewed 702 times
- TheWitness
- Developer
- Posts: 17047
- Joined: Tue May 14, 2002 5:08 pm
- Location: MI, USA
- Contact:
Re: Problem with Email Setting
If I were you, I would stick to the SNMP monitoring, and use the 1.2.x version of spine for scalability, and then leave the http monitoring to the webseer plugin. The reason for the 1.2.x version of spine is that there was a bug in the 1.2.23 version sadly.
True understanding begins only when we realize how little we truly understand...
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
Life is an adventure, let yours begin with Cacti!
Author of dozens of Cacti plugins and customization's. Advocate of LAMP, MariaDB, IBM Spectrum LSF and the world of batch. Creator of IBM Spectrum RTM, author of quite a bit of unpublished work and most of Cacti's bugs.
_________________
Official Cacti Documentation
GitHub Repository with Supported Plugins
Percona Device Packages (no support)
Interesting Device Packages
For those wondering, I'm still here, but lost in the shadows. Yearning for less bugs. Who want's a Cacti 1.3/2.0? Streams anyone?
-
- Posts: 10
- Joined: Mon Jan 09, 2023 11:31 am
Re: Problem with Email Setting
Based on your information, I tried to downgrade to 1.2.22 and test the system again. System warning email stop sending but the system down and re-alart email still had not sent. And the time issue when recover still exist. So what should I do for the issue? I also attached THold setting for your information.TheWitness wrote: ↑Tue Feb 07, 2023 9:53 pm If I were you, I would stick to the SNMP monitoring, and use the 1.2.x version of spine for scalability, and then leave the http monitoring to the webseer plugin. The reason for the 1.2.x version of spine is that there was a bug in the 1.2.23 version sadly.
https://drive.google.com/file/d/1kT6x84 ... sp=sharing
Who is online
Users browsing this forum: No registered users and 2 guests