All,

I'm running into a weird, new problem with SBBSecho. I've got the latest binaries from 12/28, and am noticing with some of my downlinks in Radius, that SBBSecho has created a proper flo file, but the link contained in the file is broken.

In one instance, the file name is:

c:\sbbs\radius\files\Outbox\00DA0191.TMP/sbbs/radius/files/outbox/0000012b.SA0 (all slashes exactly as they appear)

It doesn't happen with all of the nodes, and I can't find anything in the fido log that looks out of sorts. The snippet where this file was created is below:

2018-12-29 20:50:35 Moving packet for 1:218/401: c:\sbbs\temp\sbbsecho\5c284e9e.pkt to c:\sbbs\radius\files\outbox\5c284e9e.pkt 2018-12-29 20:50:35 Packing packet (c:\sbbs\radius\files\outbox\5c284e9e.pkt) into bundle (c:\sbbs\radius\files\outbox\0000012b.SA0) for 1:218/401 using ZIP 2018-12-29 20:50:35 Executing: zip -jD c:\sbbs\radius\files\outbox\0000012b.SA0 c:\sbbs\radius\files\outbox\5c284e9e.pkt
2018-12-29 20:50:36 File (c:\sbbs\radius\files\outbox\0000012b.SA0, 4.5KB) for 1:218/401 added to BSO/FLO file: c:\sbbs\radius\files\outbox\00da0191.flo 2018-12-29 20:50:36 Deleting c:\sbbs\radius\files\outbox\5c284e9e.pkt (from line 2579)


Here's the output from sbbsecho:

C:\sbbs\exec>sbbsecho

SBBSecho v3.03-Win32 (rev 3.61) - Synchronet FidoNet EchoMail Tosser

Loading configuration files from C:\SBBS\CTRL\
SBBSecho 3.03-Win32 r3.61 Nov 28 2017 MSC 1800 invoked with options: Configured: 6 archivers, 51 linked-nodes, 6 echolists
NetMail directory: c:\sbbs\radius\netmail\
Secure Inbound directory: C:\SBBS\radius\files\inbox\
Non-secure Inbound directory: C:\SBBS\radius\files\inbox\
Outbound (BSO root) directory: C:\SBBS\radius\files\outbox\
Reading ../data/AREAS.BBS

And here's the path setting in echocfg:

°°°°°°°°°°°°°°°°°°º ³Global Settings... º°°°°°°°°°°°°°°°°°° °°É[þ][?]ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»°°
°°º Paths and Filenames º°° °°ÌÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ͹°°
°°º ³Non-secure Inbound Directory ../radius/files/inbox/ º°°
°°º ³Secure Inbound Directory ../radius/files/inbox/ º°°
°°º ³Outbound Directory ../radius/files/outbox/ º°°
°°º ³Area File ../data/areas.bbs º°°
°°º ³Bad Area File ../data/badareas.lst º°°
°°º ³Log File ../data/fido.log º°°
°°º ³Echo Statistics File ../data/echostats.ini º°°
°°º ³Temporary File Directory ../temp/sbbsecho º°°
°°º ³Outgoing Semaphore File º°° °°ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ°°



Any clues on where to look?

Thanks!

---
þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org

Re: SBBS and temp files/directories
By: poindexter FORTRAN to All on Sun Dec 30 2018 02:40 am

All,

I'm running into a weird, new problem with SBBSecho. I've got the latest binaries from 12/28, and am noticing with some of my downlinks in Radius, that SBBSecho has created a proper flo file, but the link contained in the file is broken.

In one instance, the file name is:

c:\sbbs\radius\files\Outbox\00DA0191.TMP/sbbs/radius/files/outbox/0000012b.S A0 (all slashes exactly as they appear)

A couple of things:

1. SBBSecho always appends to the end of flo files, so it's possible that the path ending in ".TMP" was already in the file, created by some other program.

2. SBBSecho always prefixes the path with either # (for truncation) or ^ (for deletion). Neither of these characters appear in the file contents you pasted.

It doesn't happen with all of the nodes, and I can't find anything in the fido log that looks out of sorts. The snippet where this file was created is below:

