To: Digital Man
Rob, have you been getting any reports form other on errors on sbbsecho since the 2/27/22 nightly build. I deleted a log of the log before I realize a problem might exist, but here is yesterdays and part of todays error log.
I've also included the sbbsecho log at the bottom, along with the even log. I'm going to download todays build to see if that helps later today.

Tue Mar 1 21:59:55 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned -1073740791

Tue Mar 1 22:59:44 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Tue Mar 1 22:59:55 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Tue Mar 1 23:59:44 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Tue Mar 1 23:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 00:59:44 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 00:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 01:59:44 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 01:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 02:59:44 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 02:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 03:59:44 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 03:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 04:59:44 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 04:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 05:59:45 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 05:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 06:59:45 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 06:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

Wed Mar 2 07:59:45 2022 master/5b105677f
evnt FIDOOUT Timed event: FIDOOUT returned 1

Wed Mar 2 07:59:56 2022 master/5b105677f
evnt FIDOIN Timed event: FIDOIN returned 1

This is from the event log

3/2 07:59:45a FIDOOUT Running native timed event: FIDOOUT
3/2 07:59:45a FIDOOUT Executing external: c:\SBBS\exec\sbbsecho.exe -linf
3/2 07:59:45a FIDOOUT Timed event: FIDOOUT returned 1
3/2 07:59:56a FIDOIN Running native timed event: FIDOIN
3/2 07:59:56a FIDOIN Executing external: c:\SBBS\exec\sbbsecho.exe -lesr!
3/2 07:59:56a FIDOIN Timed event: FIDOIN returned 1

This is from the sbbsecho log.

2022-03-02 07:59:45 Mutex file exists (c:\SBBS\ctrl\sbbsecho.bsy): SBBSecho appears to be already running
2022-03-02 07:59:45 SBBSecho (PID 5536) exiting with error level 1
2022-03-02 07:59:56 Mutex file exists (c:\SBBS\ctrl\sbbsecho.bsy): SBBSecho appears to be already running
2022-03-02 07:59:56 SBBSecho (PID 1164) exiting with error level 1

I deleated the sbbsecho.bsy file several times, and it keeps coming back. Last night, I zipped up all the mail packets, and moved them out of the directory, and it successfuly ran for the next mail run, but it started again after that.

This is the message inside the sbbsecho.bsy file.

3884 SBBSecho 3.14-Win32 master/5b105677f Feb 27 2022 MSC 1929

Just reporting, hopefully it goes away after I install the new build.

SysOp: C.G. Learn, AKA: DesotoFireflite
Valhalla Home Services! - (Synchronet) - bbs.valhallabbs.com
Valhalla II! - (GAP) - bbs.valhallabbs.com:24
Valhalla III! - (RemoteAccess) - bbs.valhallabbs.com:5023
Valhalla IIII! - (Dungeons & Dragons BBS) - bbs.valhallabbs.com:26
Valhalla Home Services Web! - http://bbs.valhallabbs.com
A Gamers Paradise - Over 150 Registered Online Game Doors!
Home Of Odin's Maze Game Server!

--- CAT (n.), Furry keyboard cover.
■ Synchronet ■ Valhalla Home Services ■ USA ■ http://valhalla.synchro.net
--- Synchronet 3.19c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: DesotoFireflite
Re: SBBSECHO Errors since 2/27 Build
By: DesotoFireflite to Digital Man on Wed Mar 02 2022 08:46 am

> Rob, have you been getting any reports form other on errors on sbbsecho
> since the 2/27/22 nightly build. I deleted a log of the log before I realize
> a problem might exist, but here is yesterdays and part of todays error log.
> I've also included the sbbsecho log at the bottom, along with the even log.
> I'm going to download todays build to see if that helps later today.

Also running one of those sbbsecho command-lines manually (from a command prompt) and then reporting the output would be helpful. Usually, a stale lock file indicates that it's crashing for some reason. No other reports of SBBSecho crashing lately.
--
digital man (rob)

Synchronet/BBS Terminology Definition #59:
PETSCII = PET Standard Code of Information Interchange (a.k.a. CBM ASCII)
Norco, CA WX: 68.9°F, 32.0% humidity, 0 mph ENE wind, 0.00 inches rain/24hrs
--- Synchronet 3.19c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: Digital Man
Re: SBBSECHO Errors since 2/27 Build
By: Digital Man to DesotoFireflite on Wed Mar 02 2022 09:43 am

DM> Re: SBBSECHO Errors since 2/27 Build
DM> By: DesotoFireflite to Digital Man on Wed Mar 02 2022 08:46 am

>> Rob, have you been getting any reports form other on errors on
>> sbbsecho since the 2/27/22 nightly build. I deleted a log of the log
>> before I realize a problem might exist, but here is yesterdays and
>> part of todays error log. I've also included the sbbsecho log at the
>> bottom, along with the even log. I'm going to download todays build to
>> see if that helps later today.

DM> Also running one of those sbbsecho command-lines manually (from a command
DM> prompt) and then reporting the output would be helpful. Usually, a stale
DM> lock file indicates that it's crashing for some reason. No other reports
DM> of SBBSecho crashing lately.
Just letting you know, as of build 3/2/22, the issue has cleared up, with no more problems.

on another matter, is there a sbbsecho switch/option to delete/kill a bad packet, instead of just adding .bad extension to them. I looked in the wiki, but just don't see anything. Thanks in Advance.

SysOp: C.G. Learn, AKA: DesotoFireflite
Valhalla Home Services! - (Synchronet) - bbs.valhallabbs.com
Valhalla II! - (GAP) - bbs.valhallabbs.com:24
Valhalla III! - (RemoteAccess) - bbs.valhallabbs.com:5023
Valhalla IIII! - (Dungeons & Dragons BBS) - bbs.valhallabbs.com:26
Valhalla Home Services Web! - http://bbs.valhallabbs.com
A Gamers Paradise - Over 150 Registered Online Game Doors!
Home Of Odin's Maze Game Server!

--- CAT (n.), Furry keyboard cover.
■ Synchronet ■ Valhalla Home Services ■ USA ■ http://valhalla.synchro.net
--- Synchronet 3.19c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net

To: DesotoFireflite
Re: SBBSECHO Errors since 2/27 Build
By: DesotoFireflite to Digital Man on Fri Mar 04 2022 08:34 am

> DM> Also running one of those sbbsecho command-lines manually (from a
> DM> command prompt) and then reporting the output would be helpful.
> DM> Usually, a stale lock file indicates that it's crashing for some
> DM> reason. No other reports of SBBSecho crashing lately.
>
> Just letting you know, as of build 3/2/22, the issue has cleared up, with no
> more problems.

Okay, good to know.

> on another matter, is there a sbbsecho switch/option to delete/kill a bad
> packet, instead of just adding .bad extension to them. I looked in the wiki,
> but just don't see anything. Thanks in Advance.

No, it's not option. Deleting inbound/*.bad would be a one-line event or script though, if that's what you want to do.
--
digital man (rob)

This Is Spinal Tap quote #21:
So when you're playing you feel like a preserved moose on stage?
Norco, CA WX: 50.6°F, 88.0% humidity, 0 mph ESE wind, 0.01 inches rain/24hrs
--- Synchronet 3.19c-Win32 NewsLink 1.113
* Vertrauen - Riverside County, California - telnet://vert.synchro.net