Re: Synchronet BINKOUT event error
By: Nick Young to All on Mon Mar 08 2021 03:13 pm

3/8 15:12:32 evnt BINKOUT We got an M_EOB, but there are still 1 files pending M_GOT
3/8 15:12:34 evnt BINKOUT Error 104 (Connection reset by peer) in recv() of first byte of packet header, timeout = 120

Mail seems to be importing fine though, anyone seen this before? I am using Synchronet and sbbsecho/binkit.

I am using binkit here on the BBS and it works well with the binkd mailer at the other end.

I would ask your link if he is having any problems on his end. I don't know what software is at the other end but there seems to be a mis communication there and I don't think it is binkit doing that.

I have seen errors like this with irex on the other end and another poll was needed to get the job done. That was the best solution I could offer.

Ttyl :-),
Al

... Thesaurus: ancient reptile with an excellent vocabulary
--- SBBSecho 3.13-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Nick Young wrote to All <=-

Trying to setup Fidonet but getting the following error:

3/8 15:12:32 evnt BINKOUT We got an M_EOB, but there are still 1 files pending M_GOT 3/8 15:12:34 evnt BINKOUT Error 104 (Connection reset by peer) in recv() of first byte of packet header, timeout = 120

Mail seems to be importing fine though, anyone seen this before? I am using Synchronet and sbbsecho/binkit.

So, your mail is actually getting out and you are also receiving?

I sometimes see the M_EOB and M_GOT errors. I think it means that one side
was "moving a little faster" than the other. I never notice anything being missing. Actually, if I am running binkit manually using jsexec, I will
see that the transfers continue even after one of those messages show up.


... Computer Hacker wanted. Must have own axe.
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Al wrote (2021-03-08):

3/8 15:12:32 evnt BINKOUT We got an M_EOB, but there are still 1
files pending M_GOT
3/8 15:12:34 evnt BINKOUT Error 104 (Connection reset by peer) in
recv() of first byte of packet header, timeout = 120

Mail seems to be importing fine though, anyone seen this before? I
am using Synchronet and sbbsecho/binkit.

I am using binkit here on the BBS and it works well with the binkd mailer at the other end.

I would ask your link if he is having any problems on his end. I don't
know what software is at the other end but there seems to be a mis communication there and I don't think it is binkit doing that.

I see this error when I call a binkit node with binkd:

+ 13:23 [1393] sending /srv/ftn/outbound/fsxnet/21.2.116.0.out as 9f056b0c.pkt (954)
+ 13:23 [1393] sent: /srv/ftn/outbound/fsxnet/21.2.116.0.out (954, 477.00 CPS, 21:2/116@fsxnet)
*** Fatal error: The TLS connection was non-properly terminated.
*** Server has terminated the connection abnormally.

The last 2 lines are from gnutls-cli and this might be unrelated, but maybe the problem is on binkit's side.

---
* Origin: . (21:3/102)

Re: Synchronet BINKOUT event error
By: Oli to Al on Tue Mar 09 2021 01:51 pm

I see this error when I call a binkit node with binkd:

+ 13:23 [1393] sending /srv/ftn/outbound/fsxnet/21.2.116.0.out as 9f056b0c.pkt (954)
+ 13:23 [1393] sent: /srv/ftn/outbound/fsxnet/21.2.116.0.out (954, 477.00 CPS, 21:2/116@fsxnet)
*** Fatal error: The TLS connection was non-properly terminated.
*** Server has terminated the connection abnormally.

That's not a very graceful exit!

The last 2 lines are from gnutls-cli and this might be unrelated, but maybe the problem is on binkit's side.

Does the transfer complete as expected?

Maybe if we can get logs together we can pass them to the SBBS devs to look at.

You can poll my binkit mailer at trmb.synchro.net on port 24556, or 24553 for TLS. The node there is 1:153/757.2 or 21:4/106.1.

Ttyl :-),
Al

... Atheism is a non-prophet organization.
--- SBBSecho 3.13-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Re: Synchronet BINKOUT event error
By: Nick Young to All on Mon Mar 08 2021 03:13 pm

