1. Forum
  2. FidoNet
  3. SYNC SYSOPS

  • Error in data_ovl.cpp related to putmsgptrs

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Fri Nov 1 08:33:42 2024
    open https://gitlab.synchro.net/main/sbbs/-/issues/808

    ```
    Thu Oct 31 18:50:26 2024 master/7b3873e5a endofthelinebbs.com
    term Node 2 <Czar> !ERROR 11 (Resource temporarily unavailable) in data_ovl.cpp line 53 (putmsgptrs) opening "/sbbs/data/user/0613.subs" access=66
    ```

    Just saw this in my error log. It looks like a new issue to me, not seen it before.

    Nothing in syslog, noting in dmesg.

    I did see that fidoin was running. Is this a locking issue?

    ```
    event.sbbs.log:Oct 31 18:50:26 bbs synchronet: evnt BBS Events Semaphore signaled for Timed Event: FIDOIN
    event.sbbs.log:Oct 31 18:50:26 bbs synchronet: evnt FIDOIN Running native timed event: FIDOIN
    event.sbbs.log:Oct 31 18:50:26 bbs synchronet: evnt FIDOIN Executing external: /sbbs/exec/sbbsecho -ce
    ```

    I also saw this

    ```
    term.sbbs.log:Oct 31 18:50:20 bbs synchronet: term Node 2 disconnected term.sbbs.log:Oct 31 18:50:20 bbs synchronet: term Node 2 input thread terminated (received 476 bytes in 355 blocks)
    term.sbbs.log:Oct 31 18:50:20 bbs synchronet: term Node 2 output thread terminated (sent 107497 bytes in 562 blocks, 191 average, 0 short)
    term.sbbs.log:Oct 31 18:50:20 bbs synchronet: term Node 2 passthru socket disconnected
    term.sbbs.log:Oct 31 18:50:21 bbs synchronet: term Node 2 <Czar> logout initiated
    term.sbbs.log:Oct 31 18:50:26 bbs synchronet: term Node 2 <Czar> !ERROR 11 (Resource temporarily unavailable) in data_ovl.cpp line 53 (putmsgptrs) opening "/sbbs/data/user/0613.subs" access=66
    term.sbbs.log:Oct 31 18:50:26 bbs synchronet: term Node 2 <Czar> logout completed
    ```
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Fri Nov 1 12:15:36 2024
    https://gitlab.synchro.net/main/sbbs/-/issues/808#note_5845

    If it's just the one occurrence, I don't have any reason to believe this is a new issue. There's certainly been no recent changes in the functions used to open the .subs files.

    It *could* be a locking issue (since the xpdev/sopen functino for *nix uses locking), but without further instrumenting the sopen() function and reproducing the issue, that's just a guess.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)