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.
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.
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.
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.
Re: SBBSECHO Errors since 2/27 Build
By: DesotoFireflite to Digital Man on Fri Mar 04 2022 08:34 am
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.
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.
On Fri, 4 Mar 2022 23:29:46 -0800
"Digital Man" <digital.man@VERT> wrote:
Re: SBBSECHO Errors since 2/27 Build
By: DesotoFireflite to Digital Man on Fri Mar 04 2022 08:34 am
on another matter, is there a sbbsecho switch/option toAlso running one of those sbbsecho command-lines manually
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.
You can use pktdump with the -split option on a bad packet and it'll extract any good messages. I'm sure it could be scripted but I do it manually when I spot them. At least you can salvage some messages from
a packet.
You can use pktdump with the -split option on a bad packet and
it'll extract any good messages. I'm sure it could be scripted
but I do it manually when I spot them. At least you can salvage
some messages from a packet.
That worked fine, I was able to save alot of them with that method.
What bugs me is I should not be getting that many bad packets from my
hub. I get about 4 or 5 a day. I'm just going to make an event that
will process the bad ones with pktdump, and delete when done. Thanks
for the info.
Sysop: | Nelgin |
---|---|
Location: | Plano, TX |
Users: | 606 |
Nodes: | 10 (0 / 10) |
Uptime: | 136:13:17 |
Calls: | 9,608 |
Calls today: | 3 |
Files: | 16,059 |
Messages: | 1,062,030 |
Posted today: | 7 |