2018-12-29 20:50:35 Moving packet for 1:218/401: c:\sbbs\temp\sbbsecho\5c284e9e.pkt to c:\sbbs\radius\files\outbox\5c284e9e.pkt 2018-12-29 20:50:35 Packing packet (c:\sbbs\radius\files\outbox\5c284e9e.pkt) into bundle (c:\sbbs\radius\files\outbox\0000012b.SA0) for 1:218/401 using ZIP 2018-12-29 20:50:35 Executing: zip -jD c:\sbbs\radius\files\outbox\0000012b.SA0 c:\sbbs\radius\files\outbox\5c284e9e.pkt
2018-12-29 20:50:36 File (c:\sbbs\radius\files\outbox\0000012b.SA0, 4.5KB) for 1:218/401 added to BSO/FLO file: c:\sbbs\radius\files\outbox\00da0191.flo 2018-12-29 20:50:36 Deleting c:\sbbs\radius\files\outbox\5c284e9e.pkt (from line 2579)

Here's the output from sbbsecho:

C:\sbbs\exec>sbbsecho

SBBSecho v3.03-Win32 (rev 3.61) - Synchronet FidoNet EchoMail Tosser

Loading configuration files from C:\SBBS\CTRL\
SBBSecho 3.03-Win32 r3.61 Nov 28 2017 MSC 1800 invoked with options: Configured: 6 archivers, 51 linked-nodes, 6 echolists
NetMail directory: c:\sbbs\radius\netmail\
Secure Inbound directory: C:\SBBS\radius\files\inbox\
Non-secure Inbound directory: C:\SBBS\radius\files\inbox\
Outbound (BSO root) directory: C:\SBBS\radius\files\outbox\
Reading ../data/AREAS.BBS

And here's the path setting in echocfg:

°°°°°°°°°°°°°°°°°°º ³Global Settings... º°°°°°°°°°°°°°°°°°° °°É[þ][?]ÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ»°°
°°º Paths and Filenames º°° °°ÌÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ͹°°
°°º ³Non-secure Inbound Directory ../radius/files/inbox/ º°°
°°º ³Secure Inbound Directory ../radius/files/inbox/ º°°
°°º ³Outbound Directory ../radius/files/outbox/ º°°
°°º ³Area File ../data/areas.bbs º°°
°°º ³Bad Area File ../data/badareas.lst º°°
°°º ³Log File ../data/fido.log º°°
°°º ³Echo Statistics File ../data/echostats.ini º°°
°°º ³Temporary File Directory ../temp/sbbsecho º°°
°°º ³Outgoing Semaphore File º°° °°ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ°°

Any clues on where to look?

Everything from SBBSecho's perspective looks normal/correct. I wonder if Radius or some other software you're running is writing to the flo files and doing something wierd (or not locking via .bsy file)?

digital man

Synchronet/BBS Terminology Definition #7:
BinkP = BinkD Protocol
Norco, CA WX: 47.6øF, 31.0% humidity, 2 mph SSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net

Re: SBBS and temp files/directories
By: Digital Man to poindexter FORTRAN on Sun Dec 30 2018 04:42 am

Everything from SBBSecho's perspective looks normal/correct. I wonder if Radius or some other software you're running is writing to the flo files and doing something wierd (or not locking via .bsy file)?

I reverted to my old binaries (3.61 from 11/28/2017) and the problem seems to have gone away. There's probably a lot of cruft there, this \sbbs directory has been running and updated since 2006 or so.

---
þ Synchronet þ realitycheckBBS -- http://realitycheckBBS.org

Re: SBBS and temp files/directories
By: poindexter FORTRAN to Digital Man on Tue Jan 01 2019 08:12 pm

Re: SBBS and temp files/directories
By: Digital Man to poindexter FORTRAN on Sun Dec 30 2018 04:42 am

Everything from SBBSecho's perspective looks normal/correct. I wonder if Radius or some other software you're running is writing to the flo files and doing something wierd (or not locking via .bsy file)?

I reverted to my old binaries (3.61 from 11/28/2017) and the problem seems to have gone away.

Something *else* was writing to that flo file (not SBBSecho or Synchronet), so unless you changed the version of *that* software (Radius?), I don't think you've actually resolved anything. It's probably just coincidental that the problem hasn't occurred since you reversed to some old version of Synchronet (11-28-2017, should've been a v3.17a build).

There's probably a lot of cruft there, this \sbbs
directory has been running and updated since 2006 or so.

That shouldn't matter. <shrug>

digital man

This Is Spinal Tap quote #19:
Oh then, maybe it's not green. Anyway this is what I sleep in sometimes.
Norco, CA WX: 43.2øF, 26.0% humidity, 0 mph WSW wind, 0.00 inches rain/24hrs

---
þ Synchronet þ Vertrauen þ Home of Synchronet þ [vert/cvs/bbs].synchro.net