As of 11-11 My bbs is just randomly starting to crash, running linux mint, have run console and as daemon, bbs is crashing with no errors, or warning.. no segfaults.. when running from terminal when it does crash you can still type on the CLI but no text is echoed, but the command still goes through..
other than that everything is running fine on the BBS, I built a clean build on 11th and 12th and it is still doing it. I bult with options USE_DOSEMU and RELEASE, I Symlink from my exec dir to the gcc.linux.x64.*.release dirs
Until I can find a remedy to the situation I will have to make watchdog script that greps the pid and restarts the BBS if it finds it has crashed.
Re: random crashes
By: KK4QBN to All on Sun Nov 12 2017 22:41:38
Ok, more on this issue..
Just noticed the crash again, this is the second time I noticed it crash with the SMTP server active and receiving mail from a google server, so for shits and giggles I've disabled the smtp/pop3 lets see how long it stays up now..
As of 11-11 My bbs is just randomly starting to crash, running linux
mint, have run console and as daemon, bbs is crashing with no errors,
or warning.. no segfaults.. when running from terminal when it does
crash you can still type on the CLI but no text is echoed, but the
command still goes through..
What does that mean?
If you're having troubles, I recommend running a debug build (not release) and you could run it under "gdb" to determine why/how/when the process terminates unexpectedly.
Just noticed the crash again, this is the second time I noticed it
crash with the SMTP server active and receiving mail from a google
server, so for shits and giggles I've disabled the smtp/pop3 lets see
how long it stays up now..
What was the last log entry before the "crash"?
Re: random crashes
By: Digital Man to KK4QBN on Sun Nov 12 2017 21:53:23
Just noticed the crash again, this is the second time I noticed it
crash with the SMTP server active and receiving mail from a google
server, so for shits and giggles I've disabled the smtp/pop3 lets see
how long it stays up now..
What was the last log entry before the "crash"?
why "crash" it was a CRASH.. when something is working, then stops working.. it crashes :)
Nov 12 09:31:02 kk4qbn synchronet: mail 0055 SMTP Connection accepted on port 25 from: 209.85.214.65 port 40907
Nov 12 09:31:02 kk4qbn synchronet: mail 0055 SMTP Hostname: mail-it0-f65.google.com
Nov 12 09:31:03 kk4qbn kernel: [11236.358313] sbbs/smtp[11072]: segfault at 2 ip 00007fab3e6dadcc sp 00007faae9be4440 error 4 in libc-2.19.so[7fab3e690000+1a1000]
looking at syslog it does appear to be a segfault..
it did'nt show this in
the terminal ouput.. it would simply "stop working".. or crash.. or however you want to word it..
I cannot find any other received emails, other than ones that were rejected from DNSBL or ip.can to see whether it's just this particular instance only that will do it or if ANY valid incoming email will do it.. I just received email no less than 3 or so days ago.. so it's hard to say..
Okay. I think of a crash as a segfault, GPF, bus error, trap, assertion, etc. If somethign just "exits", it's not really a crash in my book.
Nov 12 09:31:02 kk4qbn synchronet: mail 0055 SMTP Connection accepted
on port 25 from: 209.85.214.65 port 40907
Nov 12 09:31:02 kk4qbn synchronet: mail 0055 SMTP Hostname:
mail-it0-f65.google.com
Nov 12 09:31:03 kk4qbn kernel: [11236.358313] sbbs/smtp[11072]:
segfault at 2 ip 00007fab3e6dadcc sp 00007faae9be4440 error 4 in
libc-2.19.so[7fab3e690000+1a1000]
looking at syslog it does appear to be a segfault..
Good, now we're getting somewhere.
If you could run in gdb and get the backtrace (bt) after that crash, then it would probably take me just a matter of minutes of fix.
Re: random crashes
By: Digital Man to KK4QBN on Sun Nov 12 2017 21:53:23
Just noticed the crash again, this is the second time I noticed it
crash with the SMTP server active and receiving mail from a google
server, so for shits and giggles I've disabled the smtp/pop3 lets see
how long it stays up now..
What was the last log entry before the "crash"?
why "crash" it was a CRASH.. when something is working, then stops working.. it crashes :)
Nov 12 09:31:02 kk4qbn synchronet: mail 0055 SMTP Connection accepted on port 25 from: 209.85.214.65 port 40907
Nov 12 09:31:02 kk4qbn synchronet: mail 0055 SMTP Hostname: mail-it0-f65.google.com
Nov 12 09:31:03 kk4qbn kernel: [11236.358313] sbbs/smtp[11072]: segfault at 2 ip 00007fab3e6dadcc sp 00007faae9be4440 error 4 in libc-2.19.so[7fab3e690000+1a1000]
[1m[34mRe[0m[34m: [1m[36mrandom crashes
mail-it0-f65.google.com
Nov 12 09:31:03 kk4qbn kernel: [11236.358313] sbbs/smtp[11072]:
segfault at 2 ip 00007fab3e6dadcc sp 00007faae9be4440 error 4 in
libc-2.19.so[7fab3e690000+1a1000]
Did you have DEBUG log level enabled at that time? I would expect to see more log entries before the crash. If you could, plese enable Debug log level output as well as the following [Mail] options in sbbs.ini:
- DEBUG_RX_HEADER
- DEBUG_TX
Re: random crashes
By: Digital Man to KK4QBN on Sun Nov 12 2017 21:52:50
As of 11-11 My bbs is just randomly starting to crash, running linux
mint, have run console and as daemon, bbs is crashing with no errors,
or warning.. no segfaults.. when running from terminal when it does
crash you can still type on the CLI but no text is echoed, but the
command still goes through..
What does that mean?
when sbbs console is running either on tty or in a terminal window, when it >would crash the terminal would still work, the command line would.. but the >text typed would not show up, but would still work.. let say after the crash I >would type 'sudo ./sbbs' and sbbs would start up again..
Re: random crashes
By: Digital Man to KK4QBN on Tue Nov 14 2017 13:53:39
[1m[34mRe[0m[34m: [1m[36mrandom crashes
mail-it0-f65.google.com
Nov 12 09:31:03 kk4qbn kernel: [11236.358313] sbbs/smtp[11072]:
segfault at 2 ip 00007fab3e6dadcc sp 00007faae9be4440 error 4 in
libc-2.19.so[7fab3e690000+1a1000]
Did you have DEBUG log level enabled at that time? I would expect to see more log entries before the crash. If you could, plese enable Debug log level output as well as the following [Mail] options in sbbs.ini:
- DEBUG_RX_HEADER
- DEBUG_TX
I had those to enabled, BUT I was runnig release version, with INFORMATIONAL as
my log level, because I've had so little issue with it.
I promise to get it back up and going to give you some info on itl
I know it did'nt happen until I start using the DNSBL, I used almost every >feature. and everytime that google domain would hit it would crash it..
What options do you have in your mail settings? I could maybe set mine
the same and see if I can get same issue. I've not really explored
them all yet.
Options=ALLOW_POP3 | ALLOW_RELAY | ALLOW_SYSOP_ALIASES |
DNSBL_THROTTLE | DNSBL_SPAMHASH | USE_SUBMISSION_PORT | ALLOW_SYSOP_ALIASES
What options do you have in your mail settings? I could maybe set mine
the same and see if I can get same issue. I've not really explored
them all yet.
trncated to fit screen:
Options=DEBUG_RX_BODY | ALLOW_POP3 | ALLOW_RX_BY_NUMBER |
ALLOW_SYSOP_ALIASES | USE_SUBMISSION_PORT | USE_TCP_DNS |
SMTP_AUTH_VIA_IP | RELAY_AUTH_LOGIN | DNSBL_REFUSE | DNSBL_BADUSER |
DNSBL_CHKRECVHDRS | DNSBL-THROTTLE | DNSBL_SPAMHASH
| Sysop: | Winzlo |
|---|---|
| Location: | Minnesota, USA |
| Users: | 11 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 495947:06:35 |
| Calls: | 82 |
| Files: | 1,070 |
| D/L today: |
27 files (11,920K bytes) |
| Messages: | 287,048 |