• ircd crash

    From Nigel Reed@1:103/705 to GitLab note in main/sbbs on Mon Jan 16 23:31:44 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/489#note_3060

    I think this only happened after a constant retry connecting to vert while it was down, since vert was the only server in my C/N lines with autoconnect configured.You may remember, I run my ircd separate from sbbs.
    --- 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 Tue Jan 17 10:48:26 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/489#note_3068

    So there might be a socket leak in that scenario. If running ircd separate from sbbs (i.e. via jsexec), you still may need to increase the open file limit, but in this case, you're probably detecting an issue because your limit is low(er).
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Randy Sommerfeld@1:103/705 to GitLab note in main/sbbs on Thu Aug 31 20:04:32 2023
    https://gitlab.synchro.net/main/sbbs/-/issues/489#note_3853

    Closing this because "open_socket failed with error 24" is an OS issue, not under control/fixable by the ircd.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Randy Sommerfeld@1:103/705 to GitLab issue in main/sbbs on Thu Aug 31 20:04:32 2023
    close https://gitlab.synchro.net/main/sbbs/-/issues/489
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)