For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Roo_150490's avatar
Roo_150490
Icon for Nimbostratus rankNimbostratus
Oct 24, 2014

VE /var/log full

Hi Guys,

 

Please can someone help me resolve the following message I keep getting when I SSH into my VE:

 

[root@SRVVLBLLX001:Active:Standalone] log Broadcast message from root (Fri Oct 24 21:21:01 2014):

 

011d0004: Disk partition var_log has only 0% free Oct 24 21:21:02 SRVVLBLLX001 emerg alertd[5866]: 01100048:0: Log disk usage still higher than 80% after logrotate and 24 times log deletion

 

df-h shows the following:

 

[root@SRVVLBLLX001:Active:Standalone] log df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/vg--db--sda-set.2.root 380M 212M 149M 59% / /dev/mapper/vg--db--sda-set.2._config 3.0G 153M 2.7G 6% /config /dev/mapper/vg--db--sda-set.2._usr 2.5G 1.8G 548M 77% /usr /dev/mapper/vg--db--sda-set.2._var 3.0G 1011M 1.9G 36% /var /dev/mapper/vg--db--sda-dat.share.1 20G 4.9G 14G 26% /shared /dev/mapper/vg--db--sda-dat.log.1 485M 484M 0 100% /var/log none 4.0G 916K 4.0G 1% /dev/shm none 4.0G 38M 3.9G 1% /shared/rrd.1.2 none 4.0G 6.9M 4.0G 1% /var/tmstat none 4.0G 1.4M 4.0G 1% /var/run prompt 4.0M 28K 4.0M 1% /var/prompt none 4.0G 8.0K 4.0G 1% /var/logd none 4.0G 0 4.0G 0% /var/loipc /dev/mapper/vg--db--sda-app.ASWADB.set.2.mysqldb 12G 687M 11G 6% /var/lib/mysql

 

Is there any way to resolve this via the GUI rather on the command line? Is there anyway I can setup all logs to just clean down after a certain threshold/time period so I dont run into this issue again?

 

Thanks Roo

 

3 Replies

  • Hi,

     

    may be this link will help you https://support.f5.com/kb/en-us/solutions/public/13000/300/sol13367.html

     

  • Do you have ASM? If yes Please check this

     

    https://support.f5.com/kb/en-us/solutions/public/17000/300/sol17344.html?sr=55878527

     

  • Just in case you wanted root cause - We had an issue similar to this where Verbose logging had been left on for monitor logging...