I got some weird stuf.
I run the command, and find out some files with size 2 GIG.
and then delete those files.
and run df -h command, it still 80% full capacity. not bad ...
i reboot the server, after that i log into ut box,...
now it was back to 78 GB free ...
woaw..... who delete those files?
YY
can you just paste the output?
I wouldn't go deleting random files.
Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
If you need Untangle support please call or email support@untangle.com
Actually all files i delete is *.log*Originally Posted by dmorris
and yes it is more than 1 GB
I can not run find / -size +1000000k -exec ls -lh {} \;
because it will display error like this (long very long record):
so I run per folder like this :Code:find: `/proc/8140/task/14509/fd/6118': No such file or directory find: `/proc/8140/task/14509/fd/6365': No such file or directory find: `/proc/8140/task/14509/fd/6798': No such file or directory find: `/proc/8140/task/14509/fd/6860': No such file or directory find: `/proc/8140/task/14509/fd/7746': No such file or directory find: `/proc/8140/task/14509/fd/7747': No such file or directory find: `/proc/8140/task/14509/fd/7748': No such file or directory find: `/proc/8140/task/14509/fd/7749': No such file or directory find: `/proc/8140/task/14509/fd/7750': No such file or directory find: `/proc/8140/task/14509/fd/8148': No such file or directory find: `/proc/8140/task/14509/fd/8149': No such file or directory
find /var -size +1000000k -exec ls -lh {} \;
find /tmp -size +1000000k -exec ls -lh {} \;
now there is no big files anymore...
Also I notice there is a file :
/var/log/uvm/gc.log.crash it is 204 MB and new ...
Here is inside that file :
Code:2010-11-04T01:00:20.559+0700: 4.961: [GC [1 CMS-initial-mark: 0K(109824K)] 5318K(128960K), 0.0020460 secs] [Times: user=0.00 sys=0.00, real=0.01 secs] 2010-11-04T01:00:20.561+0700: 4.963: [CMS-concurrent-mark-start] 2010-11-04T01:00:20.577+0700: 4.979: [CMS-concurrent-mark: 0.010/0.015 secs] [Times: user=0.02 sys=0.00, real=0.01 secs] 2010-11-04T01:00:20.577+0700: 4.979: [CMS-concurrent-preclean-start] 2010-11-04T01:00:20.578+0700: 4.980: [CMS-concurrent-preclean: 0.001/0.001 secs] [Times: user=0.00 sys=0.00, real=0.00 secs] 2010-11-04T01:00:20.578+0700: 4.980: [CMS-concurrent-abortable-preclean-start] 2010-11-04T01:00:21.186+0700: 5.588: [GC 5.588: [ParNew: 17930K->1669K(19136K), 0.0032530 secs] 17930K->1669K(128960K), 0.0032980 secs] [Times: user=0.01 sys=0.01, real=0.00 secs] 2010-11-04T01:00:21.575+0700: 5.977: [CMS-concurrent-abortable-preclean: 0.035/0.997 secs] [Times: user=0.79 sys=0.06, real=1.00 secs] 2010-11-04T01:00:21.575+0700: 5.977: [GC[YG occupancy: 12130 K (19136 K)]5.977: [Rescan (parallel) , 0.0073840 secs]5.985: [weak refs processing, 0.0000080 secs] [1 CMS-remark: 0K(109824K)] 12130K(128960K), 0.0075150 secs] [Times: user=0.02 sys=0.02, real=0.01 secs] 2010-11-04T01:00:21.583+0700: 5.985: [CMS-concurrent-sweep-start] 2010-11-04T01:00:21.583+0700: 5.985: [CMS-concurrent-sweep: 0.000/0.000 secs] [Times: user=0.00 sys=0.00, real=0.00 secs] 2010-11-04T01:00:21.583+0700: 5.985: [CMS-concurrent-reset-start] 2010-11-04T01:00:21.599+0700: 6.001: [CMS-concurrent-reset: 0.016/0.016 secs] [Times: user=0.02 sys=0.01, real=0.01 secs] 2010-11-04T01:00:21.848+0700: 6.250: [GC 6.250: [ParNew: 18693K->2112K(19136K), 0.0169870 secs] 18693K->5326K(128960K) icms_dc=38 , 0.0170490 secs] [Times: user=0.05 sys=0.00, real=0.02 secs] 2010-11-04T01:00:21.979+0700: 6.381: [GC [1 CMS-initial-mark: 3214K(109824K)] 10768K(128960K), 0.0064670 secs] [Times: user=0.00 sys=0.00, real=0.01 secs] 2010-11-04T01:00:21.985+0700: 6.387: [CMS-concurrent-mark-start] 2010-11-04T01:00:22.015+0700: 6.417: [CMS-concurrent-mark: 0.018/0.029 secs] [Times: user=0.05 sys=0.00, real=0.03 secs] 2010-11-04T01:00:22.015+0700: 6.417: [CMS-concurrent-preclean-start] 2010-11-04T01:00:22.018+0700: 6.420: [CMS-concurrent-preclean: 0.002/0.003 secs] [Times: user=0.00 sys=0.01, real=0.00 secs] 2010-11-04T01:00:22.018+0700: 6.420: [CMS-concurrent-abortable-preclean-start] 2010-11-04T01:00:22.959+0700: 7.361: [GC 7.361: [ParNew: 19136K->2112K(19136K), 0.0095620 secs] 22350K->7271K(128960K) icms_dc=51 , 0.0096200 secs] [Times: user=0.03 sys=0.00, real=0.01 secs] 2010-11-04T01:00:24.352+0700: 8.754: [CMS-concurrent-abortable-preclean: 0.149/2.334 secs] [Times: user=0.67 sys=0.13, real=2.34 secs] 2010-11-04T01:00:24.353+0700: 8.755: [GC[YG occupancy: 12941 K (19136 K)]8.755: [Rescan (parallel) , 0.0057320 secs]8.761: [weak refs processing, 0.0002020 secs] [1 CMS-remark: 5159K(109824K)] 18100K(128960K), 0.0060260 secs] [Times: user=0.03 sys=0.00, real=0.00 secs] 2010-11-04T01:00:24.359+0700: 8.761: [CMS-concurrent-sweep-start] 2010-11-04T01:00:24.361+0700: 8.763: [CMS-concurrent-sweep: 0.002/0.002 secs] [Times: user=0.00 sys=0.00, real=0.01 secs] 2010-11-04T01:00:24.361+0700: 8.763: [CMS-concurrent-reset-start] 2010-11-04T01:00:24.366+0700: 8.768: [CMS-concurrent-reset: 0.005/0.005 secs] [Times: user=0.01 sys=0.00, real=0.00 secs] 2010-11-04T01:00:24.558+0700: 8.960: [GC 8.960: [ParNew: 19136K->2112K(19136K), 0.0072570 secs] 24283K->9156K(128960K) icms_dc=44 , 0.0073140 secs] [Times: user=0.03 sys=0.00, real=0.01 secs] 2010-11-04T01:00:24.625+0700: 9.027: [GC [1 CMS-initial-mark: 7044K(109824K)] 14244K(128960K), 0.0041290 secs] [Times: user=0.01 sys=0.00, real=0.00 secs] 2010-11-04T01:00:24.629+0700: 9.031: [CMS-concurrent-mark-start] 2010-11-04T01:00:24.684+0700: 9.086: [CMS-concurrent-mark: 0.031/0.054 secs] [Times: user=0.11 sys=0.01, real=0.06 secs] 2010-11-04T01:00:24.684+0700: 9.086: [CMS-concurrent-preclean-start] 2010-11-04T01:00:24.686+0700: 9.088: [CMS-concurrent-preclean: 0.002/0.002 secs] [Times: user=0.00 sys=0.00, real=0.00 secs] 2010-11-04T01:00:24.686+0700: 9.088: [CMS-concurrent-abortable-preclean-start] 2010-11-04T01:00:24.826+0700: 9.228: [GC 9.228: [ParNew: 19136K->1698K(19136K), 0.0030060 secs] 26180K->8743K(128960K) icms_dc=59 , 0.0030550 secs] [Times: user=0.01 sys=0.00, real=0.00 secs] 2010
Please advice what happens?
Yuan
anyone know what does that crash error log mean?
YY
you can run:
find / -size +1000000k -exec ls -lh {} \; 2>/dev/null
to hide the errors.
Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
If you need Untangle support please call or email support@untangle.com
Untangle doesn't clear the log files unless you reboot the machine. (In my case at least)
Our Untangle Machine was up for 230 plus days before its first reboot. I could go back to day one of the first web violation in the log files. The reboot cleared the cache of the log files and freed up about 15GB of data from the hard drive.
I also have a very small network of 22 computers and there wouldn't have been as much data/log files as your network would create.
It rotates log files every night.
It does nothing with log files on reboot.
Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
If you need Untangle support please call or email support@untangle.com
Excuse me when I say log files. Yes it only keeps 30 days of log files.
What I mean is when you log in to Untangle and look at the statistics of each rack. These do not clear out until you reboot. Which I think is taking up the space.
Please stop confusing everyone.
1) Those events aren't kept in log files, they're kept in a database.
2) The log files are totally separate from events.
3) Neither is cleared on a reboot.
4) Both are pruned nightly.
to my knowledge the only thing cleared on reboot are the stats on the faceplate, which are only stored in memory. Hence they reset when you reboot.
Last edited by dmorris; 11-12-2010 at 03:50 PM.
Attention: Support and help on the Untangle Forums is provided by volunteers and community members like yourself.
If you need Untangle support please call or email support@untangle.com
But sometimes the pruning seems to go bad, and the pruned file or attempt at it, and the main one keep growing (found them at 2-4gb each or larger before, and delete them and you see some of the space back, but a reboot or two before it all comes back keeps going forward correctly)
LinkBack URL
About LinkBacks
