I've got a message stuck in the BBS I 'sent' back at 1:30pm my time and it's still there unsent after over 3 hours and many tens of polls. I've tried the normal ./fidopoll killbusy over and over and polling again over and over. So
I guess the next try is a total restart of Mystic (mis), yet again.

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

On 11/28/16, bcw142 pondered and said...

I've got a message stuck in the BBS I 'sent' back at 1:30pm my time and it's still there unsent after over 3 hours and many tens of polls. I've tried the normal ./fidopoll killbusy over and over and polling again
over and over. So I guess the next try is a total restart of Mystic
(mis), yet again.

When you say 'stuck' what do you mean?
Is there a packet sitting in your echomail\out directory that is not being
sent when you fidopoll?
If yes, is it a packet that's compressed or it it raw? Is there a
corresponding BSO file with it?
What did your MUTIL or FIDOPOLL logs show when creating this message /
sending it.?

..or based on your comments about killing the .bsy semaphores are you experiencing a problem there?

Sorry, just trying to understand what the situation is so I can help :)

Best, Paul

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

On 11/28/16, Avon said the following...

When you say 'stuck' what do you mean?

Just that it hasn't gotten to FSXNet even now I think.

Is there a packet sitting in your echomail\out directory that is not
being sent when you fidopoll?

Looking this is what I see:
pi@dmz:/mystic $ ls echomail/out/fidonet
00010064.flo 00010091.pnt

pi@dmz:/mystic $ cat echomail/out/fidonet/00010064.flo ^/mystic/echomail/out/fidonet/0000002d.mo2

pi@dmz:/mystic $ hexedit echomail/out/fidonet/00010091.pnt
hexedit: echomail/out/fidonet/00010091.pnt: Not a file.

pi@dmz:/mystic $ ls -la echomail/out/fidonet
total 16
drwxr-xr-x 3 pi pi 4096 Nov 27 19:15 .
drwxr-xr-x 4 pi pi 4096 Aug 29 12:42 ..
-rw-r--r-- 1 pi pi 43 Nov 26 04:09 00010064.flo
drwxr-xr-x 2 pi pi 4096 Nov 27 19:15 00010091.pnt Ahh Directory!

Hmmm, it's empty.

If yes, is it a packet that's compressed or it it raw? Is there a corresponding BSO file with it?

As you can see no BSO whatever that is.

What did your MUTIL or FIDOPOLL logs show when creating this message / sending it.?

That was what I noticed first, fidopoll showed nothing (except a poll, no data). I'll have to look for it and see where I can send it from. Restarting mis cleared the hang so I got this message here on the old BBS setup as .1,
the pi@dmz is showing the main bbs. This .1 shows as pi@rpi2:/mystic.
Still stuck there showing as Stat: Local, hmm maybe it got created as Local! Not sure why, but the message you replied to is right after the stuck one now. I'll try sending it again from here (the old .1 - old in this case is 1.11).

--- Mystic BBS v1.11 (Raspberry Pi)
* Origin: Old Mystic Pi BBS bcw142.zapto.org:2324 (21:1/145.1)