1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • Issues with IRC, MRC, and even sbbs.service with latest commit(s?)

    From Nick Boel@1:103/705 to GitLab issue in main/sbbs on Thu Jun 4 15:42:25 2026
    open https://gitlab.synchro.net/main/sbbs/-/issues/1156

    IRC

    ```
    Jun 04 17:29:01 reaper synchronet[7709]: srvc 0000 IRC !JavaScript warning /home/axisd/sbbs/exec/load/ircd/core.js line 105: Disconnected
    Jun 04 17:29:01 reaper synchronet[7709]: srvc 0000 IRC !JavaScript warning /home/axisd/sbbs/exec/load/ircd/user.js line 1556: Disconnected
    Jun 04 17:29:01 reaper synchronet[7709]: srvc 0000 IRC SynchronetIRCd-2.0 started.
    Jun 04 17:29:01 reaper synchronet[7709]: srvc 0000 IRC Trying to read configuration from: /home/axisd/sbbs/ctrl/ircd.ini
    Jun 04 17:29:01 reaper synchronet[7709]: srvc 0000 IRC !WARNING No mask provided in Ban:1. Ignoring.
    Jun 04 17:29:01 reaper synchronet[7709]: srvc 0000 IRC Routing: Auto-connecting to *.synchro.net (vert.synchro.net) on port 6667
    Jun 04 17:29:01 reaper synchronet[7709]: srvc 0000 IRC Routing: Connected to *.synchro.net (vert.synchro.net:6667), Sock (71.95.196.34:6667), Class 30. Sending handshake.
    ```

    MRC

    ```
    Jun 04 17:03:28 reaper synchronet[539]: srvc 0000 MRC-Connector Connecting to mrc.bottomlessabyss.net:5001
    Jun 04 17:03:28 reaper synchronet[539]: srvc 0000 MRC-Connector !JavaScript warning /home/axisd/sbbs/mods/../xtrn/mrc/mrc-connector.js line 182: Disconnected
    Jun 04 17:03:28 reaper synchronet[539]: srvc 0000 MRC-Connector !JavaScript warning /home/axisd/sbbs/exec/load/nodedefs.js line 160: Disconnected
    ```

    SBBS.SERVICE

    ```
    Jun 04 17:37:18 reaper systemd[1]: sbbs.service: Reload operation timed out. Killing reload process.
    ```

    Unsure if this all correlates to the same thing, but as of this latest update is the first time I've seen all three of them.
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Thu Jun 4 19:01:15 2026
    close https://gitlab.synchro.net/main/sbbs/-/issues/1156
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Thu Jun 4 19:07:12 2026
    https://gitlab.synchro.net/main/sbbs/-/issues/1156#note_9195

    Thanks for the detailed report, Accession — the three symptoms share a single root cause.

    Commit `ead5ccf16` (*song-11-earn*), "Detect disconnection in JavaScript callback," added a check to the Services server's `js_OperationCallback()` that aborts a script once its client socket has been gone for 10 consecutive callbacks. That's correct for per-connection services (which have a real accepted client socket), but **static services** (`SERVICE_OPT_STATIC` — e.g. the IRC daemon and the MRC connector) run with a zero-initialized client whose socket is never set. `socket_check()` on that unset socket fails, so those long-lived static services were wrongly warned "Disconnected" and aborted after 10 callbacks — then, being static-loop services, immediately restarted, cycling endlessly. The systemd reload timeout was downstream of that thrash during recycle.

    Fixed in `cfa6fe9e1` (*bolt-11-banner*): the disconnection check is now gated on the service **not** being static, so it only applies to real per-client connections. IRC and MRC are unaffected again.

    Pull and rebuild, and you should be back to normal. Closing as resolved — please reopen if you still see it.

    — *Authored by Claude (Claude Code), on behalf of @rswindell*
    --- SBBSecho 3.37-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Accession@1:103/705 to Rob Swindell on Fri Jun 5 09:02:32 2026
    Hey Rob!

    On Fri, 05 Jun 2026 00:07:12 , you wrote:

    https://gitlab.synchro.net/main/sbbs/-/issues/1156#note_9195

    Thanks for the detailed report, Accession — the three symptoms share a single root cause.

    Great news! I almost closed the issue myself thinking it was something I did, instead. ;)

    Fixed in `cfa6fe9e1` (*bolt-11-banner*): the disconnection check is now gated on the service **not** being static, so it only applies to real per-client connections. IRC and MRC are unaffected again.

    Pull and rebuild, and you should be back to normal. Closing as resolved
    — please reopen if you still see it.

    Definitely back to normal. Thanks for the quick fix!

    Regards,
    Nick

    ... Sarcasm: because beating people up is illegal.
    ---
    ￭ Synchronet ￭ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)