Log_size_limit issue

[GoogleCodeExporter]

Hi, we have configured ELSA NODE & WEB in the same server, server Hard disk 
size is 40GB, we haven't configured the Log_Size_limit, it has the default 
2000000000 in the node.conf file, due to this my HDD size got filled. no free 
space left & all SYslog,Mysql&other services got hanged.

how i do clear all the the logs & make my HDD free & resume ELSA working.
what should be the Log_Size_limit for a 40GB HDD ?

Original issue reported on code.google.com by vamsi.ma...@gmail.com on 1 Aug 2012 at 10:24

[GoogleCodeExporter]

You should set the default log_size_limit down from 200 GB (200000000000) to 
something like 30 GB (30000000000) for your 40 GB drive.  After changing the 
limit, the system should automatically start removing logs until it's under 
that limit.  If the system can't function because the disk is completely full, 
you can delete the oldest files in the /data/sphinx/ directory which contains 
the indexes.  If you can get MySQL started, there's a better way, but I'm 
assuming that you can't get MySQL started due to no free disk space.

Original comment by mchol...@gmail.com on 1 Aug 2012 at 1:58

• Added labels: Type-Other
• Removed labels: Type-Defect

[GoogleCodeExporter]

Thank you, 
now we have set the limit suggested by you & after setting limit system dint 
remove the logs automatically. we removed oldest file in /data/sphinx dir. 

Pls let us know what is the other you way if MySQl is running.

Original comment by vamsi.ma...@gmail.com on 2 Aug 2012 at 6:29

[GoogleCodeExporter]

If MySQL is running, you can drop the oldest 10 indexes like this:
mysql syslog -e "DELETE FROM indexes ORDER BY start ASC LIMIT 10"
Then you can have ELSA perform its validation routine as it does on normal 
startup like this:
echo "" | elsa.pl -o

Original comment by mchol...@gmail.com on 2 Aug 2012 at 1:47

[GoogleCodeExporter]

Closing due to inactivity.

Original comment by mchol...@gmail.com on 29 Nov 2012 at 10:37

• Changed state: Done