Okay, so this is a interesting dilemma for me.

Good news. NCBBS is working.

Bad news, NCBBS' can't read from the index for either message or file bases.
I also can't switch networks for some reason. As far as I'm aware local
message bases are intact with no corruption whatsoever, and I assume that carries over to networked bases. I've gone and disabled all maintenance and polling until I'm secure in pulling from HUB 2. For reference, I'm running
1.12 A46 x64 and I upgraded from A44. (Yes, I probably shouldn't have done that.)

So... *sigh*

What in funk and wagnalls is going on.

----------------------------
Nodoka Hanamura
Nugget BBS SysOp @ NeoCincinnati BBS
neocinci.bbs.io

Born too late to experience the scene.
Born too early to go back in time.
Born at the right time to look back.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)

Addendum - I'm able to use the Message Area feature to access local bases.
Both local and networked bases are present in the server config, as are filebases. It's just that the index is blank and I can't switch networks.

----------------------------
Nodoka Hanamura
Nugget BBS SysOp @ NeoCincinnati BBS
neocinci.bbs.io

Born too late to experience the scene.
Born too early to go back in time.
Born at the right time to look back.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)

Addendum - I'm able to use the Message Area feature to access local
bases. Both local and networked bases are present in the server config,
as are filebases. It's just that the index is blank and I can't switch networks.

Do you use some sort of mod to change message/file groups? The data
structures for them was changed slightly in a46. My assumption is you might
be using something like the bt-gasel mod...

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: monterey bbs (21:1/168)

On 08 Sep 2020 at 10:01a, Nodoka Hanamura pondered and said...

Addendum - I'm able to use the Message Area feature to access local
bases. Both local and networked bases are present in the server config,
as are filebases. It's just that the index is blank and I can't switch networks.

I'd check the message bases are assigned message group acs

I'd check you have message groups set up.

Personally it may be best to do a fresh install, pull a rescan of the message bases from the HUBs and copy over your menus and ansi files into the fresh install theme... just a thought.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

On 08 Sep 2020, ryan said the following...

Addendum - I'm able to use the Message Area feature to access local bases. Both local and networked bases are present in the server confi as are filebases. It's just that the index is blank and I can't switc networks.

Do you use some sort of mod to change message/file groups? The data structures for them was changed slightly in a46. My assumption is you might be using something like the bt-gasel mod...

No, I was using bog standard A44 data files before being updated to A46. I'll admit I futzed the upgrade process from A44 to A46 by not doing A45 first but from reading the patch notes and even running A45 first they didn't even
touch the data files as it looked like just a simple patch.

----------------------------
Nodoka Hanamura
Nugget BBS SysOp @ NeoCincinnati BBS
neocinci.bbs.io

Born too late to experience the scene.
Born too early to go back in time.
Born at the right time to look back.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)

Okay, so I just ran a quick check of everything and managed to find the
issue. I'll need to redo my message groups, but it's all sorted now, all network message bases and what not are still intact.

Thanks regardless for the help. I should have the board back up by at no
later than Sunday!

----------------------------
Nodoka Hanamura
Nugget BBS SysOp @ NeoCincinnati BBS
neocinci.bbs.io

Born too late to experience the scene.
Born too early to go back in time.
Born at the right time to look back.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: thE qUAntUm wOrmhOlE, rAmsgAtE, uK. bbs.erb.pw (21:1/158)

On 10 Sep 2020 at 12:29a, Nodoka Hanamura pondered and said...

Okay, so I just ran a quick check of everything and managed to find the issue. I'll need to redo my message groups, but it's all sorted now, all network message bases and what not are still intact.

Thanks regardless for the help. I should have the board back up by at no later than Sunday!

Good news! Well done on fixing things.

--- Mystic BBS v1.12 A46 2020/08/26 (Windows/32)
* Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)

134

Thanks regardless for the help. I should have the board back up by at no later than Sunday!

w00t w00t!! i want to get back on there when you do. sorry the upgrade was a hassle for ya.



|07p|15AULIE|1142|07o
|08.........

--- Mystic BBS v1.12 A45 2020/02/18 (Raspberry Pi/32)
* Origin: American Pi BBS (21:2/150)

134

reference, I'm running 1.12 A46 x64 and I upgraded from A44. (Yes, I probably shouldn't have done that.)

This same thing happened to me when I upgrade from A45 to A46. My message and file bases were in tact but I couldn't access them as there were two files
that got corrupted:
"groups_f.dat" and "groups_g.dat"

These contain the file and message groups. I blew them away and redid my groups. Fixed it but it was not fun.

Good luck

|20|15ÚÄ|16|08´ |08De|07ad|15be|07a|08tz b|07b|15s
|08ÀÄÙÃÄ¿ |08:>.|07A|08rk |0710|08:|07101|08/|0714|08.
|04þ |08À|20|15Ä|16|08Ù |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|04A|07n|15al|07o|08g |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|04.|08dPR|04. |08:>.|15S|07ci |1577|08:|151|08/|15131|08. |04°±°|08±ÛÛÜÝ|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

134
Just for sake of clarity, g00r00 added two new fields in the Groups (Message/File): Shortname and InfoFile

I suppose this is where the conversion/upgrade barfed.

|20|15ÚÄ|16|08´ |08De|07ad|15be|07a|08tz b|07b|15s
|08ÀÄÙÃÄ¿ |08:>.|07A|08rk |0710|08:|07101|08/|0714|08.
|04þ |08À|20|15Ä|16|08Ù |08:>.|10A|02gn |1046|08:|101|08/|10123|08.
|04A|07n|15al|07o|08g |08:>.|12F|04sx |1221|08:|122|08/|12123|08.
|04.|08dPR|04. |08:>.|15S|07ci |1577|08:|151|08/|15131|08. |04°±°|08±ÛÛÜÝ|08:>.|11T|03qw |111337|08:|113|08/|1113|08.

--- Mystic BBS v1.12 A46 2020/08/06 (Linux/64)
* Origin: deadbeatz.org (21:2/123)

134
On 11 Sep 2020, Analog said the following...

reference, I'm running 1.12 A46 x64 and I upgraded from A44. (Yes, I probably shouldn't have done that.)

This same thing happened to me when I upgrade from A45 to A46. My
message and file bases were in tact but I couldn't access them as there were two files that got corrupted:
"groups_f.dat" and "groups_g.dat"

These contain the file and message groups. I blew them away and redid my groups. Fixed it but it was not fun.

Good luck

Yeah, I had the same issue, sadly. I did fix it, though.

Born too late to experience the scene.
Born just in time to see it come back.
Nodoka Hanamura - NeoCincinnati BBS SYSOP - neocinci.bbs.io

--- Mystic BBS v1.12 A46 2020/08/26 (Linux/64)
* Origin: NeoCincinnati BBS - neocinci.bbs.io:23 (21:2/106)