No disk space for new files created by Tor
Dear All, Today when I was checking my Tor notice log file as usual, I noticed that they've included the following warnings: Aug 11 06:23:15.000 [warn] Unable to store router descriptorAug 11 06:23:15.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on device It seems that I've run out of space. But my VPS comes with 35GB disk space and it shouldn't be used up so fast. So how to deal with it?If I do run out of space,any advice for deleting the old files of Tor? Are there any files created by Tor are not useful anymore and can be deleted? Cheers,Tony
On Sun, Aug 11, 2013 at 1:41 PM, TonyXue <tonyxsuper@live.com> wrote:
[...] It seems that I've run out of space. But my VPS comes with 35GB disk
space and it shouldn't be used up so fast. So how to deal with it?
If I do run out of space,any advice for deleting the old files of Tor? Are there any files created by Tor are not useful anymore and can be deleted?
Assuming you're running a *nix system on your VPS, what does running df -h say? Additionally, you can try getting a list of largest directories/files on your VPS, like so: sudo -s cd / for i in G M K; do du -ah | grep [0-9]$i | sort -nr -k 1; done | head -n 1000 | tac or just run the latter on your home directory (and don't use sudo in that case, of course.) Kostas.
Fllowing are the result of df -h: Filesystem Size Used Avail Use% Mounted on/dev/xvda1 35G 17G 17G 51% /udev 235M 4.0K 235M 1% /devtmpfs 98M 192K 98M 1% /runnone 5.0M 0 5.0M 0% /run/locknone 244M 0 244M 0% /run/shm And seems /var/log/tor takes up 16G. Tony. From: kostas@jakeliunas.com Date: Sun, 11 Aug 2013 13:57:27 +0300 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] No disk space for new files created by Tor On Sun, Aug 11, 2013 at 1:41 PM, TonyXue <tonyxsuper@live.com> wrote:
[...] It seems that I've run out of space. But my VPS comes with 35GB disk space and it shouldn't be used up so fast. So how to deal with it?
If I do run out of space,any advice for deleting the old files of Tor? Are there any files created by Tor are not useful anymore and can be deleted? Assuming you're running a *nix system on your VPS, what does running
df -hsay? Additionally, you can try getting a list of largest directories/files on your VPS, like so:sudo -scd /for i in G M K; do du -ah | grep [0-9]$i | sort -nr -k 1; done | head -n 1000 | tac or just run the latter on your home directory (and don't use sudo in that case, of course.) Kostas. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Huh, curious why it fails to write stuff to disk. Does doing echo "something" > tempfile succeed? /var/log/tor is hogging diskspace indeed :) perhaps then do cd /var/log/tor sudo rm *.gz then do du -sh * to see if there are any remainder large files left there. On Sun, Aug 11, 2013 at 2:32 PM, TonyXue <tonyxsuper@live.com> wrote:
Fllowing are the result of *df -h:* * * * Filesystem Size Used Avail Use% Mounted on /dev/xvda1 35G 17G 17G 51% / udev 235M 4.0K 235M 1% /dev tmpfs 98M 192K 98M 1% /run none 5.0M 0 5.0M 0% /run/lock none 244M 0 244M 0% /run/shm
And seems /var/log/tor takes up 16G.
Tony. *
------------------------------ From: kostas@jakeliunas.com Date: Sun, 11 Aug 2013 13:57:27 +0300 To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] No disk space for new files created by Tor
On Sun, Aug 11, 2013 at 1:41 PM, TonyXue <tonyxsuper@live.com> wrote:
[...] It seems that I've run out of space. But my VPS comes with 35GB disk
space and it shouldn't be used up so fast. So how to deal with it?
If I do run out of space,any advice for deleting the old files of Tor? Are there any files created by Tor are not useful anymore and can be deleted?
Assuming you're running a *nix system on your VPS, what does running df -h say?
Additionally, you can try getting a list of largest directories/files on your VPS, like so: sudo -s cd / for i in G M K; do du -ah | grep [0-9]$i | sort -nr -k 1; done | head -n 1000 | tac
or just run the latter on your home directory (and don't use sudo in that case, of course.)
Kostas.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I also find running "du -s ./*" useful for figuring out which directories are hogging files... On 8/11/2013 6:43 AM, Kostas Jakeliunas wrote:
Huh, curious why it fails to write stuff to disk.
Does doing echo "something" > tempfile succeed?
/var/log/tor is hogging diskspace indeed :) perhaps then do cd /var/log/tor sudo rm *.gz
then do
du -sh *
to see if there are any remainder large files left there.
On Sun, Aug 11, 2013 at 2:32 PM, TonyXue <tonyxsuper@live.com <mailto:tonyxsuper@live.com>> wrote:
Fllowing are the result of /*df -h:*/ */ /* * Filesystem Size Used Avail Use% Mounted on /dev/xvda1 35G 17G 17G 51% / udev 235M 4.0K 235M 1% /dev tmpfs 98M 192K 98M 1% /run none 5.0M 0 5.0M 0% /run/lock none 244M 0 244M 0% /run/shm
And seems /var/log/tor takes up 16G.
Tony. *
------------------------------------------------------------------------ From: kostas@jakeliunas.com <mailto:kostas@jakeliunas.com> Date: Sun, 11 Aug 2013 13:57:27 +0300 To: tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> Subject: Re: [tor-relays] No disk space for new files created by Tor
On Sun, Aug 11, 2013 at 1:41 PM, TonyXue <tonyxsuper@live.com <mailto:tonyxsuper@live.com>> wrote: > > [...] > It seems that I've run out of space. But my VPS comes with 35GB disk space and it shouldn't be used up so fast. So how to deal with it? > If I do run out of space,any advice for deleting the old files of Tor? Are there any files created by Tor are not useful anymore and can be deleted?
Assuming you're running a *nix system on your VPS, what does running df -h say?
Additionally, you can try getting a list of largest directories/files on your VPS, like so: sudo -s cd / for i in G M K; do du -ah | grep [0-9]$i | sort -nr -k 1; done | head -n 1000 | tac
or just run the latter on your home directory (and don't use sudo in that case, of course.)
Kostas.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org <mailto:tor-relays@lists.torproject.org> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Sun, 11 Aug 2013 14:43:59 +0300 Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
Huh, curious why it fails to write stuff to disk.
Does doing echo "something" > tempfile succeed?
/var/log/tor is hogging diskspace indeed :) perhaps then do cd /var/log/tor sudo rm *.gz
Before deleting you should review the log files to find out what exactly is happening to Tor, that made it produce so much logs. This shouldn't ever happen during normal operation. -- With respect, Roman
On Sun, Aug 11, 2013 at 7:06 PM, Roman Mamedov <rm@romanrm.net> wrote:
On Sun, 11 Aug 2013 14:43:59 +0300 Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
Huh, curious why it fails to write stuff to disk.
Does doing echo "something" > tempfile succeed?
/var/log/tor is hogging diskspace indeed :) perhaps then do cd /var/log/tor sudo rm *.gz
Before deleting you should review the log files to find out what exactly is happening to Tor, that made it produce so much logs. This shouldn't ever happen during normal operation.
That's true. I assumed the juicy stuff would be in notices.log and notices.log.1, but yes, it would make a lot of sense to review the older logs as well. Perhaps Tor is not starting up nicely and is constantly spitting out error messages / warnings.
I checked the old notices.log file. The warning of unable to write just came out from nowhere. The log before the very first warning was my heartbeat data. However, there was something that different than "unable to store router descriptor": Aug 11 06:23:14.000 [warn] Error writing to "/var/lib/tor/cached-microdesc-consensus": No space left on deviceAug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on deviceAug 11 06:23:14.000 [warn] Error writing to "/var/lib/tor/cached-consensus": No space left on deviceAug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on deviceAug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on deviceAug 11 06:23:15.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on deviceAug 11 06:23:15.000 [warn] Unable to store router descriptorAug 11 06:23:15.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on device What's more interesting happened was I checked the new notices.log file again and seems that after Tor opening another new notices.log, everything back to normal. There is only heartbeat information in the new file for the past hours. And I didn't do anything. Tony. From: kostas@jakeliunas.com Date: Sun, 11 Aug 2013 19:28:43 +0300 To: rm@romanrm.net CC: tor-relays@lists.torproject.org Subject: Re: [tor-relays] No disk space for new files created by Tor On Sun, Aug 11, 2013 at 7:06 PM, Roman Mamedov <rm@romanrm.net> wrote: On Sun, 11 Aug 2013 14:43:59 +0300 Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
Huh, curious why it fails to write stuff to disk.
Does doing
echo "something" > tempfile
succeed?
/var/log/tor is hogging diskspace indeed :) perhaps then do
cd /var/log/tor
sudo rm *.gz
Before deleting you should review the log files to find out what exactly is happening to Tor, that made it produce so much logs. This shouldn't ever happen during normal operation. That's true. I assumed the juicy stuff would be in notices.log and notices.log.1, but yes, it would make a lot of sense to review the older logs as well. Perhaps Tor is not starting up nicely and is constantly spitting out error messages / warnings. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
I tend to kill almost all logging and use AvoidDiskWrites 1 (or whatever it is) in torrc. Also your log files will fill up a lot faster if you are a directory server. On 12 August 2013 02:18, TonyXue <tonyxsuper@live.com> wrote:
I checked the old notices.log file.
The warning of unable to write just came out from nowhere. The log before the very first warning was my heartbeat data.
However, there was something that different than "unable to store router descriptor":
Aug 11 06:23:14.000 [warn] Error writing to "/var/lib/tor/cached-microdesc-consensus": No space left on device Aug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on device Aug 11 06:23:14.000 [warn] Error writing to "/var/lib/tor/cached-consensus": No space left on device Aug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on device Aug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on device Aug 11 06:23:15.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on device Aug 11 06:23:15.000 [warn] Unable to store router descriptor Aug 11 06:23:15.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on device
What's more interesting happened was I checked the new notices.log file again and seems that after Tor opening another new notices.log, everything back to normal. There is only heartbeat information in the new file for the past hours. And I didn't do anything.
Tony.
------------------------------ From: kostas@jakeliunas.com Date: Sun, 11 Aug 2013 19:28:43 +0300 To: rm@romanrm.net CC: tor-relays@lists.torproject.org
Subject: Re: [tor-relays] No disk space for new files created by Tor
On Sun, Aug 11, 2013 at 7:06 PM, Roman Mamedov <rm@romanrm.net> wrote:
On Sun, 11 Aug 2013 14:43:59 +0300 Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
Huh, curious why it fails to write stuff to disk.
Does doing echo "something" > tempfile succeed?
/var/log/tor is hogging diskspace indeed :) perhaps then do cd /var/log/tor sudo rm *.gz
Before deleting you should review the log files to find out what exactly is happening to Tor, that made it produce so much logs. This shouldn't ever happen during normal operation.
That's true. I assumed the juicy stuff would be in notices.log and notices.log.1, but yes, it would make a lot of sense to review the older logs as well. Perhaps Tor is not starting up nicely and is constantly spitting out error messages / warnings.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
But will that configuration stop Tor writes the heartbeat information into the notices.log? I need that. Date: Mon, 12 Aug 2013 03:25:06 +0100 From: th6045@gmail.com To: tor-relays@lists.torproject.org Subject: Re: [tor-relays] No disk space for new files created by Tor I tend to kill almost all logging and use AvoidDiskWrites 1 (or whatever it is) in torrc. Also your log files will fill up a lot faster if you are a directory server. On 12 August 2013 02:18, TonyXue <tonyxsuper@live.com> wrote: I checked the old notices.log file. The warning of unable to write just came out from nowhere. The log before the very first warning was my heartbeat data. However, there was something that different than "unable to store router descriptor": Aug 11 06:23:14.000 [warn] Error writing to "/var/lib/tor/cached-microdesc-consensus": No space left on device Aug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on deviceAug 11 06:23:14.000 [warn] Error writing to "/var/lib/tor/cached-consensus": No space left on device Aug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on deviceAug 11 06:23:14.000 [warn] Error closing "/var/lib/tor/cached-microdescs.new": No space left on device Aug 11 06:23:15.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on deviceAug 11 06:23:15.000 [warn] Unable to store router descriptor Aug 11 06:23:15.000 [warn] Error writing to "/var/lib/tor/cached-descriptors.new": No space left on device What's more interesting happened was I checked the new notices.log file again and seems that after Tor opening another new notices.log, everything back to normal. There is only heartbeat information in the new file for the past hours. And I didn't do anything. Tony. From: kostas@jakeliunas.com Date: Sun, 11 Aug 2013 19:28:43 +0300 To: rm@romanrm.net CC: tor-relays@lists.torproject.org Subject: Re: [tor-relays] No disk space for new files created by Tor On Sun, Aug 11, 2013 at 7:06 PM, Roman Mamedov <rm@romanrm.net> wrote: On Sun, 11 Aug 2013 14:43:59 +0300 Kostas Jakeliunas <kostas@jakeliunas.com> wrote:
Huh, curious why it fails to write stuff to disk.
Does doing
echo "something" > tempfile
succeed?
/var/log/tor is hogging diskspace indeed :) perhaps then do
cd /var/log/tor
sudo rm *.gz
Before deleting you should review the log files to find out what exactly is happening to Tor, that made it produce so much logs. This shouldn't ever happen during normal operation. That's true. I assumed the juicy stuff would be in notices.log and notices.log.1, but yes, it would make a lot of sense to review the older logs as well. Perhaps Tor is not starting up nicely and is constantly spitting out error messages / warnings. _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
participants (5)
-
Cassey Jean Claude -
Kostas Jakeliunas -
Roman Mamedov -
Thomas Hand -
TonyXue