Welcome, Guest. Please login or register.
Did you miss your activation email?
Thursday 05 December 2024, 03:06:22 pm

Login with username, password and session length

Get the new Updates directly from Endian  HERE
14261 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  how to clean "/dev/mapper/local-var"
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: how to clean "/dev/mapper/local-var"  (Read 16559 times)
hakangunaydin
Jr. Member
*
Offline Offline

Posts: 1


« on: Thursday 03 May 2012, 05:57:48 pm »

Hi,

I am using the community version for 1.5 years.

Now the firewall says there is problem with disk space :

Filesystem            Size  Used Avail Use% Mounted on
 /dev/sda1              73G  514M   69G   1% /
 /dev/mapper/local-var
                       344G  326G     0 100% /var
 /dev/mapper/local-config
                        99M  4.9M   89M   6% /var/efw
 /dev/mapper/local-log
                        20G  145M   19G   1% /var/log


How could I clean "/dev/mapper/local-var"

Thanks
Logged
kashifmax
Sr. Member
****
Offline Offline

Gender: Female
Posts: 108


« Reply #1 on: Wednesday 09 May 2012, 06:05:33 pm »

Login to the firewall via ssh and go to /var/ /var/log/ and remove unnecessary logs. For examples compressed logs are in /var/archives/ /var/log/archives/, this is for EFW 2.5.1 and not sure that this path also exist in prior versions of EFW...
Logged
mrkroket
Hero Member
*****
Offline Offline

Posts: 495


« Reply #2 on: Thursday 10 May 2012, 12:08:50 am »

The problem is not in /var/log, the problem is in /var, they are different partitions.
/var/log has 19G free.

You should go to console (via SSH/putty or local) or WinSCP, and review the disk usage on /var
Logged
kashifmax
Sr. Member
****
Offline Offline

Gender: Female
Posts: 108


« Reply #3 on: Thursday 10 May 2012, 06:08:00 pm »

Oops! I didn't saw that also Shocked Thanks for pointing it out. Modifying comments also
Logged
blackisle
Jr. Member
*
Offline Offline

Posts: 3


« Reply #4 on: Thursday 19 July 2012, 12:47:15 am »

I've had the same issue - found that the /var/spool is the one chewing disk space, nothing to do with the logging.
On our install it's the squid directory that's lumped up 22GB in the space of 3 weeks - filling the /dev/mapper/local-var and leaving no space for further squid logs/cache items.
Reason for this: I'd set the Squid Cache size to 50000MB (27000MB more than was actually available)
Fix: either use the GUI to clear the proxy cache and set the proxy size to a sensible value (5GB now, leaves 15GB for logging)
or from ssh:
/etc/init.d/squid stop
rm -rf /var/spool/squid/*
nano /etc/squid/squid.conf     *** edit line "cache_dir aufs /var/spool/squid <cache size in MB> 16 256"
squid -z         (recreates the cache structure)
/etc/init.d/squid start

Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.109 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com