Just letting you know about a new message base that I have just configured, tqw_gentech - this will be similar to the tqw_gensci base
but have news posted relating to tech rather than science.
I been shouting this forever. :P Well, Hacker_News, but I'll teake Gen_Tech.
w00t w00t I'll be on the lookout for it.
I did just subscribe everyone to it, so feel free to unsub if you don't
want your system to get that base...
Am 15.06.21 schrieb MeaTLoTioN@1337:1/101 in TQW_GEN:
Hallo Meatlotion,
I did just subscribe everyone to it, so feel free to unsub if you don't want your system to get that base...
Ah, that's why a got an entry in my badareas.lst file :)
(and I have configured monit to send me an email as soon as this file
gets any content *g*)
I'm curious to find out what will be in this echo :)
You should have a whole bunch of messages in this new area as of this morning, hope that this information is received well by everyone here =)
I been shouting this forever. :P Well, Hacker_News, but I'll teake Gen_Tech.
w00t w00t I'll be on the lookout for it.
Yessir you have, and I hope to get hacker news feed also soon =) Christian aka MeaTLoTioN
You should have a whole bunch of messages in this new area as of this morning, hope that this information is received well by everyone here =)
Re: Re: new message base
By: MeaTLoTioN to acn on Wed Jun 16 2021 12:01 pm
You should have a whole bunch of messages in this new area as of this morning, hope that this information is received well by everyone here
Maybe it's just me, but I seem to be getting many errors daily for bad packetswith grunged messages for only this echo.
Most recent (all times are EDT):
2021-06-17 12:32:50 Unpacking bundle: C:\sbbs\fido\inbound\0000ffce.tha (41.4KB)
2021-06-17 12:32:50 Importing C:\sbbs\fido\inbound\0a62913f.pkt (Type 2e, 32.0KB) from 1337:3/100 to 1337:3/150
2021-06-17 12:32:50 Grunged message (type 2) from 1337:3/100 at offset 4913 inpacket: C:\sbbs\fido\inbound\0a62913f.pkt
2021-06-17 12:32:50 Bad packet detected: C:\sbbs\fido\inbound\0a62913f.pkt2021-06-17 12:32:50 Importing C:\sbbs\fido\inbound\0a655139.pkt (Type 2e,51.3KB) from 1337:3/100 to 1337:3/1502021-06-17 12:32:50 Importing
C:\sbbs\fido\inbound\0a66b137.pkt (Type 2e,21.5KB) from 1337:3/100 to 1337:3/1502021-06-17 12:32:50 Grunged message (type 2) from 1337:3/100
at offset 10131 inpacket: C:\sbbs\fido\inbound\0a66b137.pkt
2021-06-17 12:32:50 Bad packet detected:
C:\sbbs\fido\inbound\0a66b137.pkt
Maybe I need to delete messages on my end and do a rescan?
You should have a whole bunch of messages in this new area as ofMaybe it's just me, but I seem to be getting many errors daily for
this morning, hope that this information is received well by
everyone here
bad packetswith grunged messages for only this echo.
I'm having the same problem. I assumed it was because I didn't have the new message area setup. I've added the new area as a message base, so I'm hopeful the .bad packets issue will be resolved on the next run.
Re: Re: new message base
By: Bob Roberts to MeaTLoTioN on Sat Jun 19 2021 09:31 am
I'm having the same problem. I assumed it was because I didn't have t new message area setup. I've added the new area as a message base, so hopeful the .bad packets issue will be resolved on the next run.
Oh, I noticed the problem after I had set up the message area. Some messageswere importing fine, while others were being reported as grunged.
I ended up unsubbing from the echo, at least for now. Maybe I'll try it againat some point.
Oh, I noticed the problem after I had set up the message area. SomeAh shucks, well don't know what is making the messages get reported as grunged. Is it only happening with synchronet bbses I wonder?
messageswere importing fine, while others were being reported as grunged. [...]
pktdump says that there are "Corrupted Message Header"s...
I'm also using Synchronet and noticed that some messages get imported properly but many don't.
I also noticed .bad packages with messages for the new echo.
Here are some files that were't imported:
-rw-r--r-- 1 bbs bbs 24355 Jun 21 16:00 0cd6cefb.bad
-rw-r--r-- 1 bbs bbs 42536 Jun 21 16:30 0cd97f43.bad
-rw-r--r-- 1 bbs bbs 26050 Jun 21 17:00 0cdc4ed3.bad
-rw-r--r-- 1 bbs bbs 20608 Jun 21 17:15 0cdd9f28.bad
-rw-r--r-- 1 bbs bbs 3869 Jun 21 17:30 0cdeff1f.bad
-rw-r--r-- 1 bbs bbs 9650 Jun 21 18:30 0ce47b15.bad
pktdump says that there are "Corrupted Message Header"s...
pktdump says that there are "Corrupted Message Header"s...
Can you make some of those availabe so I can take a look.
My hub is running HPT, and I didnt have any bad messages from the new echo (and then my hub feeds my SBBS :)
My hub is running HPT, and I didnt have any bad messages from the new echo (and then my hub feeds my SBBS :)No problem.
You can download an archive here: http://files.imzadi.de/badpackets.tar.gz
Ahh, so as it turns out, I was going to expand your packets in my tmp
dir andlook at them, at which point I found a heap.
I think the problem is that the subject line is too long - it should
only be 71chars from memory.
We'll need to get ML to trim it when posting those messages.
I also noticed .bad packages with messages for the new echo.
Hi Anna, I think I have fixed it now, based on Deon's suggestion of the subject being no more than 71 chars for an SBBS system.
Hopefully the latest messages came through ok, any more problems let me know and I will try and fix them.
Re: Re: new message base
By: MeaTLoTioN to acn on Tue Jun 22 2021 12:07 pm
Hi Anna, I think I have fixed it now, based on Deon's suggestion of t subject being no more than 71 chars for an SBBS system.
Hopefully the latest messages came through ok, any more problems let know and I will try and fix them.
I'm still getting .bad packets as of right now.
-rw------- 1 sbbs sbbs 15842 Jun 22 02:16 0d39ccb7.bad
-rw------- 1 sbbs sbbs 13842 Jun 22 02:46 0d3c88cf.bad
-rw------- 1 sbbs sbbs 12842 Jun 22 03:02 0d3df87b.bad
-rw------- 1 sbbs sbbs 12924 Jun 22 03:31 0d40a8cd.bad
I looked in the packet and I see a 70 character subject, so it must be something else.
Hmm well that's interesting. What else can it be? Can you see anywhere that is giving a reason why it's bad? Do the logs suggest anything useful?
I'm still getting .bad packets as of right now.
-rw------- 1 sbbs sbbs 15842 Jun 22 02:16 0d39ccb7.bad
I looked in the packet and I see a 70 character subject, so it must be something else.
Hmm well that's interesting. What else can it be? Can you see anywhere that is giving a reason why it's bad? Do the logs suggest anything useful?
Can you zip up those bad packets and make it available for download? I'll take a look.
ML, the bad packets for me stopped last night - right after you changed the subject line length.
ML, the bad packets for me stopped last night - right after you chang the subject line length.
Bad packets are fixed. Looks good now, and I see new messages coming
in. Thanks.
Hi Anna, I think I have fixed it now, based on Deon's suggestion of the subject being no more than 71 chars for an SBBS system.
Hopefully the latest messages came through ok, any more problems let me
know and I will try and fix them.
The last .bad packages are from 12:30 yesterday, so it seems to be fixed. Thank you!
Dude! I'm loving the new GENTECH message base. Anything that limits my time onthe TrollNet is a good thing. Thanks!
ML, the bad packets for me stopped last night - right after you changed the subject line length.
Awesome, glad it's fixed for you as well. Think this just leaves Codefenix to confirm and we're golden.
Golden indeed! Many thanks.
| Sysop: | Shaun Ewing |
|---|---|
| Location: | Blue Mountains, Australia |
| Users: | 195 |
| Nodes: | 16 (0 / 16) |
| Uptime: | 218:09:26 |
| Calls: | 152 |
| Files: | 187,817 |
| Messages: | 328,111 |