Rob

I got the following this morning from Wilfred. I can confirm from my own binkd and sbbsecho log files that this h appened. It seems (today at least) that this was a one time thing, but I dont know for sure if it may have happened previously unoticed.

The first instance was not for him, but for the node shown in the log, the second instance was indeed for him and was tossed.

Any ideas?

17:20:45.912 Packet is addressed to another node (2:203/0) --> packet
is renamed to .DST

It's about this file in binkd.log:

- 09 Mar 17:20:38 [12517] TIME Wed, 9 Mar 2016 11:20:42 -0500
...
- 09 Mar 17:20:40 [12517] receiving 09112041.pkt (10457 byte(s), off
0) + 09 Mar 17:20:40 [12517] 09112041.pkt ->
/home/fido/inbound/09112041.pkt + 09 Mar 17:20:40 [12517] rcvd:
09112041.pkt (10457, 10457.00 CPS, 1:249/303@fidonet)

A little later I receive another .pkt file with the same name:

- 09 Mar 17:22:41 [12577] receiving 09112041.pkt (959 byte(s), off 0)
+ 09 Mar 17:22:41 [12577] 09112041.pkt ->
/home/fido/inbound/09112041.pkt + 09 Mar 17:22:41 [12577] rcvd:
09112041.pkt (959, 959.00 CPS, 1:249/303@fidonet)

--- SBBSecho 2.32-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: duplicate.pkt names for different destinations
By: Joe Delahaye to Digital Man or ??? on Wed Mar 09 2016 07:37 pm

Rob

I got the following this morning from Wilfred. I can confirm from my own binkd and sbbsecho log files that this h appened. It seems (today at least) that this was a one time thing, but I dont know for sure if it may have happened previously unoticed.

The first instance was not for him, but for the node shown in the log, the second instance was indeed for him and was tossed.

Any ideas?

17:20:45.912 Packet is addressed to another node (2:203/0) --> packet
is renamed to .DST

It's about this file in binkd.log:

- 09 Mar 17:20:38 [12517] TIME Wed, 9 Mar 2016 11:20:42 -0500
...
- 09 Mar 17:20:40 [12517] receiving 09112041.pkt (10457 byte(s), off
0) + 09 Mar 17:20:40 [12517] 09112041.pkt ->
/home/fido/inbound/09112041.pkt + 09 Mar 17:20:40 [12517] rcvd:
09112041.pkt (10457, 10457.00 CPS, 1:249/303@fidonet)

A little later I receive another .pkt file with the same name:

- 09 Mar 17:22:41 [12577] receiving 09112041.pkt (959 byte(s), off 0)
+ 09 Mar 17:22:41 [12577] 09112041.pkt ->
/home/fido/inbound/09112041.pkt + 09 Mar 17:22:41 [12577] rcvd:
09112041.pkt (959, 959.00 CPS, 1:249/303@fidonet)

Are you saying you sent him a packet which was not actually addressed to him? If this happened, your sbbsecho.log file with the debug-level output should provide plenty of clues about how/why that did happen. Please inspect (search for that packet filename) or share the appropriate snippets.

digital man

Synchronet "Real Fact" #48:
Synchronet program was named 'sbbs' instead of 'sync' to avoid conflict w/Unix. Norco, CA WX: 55.7øF, 55.0% humidity, 15 mph ESE wind, 0.17 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: duplicate.pkt names for different destinations
By: Digital Man to Joe Delahaye on Wed Mar 09 2016 17:44:04

Are you saying you sent him a packet which was not actually addressed to him? If this happened, your sbbsecho.log file with the debug-level output should provide plenty of clues about how/why that did happen. Please inspect (search for that packet filename) or share the appropriate snippets.

Yes, apparently so, and my logs confirm. The first log entry went to 2:203/0, and all the rest went to 2:280/464. Hopefully these log entries from my sbbsecho log file will help some??





2016-03-09 11:20:38 Node (2:203/0) successfully locked via: C:\IM\packet.002\00cb0000.bsy
2016-03-09 11:20:38 Sending packet (C:\IM\packet\09112041.pkt) to 2:203/0 2016-03-09 11:20:38 File (C:\IM\packet\09112041.pkt) for 2:203/0 added to BSO/FLO file: C:\IM\packet.002\00cb0000.dlo

