Subj : sbbsecho issue
To   : Dumas Walker
From : Digital Man
Date : Tue Sep 09 2025 16:54:15

  Re: sbbsecho issue
  By: Dumas Walker to DIGITAL MAN on Tue Sep 09 2025 10:53 am

 > I ran into a problem with sbbsecho this morning.  I noticed the FIDOIN &
 > FIDOOUT events were hanging.  I checked the sbbsecho.log and could not find
 > any error messages, and there were no error messages showing up in the
 > console.
 >
 > Killing the hung instances, opening a terminal, and running sbbsecho by hand
 > gave me this information:
 >
 > Node (618:250/1.9) externally locked via:
 > /sbbs/fido/out.26a/00fa0001.pnt/00000009.bsy (since ??:??)
 >
 > I checked and that bsy file did not exist.  However, I also noticed that
 > there was a directory permission issue.  Once fixed, sbbsecho continued and
 > exited normally.
 >
 > Would it be possible to have some error message show up either on the sbbs
 > console, or at least the sbbsecho.log, when something like this is
 > happening? As noted above, the only way I saw and fixed the error was by
 > running
 > sbbsecho manually.

That same message would have been written to the sbbsecho.log file. The lock
attempt is retried (after the configurable number of BSO lock delay seconds) and gives up (and logs a warning about "Giving up") after the configured number of BSO lock attempts. All of these messages would be written to your sbbsecho.log file as well as the console. The only reason they would not be written to the log file is if you had your "Log Level" set to something less (more severe) than "Informational" in echocfg->Global Settings.
-- 
                                            digital man (rob)

Steven Wright quote #23:
My mechanic told me, I couldn't repair your brakes, so I made your horn louder
Norco, CA WX: 81.0øF, 48.0% humidity, 10 mph WNW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.29-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.