3 Dec:04:2022:21:23:21 Linking area NETMAIL[...]
A Dec:04:2022:21:23:21 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:22 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:23 JAM ERROR: subfield is suspiciously large! (1414879828 bytes) A Dec:04:2022:21:23:23 JAM ERROR: wrongly sized subfield occured! A Dec:04:2022:21:23:24 JAM ERROR: subfield is suspiciously large! (976302592 bytes) A Dec:04:2022:21:23:24 JAM
ERROR: subfield is suspiciously large! (825360384 bytes) ----------------------- Sun 04 Dec 2022, hpt/lnx 1.9 2022-07-03
Dec:04:2022:21:23:25 Areas summary: 1 Dec:04:2022:21:23:25 End
when I view the message base using GoldED the last 4-5 messages are
empty.
I'm starting to see this error in my logs
3 Dec:04:2022:21:23:21 Linking area NETMAIL
A Dec:04:2022:21:23:21 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:22 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:23 JAM ERROR: subfield is suspiciously large!
when I view the message base using GoldED the last 4-5 messages are
empty.
is the base corrupt? How best to resolve?
Any tips/advice appreciated.
Hi there
I'm starting to see this error in my logs
3 Dec:04:2022:21:23:21 Linking area NETMAIL
A Dec:04:2022:21:23:21 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:22 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:23 JAM ERROR: subfield is suspiciously large! (1414879828 bytes)
A Dec:04:2022:21:23:23 JAM ERROR: wrongly sized subfield occured!
A Dec:04:2022:21:23:24 JAM ERROR: subfield is suspiciously large! (976302592 bytes)
A Dec:04:2022:21:23:24 JAM ERROR: subfield is suspiciously large! (825360384 bytes)
----------------------- Sun 04 Dec 2022, hpt/lnx 1.9 2022-07-03
1 Dec:04:2022:21:23:25 Start
1 Dec:04:2022:21:23:25 Start packing...
4 Dec:04:2022:21:23:25 EchoTossLogFile not found -> Scanning all areas
4 Dec:04:2022:21:23:25 Scanning NetmailArea NETMAIL
A Dec:04:2022:21:23:25 JAM ERROR: wrongly sized subfield occured!
4 Dec:04:2022:21:23:25 Scanning NetmailArea NETMSG
D Dec:04:2022:21:23:25 Statistics
D Dec:04:2022:21:23:25 areas: 2 msgs: 54
D Dec:04:2022:21:23:25 exported: 0
E Dec:04:2022:21:23:25 Areas summary:
1 Dec:04:2022:21:23:25 End
when I view the message base using GoldED the last 4-5 messages are empty.
is the base corrupt? How best to resolve?
Do you have a "-$m xxxx" on the line for that area, and have you been running sqpack?
Any tips/advice appreciated.
I would recommend storing netmail in OPUS MSG base and using https://brorabbit.g0x.ru/files/perl/maintmsg.pl
I have seen the same. You could try to delete those empty messages with GoldED and then run "sqpack NETMAIL".
Any tips/advice appreciated.
I would recommend storing netmail in OPUS MSG base and using
https://brorabbit.g0x.ru/files/perl/maintmsg.pl
thanks will check this out Stas.. :)
I don't know for what reason, but it seems to me that storing netmail in jam or squish is unnatural for it. I've noticed that this isn't the
first time that netmail has gotten into trouble with jam or squish.
Have a nice night.
I don't know for what reason, but it seems to me that storing netmail
in jam or squish is unnatural for it. I've noticed that this isn't
the first time that netmail has gotten into trouble with jam or
squish.
I have never seen JAM related problems in netmail and I have used JAM netmail from day zero with GEcho/GoldED/Concord/Etc...
SM>> I don't know for what reason, but it seems to me that storing netmail
SM>> in jam or squish is unnatural for it. I've noticed that this isn't
SM>> the first time that netmail has gotten into trouble with jam or
SM>> squish.
TK> I have never seen JAM related problems in netmail and I have used JAM
TK> netmail from day zero with GEcho/GoldED/Concord/Etc...
I can't say that I understand why this is happening. I just noticed that there are regular questions about netmail crashes in JAM or Squish in
various echo conferences. And no one has ever complained about MSG.
TK> I have never seen JAM related problems in netmail and I have used
JAM
TK> netmail from day zero with GEcho/GoldED/Concord/Etc...
I can't say that I understand why this is happening. I just noticed that
there are regular questions about netmail crashes in JAM or Squish in
various echo conferences. And no one has ever complained about MSG.
Hmm, strange. Well this is husky echo, are those questions/complaints related to husky?
The only problem running SQPACK is that it always renumbers the
message base. Not acceptable with nntp clients. :(
The only problem running SQPACK is that it always renumbers the
message base. Not acceptable with nntp clients. :(
Is that because sqpack doesn't have an option to not renumber,
something about the Squish format itself?
How do you purge messages in JAM without renumbering?
How do you purge messages in JAM without renumbering?
CrashMail II's 'crashmaint PACK' seems to work fine.
How do you purge messages in JAM without renumbering?
CrashMail II's 'crashmaint PACK' seems to work fine.
Thanks, I'll check it some day.
Does it work ok in Linux/64bit? Jamnntpd does not, and they are
related...
Hi Carlos.
How do you purge messages in JAM without renumbering?
CrashMail II's 'crashmaint PACK' seems to work fine.
Thanks, I'll check it some day.
Does it work ok in Linux/64bit? Jamnntpd does not, and they are related...
Does it work ok in Linux/64bit? Jamnntpd does not, and they are related...
I haven't tested it, but I believe so.
Both are available for Debian in 64-bit. Do we have to file a bug
report?
Both are available for Debian in 64-bit. Do we have to file a bug
report?
In this debian 64bit I tried "sudo apt install crashmail", then created a very
basic crashmail.prefs with one area
area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
keepnum 99
keepdays 99
crashmaint maint verbose
Processing rbb.test.9...
0 messages deleted by number, 4278124318 messages left
0 messages deleted by date, 4278124318 messages left
And the jam base is now broken. Hpt cannot work with it, Golded cannot work
with it. :(
So yes, we have to file a bug report. Just test by yourself and go ahead.
Both are available for Debian in 64-bit. Do we have to file a bug
report?
In this debian 64bit I tried "sudo apt install crashmail", then
created a very basic crashmail.prefs with one area
area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
keepnum 99
keepdays 99
crashmaint maint verbose
Processing rbb.test.9...
0 messages deleted by number, 4278124318 messages left
0 messages deleted by date, 4278124318 messages left
And the jam base is now broken. Hpt cannot work with it, Golded cannot work with it. :(
So yes, we have to file a bug report. Just test by yourself and go
ahead.
And the jam base is now broken. Hpt cannot work with it, Golded cannot
work with it. :(
So yes, we have to file a bug report. Just test by yourself and go
ahead.
If I'm not mistaken, the crashmail debian stuff was maintained by RJ Clay (as
was most FTN related debian packages), who hasn't been around in at *least* 2
years, and a small search does show someone with his name unfortunately passed
away on October 28, 2021. The bug report may not go anywhere for you if he was
the only person with read/write access. You may want to try one of the forks
(or create your own) and proceed from there. Just an FYI.
And the jam base is now broken. Hpt cannot work with it, Golded
cannot work with it. :(
So yes, we have to file a bug report. Just test by yourself and go
ahead.
If I'm not mistaken, the crashmail debian stuff was maintained by RJ Clay (as was most FTN related debian packages),
who hasn't been around in at *least* 2 years,
and a small search does show someone with his name
unfortunately passed away on October 28, 2021.
The bug report may not go anywhere for you if he was the only person
with read/write access.
You may want to try one of the forks (or create
your own) and proceed from there. Just an FYI.
Hi Oli.
Does it work ok in Linux/64bit? Jamnntpd does not, and they are
related...
I haven't tested it, but I believe so.
Not good enough for me. Not a matter of religion. :)
Both are available for Debian in 64-bit. Do we have to file a bug
report?
In this debian 64bit I tried "sudo apt install crashmail", then created a very basic crashmail.prefs with one area
area rbb.test.9 2:221/6 jam /bbs/piste/msgbase/rbb.test.9
keepnum 99
keepdays 99
crashmaint maint verbose
Processing rbb.test.9...
0 messages deleted by number, 4278124318 messages left
0 messages deleted by date, 4278124318 messages left
And the jam base is now broken. Hpt cannot work with it, Golded cannot work with it. :(
Sysop: | Nitro |
---|---|
Location: | Portland, OR |
Users: | 2 |
Nodes: | 10 (0 / 10) |
Uptime: | 27:28:25 |
Calls: | 132 |
Files: | 728 |
Messages: | 88,523 |