• Adding new message areas corrupts msgs.ini

    From Nigel Reed@1:103/705 to GitLab issue in main/sbbs on Sunday, January 22, 2023 14:02:15
    open https://gitlab.synchro.net/main/sbbs/-/issues/502

    Keyop also tested this with the same result.If you add a new message area in scfg, when you have it'll corrupt your msgs.ini file.As discussed on irc. So this is not an isolated problem.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rick Smith@1:105/10 to Nigel Reed on Sunday, January 22, 2023 15:02:12
    Greetings Nigel!

    Sunday January 22 2023 14:02, you wrote to GitLab issue in main/sbbs about an urgent matter!:

    open https://gitlab.synchro.net/main/sbbs/-/issues/502

    Keyop also tested this with the same result.If you add a new message
    area in scfg, when you have it'll corrupt your msgs.ini file.As
    discussed on irc. So this is not an isolated problem.

    Whats the fix?

    ----
    Regards,


    Rick Smith (Nitro)

    ... Sleep... The thing "some" SysOps go without, cuz BBSing is too fun;-)
    --- GoldED+/LNX 1.1.5-b20220504
    * Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)
  • From Nigel Reed@1:124/5016 to Rick Smith on Sunday, January 22, 2023 19:34:59
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Nigel Reed on Sun Jan 22 2023 15:02:12

    Whats the fix?

    1. Don't ever add/change your message area until it has been fixed.
    2. If you have already made changes, then you'll need to look back in your msgs.*.ini files to find the last uncorrupted file and replace msgs.ini. You can probably do this while the BBS is up but I would highly recommend shutting down first to save further corruption. I would manually reenter and new groups you may have added until fixed.
    --- SBBSecho 3.20-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Rob Swindell@1:103/705 to GitLab note in main/sbbs on Sunday, January 22, 2023 15:16:21
    https://gitlab.synchro.net/main/sbbs/-/issues/502#note_3129

    More details: the issue here is the corruption of a QWKnet hub conference number -> sub-board mapping. This issue only appears to happen if a new group (with a least one sub-board) is *inserted* before a QWKnet message group in SCFG.Adding an empty message group or a message group with no sub-boards would not trigger this issue.
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rob Swindell@1:103/705 to GitLab issue in main/sbbs on Sunday, January 22, 2023 17:39:44
    close https://gitlab.synchro.net/main/sbbs/-/issues/502
    --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Rick Smith on Sunday, January 22, 2023 20:11:16
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Nigel Reed on Sun Jan 22 2023 03:02 pm

    Greetings Nigel!

    Sunday January 22 2023 14:02, you wrote to GitLab issue in main/sbbs about an urgent matter!:

    open https://gitlab.synchro.net/main/sbbs/-/issues/502

    Keyop also tested this with the same result.If you add a new message area in scfg, when you have it'll corrupt your msgs.ini file.As discussed on irc. So this is not an isolated problem.

    Whats the fix?

    Are your QWKnet hub sub-boards messed up? If not, don't worry about it (just get the latest and greatest v3.20a), but if they are, then you can fix them by hand in SCFG or by editing your ctrl/msgs.ini file to match https://wiki.synchro.net/howto:dove-net
    --
    digital man (rob)

    Synchronet "Real Fact" #42:
    Rob Swindell was laughed out of a FidoNet Net103 (OC, Calif.) meeting in 1992 Norco, CA WX: 49.2F, 75.0% humidity, 2 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nigel Reed@1:124/5016 to Rick Smith on Sunday, January 22, 2023 19:37:28
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Nigel Reed on Sun Jan 22 2023 15:02:12

    Whats the fix?

    Also, if your msgs.ini is already corrupt, then you're likely writing posts into the wrong groups. I was alerted today that SYNCDATA was getting posted into SYNCPROG.

    You can check for corruption by going info scfg > networks > qwk > hubs > vert (or whatevr qwk hub you have) > subforums. Compare them to the list in the wiki:

    https://wiki.synchro.net/network:dove-net
    --- SBBSecho 3.20-Linux
    * Origin: End Of The Line BBS - endofthelinebbs.com (1:124/5016)
  • From Nelgin@1:103/705 to Digital Man on Monday, January 23, 2023 02:45:06
    Re: Adding new message areas corrupts msgs.ini
    By: Digital Man to Rick Smith on Sun Jan 22 2023 20:11:16

    Are your QWKnet hub sub-boards messed up? If not, don't worry about it (just get the latest and greatest v3.20a), but if they are, then you can fix them by hand in SCFG or by editing your ctrl/msgs.ini file to match https://wiki.synchro.net/howto:dove-net

    It will mess up other qwk networks too. It would be best to restore and then hand edit to include any new areas added. That's what I ended up doing and it seems to work ok.
    ---
    Synchronet End Of The Line BBS - endofthelinebbs.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Rick Smith@1:105/10 to Digital Man on Monday, January 23, 2023 05:30:52
    Greetings Digital!

    Sunday January 22 2023 20:11, you wrote to me about an urgent matter!:

    * Forwarded from area 'SYNC_SYSOPS'
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Nigel Reed on Sun Jan 22 2023 03:02 pm

    Greetings Nigel!

    Sunday January 22 2023 14:02, you wrote to GitLab issue in
    main/sbbs about an urgent matter!:

    open https://gitlab.synchro.net/main/sbbs/-/issues/502

    Keyop also tested this with the same result.If you add a new
    message
    area in scfg, when you have it'll corrupt your msgs.ini
    file.As
    discussed on irc. So this is not an isolated problem.

    Whats the fix?

    Are your QWKnet hub sub-boards messed up? If not, don't worry about it (just get the latest and greatest v3.20a), but if they are, then you
    can fix them by hand in SCFG or by editing your ctrl/msgs.ini file to
    I do not appear to even have a msgs.ini doesnt seem possible? But I cannot find it... Ive search the entire server for it... While searching for it though I noticed something that caught my eye, probably isnt anything but worth mentioning.

    while most things are owned by bbsowner is appears that some of the files are now owned by root?

    -rw-r--r-- 1 root root 217188 Jan 23 05:28 msgs.cnf
    -rw-r--r-- 1 bbsowner bbsowner 1084 Oct 27 2021 newslink.cfg

    Just an example of what I am seeing... But anyhow ../ctrl/msgs.ini does not exist on this system.


    ----
    Regards,


    Rick Smith (Nitro)

    ... YKYHW: You consider BBSing better than sex.
    --- GoldED+/LNX 1.1.5-b20220504
    * Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)
  • From Rick Smith@1:105/10 to Nigel Reed on Monday, January 23, 2023 06:08:42
    Greetings Nigel!

    Sunday January 22 2023 19:37, you wrote to me about an urgent matter!:

    * Forwarded from area 'SYNC_SYSOPS'
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Nigel Reed on Sun Jan 22 2023 15:02:12

    Whats the fix?

    Also, if your msgs.ini is already corrupt, then you're likely writing posts into the wrong groups. I was alerted today that SYNCDATA was
    getting posted into SYNCPROG.

    You can check for corruption by going info scfg > networks > qwk >
    hubs > vert (or whatevr qwk hub you have) > subforums. Compare them to
    the list in the wiki:

    Ill check it, however as I have discovered I do not have a msgs.ini that I can find anyhow.. Ive looked most everywhere for it...


    ----
    Regards,


    Rick Smith (Nitro)

    ... Ura BBS addict when you consider BBSing better than coffee
    --- GoldED+/LNX 1.1.5-b20220504
    * Origin: ----> Abacus BBS! --->>>>bbs.abon.us:2323 (1:105/10)
  • From Digital Man@1:103/705 to Rick Smith on Monday, January 23, 2023 09:10:04
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Digital Man on Mon Jan 23 2023 05:30 am

    Greetings Digital!

    Sunday January 22 2023 20:11, you wrote to me about an urgent matter!:

    * Forwarded from area 'SYNC_SYSOPS'
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Nigel Reed on Sun Jan 22 2023 03:02 pm

    Greetings Nigel!

    Sunday January 22 2023 14:02, you wrote to GitLab issue in
    main/sbbs about an urgent matter!:

    open https://gitlab.synchro.net/main/sbbs/-/issues/502

    Keyop also tested this with the same result.If you add a new
    message
    area in scfg, when you have it'll corrupt your msgs.ini
    file.As
    discussed on irc. So this is not an isolated problem.

    Whats the fix?

    Are your QWKnet hub sub-boards messed up? If not, don't worry about it (just get the latest and greatest v3.20a), but if they are, then you can fix them by hand in SCFG or by editing your ctrl/msgs.ini file to

    I do not appear to even have a msgs.ini doesnt seem possible?

    msgs.ini was introduced in v3.20 (still in active development, unreleased), it's a newer-format of msgs.cnf.
    --
    digital man (rob)

    Synchronet "Real Fact" #116:
    Synchronet v1a r5 (for MS-DOS) was released on February 19, 1992
    Norco, CA WX: 50.5F, 30.0% humidity, 2 mph WNW wind, 0.00 inches rain/24hrs --- SBBSecho 3.20-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Nelgin@1:103/705 to Rick Smith on Tuesday, January 24, 2023 13:39:53
    Re: Adding new message areas corrupts msgs.ini
    By: Rick Smith to Nigel Reed on Mon Jan 23 2023 06:08:42

    Ill check it, however as I have discovered I do not have a msgs.ini that I can find anyhow.. Ive looked most everywhere for it...

    Then you've not updated to the latest and greatest yet then, so you're good. ---
    Synchronet End Of The Line BBS - endofthelinebbs.com
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)