<html><head></head><body> I am running two relays and the error message is the same for both:<div><br></div><div>Mar 30 08:13:01 freebsd kernel: pod 1745 (tor) , jid 0 , uid 256, was killed: out of swap space</div><div><br></div>If I run <div># dd if=/dev/zero of=/usr/swap0 bs=1m count=512</div><div><br></div><div>#chmod 0600 /usr/swap0</div><div><br></div>#swapon -aL <div><br></div><div>Will that fix the error above? </div><div><br></div><div>Thanks! </div><div><br></div><div><caret></caret><br><div><div><div><br></div><div id="protonmail_mobile_signature_block"><div>Sent from ProtonMail for iOS</div></div> <div><br></div><div><br></div>On Tue, Mar 30, 2021 at 1:31 AM, Scott Bennett <<a href="mailto:bennett@sdf.org" class="">bennett@sdf.org</a>> wrote:<blockquote class="protonmail_quote" type="cite"> xplato <xplato@protonmail.com> wrote:<br><br>> I am a bit of a noob here so please bear with me. I ran a relay using Ubuntu with very few issues however I decide to add an additional relay and decided to use FreeBSD. They will only run for around 18 hours and then they shut down. I have adjust the torrc file every way I know how and increased the Max vnodes thinking this may have been my issue. I can post the sysrc and torrc if needed. Anyone that might help me figure this out I would be grateful otherwise I am going to reluctantly move them both back to Ubuntu.<br>><br> Thanks for attempting to run a relay in a diversifying environment.<br>Unfortunately, your timing has left you high and dry. What is happening<br>is not your fault. Both 0.4.5.7 and 0.4.6.1-alpha have a fatal bug. I<br>don't know which version of tor introduced it because I have been running<br>0.4.5.2-alpha until a few days ago, when I "upgraded" to 0.4.6.1-alpha.<br>That crashed in under 24 hours twice, so I switched to the allegedly<br>"stable" version, 0.4.5.7 only to have it crash the same way in about 12<br>or 13 hours. Also, 0.4.6.1-alpha was filling its notice-level log file<br>with many bug messages the whole time it was running. I posted a message<br>on this list about it, including the last few hours of the log up through<br>the crash messages. At the crash, the console log (also in /var/log/messages)<br>had a message like this.<br><br>Mar 27 18:29:26 hellas kernel: pid 17047 (tor), jid 0, uid 256: exited on signal 6<br><br> After the second crash I made the switch mentioned above. It has been<br>crashing ever since, and I am getting very tired of discovering that it has<br>been down for several hours. There have been no responses to my earlier<br>posting, but your query is on the same topic, if a different Subject: line,<br>so I am replying.<br> This sort of thing has not hit me in tor in many years, and I hope the<br>tor project developers will fix it ASAP. My suggestion is that you hold<br>off a bit and try again once the bug has been squashed. Alternatively, if<br>you a different BSD system (i.e., DragonflyBSD, NetBSD, or OpenBSD), running<br>your relay on that system would help diversify the systems running relays<br>as much as, or more than, running it on FreeBSD. IOW, it depends on how<br>urgently you want to get a relay up and running vs. your level of patience<br>to wait for a bug fix. Like I wrote above, this situation hardly ever<br>happens, so if you can be patient, it may be fixed within a few days.<br><br><br> Scott Bennett, Comm. ASMELG, CFIAG<br>**********************************************************************<br>* Internet: bennett at sdf.org *xor* bennett at freeshell.org *<br>*--------------------------------------------------------------------*<br>* "A well regulated and disciplined militia, is at all times a good *<br>* objection to the introduction of that bane of all free governments *<br>* -- a standing army." *<br>* -- Gov. John Hancock, New York Journal, 28 January 1790 *<br>**********************************************************************<br></blockquote><div><br></div><div><br></div></div></div></div></body></html>