Avon, I'm ready to start to debug why Crytopgenic is having some
troubles when you are about...
Happy to do so.
Seems CH does not know my AKA?
Yeah, I noticed today a bug in my commit yesterday - I'm pushing out the update now, so it should be happier once that is active in a few minutes.
Yeah, I noticed today a bug in my commit yesterday - I'm pushing out the update now, so it should be happier once that is active in a few minutes.
I can see connects now but still some errors towards the end of the session.
bytes, which I receive and reply with a confirmation - but your system keeps sending it to me.
I might have had something similar here. I replied to a message and it sent to clearing houz but Mystic was stuck on "waiting for sent confirmation" and then tried sending it again the next time I polled.
I'll play with that here a bit and see if I can gather some logs for you.
And trying to send it again with more verbose logging set:
Leave that message in the queue, and I'll enable some more debugging to see if I can figure out what is going on. If you can turn up your
logging and sending me a copy that might be helpful as well.
Does Mystic have "NR mode"? If you turn that on, does the transfer work OK?
It doesn't look like Mystic has a non reliable mode:
Oh, OK.
I've turned of NR mode on my side, lets see if that is the reason...
OK, it isnt an NR mode issue, per se - I think my side is sending a
"GET" when it shouldnt (unless in NR mode). I've just pushed an update
to stop that, lets see if that helps...
+ 2023.07.08 17:28:56 1-R: GET 05247b21.pkt 391 1688851568 0+ 2023.07.08 17:29:26 1-Session timeout
Still seems to be an issue. I just sent another test in FSX_TST and had it send to both 3/100 and 3/2744.
When sending to 3/100 I received a "GOT 05887e72.pkt" once your side received it. When sending to Clearing Houz I'm not getting back anything now.
I noticed yesterday I was getting a "GET <packetname>" and not "GOT <packetname>" from Clearing Houz, could that be something?
Yes, I can see in my logs that I'm queuing that up to be sent, but I'll need to turn up my debugging to see that it is actually sent. (And clearly its not, since you dont receive it.)
(And it is sent pretty much immediately - yet 30s later, mystic is closing the connection.)
So I worked it out.
I was actually sending you the GOT that I received your file, but that
was after I was also sending an extra EOB (End of batch) - ie: I have no more files for you. I'm thinking that extra EOB was messing things up.
Could you send another packet, hopefully that was it and I havent messed anythign else up...
On 11 Jul 2023, deon said the following...
That seemed to do the trick:
Thanks, I see it worked, but I saw another problem (you didnt get a
reply to the TEST back?).
I dont think Mystic supports multibatch, but I saw another problem where
I created the reply to the test, but your system disconnected after successfully sending the packet.
I'll work on that (related to something else that I wanted to improve),
so that you dont miss messages...
Sysop: | Chris Crash |
---|---|
Location: | Huntington Beach, CA. |
Users: | 584 |
Nodes: | 8 (0 / 8) |
Uptime: | 06:11:28 |
Calls: | 10,746 |
Files: | 5 |
Messages: | 447,235 |
Posted today: | 1 |