The newest A47 is working fine so far and no busy nodes, but I'm only polling FSXNet which also has Mystic, which is likely why. Still the best things have worked since A46 and all the new echo areas are coming in fine. I've turned off all my extra cron tasks and stuff and am using just the latest Mystic.

...This line left blank on purpose.

--- Mystic BBS v1.12 A47 2021/05/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

The newest A47 is working fine so far and no busy nodes, but I'm only polling FSXNet which also has Mystic, which is likely why. Still the
best things have worked since A46 and all the new echo areas are coming
in fine. I've turned off all my extra cron tasks and stuff and am using just the latest Mystic.

Thanks for posting this, I'll give the current 05/21 build another go. Yer on Raspberry Pi, too - I wonder if g00r00 made some update to that 5/21 build - or if I have an isolated issue on MY system; I haven't tried this one, and thank you for your post bcw.




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

--- Mystic BBS v1.12 A47 2021/05/03 (Raspberry Pi/32)
* Origin: 2o fOr beeRS bbs>>>20ForBeers.com:1337 (21:2/150)

Hi Paulie,

I saw you had visited a while back, and wanted to thank you for stopping by :)

I also bumped up your sec level so you *should* be able to post and
participate in the echo's on Vger now.... That is, once I sort out why most
of my message bases in Fidonet and fsxNet and tqwnet are virtually empty.

I got a few new messages in each net's message bases, but something is amiss.

So far, I've checked my %LINKED in AreaFix on fsxNet and all seemed good
there so did a %RESCAN D=365 so I've got a full message base with about
50,000 messages (about 30,000 in dups though).

I have no idea what's gone wrong, but I'm going to do a rescan next in
FidoNet (Al, that's you, coz you're my HUB) and tqwnet which has never
actually worked as it should have, so I'll look more into that in the coming days/week.

Anyway, thoughts and suggestions are welcome from anyone.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

So far, I've checked my %LINKED in AreaFix on fsxNet and all seemed good there so did a %RESCAN D=365 so I've got a full message base with about 50,000 messages (about 30,000 in dups though).

On Mystic if you want to do a rescan you can delete your data/echodupes.dat so the messages coming in are not detected as dupes. Normally you wouldn't want to do that unless something has happened to you message areas and you want to start over.

I have no idea what's gone wrong, but I'm going to do a rescan next in FidoNet (Al, that's you, coz you're my HUB) and tqwnet which has never actually worked as it should have, so I'll look more into that in the coming days/week.

As far as I know everything is tossing to your node as it should. Let me know if that is not so and I'll look into it.

Am I your only link in fidonet? I ask because my tosser will not toss mail to your node if your node is listed in the seen bys.

In any case you can do a %list request to areafix and make sure you are connected to the area you expect to be. There are new areas also in that list that you may find interesting so go ahead and get conneceted to whatever areas (mail or files) you want to be connected to.

You can also rescan any areas at any time if you need to do that.

%rescan * <- rescan all mail in every connected area
%rescan * 200 <- the same but only the last 200 messages in each area
%rescan * 365 days <- the same, get 365 days worth of mail in each area

You can do that any time you need/want to do that. You can do the same thing in file areas although the command is to Filefix.

%resend filename.zip filearea

I'm going to send you a %list in a few minutes so check things are as they should be and adjust as needed and rescan if you like.

I'd also consider an upgrade. There have been good changes to the way echomail works in recent versions of Mystic. There are changes though, there is a new themes setup and fidopoll is no more. Current A47 versions of Mystic use mis to poll. The command line is the same but starts with ./mis, not fidopoll.

"mis poll forced [type]" is broken currently, so stay away from that one.

If you ever have some sort of issues feel free to netmail me and I'll have a look at my end and be sure things are what they need to be.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

On 31 May 2021, tallship said the following...

I got a few new messages in each net's message bases, but something is amiss.

I have no idea what's gone wrong, but I'm going to do a rescan next in FidoNet (Al, that's you, coz you're my HUB) and tqwnet which has never actually worked as it should have, so I'll look more into that in the coming days/week.

Anyway, thoughts and suggestions are welcome from anyone.

--- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
* Origin: Vger.Cloud - NOMAD Internetwork (21:2/104)

OK, Al did answer you already, just adding my two cents since I had troubles with the latest A47 Alpha in the past (seems to be fine now). You seem to be running A43, old but was functional. You mention things not coming in, one thing Al didn't tell you to check was for stuck fidopoll busy. I use a script in mystic root (showing only the fsxnet part here):
#!/bin/bash
# busy - check for bsy flags
ls semaphore/*.bsy
ls echomail/out/fidonet/*.bsy echomail/out/fidonet/00010091.pnt/*.bsy
ls echomail/out/retronet.050/*.bsy echomail/out/retronet.050/025b0000.pnt/*.bsy

It should return:
ls: cannot access 'echomail/out/fidonet/*.bsy': No such file or directory
ls: cannot access 'echomail/out/fidonet/00010091.pnt/*.bsy': No such file or directory

If so it's not busy, but if it shows errors you need to do killbusy:
./fidopoll killbusy all
Then check again and it should be clear showing 'No such file or directory'. Then do your fidopoll and stuff should come in.

The fidopoll forced should be OK on A43, I remember that as a pretty stable version as is A46 (current release). From my tagline you'll see I'm running the latest A47 Alpha which is working fine now on my Pi/32 and my Linux/64 (AlphaTest) system as well, I made the script above because some Alphas seem to have a lot of busy errors in the past and it was a quick way to know if
I needed to do a killbusy. Any Linux users with issues with polling should try it ;)

--- Mystic BBS v1.12 A47 2021/05/21 (Raspberry Pi/32)
* Origin: Mystic Pi BBS bcw142.zapto.org:23 (21:1/145)

OK, Al did answer you already, just adding my two cents since I had troubles with the latest A47 Alpha in the past (seems to be fine now). You seem to be running A43, old but was functional. You mention things not coming in, one thing Al didn't tell you to check was for stuck fidopoll busy.

Yep, I forgot about that. I've seen that happen a few times and then mail doesn't get tossed. It'll never toss until you clear the busy files.

It's a good idea to have a look in your inbound periodically and make sure nothing is getting forgottten about in there.

The same is true of the insecure inbound. Depending on your setup stuff may not be getting tossed from there. I sometimes find netmail in arcmail bundles sitting in my insecure inbound because (compressed) mail is not tossed in there.

--- BBBS/Li6 v4.10 Toy-4
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.2)

On 31 May 2021 at 10:43p, Al pondered and said...

In any case you can do a %list request to areafix and make sure you are connected to the area you expect to be. There are new areas also in that list that you may find interesting so go ahead and get conneceted to whatever areas (mail or files) you want to be connected to.

Hi all

NET 1,3,4 are running HPT so areafix commands differ a little from Mystic.

My advice is to send a %HELP to your HUB to confirm the best commands to use
to rescan etc. :)

NET 2 is running Mystic to toss packets at present but will likely change to HPT in time as well.

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