Crash Report? daemon-core BYOND 515.1606

ID:2870251
 
May 17 2023, 7:53 am (Edited by moderator on May 17 2023, 8:30 am)
Descriptive Problem Summary:

Cannot open port, apparently my host/byondpanel isntructed me to send this message to you guys.


Numbered Steps to Reproduce Problem:
Upgraded from 1603 to 1606 from ByondPanel. Crashed my game and hasn't been able to open port. Reverting the versions also did not work, however I do not think this is the problem. I'm actually REALLY not sure what the problem is as this was just random. I came to think it was just the hosts problem, but I saw this in the error logs: So;

Code Snippet (if applicable) to Reproduce Problem:
Wed May 17 14:40:12 2023
World opened on network port 12117.
Welcome BYOND! (5.0 Beta Version 515.1606)
BUG: Crashing due to an illegal operation!
proc name:
  usr: null
  src:
  call stack:
: ()

Backtrace for BYOND 515.1606 on Linux:
Generated at Wed May 17 14:40:12 2023

DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804b604]
(unknown) ??
 [0xb774f000, 0xb774f410], [0xb774f000, 0xb774f410]
(unknown) ??
libbyond.so [0xb7062000, 0x0], 0x322123
libbyond.so [0xb7062000, 0x0], 0x353554
libbyond.so [0xb7062000, 0x0], 0x35615b
libbyond.so [0xb7062000, 0x0], 0x312654
libbyond.so [0xb7062000, 0x0], 0x312993
libbyond.so [0xb7062000, 0x0], 0x31515d
libbyond.so [0xb7062000, 0x0], 0x3159a6
libbyond.so [0xb7062000, 0x0], 0x30ecfe
libbyond.so [0xb7062000, 0x0], 0x310086
libbyond.so 0x3ab660, 0x3ab6af
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804ace9]
libc.so.6 0x19440, 0x19533 (__libc_start_main)

To help the BYOND developers debug this, please send the above trace as part
of a very detailed bug report: http://www.byond.com/members/?command=view_tracker&tracker=1


DreamDaemon will now produce a file called 'core' that you can send to the
BYOND developers for more analysis.  For instructions, please contact us at
http://www.byond.com/support/


Expected Results:

Actual Results:

Does the problem occur:
Every time? Or how often?
In other games?
In other user accounts?
On other computers?

When does the problem NOT occur?

Did the problem NOT occur in any earlier versions? If so, what was the last version that worked? (Visit http://www.byond.com/download/build to download old versions for testing.) 1603, however there was still crashes there.

Workarounds:
none so far, cannot open any ports.
May 17 2023, 8:44 am
Failure to open ports has nothing to do with a crash. A crash is a crash, but it isn't at all clear that this isn't a problem with the installation.

So far it appears that the problem is happening during world init. If there is an actual bug in play, it could be a problem with your specific source. If so, I need a copy of your source to test.
May 17 2023, 3:01 pm
I see, so far I had to downgrade to 1603 on Byond Panel to get it to work.

However, there is a constant crash error in which, yes you are absolutely right it looks like it has to do with a "SIGTERM".

First time ever coming across this error especially as a new Dev, so I'm alittle bummed out.

Any context on this:

Wed May 17 15:00:23 2023
Dream Daemon: invalid option '-threads'
Wed May 17 15:01:42 2023
Dream Daemon: invalid option '-threads'
Wed May 17 15:02:18 2023
World opened on network port 58471.
Welcome BYOND! (5.0 Beta Version 515.1603)
The BYOND hub reports that port 58471 is reachable.

******************************************
Caught SIGTERM, attempting clean shutdown.

Wed May 17 15:05:31 2023
World opened on network port 42662.
Welcome BYOND! (5.0 Beta Version 515.1600)
The BYOND hub reports that port 42662 is reachable.
May 18 2023, 12:15 am
Sounds like the installation got messed up somehow and it was mixing files from different versions.

As far as SIGTERM, that's a signal coming from the OS. It wouldn't be related to any installation problems. It's something to ask your host about.
May 19 2023, 5:57 am
Thank you! I asked my host and it should hopefully be resolved soon!