Just a sample of the Echomail archive
[ << oldest | < older | list | newer > | newest >> ]
|  Message 32547  |
|  Nigel Reed to GitLab note in main/sbbs  |
|  event thread chucked up a core dump  |
|  04 Oct 25 23:09:11  |
 TZUTC: -0700 MSGID: 58672.sync_sys@1:103/705 2d4826b7 PID: Synchronet 3.21a-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 TID: SBBSecho 3.30-Linux master/88b423313 Sep 29 2025 GCC 12.2.0 BBSID: VERT CHRS: ASCII 1 FORMAT: flowed https://gitlab.synchro.net/main/sbbs/-/issues/981#note_7705 Not sure if this would explain it: Corefile was created Oct 3 16:04 ``` Oct 3 16:03:13 bbs synchronet: term Recycle semaphore file (/sb s/ctrl/recycle) detected Oct 3 16:03:13 bbs synchronet: term Waiting for events thread to terminate... Oct 3 16:03:13 bbs synchronet: term Terminal Server output thread terminated (sent 184611 bytes in 2455 blocks, 75 average, 0 short) Oct 3 16:03:14 bbs synchronet: term Done waiting for events thread to terminate Oct 3 16:03:14 bbs synchronet: term Terminal Server destructor begin Oct 3 16:03:14 bbs synchronet: term Terminal Server destructor end Oct 3 16:03:14 bbs synchronet: term Terminal Server thread terminating [snip] Oct 3 16:03:16 bbs synchronet: term Recycling server... Oct 3 16:03:18 bbs synchronet: term Synchronet Terminal Server Version 3.21a Debug [snip] Oct 3 16:03:36 bbs synchronet: term Terminal Server thread started for nodes 1 through 10 Oct 3 16:03:36 bbs synchronet: term Recycle semaphore signaled Oct 3 16:03:36 bbs synchronet: term Waiting for system output thread to terminate... Oct 3 16:03:36 bbs synchronet: term Done waiting for system output thread to terminate [snip] Oct 3 16:03:36 bbs synchronet: term Recycling server... Oct 3 16:05:07 bbs synchronet: term Synchronet Terminal Server Version 3.21a Debug ``` There was a lot of recycling and a big gap between 16:03:36 and 16:05:07 which, I assume, is when it was doing a core dump. event thread just has ``` Oct 3 16:02:53 bbs synchronet: evnt FIDOIN Running native background timed event: /sbbs/exec/sbbsecho -ce Oct 3 16:02:53 bbs synchronet: evnt FIDOIN Executing external: sbbs/exec/sbbsecho -ce Oct 3 16:02:54 bbs synchronet: evnt FIDOIN Background timed event spawned: /sbbs/exec/sbbsecho -ce Oct 3 16:03:14 bbs synchronet: evnt BBS Events JavaScript: Destroying context Oct 3 16:03:14 bbs synchronet: evnt BBS Events JavaScript: Destroying runtime Oct 3 16:03:14 bbs synchronet: evnt BBS Events BBS Events thread terminated Oct 3 16:03:14 bbs synchronet: evnt BBS Events destructor begin Oct 3 16:03:14 bbs synchronet: evnt BBS Events destructor end Oct 3 16:03:36 bbs synchronet: evnt BBS Events constructor using socket -1 (settings=8212) Oct 3 16:03:36 bbs synchronet: evnt BBS Events temporary file directory: /sbbs/tmp/event/ Oct 3 16:03:36 bbs synchronet: evnt BBS Events BBS Events thread started Oct 3 16:03:36 bbs synchronet: evnt BBS Events JavaScript: Creating event runtime: 536870912 bytes Oct 3 16:03:36 bbs synchronet: evnt BBS Events destructor begin Oct 3 16:03:36 bbs synchronet: evnt BBS Events destructor end Oct 3 16:05:09 bbs synchronet: evnt BBS Events constructor using socket -1 (settings=8212) Oct 3 16:05:09 bbs synchronet: evnt BBS Events temporary file directory: /sbbs/tmp/event/ Oct 3 16:05:09 bbs synchronet: evnt BBS Events BBS Events thread started Oct 3 16:05:09 bbs synchronet: evnt BBS Events JavaScript: Creating event runtime: 536870912 bytes ``` Surprised nothing actually reported a seg fault --- SBBSecho 3.30-Linux * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705) SEEN-BY: 10/0 1 102/401 103/1 13 17 705 105/81 106/201 124/5016 128/187 SEEN-BY: 129/14 153/7715 154/110 214/22 218/0 1 215 601 610 700 840 SEEN-BY: 218/860 880 226/30 227/114 229/110 206 317 400 426 428 470 SEEN-BY: 229/700 705 266/512 280/464 291/111 301/1 320/219 322/757 SEEN-BY: 342/200 396/45 460/58 633/280 712/848 902/26 5075/35 PATH: 103/705 218/700 229/426 |
[ << oldest | < older | list | newer > | newest >> ]