I'm sorry if this is totally useless. I haven't caught up here yet, and I don't know if there's more information about how I can go about forcing the core dumps that aren't happening any more, but I just got another segfault, this time luckily while I was at the terminal, so I was able to verify better the fact that this occurred within a short amount of time of what the console log, at the very least, specified:

12/18 13:31:22 term Node 2 Telnet <no name> [119.18.109.39]
12/18 13:31:57 term 0044 Telnet connection accepted from: 201.187.106.155 port 3672
12/18 13:31:57 term 0044 Hostname: <no name>
12/18 13:31:57 term Node 3 constructor using socket 44 (settings=8012)
12/18 13:31:57 term Node 3 temporary file directory: /sbbs/node3/temp/
12/18 13:31:57 term Node 3 !ERROR -1 (54) getting address/port
12/18 13:31:57 term 0044 Node 3 !Initialization failure
12/18 13:31:57 term Terminal Server !ERROR 32 sending on socket 44
[Threads: 18 Sockets: 33 Clients: 3 Served: 110 Errors: 3] (?=Help): Segmentation fault

As you can see, the last entry is @ 13:31 today... The crash happened at approximately 13:33-13:34, so there is a chance that this has something to do with the debauchery.
I'll try to make sure that I get caught up in this sub-board right away so that I'm not pointlessly spamming this shit if it's completely unnecessary until I get other debugging data collection methods in place.
TIA, and sorry if this is a wasted poast right now.

---
þ Synchronet þ Tinfoil Te

Re: more crap before I've even caught up on OBSD Synchronet crashes :|
By: Khelair to All on Thu Dec 18 2014 01:35 pm

I'm sorry if this is totally useless. I haven't caught up here yet, and
I don't know if there's more information about how I can go about forcing the core dumps that aren't happening any more, but I just got another segfault, this time luckily while I was at the terminal, so I was able to verify better the fact that this occurred within a short amount of time of what the console log, at the very least, specified:

12/18 13:31:22 term Node 2 Telnet <no name> [119.18.109.39]
12/18 13:31:57 term 0044 Telnet connection accepted from: 201.187.106.155 port 3672
12/18 13:31:57 term 0044 Hostname: <no name>
12/18 13:31:57 term Node 3 constructor using socket 44 (settings=8012)
12/18 13:31:57 term Node 3 temporary file directory: /sbbs/node3/temp/
12/18 13:31:57 term Node 3 !ERROR -1 (54) getting address/port

Since I don't run OpenBSD, I can't tell you what error 54 is. Check your /usr/include/errno.h (or similarly named file) for the value 54 and what error macro/description is associated with that value. That might provide the necessary clue.

12/18 13:31:57 term 0044 Node 3 !Initialization failure
12/18 13:31:57 term Terminal Server !ERROR 32 sending on socket 44
[Threads: 18 Sockets: 33 Clients: 3 Served: 110 Errors: 3] (?=Help): Segmentation fault

It's possible that the initialization failure is not handled gracefully and that the root-cause is that "ERROR -1 (54) getting address/port". I'm assuming this doesn't happen for *every* Telnet connection?

digital man

Synchronet "Real Fact" #23:
1584 Synchronet BBS Software registrations were sold between 1992 and 1996. Norco, CA WX: 56.7øF, 69.0% humidity, 3 mph ESE wind, 0.00 inches rain/24hrs ---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: more crap before I've even caught up on OBSD Synchronet crashes :|
By: Digital Man to Khelair on Thu Dec 18 2014 16:48:49

12/18 13:31:57 term Node 3 !ERROR -1 (54) getting address/port

Since I don't run OpenBSD, I can't tell you what error 54 is. Check your /usr/include/errno.h (or similarly named file) for the value 54 and what error macro/description is associated with that value. That might provide the necessary clue.

12/18 13:31:57 term Terminal Server !ERROR 32 sending on socket 44
[Threads: 18 Sockets: 33 Clients: 3 Served: 110 Errors: 3]
(?=Help): Segmentation fault