2016-03-09 11:20:38 Node (2:280/464) successfully locked via: C:\IM\packet.002\011801d0.bsy
2016-03-09 11:20:38 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:38 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:20:38 File (C:\IM\packet\09112041.pkt) for 2:280/464 added to BSO/FLO file: C:\IM\packet.002\011801d0.dlo

2016-03-09 11:20:39 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:39 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464


2016-03-09 11:20:40 Node (2:280/464) successfully locked via: C:\IM\packet.002\011801d0.bsy
2016-03-09 11:20:40 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:40 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:20:40 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:40 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:20:40 Deleting C:\IM\packet.002\011801d0.bsy

2016-03-09 11:22:40 Node (2:280/464) successfully locked via: C:\IM\packet.002\011801d0.bsy
2016-03-09 11:22:40 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:22:40 File (C:\IM\packet\09112041.pkt) for 2:280/464 added to BSO/FLO file: C:\IM\packet.002\011801d0.dlo
--- SBBSecho 2.32-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: duplicate.pkt names for different destinations
By: Joe Delahaye to Digital Man on Thu Mar 10 2016 11:41 am

Re: duplicate.pkt names for different destinations
By: Digital Man to Joe Delahaye on Wed Mar 09 2016 17:44:04

Are you saying you sent him a packet which was not actually addressed to him? If this happened, your sbbsecho.log file with the debug-level output should provide plenty of clues about how/why that did happen. Please inspect (search for that packet filename) or share the appropriate snippets.

Yes, apparently so, and my logs confirm. The first log entry went to 2:203/0, and all the rest went to 2:280/464. Hopefully these log entries from my sbbsecho log file will help some??

2016-03-09 11:20:38 Node (2:203/0) successfully locked via: C:\IM\packet.002\00cb0000.bsy
2016-03-09 11:20:38 Sending packet (C:\IM\packet\09112041.pkt) to 2:203/0 2016-03-09 11:20:38 File (C:\IM\packet\09112041.pkt) for 2:203/0 added to BSO/FLO file: C:\IM\packet.002\00cb0000.dlo

2016-03-09 11:20:38 Node (2:280/464) successfully locked via: C:\IM\packet.002\011801d0.bsy
2016-03-09 11:20:38 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:38 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:20:38 File (C:\IM\packet\09112041.pkt) for 2:280/464 added to BSO/FLO file: C:\IM\packet.002\011801d0.dlo

2016-03-09 11:20:39 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:39 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464

2016-03-09 11:20:40 Node (2:280/464) successfully locked via: C:\IM\packet.002\011801d0.bsy
2016-03-09 11:20:40 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:40 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:20:40 ERROR line 1836 renaming C:\IM\packet\09112041.pk_ to C:\IM\packet\09112041.pkt
2016-03-09 11:20:40 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:20:40 Deleting C:\IM\packet.002\011801d0.bsy

2016-03-09 11:22:40 Node (2:280/464) successfully locked via: C:\IM\packet.002\011801d0.bsy
2016-03-09 11:22:40 Sending packet (C:\IM\packet\09112041.pkt) to 2:280/464 2016-03-09 11:22:40 File (C:\IM\packet\09112041.pkt) for 2:280/464 added to BSO/FLO file: C:\IM\packet.002\011801d0.dlo

Those "ERROR ... renaming" errors are key. This issue was addressed in SBBSecho v2.33 (on Jan-26). Is there a reason you're still running v2.32?

digital man

Synchronet "Real Fact" #74:
Rob's alias "digital man" was inspired by a song on Rush's 1982 "Signals" album.
Norco, CA WX: 55.7øF, 55.0% humidity, 15 mph ESE wind, 0.17 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

Re: duplicate.pkt names for different destinations
By: Digital Man to Joe Delahaye on Thu Mar 10 2016 17:24:05

Those "ERROR ... renaming" errors are key. This issue was addressed in SBBSecho v2.33 (on Jan-26). Is there a reason you're still running v2.32?

No particular reason, although it was not that long ago I updated from the dailies. I will update in that case
--- SBBSecho 2.32-Win32
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net