Hey Rob,

The Segfault, Crashing I messaged you about a few days ago has went away when I took two DNSBL options out of sbbs.ini:

DNSBL_SPAMHASH | DNSBL_THROTTLE

Took those out and have'nt had any type of segfault in 2 days now, running either in daemon or terminal mode.

but have a new one on you.

getting this when first initilizing when starting up fresh, not recycling.

11/21 21:49:21 term Synchronet Terminal Server Version 3.17 Revision A
11/21 21:49:21 term Compiled Nov 12 2017 18:16:59 with GCC 4.9.2
11/21 21:49:21 term Initializing on Tue Nov 21 21:49:21 2017 with options: 183a 11/21 21:49:21 term Loading configuration files from /sbbs/ctrl/
11/21 21:49:21 term Configured time zone (AST, 0x40F0, offset: -240) does not match system-local time zone offset: -300


Have made no time changes in my system, I'm set to EDT.

Thanks.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA

Re: Segfault/Crash
By: KK4QBN to Digital Man on Tue Nov 21 2017 10:04 pm

Hey Rob,

The Segfault, Crashing I messaged you about a few days ago has went away when I took two DNSBL options out of sbbs.ini:

DNSBL_SPAMHASH | DNSBL_THROTTLE

Took those out and have'nt had any type of segfault in 2 days now, running either in daemon or terminal mode.

Unfortunately, that doesn't really help. Can you re-enable the configuration you had to reproduce the problem and provide a backtrace from gdb? That'd help. :-)

but have a new one on you.

getting this when first initilizing when starting up fresh, not recycling.

11/21 21:49:21 term Synchronet Terminal Server Version 3.17 Revision A
11/21 21:49:21 term Compiled Nov 12 2017 18:16:59 with GCC 4.9.2
11/21 21:49:21 term Initializing on Tue Nov 21 21:49:21 2017 with options: 183a 11/21 21:49:21 term Loading configuration files from /sbbs/ctrl/
11/21 21:49:21 term Configured time zone (AST, 0x40F0, offset: -240) does not match system-local time zone offset: -300

Have made no time changes in my system, I'm set to EDT.

Synchronet seems to think you have SCFG->System->Local Time Zone set to "AST". You want to double-check that?

digital man

Synchronet "Real Fact" #72:
Synchronet CIOXTRN (created by Deuce) is a 32-bit replacement for DOORWAY. Norco, CA WX: 77.1øF, 22.0% humidity, 0 mph SW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Segfault/Crash
By: Digital Man to KK4QBN on Tue Nov 21 2017 22:06:35

Unfortunately, that doesn't really help. Can you re-enable the configuration you had to reproduce the problem and provide a backtrace from gdb? That'd help. :-)

shucks :)

Was'nt hopeing not to.. but if it gets it fixed it'll be worth it.

Have made no time changes in my system, I'm set to EDT.

Synchronet seems to think you have SCFG->System->Local Time Zone set to "AST". You want to double-check that?

no, it's edt.. I promise.. :)

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA

On 2017 Nov 22 09:10:54, you wrote to Digital Man:

Synchronet seems to think you have SCFG->System->Local Time Zone set
to "AST". You want to double-check that?

no, it's edt.. I promise.. :)

FWIW: it should be EST (UTC-0500) now that the time has sprung back to Eastern Standard Time... EDT (UTC-0400) is Eastern Daylight [saving] Time ;)

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it wrong...
... Cleaned desk and found key board. Now I can answer E-Mail
---
* Origin: (1:3634/12.73)
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Segfault/Crash
By: mark lewis to KK4QBN on Wed Nov 22 2017 11:51:24

no, it's edt.. I promise.. :)

FWIW: it should be EST (UTC-0500) now that the time has sprung back to Eastern Standard Time... EDT (UTC-0400) is Eastern Daylight [saving] Time ;)

haha.. well never thought of that.. (duh).. and it is when it happened.. I had thought (for many years now) and have had it set up for EDT all those years that if ou set it to EDT, it will allow for the time switch, and only set to EST if not following dst standards.. I'll switch to est and see what happens..

thank you.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA

Re: Segfault/Crash
By: Digital Man to KK4QBN on Tue Nov 21 2017 10:06 pm

Re: Segfault/Crash
By: KK4QBN to Digital Man on Tue Nov 21 2017 10:04 pm

Hey Rob,

The Segfault, Crashing I messaged you about a few days ago has went away when I took two DNSBL options out of sbbs.ini:

DNSBL_SPAMHASH | DNSBL_THROTTLE

Took those out and have'nt had any type of segfault in 2 days now, running either in daemon or terminal mode.

Unfortunately, that doesn't really help. Can you re-enable the configuration you had to reproduce the problem and provide a backtrace from gdb? That'd help. :-)

but have a new one on you.

getting this when first initilizing when starting up fresh, not recycling.

11/21 21:49:21 term Synchronet Terminal Server Version 3.17 Revision A 11/21 21:49:21 term Compiled Nov 12 2017 18:16:59 with GCC 4.9.2
11/21 21:49:21 term Initializing on Tue Nov 21 21:49:21 2017 with options: 183a 11/21 21:49:21 term Loading configuration files from /sbbs/ctrl/
11/21 21:49:21 term Configured time zone (AST, 0x40F0, offset: -240) does not match system-local time zone offset: -300