It's possible that the initialization failure is not handled gracefully and that the root-cause is that "ERROR -1 (54) getting address/port".
I'm assuming this doesn't happen for *every* Telnet connection?

Okay, so error 54 is ECONNRESET (Connection reset by peer), which I'll do more correlation on.
Thirty-two, if that is a non-Synchronet error, on BSD, is EPIPE/broken pipe.

---
þ Synchronet þ Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

Re: more crap before I've even caught up on OBSD Synchronet crashes :|
By: Khelair to Digital Man on Thu Dec 18 2014 09:22 pm

Re: more crap before I've even caught up on OBSD Synchronet crashes :|
By: Digital Man to Khelair on Thu Dec 18 2014 16:48:49

12/18 13:31:57 term Node 3 !ERROR -1 (54) getting address/port

Since I don't run OpenBSD, I can't tell you what error 54 is. Check your /usr/include/errno.h (or similarly named file) for the value 54 and what error macro/description is associated with that value. That might provide the necessary clue.

12/18 13:31:57 term Terminal Server !ERROR 32 sending on socket 44
[Threads: 18 Sockets: 33 Clients: 3 Served: 110 Errors: 3]
(?=Help): Segmentation fault

It's possible that the initialization failure is not handled
gracefully and that the root-cause is that "ERROR -1 (54) getting address/port". I'm assuming this doesn't happen for *every* Telnet connection?

Okay, so error 54 is ECONNRESET (Connection reset by peer), which I'll do more correlation on.
Thirty-two, if that is a non-Synchronet error, on BSD, is EPIPE/broken pipe.

Yes, the 32 is a non-Synchronet error. So these errors make sense if the connecting client immediately disconnects after the connection was accepted. I tried to reproduce the crash here on Windows by simulating that error "getting address/port" code path, but it did not crash. A crash callstack would be helpful.

digital man

Synchronet "Real Fact" #57:
The last version of Synchronet to run on MS-DOS and OS/2 was v2.30c (1999). Norco, CA WX: 52.1øF, 83.0% humidity, 0 mph NW wind, 0.00 inches rain/24hrs
---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

El 19/12/14 a las 02:22, Khelair escibió:

Re: more crap before I've even caught up on OBSD Synchronet crashes :|
By: Digital Man to Khelair on Thu Dec 18 2014 16:48:49

12/18 13:31:57 term Node 3 !ERROR -1 (54) getting address/port

Since I don't run OpenBSD, I can't tell you what error 54 is. Check your /usr/include/errno.h (or similarly named file) for the value 54 and what error macro/description is associated with that value. That might provide
the necessary clue.

12/18 13:31:57 term Terminal Server !ERROR 32 sending on socket 44
[Threads: 18 Sockets: 33 Clients: 3 Served: 110 Errors: 3]
(?=Help): Segmentation fault

It's possible that the initialization failure is not handled gracefully and that the root-cause is that "ERROR -1 (54) getting address/port". I'm assuming this doesn't happen for *every* Telnet connection?

Okay, so error 54 is ECONNRESET (Connection reset by peer), which I'll do more correlation on.
Thirty-two, if that is a non-Synchronet error, on BSD, is EPIPE/broken pipe.

---
� Synchronet � Tinfoil Tetrahedron BBS telnet://tinfoil.synchro.net

can you run with gdb in bsd? and get a backtrace?

Re: Re: more crap before I've even caught up on OBSD Synchronet crashes:|
By: Ragnarok to Khelair on Sun Dec 21 2014 12:09:47

can you run with gdb in bsd? and get a backtrace?

I actually did manage to get ahold of one. Right before my system got completely hosed due to upgrading issues... I figured I'd upgrade, try another attempt at compiling from source, and see if that fixed things before I bitched and whined more. Ended up having to reinstall everything on the machine and restore the BBS from backup. It's a fresh compile of the most recent code, so I'm hoping that this one isn't going to have the same issues. If it does, I will be getting a debug with backtrace now that I've taught myself what it entails, though.

---