Descriptive Problem Summary: Live server crashed. Unsure why, just posting the trace as requested.
Does the problem occur:
This is the first time I've seen a crash on the current stable. Although there have been hangs, but no error logs to work with in those cases. Recent changes to the game code are unlikely to have triggered this.
BUG: Crashing due to an illegal operation!
Backtrace for BYOND 514.1585 on Linux:
Generated at Sat Feb 25 13:11:58 2023
DreamDaemon [0x8048000, 0x0], [0x8048000, 0x804bd94]
libbyond.so [0xf78ac000, 0x0], 0x23e480
linux-gate.so.1 [0xf7f38000, 0xf7f38b70], [0xf7f38000, 0xf7f38b70]
libbyond.so [0xf78ac000, 0x0], 0x23e480
libbyond.so [0xf78ac000, 0x0], 0x24189c
libbyond.so [0xf78ac000, 0x0], 0x23efd7
libbyond.so [0xf78ac000, 0x0], 0x23f24e
libbyond.so [0xf78ac000, 0x0], 0x23f4f4
libbyond.so [0xf78ac000, 0x0], 0x282998
libbyond.so [0xf78ac000, 0x0], 0x32f2a7
libbyond.so [0xf78ac000, 0x0], 0x33649b
libbyond.so [0xf78ac000, 0x0], 0x33660b
libbyond.so [0xf78ac000, 0x0], 0x241880
libbyond.so [0xf78ac000, 0x0], 0x23efd7
libbyond.so [0xf78ac000, 0x0], 0x23f24e
libbyond.so [0xf78ac000, 0x0], 0x23f4f4
libbyond.so [0xf78ac000, 0x0], 0x282998
libbyond.so [0xf78ac000, 0x0], 0x32f2a7
libbyond.so [0xf78ac000, 0x0], 0x33649b
libbyond.so [0xf78ac000, 0x0], 0x33660b
libbyond.so [0xf78ac000, 0x0], 0x241880
libbyond.so [0xf78ac000, 0x0], 0x23efd7
libbyond.so [0xf78ac000, 0x0], 0x23f24e
libbyond.so [0xf78ac000, 0x0], 0x23f4f4
libbyond.so [0xf78ac000, 0x0], 0x282998
libbyond.so [0xf78ac000, 0x0], 0x32f2a7
libbyond.so [0xf78ac000, 0x0], 0x33649b
libbyond.so [0xf78ac000, 0x0], 0x33660b
libbyond.so [0xf78ac000, 0x0], 0x241880
libbyond.so [0xf78ac000, 0x0], 0x23efd7
libbyond.so [0xf78ac000, 0x0], 0x23f24e
libbyond.so [0xf78ac000, 0x0], 0x23f4f4
libbyond.so [0xf78ac000, 0x0], 0x282998
libbyond.so [0xf78ac000, 0x0], 0x32f2a7
libbyond.so [0xf78ac000, 0x0], 0x33649b
libbyond.so [0xf78ac000, 0x0], 0x33660b
libbyond.so [0xf78ac000, 0x0], 0x241880
libbyond.so [0xf78ac000, 0x0], 0x23efd7
libbyond.so [0xf78ac000, 0x0], 0x23f24e
libbyond.so [0xf78ac000, 0x0], 0x23f4f4
libbyond.so [0xf78ac000, 0x0], 0x282998
libbyond.so [0xf78ac000, 0x0], 0x32f2a7
libbyond.so [0xf78ac000, 0x0], 0x33649b
libbyond.so [0xf78ac000, 0x0], 0x33660b
libbyond.so [0xf78ac000, 0x0], 0x241880
libbyond.so [0xf78ac000, 0x0], 0x23efd7
libbyond.so [0xf78ac000, 0x0], 0x23f24e
libbyond.so [0xf78ac000, 0x0], 0x23f4f4
libbyond.so [0xf78ac000, 0x0], 0x269e2b
libbyond.so [0xf78ac000, 0x0], 0x27eb97
Recent proc calls:
/world/Error
/mob/player/proc/SaveClientData
/mob/player/proc/HarvestData
/mob/player/HarvestData
/mob/player/HarvestData
/mob/player/HarvestData
/mob/player/proc/SaveHarvest
/mob/player/proc/SaveCharacter
/mob/proc/calcManaMax
/mob/proc/calcHealth
/mob/proc/calcStats
/HUD/proc/updateMana
/HUD/proc/updateHealth
/mob/proc/UpdateHealthBar
/HUD/proc/update_all
/regex/proc/Replace
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
ID:2856988
Feb 25 2023, 2:31 pm (Edited on Feb 25 2023, 2:36 pm)
|
|||||||||||||
| |||||||||||||
It's presence in the backtrace would suggest a crash happened during a system call.
the SaveClientData() in the proc trace suggests this might have happened while writing to disk, which involves system calls.
byond might not be handling some error response during a disk operation, but if so, said error response might be something for you to look into, make sure the disk(s) aren't in a prefailure state just to be sure.