Put this on my AlphaTest and now it doesn't send to this system (Main BBS):
Nov 06 17:08:04 FIDOPOLL Version 1.12 A36
Nov 06 17:08:04 Scanning 80:603/0
Nov 06 17:08:04 Queued 0 files (0 bytes) to 80:603/0
Nov 06 17:08:04 Polling BINKP node 80:603/0
Nov 06 17:08:04 Connecting to 10.0.0.21:24556
Nov 06 17:08:05 Connected
Nov 06 17:08:05 Authorization State: 1 Have:FALSE Need:TRUE
Nov 06 17:08:05 Sent Frame: NUL SYS AlphaTest
Nov 06 17:08:05 Sent Frame: NUL ZYZ bcw142
Nov 06 17:08:05 Sent Frame: NUL VER Mystic/1.12A36 binkp/1.0
Nov 06 17:08:05 Sent Frame: ADR 80:603/0.2@retronet
Nov 06 17:08:05 Authorization State: 2 Have:FALSE Need:TRUE
Nov 06 17:08:05 Begin command frame: NUL (Size=45)
Nov 06 17:08:05 End Command frame: NUL OPT CRAM-MD5-cb88993bb8e41669a60ac8d113f4c9d2
Nov 06 17:08:05 Authorization State: 2 Have:TRUE Need:FALSE
Nov 06 17:08:05 Received challenge (cb88993bb8e41669a60ac8d113f4c9d2)
Nov 06 17:08:05 Begin command frame: NUL (Size=17)
Nov 06 17:08:05 End Command frame: NUL SYS Mystic Pi BBS
Nov 06 17:08:05 System Mystic Pi BBS
Nov 06 17:08:05 Begin command frame: NUL (Size=10)
Nov 06 17:08:05 End Command frame: NUL ZYZ bcw142
Nov 06 17:08:05 SysOp bcw142
Nov 06 17:08:05 Begin command frame: NUL (Size=28)
Nov 06 17:08:05 End Command frame: NUL VER Mystic/1.12A35 binkp/1.0
Nov 06 17:08:05 Mailer Mystic/1.12A35 binkp/1.0
Nov 06 17:08:05 Begin command frame: ADR (Size=33)
Nov 06 17:08:05 End Command frame: ADR 21:1/145@fsxnet 80:603/0@retronet
Nov 06 17:08:05 Sent Frame: PWD CRAM-MD5-209c6491ce76dca357e955df774f8078
Nov 06 17:08:05 Authorization State: 5 Have:FALSE Need:TRUE
Nov 06 17:08:05 Begin command frame: OK (Size=6)
Nov 06 17:08:05 End Command frame: OK secure
Nov 06 17:08:05 Authorization State: 5 Have:TRUE Need:FALSE
Nov 06 17:08:05 State Rx:WaitFile Tx:NextFile Have:FALSE Need:TRUE
Nov 06 17:08:05 Sent Frame: EOB
Nov 06 17:08:05 Begin command frame: EOB (Size=0)
Nov 06 17:08:05 End Command frame: EOB
Nov 06 17:08:05 State Rx:WaitFile Tx:Done Have:TRUE Need:FALSE
Nov 06 17:08:05 Session complete (0 sent, 0 rcvd, 0 skip)

I only changed from 11/04 to 11/06 to make this change.

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

Put this on my AlphaTest and now it doesn't send to this system (Main BBS): Nov 06 17:08:04 FIDOPOLL Version 1.12 A36

There are no errors in the log. What is that you want me to look at?

--- Mystic BBS v1.12 A36 2017/11/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/06/17, g00r00 pondered and said...

Put this on my AlphaTest and now it doesn't send to this system (Main BBS): Nov 06 17:08:04 FIDOPOLL Version 1.12 A36

* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

OK, I don't get something then, I see a number of messages like:
Authorization State: 1 Have:FALSE Need:TRUE
Authorization State: 2 Have:FALSE Need:TRUE
Authorization State: 2 Have:TRUE Need:FALSE
State Rx:WaitFile Tx:NextFile Have:FALSE Need:TRUE
Sent Frame: EOB

The last two I think I get, it was waiting for the EOB message and didn't
have it yet so that State message just shows it hadn't got it yet. Are the others the same thing, a wrong state for a fraction of a second before
getting the message?

