What do you have set for Log notice in /etc/tor/torrc? I run a tor relay without problems on 6.7 and use: Log notice syslog
On Sun, 28 Jun 2020 at 13:59, Salvatore Cuzzilla <salvat...@cuzzilla.org> wrote: > the issue is temporary “solved": > > 03:42:36 -ksh ToTo@APU2c4 ~ $ doas cat /etc/tor/torrc | egrep "^Log " > Log debug file /dev/null > Log info file /dev/null > Log notice file /dev/null > > it’s confirmed that something is not going well with the logs handling ... > > > > On 25 Jun 2020, at 15:39, Stuart Henderson <s...@spacehopper.org> wrote: > > On 2020/06/25 14:59, Salvatore Cuzzilla wrote: > > > > Unfortunately the only think i know for sure is that the /var folder is > > constantly loosing free space & When i restart tor it gets back to > > normal. I can't (I don't know how to) figure out the involved files ... > > > > "du" is not really helping nor "fstat" ... Is there anything else > > i could test? > > du won't show size of an unlinked file. > > fstat won't show filenames but will show inode numbes. If it is from a > file that existed at startup and was then moved away, you could capture > inode numbers of all files on the filesystem when starting (find /var > -ls, the first number is the inode number), then compare with the INUM > column in fstat. > > Or, if you change logs to syslog, and that fixes the problem, you have > your answer... > > > > On 25.06.2020 09:29, Stuart Henderson wrote: > >> On 2020-06-24, Salvatore Cuzzilla <salvat...@cuzzilla.org> wrote: > >>> After few attempts, I can't still don't understand what's going on > >>> it seems that the only way to free up the /var folder is to restart the > >>> tor's daemon. > >>> > >>> "pkill -HUP -u _tor -U _tor -x tor" didn't help ... > >>> > >>> Other ideas? > >> > >> Did you figure out what files are involved? > >> > >> If it's logs, use syslog instead. > >> > > > > ------- > > :wq, > > Salvatore. > > >
