Re: [tor-relays] No disk space for new files created by Tor

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: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@xxxxxxxxxxxxxx
Date: Sun, 11 Aug 2013 19:28:43 +0300
To: rm@xxxxxxxxxxx
CC: tor-relays@xxxxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxx> wrote:

On Sun, 11 Aug 2013 14:43:59 +0300
Kostas Jakeliunas <kostas@xxxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxxx https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays