• Hub 3 - Clrghouz updates

    From deon@21:2/116 to All on Tue Feb 24 14:52:07 2026
    Howdy,

    I've been doing smoe work on clrghouz the last week or two, and I started rolling out those updates over the last week.

    I've basically optimised the message store, changing compression from zstd to brotli, as well as changing how its stored in the DB - which looks like has bought me a 60-70% reduction in message stoage - yay :)

    I also reworked how packets are parsed, that I think gives me a performance boost now, but primarily enables me to skip past bad messages in a packet and hopefully just throw away that one bad one.

    Unfortunately, I broke a few things along the way, and I'm now chasing the final bugs hopefully. Every now and again I see an exception in the logs that I fix, and those exceptions are not happening as often now.

    The DB will be going through a conversion over the next few hours (got 1m messages in there!) to take advantage of that space, before I upgrade it to a later version (when thats done).

    If you see something odd, please let me know.


    ...δεσ∩
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Warpslide@21:3/110 to deon on Tue Feb 24 06:01:12 2026
    On 24 Feb 2026, deon said the following...

    If you see something odd, please let me know.

    I have seen quite a few dupes on my side lately, a lot of them are ibbslastcall messages, others include:

    MSGID: 21:4/148@fsxnet 699c29b8 from "Roon" in FSX_TST
    MSGID: 21:4/131 0192ef2d from "Wrong Number Family BBS'" in FSX_ADS


    This last batch all seem to be from Hub 4, so may not be Clrghouz related.


    Jay

    ... The cause of problems are solutions!

    --- Mystic BBS v1.12 A49 2024/05/29 (Linux/64)
    * Origin: Northern Realms (21:3/110)
  • From deon@21:2/116 to Warpslide on Tue Feb 24 23:21:17 2026
    Re: Re: Hub 3 - Clrghouz updates
    By: Warpslide to deon on Tue Feb 24 2026 06:01 am

    Howdy,

    I have seen quite a few dupes on my side lately, a lot of them are ibbslastcall messages, others include:

    MSGID: 21:4/148@fsxnet 699c29b8 from "Roon" in FSX_TST
    MSGID: 21:4/131 0192ef2d from "Wrong Number Family BBS'" in FSX_ADS

    This last batch all seem to be from Hub 4, so may not be Clrghouz related.

    They were likely clrghouz.

    I discovered clrghouz wasnt processing the seen-by (or path/via lines) from messages (echomail & netmail), so its likely it sent them out again to the hubs.

    Should be good now though, fixed it this morning...

    If they keep coming, please let me know...


    ...δεσ∩
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)
  • From Avon@21:1/101 to Warpslide on Sat Feb 28 15:58:04 2026
    On 24 Feb 2026 at 06:01a, Warpslide pondered and said...

    This last batch all seem to be from Hub 4, so may not be Clrghouz
    related.

    could well be a bunch of stuff I had processed after restarting the HUBs in recent days...

    Kerr Avon [Blake's 7] 'I'm not expendable, I'm not stupid and I'm not going' avon[at]bbs.nz | bbs.nz | fsxnet.nz

    --- Mystic BBS v1.12 A48 (Linux/64)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From slacker@21:3/193 to deon on Sat Feb 28 03:36:02 2026
    Hey Deon,

    If you see something odd, please
    let me know.

    I noticed that viewing the last echomails sent and received via the web no longer works.

    The 'sent to you' doesn't have a clickable msgid and clicking on any in the 'you sent' throws an error 'That didnt work? Please try again..."

    Other than that, I haven't noticed any issues on my end.

    Thanks!


    --- NE BBS v1.15 (linux; x64)
    * Origin: NE BBS - nebbs.servehttp.com:9223 (21:3/193)
  • From deon@21:2/116 to slacker on Sat Feb 28 22:05:17 2026
    Re: Re: Hub 3 - Clrghouz updates
    By: slacker to deon on Sat Feb 28 2026 03:36 am

    Howdy,

    I noticed that viewing the last echomails sent and received via the web no longer works.

    The 'sent to you' doesn't have a clickable msgid and clicking on any in the 'you sent' throws an error 'That didnt work? Please try again..."

    Thanks, I'd nearly forgotten to look at that.

    I've changed the logging a little, and record now the archive that a packet comes in (makes it a little easier to track problematic packets), and that has broken that page.

    I'll fix that soon :)

    Other than that, I haven't noticed any issues on my end.

    Awesome.

    Some folks may have been getting dups - I've been tracking down a duplicate issue, where clrghouz was sending out mail to folks who had already received it (probably via another route). I think I've got it now.

    Some from now, hopefully no more dupes :)


    ...δεσ∩
    --- SBBSecho 3.29-Linux
    * Origin: I'm playing with ANSI+videotex - wanna play too? (21:2/116)