3/8 15:12:32 evnt BINKOUT We got an M_EOB, but there are still 1 files pending M_GOT
3/8 15:12:34 evnt BINKOUT Error 104 (Connection reset by peer) in recv() of first byte of packet header, timeout = 120

Mail seems to be importing fine though, anyone seen this before? I am using Synchronet and sbbsecho/binkit.

I am using binkit here on the BBS and it works well with the binkd mailer at the other end.

I would ask your link if he is having any problems on his end. I don't know what software is at the other end but there seems to be a mis communication there and I don't think it is binkit doing that.

I have seen errors like this with irex on the other end and another poll was needed to get the job done. That was the best solution I could offer.

Ttyl :-),
Al

... Thesaurus: ancient reptile with an excellent vocabulary
--- SBBSecho 3.13-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)

Nick Young wrote to All <=-

Trying to setup Fidonet but getting the following error:

3/8 15:12:32 evnt BINKOUT We got an M_EOB, but there are still 1 files pending M_GOT 3/8 15:12:34 evnt BINKOUT Error 104 (Connection reset by peer) in recv() of first byte of packet header, timeout = 120

Mail seems to be importing fine though, anyone seen this before? I am using Synchronet and sbbsecho/binkit.

So, your mail is actually getting out and you are also receiving?

I sometimes see the M_EOB and M_GOT errors. I think it means that one side
was "moving a little faster" than the other. I never notice anything being missing. Actually, if I am running binkit manually using jsexec, I will
see that the transfers continue even after one of those messages show up.


... Computer Hacker wanted. Must have own axe.
--- MultiMail
* Origin: Possum Lodge South * possumso.fsxnet.nz:7636/SSH:2122 (21:4/134)

Al wrote (2021-03-08):

3/8 15:12:32 evnt BINKOUT We got an M_EOB, but there are still 1
files pending M_GOT
3/8 15:12:34 evnt BINKOUT Error 104 (Connection reset by peer) in
recv() of first byte of packet header, timeout = 120

Mail seems to be importing fine though, anyone seen this before? I
am using Synchronet and sbbsecho/binkit.

I am using binkit here on the BBS and it works well with the binkd mailer at the other end.

I would ask your link if he is having any problems on his end. I don't
know what software is at the other end but there seems to be a mis communication there and I don't think it is binkit doing that.

I see this error when I call a binkit node with binkd:

+ 13:23 [1393] sending /srv/ftn/outbound/fsxnet/21.2.116.0.out as 9f056b0c.pkt (954)
+ 13:23 [1393] sent: /srv/ftn/outbound/fsxnet/21.2.116.0.out (954, 477.00 CPS, 21:2/116@fsxnet)
*** Fatal error: The TLS connection was non-properly terminated.
*** Server has terminated the connection abnormally.

The last 2 lines are from gnutls-cli and this might be unrelated, but maybe the problem is on binkit's side.

---
* Origin: . (21:3/102)

Re: Synchronet BINKOUT event error
By: Oli to Al on Tue Mar 09 2021 01:51 pm

I see this error when I call a binkit node with binkd:

+ 13:23 [1393] sending /srv/ftn/outbound/fsxnet/21.2.116.0.out as 9f056b0c.pkt (954)
+ 13:23 [1393] sent: /srv/ftn/outbound/fsxnet/21.2.116.0.out (954, 477.00 CPS, 21:2/116@fsxnet)
*** Fatal error: The TLS connection was non-properly terminated.
*** Server has terminated the connection abnormally.

That's not a very graceful exit!

The last 2 lines are from gnutls-cli and this might be unrelated, but maybe the problem is on binkit's side.

Does the transfer complete as expected?

Maybe if we can get logs together we can pass them to the SBBS devs to look at.

You can poll my binkit mailer at trmb.synchro.net on port 24556, or 24553 for TLS. The node there is 1:153/757.2 or 21:4/106.1.

Ttyl :-),
Al

... Atheism is a non-prophet organization.
--- SBBSecho 3.13-Linux
* Origin: The Rusty MailBox - Penticton, BC Canada (21:4/106.1)