Details
Minor Description
Hi there,
I enabled the syslog server about a month ago, and added 10 different hosts that dump their syslogs here... I quickly ran into space issues and added more space to the server because of this... I thought I had setup the housekeeping script, but I forgot to add the "s" option, so the syslogs were never purged... (I have setup 7 days in the config file)
Now another thing I noticed, was that mysql had created many binlog files (logfiles I guess) which I had to purge first and actually they where the main issue in regards to taking up space.. I have since disabled this logging.
But I still have a 70GB syslog.idb mysql file which I would like to purge down to 7 days.
When I run the housekeeping script, after awhile it asks me if I want to purge 80477997 syslog entries to which I agreed... then it just sits there for like 12 hours now...
The mysql processes is running at 200% so I guess something is "working", yet there is no updates in the housekeeping log... ?
Am I doing something wrong here?
Now the database files are not on a seperate drive, but everything is on enterprise SSDs.
The system is running Ubuntu 20.04, as a virtual VM in VMWare. (4 vCPUS, 16GB Memory, 300GB SSD)
The VM isn't doing much... using about 3GB of memory and using about 50% CPU and not much disk IO...
The Ubuntu nore mysql has been optimized in anyway and is pretty much stock.
So I am a bit confused as to what is going on? And maybe I'm doing something wrong here?
Attachments
Activity
Eventually the housekeeping script finished the purge of syslogs...
But it took about 3-4 days... seems now to finish normally every night as it purges...
General questions and device support can be discussed in our Discord channel, click here to join.
Please make and attach additional information about the device:
- full snmp dump from device:
snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalksnmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalkIf device not support SNMP version 2c, replace -v2c with -v1.
- If you have problems with discovery or poller processes, please do and attach these debugs:
./discovery.php -d -h <device>./poller.php -d -h <device>
- additionally attach device and/or vendor specific MIB files
This comment is added automatically.
Hi Heino,
Sorry, I forgot to reply to this when I first read it!
If you've not run housekeeping on syslog before, it's better to just truncate the table, since deleting the entries by housekeeping has to be done in batches to prevent locking up the MySQL server.
MySQL won't release the space it used up, but if you want your 70GB back you can delete the table from MySQL and recreate it. If you have phpmyadmin or similar on the system it is probably sufficient to copy the table to another table, delete the original one, and then copy it back.
Thanks,
adam.