Have made no time changes in my system, I'm set to EDT.

Synchronet seems to think you have SCFG->System->Local Time Zone set to "AST". You want to double-check that?

Okay, but wouldn't it be EST (standard time) now?

But 0x40f0 is definitely "AST" (from smbdefs.h):
#define AST 0x40F0 /* Atlantic (-04:00) */
#define EDT 0xC12C /* Eastern (-04:00) */

They're both -240 (-4:00) from UTC, but daylight saving time is not in effect right now (here in the U.S. at least), so perhaps just changing that to EDT will fix it (or enable Auto-DST).

digital man

This Is Spinal Tap quote #4:
David St. Hubbins: He died in a bizarre gardening accident...
Norco, CA WX: 81.7øF, 23.0% humidity, 1 mph WSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: Segfault/Crash
By: Digital Man to KK4QBN on Wed Nov 22 2017 18:48:03

They're both -240 (-4:00) from UTC, but daylight saving time is not in effect right now (here in the U.S. at least), so perhaps just changing that to EDT will fix it (or enable Auto-DST).

Yes, Mark pointed that earlier.. I presume it's just one of those dug moments, because it started happening when time went back.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA

On Tue, 21 Nov 2017 22:04:02 -0400, "KK4QBN" <kk4qbn@VERT/KK4QBN>
wrote:

Hey Rob,

The Segfault, Crashing I messaged you about a few days ago has went away when I
took two DNSBL options out of sbbs.ini:

DNSBL_SPAMHASH | DNSBL_THROTTLE

I have DNSBL_SPAMHASH configured but had no problems. I didn't have DNSBL_THROTTLE so I just added it to see if I can also get the
segfault.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: Re: Segfault/Crash
By: Nelgin to KK4QBN on Sun Nov 26 2017 09:00:15

I have DNSBL_SPAMHASH configured but had no problems. I didn't have DNSBL_THROTTLE so I just added it to see if I can also get the
segfault.

Have'nt had one since I took both out, I need to really recompile debug versions and try to get it to happen again. It's something to do with an email coming from googles servers, thats the only time it ever crashed. when I took those two options outm the email from that server came through. so Even If I do re-create the scenario for it to happen, the perfect storm may never come back.

and truthfully the system has been running too good for me to want to bring down for the moment.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA

On Mon, 27 Nov 2017 20:12:47 -0500, "KK4QBN" <kk4qbn@VERT/KK4QBN>
wrote:

Re: Re: Segfault/Crash
By: Nelgin to KK4QBN on Sun Nov 26 2017 09:00:15

I have DNSBL_SPAMHASH configured but had no problems. I didn't have DNSBL_THROTTLE so I just added it to see if I can also get the
segfault.

Have'nt had one since I took both out, I need to really recompile debug >versions and try to get it to happen again. It's something to do with an email >coming from googles servers, thats the only time it ever crashed. when I took >those two options outm the email from that server came through. so Even If I do
re-create the scenario for it to happen, the perfect storm may never come back.

and truthfully the system has been running too good for me to want to bring >down for the moment.

I double checked and I did have DNSBL_THROTTLE already buried in my
list of options. Would be interesting to see what that email from the
Google servers consists of that would cause the fault.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com

Re: Re: Segfault/Crash
By: Nelgin to All on Tue Nov 28 2017 01:30:22

I double checked and I did have DNSBL_THROTTLE already buried in my
list of options. Would be interesting to see what that email from the Google servers consists of that would cause the fault.

Yeah, it would be.. and afaik it is not logged, I was running in terminal mode every time so none of the output was logged, it may still be around here on the system somewhere but I need to try to replicate the issue again, and don't know If that will ever happen.

--

Tim Smith (KK4QBN)
KK4QBN BBS

---
* Synchronet * KK4QBN BBS - kk4qbn.com - kk4qbn.synchro.net - Chatsworth GA USA

On Tue, 28 Nov 2017 11:48:34 -0500, "KK4QBN" <kk4qbn@VERT/KK4QBN>
wrote:

Re: Re: Segfault/Crash
By: Nelgin to All on Tue Nov 28 2017 01:30:22

I double checked and I did have DNSBL_THROTTLE already buried in my
list of options. Would be interesting to see what that email from the Google servers consists of that would cause the fault.

Yeah, it would be.. and afaik it is not logged, I was running in terminal mode >every time so none of the output was logged, it may still be around here on the
system somewhere but I need to try to replicate the issue again, and don't know
If that will ever happen.

If you run in terminal mode then just redirect the output to a file
and then you can tail -f the file if you want to see what is happening
real time.

Another option would be to run tcpdump on port 25 and capture any
incoming packets. It may be possible to reconstruct the offending
email if/when it crashes from the data load in the packets.

Yet one final option might be to attach strace to the process but that
is going to generate heaps load of data, most of which you wouldn't
want but it can be good for tracking down when in a program a segfault
occurs.

Finally finally, check your ulimit -c is unlimited, if it's set to 0
then no core files will be created. A core might be useful if the seg
fault causes a core dump, in which case it can be analyzed with gdb
after the fact.

Of course, I might be teaching you how to suck eggs here, but just in
case, those are some options I would look at.

---
þ Synchronet þ End Of The Line BBS - endofthelinebbs.com