I think that we've got to much information in our syslog db.
When i try to open haloe, i takes about 10 minutes before it opens, and when i select some else, it takes again more then 10 minutes.
Is there a way to empty the data that is in there? I think there's to much in there. we made a mistake and sent all our firewall logs to the machine, so i think it was a little bit to much...
The rest of the machine is working fine...
Empty Haloe
Moderators: Developers, Moderators
We had the same issue, and ever since I rebuilt Cacti on a new server we just cannot get the syslog plugin to work again. I've played with exceptions and everything and it doesn't seem to improve performance. I'm hesitant to even troubleshoot Haloe since I'm afraid it's going to be useless after a few weeks of data.
Registered Linux User: 439431
Cacti Version 0.8.8a (not installed via rpm)
Cacti OS unix (OpenSUSE 12.3 x64 on HP DL360 G7)
SNMP Version NET-SNMP version: 5.7.1
RRDTool Version RRDTool 1.4.7
Poller Type SPINE
Cacti Version 0.8.8a (not installed via rpm)
Cacti OS unix (OpenSUSE 12.3 x64 on HP DL360 G7)
SNMP Version NET-SNMP version: 5.7.1
RRDTool Version RRDTool 1.4.7
Poller Type SPINE
- chrisgapske
- Cacti User
- Posts: 278
- Joined: Tue May 22, 2007 7:56 am
- Location: Pensacola, Fl - Padacuh, Ky-Alpena, MI-Gulf Shores,AL
Try this.
http://forums.cacti.net/viewtopic.php?t ... highlight=
Try to optimize the syslog mysql table.
OPTIMIZE TABLE table_name[,table_name]
That helped me..
http://forums.cacti.net/viewtopic.php?t ... highlight=
Try to optimize the syslog mysql table.
OPTIMIZE TABLE table_name[,table_name]
That helped me..
Who is online
Users browsing this forum: No registered users and 3 guests