Greetings,

I have started getting a "Smapi" out of bounds I believe error when doing an echo scan? Is that a husky issue? If so what should I look for? Im on linux
if that is important, sorry I am not at that machine currently if you need exact error I can post that later..

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/29 (Windows/64)
* Origin: Abacus BBS! ---> bbs.abon.us:2323 (1:340/202)

Re: Echoscan error
By: Rick Smith to All on Sat May 02 2020 20:52:03

I have started getting a "Smapi" out of bounds I believe error when
doing an echo scan? Is that a husky issue? If so what should I look
for? Im on linux if that is important, sorry I am not at that
machine currently if you need exact error I can post that later..

yes, the exact error message is almost always necessary...

are you on 32bit or 64bit linux?

is your husky stuff compiled for 32bit or 64bit?

what message base format is the error occuring with?


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Greetings,

yes, the exact error message is almost always necessary...

fido@Thinkpad:~$ echoscan.shSMAPI ERROR: wrongly sized subfield occured!

are you on 32bit or 64bit linux?
is your husky stuff compiled for 32bit or 64bit?

64 bit linux, and I am sorry as I set this up all within a script I do not
know what husky is 32 or 64 How can I check for you?

So everything has been running just fine. Last couple of days if I run echoscan.sh from the command line I get the above error.

echoscan is a script that scans msgbase for outgoing msg's/ I tried pasting
it here but it jumbles up the code, would have looked like one of my old ansi messages!<VBG>

---
Regards,

Rick // Nitro

--- Mystic BBS v1.12 A46 2020/04/29 (Windows/64)
* Origin: Abacus BBS! ---> bbs.abon.us:2323 (1:340/202)

Re: Re: Echoscan error
By: Rick Smith to mark lewis on Sun May 03 2020 08:33:37

yes, the exact error message is almost always necessary...

fido@Thinkpad:~$ echoscan.shSMAPI ERROR: wrongly sized subfield occured!

weird... might be a corrupted message area... what format are you using for that message base area??

are you on 32bit or 64bit linux?
is your husky stuff compiled for 32bit or 64bit?

64 bit linux, and I am sorry as I set this up all within a script
I do not know what husky is 32 or 64 How can I check for you?

run file on the binaries...

$ file h*

hpt: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=8b6f581980c9e80c2cb70eac7a9a671b600388df, stripped

hptlink: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=ed05b0430831fabeb4bd11558b80214d9b1be11d, stripped

hpttree: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=28917d9ded201766bf007e34565a32fe549e54e2, stripped

htick: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.24, BuildID[sha1]=daa163ffffa35f03b3193e713f19a160416484b7, stripped

but looking at mine above, it doesn't look like it would be a 32bit vs 64bit problem...

So everything has been running just fine. Last couple of days if I
run echoscan.sh from the command line I get the above error.

hummm...

echoscan is a script that scans msgbase for outgoing msg's/ I tried pasting it here but it jumbles up the code, would have looked like
one of my old ansi messages!<VBG>

hahaha... you could maybe paste it to pastebin and give us the link to the paste... or just make it available via http or ftp or similar... maybe...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello Rick,

So everything has been running just fine. Last couple of days if I
run echoscan.sh from the command line I get the above error.

Was echoscan.sh working previously?

echoscan is a script that scans msgbase for outgoing msg's/ I tried pasting it here but it jumbles up the code, would have looked like one
of my old ansi messages!<VBG>

What happens if you run "hpt scan" from the command line?

I have never seen an error like the one you posted. If "hpt scan" runs correctly then there may be a typo in your echoscan.sh.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

See if this works
SEEN-BY: 50/109 153/757 154/10 30 40 50 700 203/0 221/0 6 227/201 400 280/464 SEEN-BY: 335/364 463/68 467/888 3634/12 4500/1 5000/111 5001/100 5005/49 SEEN-BY: 5010/352 5019/40 5020/828 846 1042 2047 4441 5053/51 55 5054/8 SEEN-BY: 5064/56 5080/68 102 5083/444 116/116 123/25 150 755 135/300 153/7715 SEEN-BY: 261/38 3634/15 27 50 119 123/50 14/6 300/4 123/160 170 3634/0 18/0 SEEN-BY: 123/0 1/120

Re: Echoscan error
By: Rick Smith to mark lewis on Sun May 03 2020 11:03:47

See if this works
SEEN-BY: 50/109 153/757 154/10 30 40 50 700 203/0 221/0 6 227/201 400

280/464

SEEN-BY: 335/364 463/68 467/888 3634/12 4500/1 5000/111 5001/100 5005/49 SEEN-BY: 5010/352 5019/40 5020/828 846 1042 2047 4441 5053/51 55 5054/8 SEEN-BY: 5064/56 5080/68 102 5083/444

nope, i don't think so... if those seenby lines are in your script, then it would appear that it got corrupted/crosslinked or you somehow managed to paste seenbys from some post into your script...


)\/(ark
--- SBBSecho 3.11-Linux
* Origin: SouthEast Star Mail HUB - SESTAR (1:3634/12)

Hello Rick,

@TID: Mystic BBS 1.12 A46
@MSGID: 1:340/202 cf54e070
@TZUTC: -0700
See if this works
SEEN-BY: 50/109 153/757 154/10 221/0 6 335/364 463/68 467/888 4500/1 5000/111
SEEN-BY: 5001/100 5005/49 5010/352 5019/40 5020/828 846 1042 2047 4441 5053/51
SEEN-BY: 5053/55 5054/8 5064/56 5080/68 102 5083/444
@PATH: 340/400 261/38 5020/1042 221/6

That's what I see here.

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)

Hello Rick,

See if this works

No tear or origin line.. Hmm..

Ttyl :-),
Al

--- GoldED+/LNX
* Origin: The Rusty MailBox - Penticton, BC Canada (1:153/757)