I was having problems with the hub, noticed it hadn't updated with DST, so shutdown mis and mis2 and restarted. Then found no answer at port 23, dropped everything, cleared the stuck mis.bsy and restarted and something has hung. Then tried restarting the system and it's now down. I may have to rebuild my system again when I get home. ;( Till then will check messages here on Agency.

--- Mystic BBS v1.12 A36 (Windows/32)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)

have it yet so that State message just shows it hadn't got it yet. Are
the others the same thing, a wrong state for a fraction of a second
before getting the message?

No, there is nothing unusual or wrong about the logs you're posting.

BINKP needs frames at certain times, and it has frames waiting at certain times, thats all those logs are showing, along with the "state" of the protocol. They are logged whenever any of those things change as part of the debug logging so if something *does* happen its easier for me to see exactly what was going on when it did.

In the case of your log you posted everything was correct.

I was having problems with the hub, noticed it hadn't updated with DST,
so shutdown mis and mis2 and restarted. Then found no answer at port 23, dropped everything, cleared the stuck mis.bsy and restarted and

If you have to clear BSY files then things are not getting shut down
correctly.

Are you using kill -9 because it will absolutely destroy your system eventually. And that is not just a Mythic thing. Or are you using one of those buggy restart mis scripts?

--- Mystic BBS v1.12 A36 2017/11/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/07/17, g00r00 said the following...

If you have to clear BSY files then things are not getting shut down correctly.

Yes, but all kinds of things happen including Internet outages and program/OS crashes.

Are you using kill -9 because it will absolutely destroy your system eventually. And that is not just a Mythic thing. Or are you using one
of those buggy restart mis scripts?

No kill -9 used today. The system will die because it's on a microSD as
well. I've never had one last much over a year if it's always on. I got a
year and a half out of one once. With all the DDoS attacks they don't last
long (due to all the writes). No restart scripts except rc.local to boot
after a reset. Since I haven't been home since it happened I really don't
know what state the Pi is in, just that I can't get to it remotely. I changed to dmz setting to the older one which is running though it has problems.

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

No kill -9 used today. The system will die because it's on a microSD as well. I've never had one last much over a year if it's always on. I got a year and a half out of one once. With all the DDoS attacks they don't
last long (due to all the writes). No restart scripts except rc.local to boot after a reset. Since I haven't been home since it happened I really don't know what state the Pi is in, just that I can't get to it
remotely. I changed to dmz setting to the older one which is running though it has problems.

Could you run Raspbian off the sdcard and then install Mystic onto a USB
thumb drive? That'd reduce the writes hitting the sdcard.

I've had an sdcard go bad on my Pi before, but I think that was due to
turning it off by pulling the power cable. Ever since I got into the habit of SSHing in and running shutdown, haven't had the issue again. (But power
outages are unavoidable.)

--- Mystic BBS v1.12 A36 2017/11/06 (Windows/32)
* Origin: Deep Space '94 * telnet://deepspace94.com * fnord (21:2/136)

Seems something caused a fidopoll hang on the A35 Pi I use as a hub, so
that's that caused that polling data - fidopoll.bsy for the last 4 hours ;(

--- Mystic BBS v1.12 A36 2017/11/06 (Linux/64)
* Origin: Mystic AlphaTest bcw142.zapto.org:2323 (21:1/145.2)

No kill -9 used today. The system will die because it's on a microSD as well. I've never had one last much over a year if it's always on. I got a

Gotcha that makes sense. Maybe a similar product with a build in flash space or a USB drive would be a option.

--- Mystic BBS v1.12 A36 2017/11/06 (Windows/32)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

deepthaw wrote to bcw142 <=-

Could you run Raspbian off the sdcard and then install Mystic onto a
USB thumb drive? That'd reduce the writes hitting the sdcard.

That's an idea. Might even consider that myself. You can also put parts of the filesystem like /tmp and even the logs directory into RAMdisk. Only concern I have with using a USB drive is I/O performance (or lack thereof).

I've had an sdcard go bad on my Pi before, but I think that was due to turning it off by pulling the power cable. Ever since I got into the
habit of SSHing in and running shutdown, haven't had the issue again.
(But power outages are unavoidable.)

I've had one drop dead recently, have to make sure I have good backups of this one now.


... Bad day: Smokey the Bear stamps out your birthday cake.
___ MultiMail/Win32 v0.49

--- Mystic BBS/QWK v1.12 A35 (Raspberry Pi/32)
* Origin: The Bridge - bridge.vkradio.com (21:1/143)