Hello..
I haven't been upgrading regularly. The last sucessful build I applied was on June Third at around noon est. I again tried to upgrade on 6-21 and while the build was successfull.. when starting sbbs it crashes and with invalid opcode error.
I am running on ubuntu 18.04.2 32bit
I set loglevel to Debug but nothing helpful is logged in synchronet.log.. however this is logged in syslog at the crash:
bbs kernel: [170891.363698] traps: sbbs/webServer[9392] trap invalid opcode ip:b7cdf8bd sp:b418e83c error:0 in libsbbs.so[b77da000+6a2000]
if I disable webserver in sbbs.ini I get this:
bbs kernel: [171144.758026] traps: sbbs/termServer[12701] trap invalid opcode ip:b7ce18bd sp:b61967cc error:0 in libsbbs.so[b77dc000+6a2000]
If I disble the Terminal Server, then BBS starts.. but without web or terminal services of course.
I have reverted back to prior build for now.
Anything insight would be appreciated.
If it's only the Web Server and Terminal Server that's giving issues, it could be related to TLS (https) and SSH support - so you could try also just disabling those features as a test (not a solution). If the backtrace from gdb shows cryptlib functions in the crashed thread, then that's likely the issue.
Re: invalid opcode after update
By: Digital Man to Rastus on Sat Jun 22 2019 04:04 pm
If it's only the Web Server and Terminal Server that's giving issues, it could be related to TLS (https) and SSH support - so you could try also just disabling those features as a test (not a solution). If the backtrace from gdb shows cryptlib functions in the crashed thread, then that's likely the issue.
I had compiled with a clean build..
Disabling SSH in Terminal Server and TLS in Webserver allowed SBBS to start.
Debug info:
[New Thread 0xb34ffb40 (LWP 20929)]
Thread 4 "sbbs/termServer" received signal SIGILL, Illegal instruction. [Switching to Thread 0xb60ffb40 (LWP 20924)]
0xb7dbc8bd in aes_ecb_encrypt ()
from /sbbs/src/sbbs3/gcc.linux.lib.release/libsbbs.so
(gdb) bt full
#0 0xb7dbc8bd in aes_ecb_encrypt ()
from /sbbs/src/sbbs3/gcc.linux.lib.release/libsbbs.so
No symbol table info available.
#1 0xb60fc900 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Debug info:
[New Thread 0xb34ffb40 (LWP 20929)]
Thread 4 "sbbs/termServer" received signal SIGILL, Illegal instruction.
[Switching to Thread 0xb60ffb40 (LWP 20924)]
0xb7dbc8bd in aes_ecb_encrypt ()
from /sbbs/src/sbbs3/gcc.linux.lib.release/libsbbs.so
(gdb) bt full
#0 0xb7dbc8bd in aes_ecb_encrypt ()
from /sbbs/src/sbbs3/gcc.linux.lib.release/libsbbs.so
No symbol table info available.
#1 0xb60fc900 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Definitely appears to be a cryptlib issue.
You could try getting the previous version of cryptlib (3.4.4) from
cvs: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/3rdp/dist/cryptl ib.zi p?revision=1.5 And overwrite the file of the same name in your
sbbs 3rdp/dist directory.
That should still be compatible with the current sbbs source (I hope).
On 2019 Jun 23 13:18:14, you wrote to Rastus:
Debug info:
[New Thread 0xb34ffb40 (LWP 20929)]
Thread 4 "sbbs/termServer" received signal SIGILL, Illegal instruction.
[Switching to Thread 0xb60ffb40 (LWP 20924)]
0xb7dbc8bd in aes_ecb_encrypt ()
from /sbbs/src/sbbs3/gcc.linux.lib.release/libsbbs.so
(gdb) bt full
#0 0xb7dbc8bd in aes_ecb_encrypt ()
from /sbbs/src/sbbs3/gcc.linux.lib.release/libsbbs.so
No symbol table info available.
#1 0xb60fc900 in ?? ()
No symbol table info available.
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
Definitely appears to be a cryptlib issue.
i posted about a maybe similar problem i'm seeing with letsencrypt in sync_programming...
You could try getting the previous version of cryptlib (3.4.4) from cvs: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/3rdp/dist/cryptl ib.zi p?revision=1.5 And overwrite the file of the same name in your sbbs 3rdp/dist directory.
will that affect the patch files that are also used on the cryptlib sources?
That should still be compatible with the current sbbs source (I hope).
i'm fairly sure that that's what i was using before updating to 3.4.5... i'm guessing that most folks running 3.17c were, too...
Definitely appears to be a cryptlib issue.
i posted about a maybe similar problem i'm seeing with letsencrypt in
sync_programming...
You were seeing a TLS client exception, not a crash, so not really that similar.
will that affect the patch files that are also used on the cryptlib
sources?
It might. Some of the patches may fail to apply which may mean the build with fail, I'm not sure.
Re: invalid opcode after update
By: Rastus to Digital Man on Sun Jun 23 2019 12:10 pm
Definitely appears to be a cryptlib issue. You could try getting the previous version of cryptlib (3.4.4) from cvs: http://cvs.synchro.net/cgi-bin/viewcvs.cgi/*checkout*/3rdp/dist/cryptlib.z ip?revision=1.5 And overwrite the file of the same name in your sbbs 3rdp/dist directory.
That should still be compatible with the current sbbs source (I hope).
It might. Some of the patches may fail to apply which may mean the build with fail, I'm not sure.
Re: invalid opcode after update
By: Digital Man to mark lewis on Sun Jun 23 2019 01:41 pm
It might. Some of the patches may fail to apply which may mean the
build with fail, I'm not sure.
Re: invalid opcode after update
By: Rastus to Digital Man on Sun Jun 23 2019 09:03 pm
I believe I found this issue that was causing my problems with the new TLS stuff... the gcc.linux..... directory in the 3rdp were not being removed during a clean build.. I also removed the 3rdp src directory and then rebuilt.. I think it worked, but I'm getting other errors this evening due to ongoing word with smb etc...
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 30:17:40 |
| Calls: | 508 |
| Messages: | 220008 |