So, I'm not really sure if anybody is following this any more or not, but I managed (with the help of Cjammer) to narrow down exactly what is causing the crashes that are still occurring on my OBSD 5.6 build of Synchronet 3.16. It seems that not only is a QWK download a requisite, but that the scanned rooms also contain usenet groups. I'm still not able to locate a core file, and the required changes to allow a core dump file hasn't given me anything to work with yet, for some reason, but I'll look over those instructions and see if there's anything that I've missed again here.
One thought that comes to mind is that the usenet groups often end up corrupted in the whereabouts of these crashes. I'm not certain if it happens before or after... Something leads me to believe that it's before, as I've stumbled upon those corrupt rooms a few times [I believe out of nowhere without a recent crash] and had to run fixsmb on them after noticing with a normal message scan. It's been awhile, though, and I could be misremembering this.
So for now the crashes are 'fixed' by not having usenet groups in the user's message scan config for qwk messages. I'd really like something better than that, if possible, though. Any suggestions?
TIA

-D/K

---
Borg Burgers: We do it our way; your way is irrelevant.
þ Synchronet þ Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

Re: OpenBSD Synchronet crashes
By: Khelair to All on Sat May 02 2015 09:55 am

So, I'm not really sure if anybody is following this any more or not, but I managed (with the help of Cjammer) to narrow down exactly what is causing the crashes that are still occurring on my OBSD 5.6 build of Synchronet 3.16. It seems that not only is a QWK download a requisite, but that the scanned rooms also contain usenet groups. I'm still not able to locate a core file, and the required changes to allow a core dump file hasn't given me anything to work with yet, for some reason, but I'll look over those instructions and see if there's anything that I've missed again here.
One thought that comes to mind is that the usenet groups often end up corrupted in the whereabouts of these crashes. I'm not certain if it happens before or after... Something leads me to believe that it's before, as I've stumbled upon those corrupt rooms a few times [I believe out of nowhere without a recent crash] and had to run fixsmb on them after noticing with a normal message scan. It's been awhile, though, and I could be misremembering this.
So for now the crashes are 'fixed' by not having usenet groups in the user's message scan config for qwk messages. I'd really like something better than that, if possible, though. Any suggestions?

Yes, please provide a backtrace of the crash.

digital man

Synchronet "Real Fact" #49:
JAM and Squish were considered before developing Synchronet Message Base format.
Norco, CA WX: 83.0øF, 26.0% humidity, 9 mph ESE wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net