So if no one has any issues with the current BINKP or MIS2 then I am going to package up A36 for official release.

Please let me know if you have tried MIS2 and have any open issues. Paul if you see this how has the HUB ran with the newer release?

I expect A36 might be the last alpha for MIS before it goes away in A37!

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

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

Please let me know if you have tried MIS2 and have any open issues.
Paul if you see this how has the HUB ran with the newer release?

James, there was an issue overnight here. It seems Fidopoll stalled when polling a node and just sat locked up, not shutting down etc. The result was MIS2 has events backed up (overnight maint, semaphores for incoming and outgoing echomail, and a timed event for polling Usenet server) that were in limbo. It seemed that because the semaphore event that caused the failed fidopoll to run did not ever end, nothing else would run.. makes sense..

And when I did clear the fidopoll.bsy and run things, I needed to killall the *.bsy files to get things moving again.

Restarting MIS2 a bunch of events that were waiting to run then kicked off (overnights etc...) I closed MIS2 down again, let the MUTIL overnights
finish. Ran the mailin.ini to toss .TIC files and process a full echomail\in directory.

Ran Fidopoll send manually (without MIS2 / BinkP server etc. running) and saw the same lockup when polling reached the same node as last time.

CTRL-X to break Fidopoll out of it's stalled process, removed the *.bsy semaphore and *.bsy in echomail dirs... set the offending node to HOLD so Fidopoll would not deliver to it, re-ran fidopoll send and cleared held mail and files for CRASH nodes, then restarted MIS2...

Can you send me a Fidopoll with debugging logging on, and I will test again with this node to see what's up... at the moment I can't see anything other than an 'connected' followed by nothing ...

So folks that's why it's been quiet over the last 9 hours :)

Best, Paul

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

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

So if no one has any issues with the current BINKP or MIS2 then I am
going to package up A36 for official release.

Please let me know if you have tried MIS2 and have any open issues.
Paul if you see this how has the HUB ran with the newer release?

I expect A36 might be the last alpha for MIS before it goes away in A37!

I've not seen any issues on my end with ... whichever version I'm running.
QWK and FTN traffic seems to be flowing fine, and I've switched as many events/services over to MIS2 as I can.

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

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

So if no one has any issues with the current BINKP or MIS2 then I am
going to package up A36 for official release.

Please let me know if you have tried MIS2 and have any open issues.
Paul if you see this how has the HUB ran with the newer release?

Found this now pops up after updating to the most current and unsure why ..

MPL Invalid executable: newuserapp.mpx

This is messing up my newuser custom style I had done for my system. I am working to see if I can fix this tonight with some work around.

Cheers! Pequito

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

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

So if no one has any issues with the current BINKP or MIS2 then I am
going to package up A36 for official release.
Please let me know if you have tried MIS2 and have any open issues.
Paul if you see this how has the HUB ran with the newer release?
I expect A36 might be the last alpha for MIS before it goes away in A37!

did you get the report about the error message :

MPL Invalid executable: c:\mystic_a36\scripts\newuserapp.mpx when some one applies and we don't use that?

|08 .|05ú|13ù|15Dr|07e|08am Ma|07st|15er|13ù|05ú|08.
|08 øù|05ú|13ùø |13øù|05ú|08ùø
|11 DoRE|03!|11ACiDiC|03!|11Demonic |08[|15dreamland|09.|15darktech|09.|15org|08]

--- Mystic BBS v1.12 A36 2017/11/07 (Windows/64)
* Origin: |08--[|15!|07dreamland BBS dreamland.darktech.org (21:1/163)

Found this now pops up after updating to the most current and unsure why ..
MPL Invalid executable: newuserapp.mpx

Have you recompiled it with the latest version of mplc?

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

On 11/09/17, deepthaw said the following...

Found this now pops up after updating to the most current and unsure ..
MPL Invalid executable: newuserapp.mpx

Have you recompiled it with the latest version of mplc?

I don't even have one in my folder so why it is searching for it or trying to use it beyond me. =( This only started when I was testing A36.

Cheers!
Pequito

--- Mystic BBS v1.12 A35 (Linux/32)
* Origin: Twinkle BBS # (21:1/126)

James, there was an issue overnight here. It seems Fidopoll stalled when polling a node and just sat locked up, not shutting down etc. The result was MIS2 has events backed up (overnight maint, semaphores for incoming and outgoing echomail, and a timed event for polling Usenet server) that were in limbo. It seemed that because the semaphore event that caused
the failed fidopoll to run did not ever end, nothing else would run.. makes sense..

I've since seen this too. It doesn't really lock up it just needs you to
press a key on the keyboard its really odd. I've polled a system 100 times
and it hasn't happened though, so its very tricky.

Can you send me a Fidopoll with debugging logging on, and I will test again with this node to see what's up... at the moment I can't see anything other than an 'connected' followed by nothing ...

Unfortunately you wont see anything in the log as its not related to BINKP.

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

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

I've since seen this too. It doesn't really lock up it just needs you to press a key on the keyboard its really odd. I've polled a system 100 times and it hasn't happened though, so its very tricky.

Hmm.. OK I may try a forced poll to the node in question again, the thing is, in my case it was a halt when it polled the same node on two separate
occasions so I'd figured it might have been something in the handshake after connection... I'll do some more tests

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

On 11/10/17, Avon pondered and said...

I've since seen this too. It doesn't really lock up it just needs yo press a key on the keyboard its really odd. I've polled a system 100 times and it hasn't happened though, so its very tricky.

Hmm.. OK I may try a forced poll to the node in question again, the
thing is, in my case it was a halt when it polled the same node on two separate occasions so I'd figured it might have been something in the handshake after connection... I'll do some more tests

I tried another stand-alone poll to the node in question, same thing, it
shows connected then nada... just sits and nothing... until I ctrl-c ... pressing any key does not fix this, a fidopoll I can try with logging on it would be a good move for me to test with me thinks ;-)

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

