polyanthum out of disk space on root filesystem

The log file at /home/bridgestrap/logs/bridgestrap.log has run away and grown to 28G, filling up all available space on polyantum's root filesystem.

assigned to @lavamind

I've stopped bridgestrap.service and truncated the log file's first 10G using

fallocate -c -o 0 -l 10G /home/bridgestrap/logs/bridgestrap.log

@anarcat Do you know if this could be related to the work being done as part of #41613 (closed) ?

The log seems to have been filled with lines like this:

2024/06/18 12:39:25 Discarding event because we're not testing bridges.

that is likely, @meskio any idea what's going on here? your log files are going nuts on polyanthum...

Those are tor events received when we are not testing bridges. I wonder why are we getting so many now, what has changed.

I don't see anything else interesting in the logs. I restarted the service while I investigate more the code and consider if I need a version that publishes what event is actually arriving.

changed the severity to High - S2

changed the incident status to Acknowledged

assigned to @anarcat and unassigned @lavamind

added Needs Information label

assigned to @meskio and unassigned @anarcat

After removing the log file and a restart things are looking good. I'll improve the log situation of bridgestrap in: tpo/anti-censorship/bridgestrap#43 (closed)

I think this issue can be closed.

thanks for the prompt followup!

closed

changed the incident status to Resolved by closing the incident