Hmm.. OK I may try a forced poll to the node in question again, the
thing is, in my case it was a halt when it polled the same node on two separate occasions so I'd figured it might have been something in the handshake after connection... I'll do some more tests

Okay let me know. I had it happen to me once but not anytime recently, so I don't know if whatever it was has been fixed.

I have a test network set up here and I made a batch file that has FidoPoll calling MIS2 over and over again hundreds upon hundreds of times and there
has been no lockup.

But this is a local network so its not the best test base. I suspect its a socket library problem that is not really related to BINKP itself, only in that it is used *by* the BINKP server.

If you can reproduce it regularly that would be excellent! Also, if you have any system running the 11/09+ release and it happens let me know. Like I
said, I haven't seen it happen in a long time in my tests here.

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

I tried another stand-alone poll to the node in question, same thing, it shows connected then nada... just sits and nothing... until I ctrl-c ... pressing any key does not fix this, a fidopoll I can try with logging on it would be a good move for me to test with me thinks ;-)

Have you tried with the latest version though? 11/09?

I will make you one with logging that sounds like it could be different than the thing I saw. I will put it in the pre-alpha area.

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

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

I tried another stand-alone poll to the node in question, same thing, shows connected then nada... just sits and nothing... until I ctrl-c pressing any key does not fix this, a fidopoll I can try with logging it would be a good move for me to test with me thinks ;-)

Have you tried with the latest version though? 11/09?

I will make you one with logging that sounds like it could be different than the thing I saw. I will put it in the pre-alpha area.

Thanks for the debug version - appreciated ... and I have now updated 1/100 and 1/101 to both the latest version.

I installed 11/09 on 1/100 and then let things run for a few mins and grabbed the logs... saved them in a folder called 'v1109-after-install-at-hub'

Then I swapped out the fidopoll with the debugging version and let that run
one instance of processing and polling crash nodes... saved in a folder
called 'debug-hub-poll-all-crash-nodes'

Then I disabled processing of incoming/outbound traffic at 1/100 but kept
MIS2 BinkP running... did this so I could then run a test fidopoll (debug version) on the node causing issues y/day

Frustratingly when I did poll it (I had set it to hold so it was not part of the above tests) it worked fine. I have saved that telemetry as 'fido-node-xxx-debug.txt'

So at this point it's really hard to say if changes at my end have fixed
things or if the node found issues at their end over the last 24 hours and
self corrected it etc... not sure .. ;(

I have set the node to crash again, and reverted to the 11/09 standard
version of fidopoll now and will monitor over the next 24 hours to see what
(if anything) crops up :)

Don't want to tempt fate to say things are sorted just yet :)

I will zip all of the above data into a zip (g00r00.zip) and drop it in your filebox, at the very least it give you some more 'real world' telemetry to
have on file :)

Best, Paul

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

I will zip all of the above data into a zip (g00r00.zip) and drop it in your filebox, at the very least it give you some more 'real world' telemetry to have on file :)

Go figure it works when you're watching closely.

Thank you for collecting the data and trying to catch it.

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

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

Go figure it works when you're watching closely.
Thank you for collecting the data and trying to catch it.

I know... sigh... and you're welcome :)

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

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

So if no one has any issues with the current BINKP or MIS2 then I am
going to package up A36 for official release.

Please let me know if you have tried MIS2 and have any open issues.
Paul if you see this how has the HUB ran with the newer release?

I expect A36 might be the last alpha for MIS before it goes away in A37!

I'm running MIS2 exclusively and have not had any issues thus far.

Immortal

--- Mystic BBS v1.12 A36 2017/11/08 (Linux/64)
* Origin: Lightning BBS -- lightningbbs.com:2400 (21:1/185)