ATTN. Trevor: "Can't post to news.mozilla.org" - take two

[Barbara]

I initially posted the following on July 3, 2010, and apparently am
the only person who can see it. This post is from my laptop. Since I
did copy Pronews2 from an older computer to the one that is the
subject of this post, do you think a complete wipe-out and new
installation might fix things? Incidentally I've done the copy thing
from one computer to another and never had problems.

============= Following part Posted July 3, 2010 =================


Like everybody else, I've installed eCS20GA on a new computer and one
of the tasks was to migrate/copy/transfer (whatever word you like)
Pronews V1.60 from my old computer running Warp 4 to the new computer
running eCS.

Everything appears to be working great except ONE newsgroup,
mozilla.dev.ports.os2.

I can read, write, post, etc. to all other subscribed groups other
than this one. When I send a message to this group, it appears to go,
but never shows up. The odd line I see in the current LOG file is:

"03 Jul 11:12:16.23 TID 8 [WARNING] [ARTWND] Group Sent Messages#255
contains more articles (761) than NumAutoLimitHeaders (450) allows"

And yes, I have set the number of Headers to Automatically limit to
450. But it doesn't seem to bother any of the other subscribed
groups. The [WARNING} Only shows up when I attempt to post to-->
mozilla.dev.ports.os2.

I have unsubscribed and re-subscribed to this group with no change,
and I hate to reinstall Pronews from scratch when all else is working.

Any hints or suggestions?

[Trevor Hemsley]

On Sun, 24 Apr 2011 02:20:47 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
"03 Jul 11:12:16.23 TID 8 [WARNING] [ARTWND] Group Sent Messages#255
contains more articles (761) than NumAutoLimitHeaders (450) allows"
And yes, I have set the number of Headers to Automatically limit to
450. But it doesn't seem to bother any of the other subscribed
groups. The [WARNING} Only shows up when I attempt to post to-->
mozilla.dev.ports.os2.

Sent Messages is a special case group that never gets purged automatically.
Looks to me like you've found a bug by trying to artificially limit it to only
450 posts and the easy solution would be to increase the number allowed in that
group. Is your limit a global one or just in that group?

[Barbara]

On Sun, 24 Apr 2011 11:42:24 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
On Sun, 24 Apr 2011 02:20:47 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
"03 Jul 11:12:16.23 TID 8 [WARNING] [ARTWND] Group Sent Messages#255
contains more articles (761) than NumAutoLimitHeaders (450) allows"
And yes, I have set the number of Headers to Automatically limit to
450. But it doesn't seem to bother any of the other subscribed
groups. The [WARNING} Only shows up when I attempt to post to-->
mozilla.dev.ports.os2.

Sent Messages is a special case group that never gets purged automatically.
Looks to me like you've found a bug by trying to artificially limit it to only
450 posts and the easy solution would be to increase the number allowed in that
group. Is your limit a global one or just in that group?

So far as I know the settings are global and identical on all
computers where I use Pronews. And when no one responded to the
invisible message, I messed around and NOW no longer see the buggy
comment you see above in my July 3 2010 log file.

Just now I just started Pronews on the mis-behaving computer, and went
online with the news.mozilla.org server. Everything connects and
shows up perfectly. Then I shut down. Here's the log snippet from
that operation:

24 Apr 06:59:57.30 TID 2 [INFO] ProNews/2 V1.60.cp125 started
24 Apr 06:59:57.30 TID 2 [INFO] PNMAXLOGSIZE is set to use 10 log
files of 250KB
24 Apr 06:59:57.31 TID 2 [INFO] Pronews can use virtual addresses >
512MB on this o/s!
24 Apr 06:59:57.31 TID 2 [INFO] Pronews has enabled filter
tokenisation.
24 Apr 06:59:57.31 TID 2 [INFO] Pronews has disabled bulk database
updates.
24 Apr 06:59:57.31 TID 2 [INFO] Pronews will single-thread UConv
operations.
24 Apr 07:04:32.27 TID 8 [INFO] [NNTP] Successfully connected to
[news.mozilla.org].
24 Apr 07:04:32.34 TID 8 [INFO] [NNTP] NNTP Server login message was
[200 news.mozilla.org]
24 Apr 07:04:32.51 TID 8 [INFO] [ARTWND] Refiltering
[mozilla.dev.ports.os2#1].
24 Apr 07:04:32.53 TID 8 [INFO] [ARTWND] Refiltering
[mozilla.dev.ports.os2#1] done.
24 Apr 07:07:10.14 TID 2 [INFO] ProNews/2 shut down.

My last two attempts to post to mozilla.dev.ports.os2 have failed to
show up in the group.

And for what it's worth, I'm using Pronews V. 1.59 on this ThinkPad
which I'm posting from right now. The newer computer which is unable
to post correctly is using Pronews V. 1.60.

[Trevor Hemsley]

On Sun, 24 Apr 2011 13:34:24 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
24 Apr 07:04:32.27 TID 8 [INFO] [NNTP] Successfully connected to
[news.mozilla.org].

Nothing obvious springs out at me from that lot. I would try increasing your
logging level by adding -3 to the list of parameters passed to pronews.exe from
its icon and see if it logs anything new. You could also try editing pronews.env
and uncommenting the PNDEBUG= line then restarting. Be aware that this logs all
data traffic between you and the server including passwords etc to the file
debug.log.

[Barbara]

On Mon, 25 Apr 2011 12:13:51 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
On Sun, 24 Apr 2011 13:34:24 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
24 Apr 07:04:32.27 TID 8 [INFO] [NNTP] Successfully connected to
[news.mozilla.org].

Nothing obvious springs out at me from that lot. I would try increasing your
logging level by adding -3 to the list of parameters passed to pronews.exe from
its icon and see if it logs anything new. You could also try editing pronews.env
and uncommenting the PNDEBUG= line then restarting. Be aware that this logs all
data traffic between you and the server including passwords etc to the file
debug.log.

I just don't have the skills to make any sense of this. Using the -3
parameter my "bad" machine running ProNews V 1.60 (log file) once spit
out (among many other things) the following:

25 Apr 07:50:15.04 TID 9 [DEBUG1] [NNTP] ugh, too many headers in
group mozilla.dev.ports.os2#1
25 Apr 07:50:15.04 TID 9 [DEBUG1] [NNTP] nfh.LastMsg=15224 nfh.Lo=2
nfh.Hi=15224 nfh.Num=450
25 Apr 07:50:15.04 TID 9 [DEBUG1] [ARTWND] Purged 3 headers from
mozilla.dev.ports.os2#1
25 Apr 07:50:15.04 TID 9 [DEBUG1] [ARTWND] AutoPurgeHeaders deleted 3
articles
25 Apr 07:50:15.04 TID 9 [INFO] [NNTP] Compacting bodies for
[mozilla.dev.ports.os2#1].
25 Apr 07:50:15.17 TID 9 [INFO] [ARTWND] Selecting bodies in
mozilla.dev.ports.os2#1 for deletion
25 Apr 07:50:15.17 TID 9 [DEBUG1] [ARTWND] Selected 3 bodies for
deletion from mozilla.dev.ports.os2#1
25 Apr 07:50:15.17 TID 9 [DEBUG1] [DBLOCK] disk space avail
23606345728, wanted 1108980, drive E:
25 Apr 07:50:15.17 TID 9 [DEBUG1] [ARTWND] Writing new bodies file
for mozilla.dev.ports.os2#1
25 Apr 07:50:15.18 TID 9 [DEBUG1] [ARTWND] Closing new bodies file,
deleted 3 bodies from mozilla.dev.ports.os2#1
25 Apr 07:50:15.18 TID 9 [DEBUG1] [ARTWND] Delete old bodies file
\ARTICLES\022754da.DAT for mozilla.dev.ports.os2#1
25 Apr 07:50:15.18 TID 9 [DEBUG1] [ARTWND] Renaming new bodies file
\ARTICLES\092754df.TMP to .\ARTICLES\022754da.DAT for
mozilla.dev.ports.os2#1

Then the next time I tried it, it didn't include the above statements.
Puzzling part is it looks perfectly normal from my perspective when
posting "new" or replying to group articles. That's in terms of the
"send" and "save" function. Sometimes they show up on my reader after
posting, sometimes they don't. And it's obvious they don't show up on
other people's readers.

And to make matters worse, the working ThinkPad has the following:
Pronews/2 V 1.59
eCS 1.2
Pronews installed on HPFS formatted directory

The non-working newer computer has this:
Pronews/2 V 1.60
eCS 2.0
Pronews installed on JFS formatted directory

I'm sure theres nothing strange about the differences, but there's a
tiny glitch somewhere, and after so much time puzzling over it I'm
ready to delete Pronews from the newer computer and perhaps trying a
new install on a FAT32 formatted directory.

[Steven Levine]

On Mon, 25 Apr 2011 15:00:28 UTC, "Barbara"
<***@nospam.attglobal.net> wrote:

Hi Barbara,

Post by Barbara
25 Apr 07:50:15.04 TID 9 [DEBUG1] [NNTP] ugh, too many headers in
group mozilla.dev.ports.os2#1

This is all normal. You triggered an auto-compact based on your
settings.

What you be more useful is the log from a failed posting attempt.

Post by Barbara
I'm sure theres nothing strange about the differences, but there's a
tiny glitch somewhere, and after so much time puzzling over it I'm
ready to delete Pronews from the newer computer and perhaps trying a
new install on a FAT32 formatted directory.

I guess it's possible you have news database corruption. You might
want to try some of the suggestions in utility.txt.

Run

CLNHDIDX

first. If any errors are reports, I would ask here before attempting
to correct them, unless you have a good backup of you news database.

Then run

SHOWHEAD /ERRORS mozilla.dev.ports.os2

Steven

[Barbara]

On Mon, 25 Apr 2011 17:07:14 UTC, "Steven Levine"

Post by Steven Levine
On Mon, 25 Apr 2011 15:00:28 UTC, "Barbara"
Hi Barbara,

Post by Barbara
25 Apr 07:50:15.04 TID 9 [DEBUG1] [NNTP] ugh, too many headers in
group mozilla.dev.ports.os2#1

This is all normal. You triggered an auto-compact based on your
settings.

That figures. :)

Post by Steven Levine
What you be more useful is the log from a failed posting attempt.

Only problem with this is I can't tell when the posting fails, and sit
here like a big ninny wondering why no one replies. In other words, I
can see them on the server, others can't. By the time I figure it
out, I have problems locating the "failed" post messages in the long
gone log file. I'll have to pay more attention the time, date,
hour-minute-second.

Post by Steven Levine

Post by Barbara
I'm sure theres nothing strange about the differences, but there's a
tiny glitch somewhere, and after so much time puzzling over it I'm
ready to delete Pronews from the newer computer and perhaps trying a
new install on a FAT32 formatted directory.

I guess it's possible you have news database corruption. You might
want to try some of the suggestions in utility.txt.
Run
CLNHDIDX
first. If any errors are reports, I would ask here before attempting
to correct them, unless you have a good backup of you news database.
Then run
SHOWHEAD /ERRORS mozilla.dev.ports.os2

Thanks Steven! I'll work on this. Only reason I haven't deleted
and started Pronews from scratch is that it's so *CLOSE* to working
properly and it is configured like all my other computers. When I
first installed eCS 2.0 on this newer computer, I was posting from
Pronews on that machine all the time in the ECS groups. People saw
them... People answered. I usually only read or lurk in the
mozilla.dev.ports.os2 group and rarely post.

[Steven Levine]

On Mon, 25 Apr 2011 18:24:48 UTC, "Barbara"
<***@nospam.attglobal.net> wrote:

Hi Barbara,

Post by Barbara
Only problem with this is I can't tell when the posting fails, and sit
here like a big ninny wondering why no one replies. In other words, I
can see them on the server, others can't.

What do you mean by you can see them on the server? If they were on
the server, anyone could see them. Do you mean that you can see them
in your Sent messages folder?

Post by Barbara
By the time I figure it
out, I have problems locating the "failed" post messages in the long
gone log file. I'll have to pay more attention the time, date,
hour-minute-second.

Assuming you don't have any unusual filters set up, the way it work is
that the message is sent to the newsgroup and the next time you fetch
articles from the newsgroup is shows up in the article window.

Post by Barbara
When I
first installed eCS 2.0 on this newer computer, I was posting from
Pronews on that machine all the time in the ECS groups. People saw
them... People answered. I usually only read or lurk in the
mozilla.dev.ports.os2 group and rarely post.

The the eCS newsserver and the Mozilla newsserver use different
newsserver software, but this should not affect your ability to post.
FWIW, the eCS newsserver is changi and it has more known issues that
the Mozilla newsserver.

Steven

[Barbara]

On Tue, 26 Apr 2011 02:33:35 UTC, "Steven Levine"

Post by Steven Levine
What do you mean by you can see them on the server? If they were on
the server, anyone could see them. Do you mean that you can see them
in your Sent messages folder?

I've confused my attempts to explain.

My posts from the "bad" computer to news.mozilla.org do NOT show up
for me or anyone else.

My posts from the "bad" computer to comp.os.os2.mail-news show up for
me on both my "bad" and "good" computers, but I'm not sure they show
up for anyone else. Trevor couldn't find my July 3, 2010 post
explaining the original problem.

I just posted a "Test post" titled message to comp.os.os2.mail-news
from the "bad" computer. I can see it from both my computers. Can
you see it? (I'm using the "good" computer right now.) So far no one
has replied.

[Barbara]

On Mon, 25 Apr 2011 17:07:14 UTC, "Steven Levine"

Post by Steven Levine
I guess it's possible you have news database corruption. You might
want to try some of the suggestions in utility.txt.
Run
CLNHDIDX

Here's the result from the "bad" computer:


======
This program will attempt to clean up your Pronews/2 1.5x headers.idx
file
It should be run from the \pronews directory.

It will ask for confirmation of all actions before it proceeds.

Pronews/2 must be shutdown before continuing
headers.idx contains 169 group entries
Read group entries from headers.idx and closed file
Server 68 Group eletedGroup ... [invalid]
Could not open file .\ARTICLES\0203435e.DAT, errno = 0
Remove entry for DeletedGroup from headers.idx? Y/N
======

At that point I bailed out and did not press Y

Post by Steven Levine
first. If any errors are reports, I would ask here before attempting
to correct them, unless you have a good backup of you news database.
Then run
SHOWHEAD /ERRORS mozilla.dev.ports.os2

The output from this exercise produced a 257,756 file full of header
information.

Should I go ahead and "yes" the response from CLNHDIDX? Keep in mind
it's not working correctly now, and I don't mind making it worse. A
new install is painful in terms of configuration, but I'm about ready
to go that route.

[Trevor Hemsley]

On Mon, 25 Apr 2011 19:21:03 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
The output from this exercise produced a 257,756 file full of header
information.

That's because the utility has been broken since the start of 2011. It has a
check for a valid date range in there and the upper limit was set to 2010.
Ignore those errors, they're probably not errors.

[Trevor Hemsley]

On Mon, 25 Apr 2011 15:00:28 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
Sometimes they show up on my reader after
posting, sometimes they don't. And it's obvious they don't show up on
other people's readers.

Your log excerpt only showed the group being closed and there didn't look to be
anything unusual in it.

Can you ping news.mozilla.org from both machines and make sure they point to the
same place please?

[Barbara]

On Mon, 25 Apr 2011 17:19:03 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
On Mon, 25 Apr 2011 15:00:28 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
Sometimes they show up on my reader after
posting, sometimes they don't. And it's obvious they don't show up on
other people's readers.

Your log excerpt only showed the group being closed and there didn't look to be
anything unusual in it.

I only posted that to say that sometimes I see it and sometimes I
don't, with no changes in settings or options.

Post by Trevor Hemsley
Can you ping news.mozilla.org from both machines and make sure they point to the
same place please?

They are identical:

"bad" computer:

[D:\]ping news.mozilla.org
PING news.mozilla.giganews.com: 56 data bytes
64 bytes from 216.196.97.169: icmp_seq=0. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=1. time=60. ms
64 bytes from 216.196.97.169: icmp_seq=2. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=3. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=4. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=5. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=6. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=7. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=8. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=9. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=10. time=60. ms
64 bytes from 216.196.97.169: icmp_seq=11. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=12. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=13. time=60. ms

----news.mozilla.giganews.com PING Statistics----
14 packets transmitted, 14 packets received, 0% packet loss
round-trip (ms) min/avg/max = 50/52/60


"good" computer:

d:\ping news.mozilla.org
PING news.mozilla.giganews.com: 56 data bytes
64 bytes from 216.196.97.169: icmp_seq=0. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=1. time=60. ms
64 bytes from 216.196.97.169: icmp_seq=2. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=3. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=4. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=5. time=60. ms
64 bytes from 216.196.97.169: icmp_seq=6. time=60. ms
64 bytes from 216.196.97.169: icmp_seq=7. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=8. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=9. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=10. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=11. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=12. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=13. time=50. ms
64 bytes from 216.196.97.169: icmp_seq=14. time=50. ms

----news.mozilla.giganews.com PING Statistics----
15 packets transmitted, 15 packets received, 0% packet loss
round-trip (ms) min/avg/max = 50/52/60

[Trevor Hemsley]

On Mon, 25 Apr 2011 18:09:49 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
I only posted that to say that sometimes I see it and sometimes I
don't, with no changes in settings or options.

Maybe I'm misunderstanding but I thought you were having problems from one of
two machines where ALL posts you made from the problem machine to the newsgroups
on news.mozilla.org were going AWOL. The only reason I could think of for the
posts only appearing for you was that you were somehow pointing to a different
server than all of us and from your working machine. Your ping seems to have
disproved that.

So what I need you to do is to turn up the log level on the problem machine and
to make a post to the problem group and only do that and nothing else so that
the log doesn't get cluttered up with extraneous information that will hide the
problem. Post the relevant section of the log file from that attempt here.

If that proves inconclusive then turning on PNDEBUG in pronews.env will log all
traffic between you and all your servers but if you really want to discover
what's going on then that would be the best route to take. Don't post the
debug.log file here, check it for sensitive information then zip it and mail it
directly to me please.

[Barbara]

On Tue, 26 Apr 2011 00:12:04 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
On Mon, 25 Apr 2011 18:09:49 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
I only posted that to say that sometimes I see it and sometimes I
don't, with no changes in settings or options.

Maybe I'm misunderstanding but I thought you were having problems from one of
two machines where ALL posts you made from the problem machine to the newsgroups
on news.mozilla.org were going AWOL. The only reason I could think of for the
posts only appearing for you was that you were somehow pointing to a different
server than all of us and from your working machine. Your ping seems to have
disproved that.

None of my posts/replies from the "bad" machine show up on
news.mozilla.org. I can't see them.

My original July 3, 2010 post to comp.os.os2.mail-news about this
problem that *YOU* could not see, I could see. Perhaps we should
forget about that one for now. It gets too confusing to talk about
two different servers and two different group at the same time.

Post by Trevor Hemsley
So what I need you to do is to turn up the log level on the problem machine and
to make a post to the problem group and only do that and nothing else so that
the log doesn't get cluttered up with extraneous information that will hide the
problem. Post the relevant section of the log file from that attempt here.

I start up all Pronews servers OFFline. So following your
instructions, I:

1. In the Pronews program folder, I set -3 (full logging) in the
parameters field.
2. Started Pronews
3. Went online with the news.mozilla.org server.
4. I posted a new article called "Test-"
5. I shut down Pronews.

Log output is pretty large, but here's what you asked for:

==
25 Apr 18:45:08.19 TID 2 [INFO] ProNews/2 V1.60.cp125 started
25 Apr 18:45:08.19 TID 2 [DEBUG1] Maximum file handles increased from
120 to 375
25 Apr 18:45:08.19 TID 2 [INFO] PNMAXLOGSIZE is set to use 10 log
files of 250KB
25 Apr 18:45:08.19 TID 2 [INFO] Pronews can use virtual addresses >
512MB on this o/s!
25 Apr 18:45:08.20 TID 2 [INFO] Pronews has enabled filter
tokenisation.
25 Apr 18:45:08.20 TID 2 [INFO] Pronews has disabled bulk database
updates.
25 Apr 18:45:08.20 TID 2 [INFO] Pronews will single-thread UConv
operations.
25 Apr 18:45:08.23 TID 2 [DEBUG1] [POSTQ] Loading 0 posts from queue
25 Apr 18:45:13.67 TID 7 [DEBUG1] [PCSMGR] CreateConnection found
free connection at position 0
25 Apr 18:45:13.67 TID 8 [DEBUG1] [NNTP] Connect thread 8 created
25 Apr 18:45:13.67 TID 8 [DEBUG1] [NNTP] Issuing lookup of
news.mozilla.org
25 Apr 18:45:13.89 TID 8 [DEBUG1] [NNTP] Connecting to IP
216.196.97.169
25 Apr 18:45:13.94 TID 8 [INFO] [NNTP] Successfully connected to
[news.mozilla.org].
25 Apr 18:45:13.99 TID 8 [INFO] [NNTP] NNTP Server login message was
[200 news.mozilla.org]
25 Apr 18:45:14.00 TID 8 [DEBUG1] [NNTP] Connection thread 8 finished
successfully, connection 166F85DC
25 Apr 18:45:14.01 TID 9 [DEBUG1] [DBLOCK] loading 0 local filters
for group mozilla.dev.ports.os2#1
25 Apr 18:45:14.08 TID 9 [DEBUG1] [ARTWND] Thread 8 created
successfully for group mozilla.dev.ports.os2#1
25 Apr 18:45:14.08 TID 9 [DEBUG1] [ARTWND] releasing semaphore for
group mozilla.dev.ports.os2#1
25 Apr 18:45:14.08 TID 8 [DEBUG1] Group mozilla.dev.ports.os2#1:
SaveHeaderData BuildHeaderTree ReFilterGroup
25 Apr 18:45:14.08 TID 8 [INFO] [ARTWND] Refiltering
[mozilla.dev.ports.os2#1].
25 Apr 18:45:14.08 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="\"mikeyhsd\" <***@sport.rr.com>""
25 Apr 18:45:14.08 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="\"mikeyhsd\" <***@sprintpcs.com>""
25 Apr 18:45:14.08 TID 8 [DEBUG1] [FILTER] tokenised filter
"subject="*M?I?5*""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"subject="*MI5*""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="\" The OS/2 Guy \" <***@gmail.com>""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="\"\(c\) The OS/2 Guy \(c\)\" <***@gmail.com>""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="***@posting.org""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="\"Chuck Wilson \(Los Angeles Area\)\" <***@myw""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="Lone Haranguer <***@hughes.net>""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="Chuck Wilson <***@myway.com>""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="blog*@watchesblog.cn""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"subject="*? Watches?*""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="*watches*""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="Chets_Turdley <***@live.com>""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"subject="*wholesale*""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="\"Robert Bates\" <***@btinternet.com>""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"subject="The TruthNBP Unregistered." or subject="Re: The TruthNBP
Unregistered.")"
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="\"Robert Bates\" <***@btinternet.com>" and
(subject="The TruthNBP Unregistered." or subject="Re: The TruthNBP
Unregistered.")"
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"subject="Gary Spatz Best Acting Teacher, Gary Spatz Playground,
GarySpatz.com, 16" or subject="Re: Gary Spatz Best Acting Teacher,
Gary Spatz Playground, GarySpatz.com, 16""
25 Apr 18:45:14.09 TID 8 [DEBUG1] [FILTER] tokenised filter
"composer="Gary Spatz Best Acting Teacher - Gary Spatz The P""
25 Apr 18:45:14.09 TID 8 [DEBUG1] Marking articles 0 read, 0 unread,
0 Decoded, 0 Deleted
25 Apr 18:45:14.09 TID 8 [INFO] [ARTWND] Refiltering
[mozilla.dev.ports.os2#1] done.
25 Apr 18:45:14.09 TID 8 [DEBUG1] [ARTWND] SaveHeaderData: group
mozilla.dev.ports.os2#1 NumHeaders = 449
25 Apr 18:45:14.10 TID 8 [DEBUG1] [ARTWND] SaveHeaderData: complete
25 Apr 18:45:14.10 TID 8 [DEBUG1] Closing article thread TID 8
25 Apr 18:45:21.76 TID 2 [DEBUG1] [ARTWND] Thread 8 created
successfully for group mozilla.dev.ports.os2#1
25 Apr 18:45:21.76 TID 2 [DEBUG1] [ARTWND] releasing semaphore for
group mozilla.dev.ports.os2#1
25 Apr 18:45:21.77 TID 8 [DEBUG1] Group mozilla.dev.ports.os2#1:
LoadHeaderData BuildHeaderTree ReFilterGroup
25 Apr 18:45:21.77 TID 8 [DEBUG1] [ARTWND] mozilla.dev.ports.os2#1
does not need filtering
25 Apr 18:45:21.80 TID 8 [DEBUG1] Closing article thread TID 8
25 Apr 18:47:15.32 TID 2 [DEBUG1] [POSTWND] 1 posts in queue of 2048
allowed)
25 Apr 18:47:15.35 TID 8 [DEBUG1] [MESSAGE ID]
DeXnHmMUzXdD-pn2-***@8113
25 Apr 18:47:15.36 TID 8 [DEBUG1] [PCSMGR] CreateConnection found
free connection at position 1
25 Apr 18:47:15.38 TID 10 [DEBUG1] [NNTP] Connect thread 10 created
25 Apr 18:47:15.38 TID 10 [DEBUG1] [NNTP] Issuing lookup of
news.mozilla.org
25 Apr 18:47:15.45 TID 10 [DEBUG1] [NNTP] Connecting to IP
216.196.97.169
25 Apr 18:47:15.51 TID 10 [INFO] [NNTP] Successfully connected to
[news.mozilla.org].
25 Apr 18:47:15.57 TID 10 [INFO] [NNTP] NNTP Server login message was
[200 news.mozilla.org]
25 Apr 18:47:15.57 TID 10 [DEBUG1] [NNTP] Connection thread 10
finished successfully, connection 166F8A44
25 Apr 18:47:15.79 TID 8 [WARNING] [ARTWND] Group Sent Messages#255
contains more articles (778) than NumAutoLimitHeaders (450) allows
25 Apr 18:47:15.84 TID 8 [DEBUG1] [DBLOCK] loading 0 local filters
for group Sent Messages#255
25 Apr 18:47:15.84 TID 8 [DEBUG1] [ARTWND] SaveHeaderData: group Sent
Messages#255 NumHeaders = 779
25 Apr 18:47:15.85 TID 8 [DEBUG1] [ARTWND] SaveHeaderData: complete
25 Apr 18:47:22.27 TID 2 [DEBUG1] [ARTWND] Thread 10 created
successfully for group mozilla.dev.ports.os2#1
25 Apr 18:47:22.27 TID 2 [DEBUG1] [ARTWND] releasing semaphore for
group mozilla.dev.ports.os2#1
25 Apr 18:47:22.28 TID 10 [DEBUG1] Group mozilla.dev.ports.os2#1:
SaveHeaderData DestroyWindow CompactBodies AutoPurge
25 Apr 18:47:22.28 TID 10 [INFO] [ARTWND] Purging
[mozilla.dev.ports.os2#1].
25 Apr 18:47:22.28 TID 10 [DEBUG1] [ARTWND] Purged 0 headers from
mozilla.dev.ports.os2#1
25 Apr 18:47:22.28 TID 10 [DEBUG1] [ARTWND] AutoPurgeHeaders deleted 0
articles
25 Apr 18:47:22.28 TID 10 [INFO] [ARTWND] Compacting bodies for
[mozilla.dev.ports.os2#1].
25 Apr 18:47:22.29 TID 10 [INFO] [ARTWND] Selecting bodies in
mozilla.dev.ports.os2#1 for deletion
25 Apr 18:47:22.29 TID 10 [DEBUG1] [ARTWND] Selected 0 bodies for
deletion from mozilla.dev.ports.os2#1
25 Apr 18:47:22.29 TID 10 [DEBUG1] [ARTWND] Closing old bodies file
unchanged for mozilla.dev.ports.os2#1
25 Apr 18:47:22.29 TID 10 [DEBUG1] [ARTWND] Finished purging 0 dead
headers from mozilla.dev.ports.os2#1
25 Apr 18:47:22.29 TID 10 [INFO] [ARTWND] Compacting bodies done for
[mozilla.dev.ports.os2#1].
25 Apr 18:47:22.29 TID 10 [INFO] [ARTWND] Compacting XRefs for
[mozilla.dev.ports.os2#1].
25 Apr 18:47:22.30 TID 10 [DEBUG1] [ARTWND] CompactXRefs loaded 449
XRefs for 449 articles
25 Apr 18:47:22.30 TID 10 [DEBUG1] [DBLOCK] disk space avail
23606398976, wanted 18270, drive E:
25 Apr 18:47:22.31 TID 10 [DEBUG1] [ARTWND] SaveHeaderData: group
mozilla.dev.ports.os2#1 NumHeaders = 449
25 Apr 18:47:22.31 TID 10 [DEBUG1] [ARTWND] SaveHeaderData: complete
25 Apr 18:47:22.33 TID 10 [DEBUG1] Closing article thread TID 10
25 Apr 18:47:34.35 TID 9 [DEBUG1] [NNTP] Close socket 764. Recv'd 63
Bytes, 2 waits - 0.06KB/sec
25 Apr 18:47:34.42 TID 8 [DEBUG1] [NNTP] Close socket 765. Recv'd 60
Bytes, 3 waits - 0.00KB/sec
25 Apr 18:47:34.50 TID 7 [DEBUG1] [CTRLPAN] maximum memory used for
waiting thread parameters 0 bytes
25 Apr 18:47:34.52 TID 2 [INFO] ProNews/2 shut down.
====

Post by Trevor Hemsley
If that proves inconclusive then turning on PNDEBUG in pronews.env will log all
traffic between you and all your servers but if you really want to discover
what's going on then that would be the best route to take. Don't post the
debug.log file here, check it for sensitive information then zip it and mail it
directly to me please.

You'll have to tell me how inconclusive it is.

[Barbara]

On Tue, 26 Apr 2011 00:12:04 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
If that proves inconclusive then turning on PNDEBUG in pronews.env will log all
traffic between you and all your servers but if you really want to discover
what's going on then that would be the best route to take. Don't post the
debug.log file here, check it for sensitive information then zip it and mail it
directly to me please.

Trevor do I have to put a number in place of the "0" as in PNDEBUG=0?
I tried just removing the disable # character, and the debug.log file
is tiny (529k). That's with only news.mozilla.org online.

Wouldn't I have to go online with ALL my (4) servers before it would
"log all traffic between you and all your servers"....

[Trevor Hemsley]

On Tue, 26 Apr 2011 01:30:25 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
On Tue, 26 Apr 2011 00:12:04 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
If that proves inconclusive then turning on PNDEBUG in pronews.env will log all
traffic between you and all your servers but if you really want to discover
what's going on then that would be the best route to take. Don't post the
debug.log file here, check it for sensitive information then zip it and mail it
directly to me please.

Trevor do I have to put a number in place of the "0" as in PNDEBUG=0?
I tried just removing the disable # character, and the debug.log file
is tiny (529k). That's with only news.mozilla.org online.

The fact that the log file exists is proof that it is working :-) The check is
whether the env variable exists, it doesn't check what it's set to

Post by Barbara
Wouldn't I have to go online with ALL my (4) servers before it would
"log all traffic between you and all your servers"....

Yeah but that was meant to be a warning that it wasn't server specific so that
if you did do any activity on other servers then everything would be logged.
Save you sending me anything you didn't intend to.

[Barbara]

On Tue, 26 Apr 2011 02:21:28 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
On Tue, 26 Apr 2011 01:30:25 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
On Tue, 26 Apr 2011 00:12:04 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
If that proves inconclusive then turning on PNDEBUG in pronews.env will log all
traffic between you and all your servers but if you really want to discover
what's going on then that would be the best route to take. Don't post the
debug.log file here, check it for sensitive information then zip it and mail it
directly to me please.

Trevor do I have to put a number in place of the "0" as in PNDEBUG=0?
I tried just removing the disable # character, and the debug.log file
is tiny (529k). That's with only news.mozilla.org online.

The fact that the log file exists is proof that it is working :-) The check is
whether the env variable exists, it doesn't check what it's set to

Post by Barbara
Wouldn't I have to go online with ALL my (4) servers before it would
"log all traffic between you and all your servers"....

Yeah but that was meant to be a warning that it wasn't server specific so that
if you did do any activity on other servers then everything would be logged.
Save you sending me anything you didn't intend to.

Do you still want that little debug.log file zipped and emailed to
you?

Sorry I'm so ignorant trying to wade through this. :(

[Trevor Hemsley]

On Tue, 26 Apr 2011 03:15:25 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
Do you still want that little debug.log file zipped and emailed to
you?

If you're still having trouble then, yes, why not.

[Trevor Hemsley]

On Tue, 26 Apr 2011 10:56:37 UTC in comp.os.os2.mail-news, "Trevor Hemsley"

Post by Trevor Hemsley
On Tue, 26 Apr 2011 03:15:25 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
Do you still want that little debug.log file zipped and emailed to
you?

If you're still having trouble then, yes, why not.

Great, looks like my debug code only logs incoming data from the server, not
outgoing. I see the responses from the server in that lot but nothing going out.
I'll look a bit later on and amend it to log data in both directions and point
you to a debug build. What I do see is that the server takes your post and
appears to accept it.

[Trevor Hemsley]

On Tue, 26 Apr 2011 10:56:37 UTC in comp.os.os2.mail-news, "Trevor Hemsley"

Post by Trevor Hemsley
On Tue, 26 Apr 2011 03:15:25 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
Do you still want that little debug.log file zipped and emailed to
you?

If you're still having trouble then, yes, why not.

OK, it turns out that the problem is that the mozilla news server silently
discards articles that it thinks have invalid message-ids. At least, Barbara was
posting articles with message-ids that ended with @8113 and as soon as she
changed her hostname or PNHOSTNAME= in pronews.env to something that started
with an alphabetic character, then it started working. So, @a8113 works but
@8113 does not.

[Barbara]

On Wed, 27 Apr 2011 14:01:48 UTC, "Trevor Hemsley"

Post by Trevor Hemsley
On Tue, 26 Apr 2011 10:56:37 UTC in comp.os.os2.mail-news, "Trevor Hemsley"

Post by Trevor Hemsley
On Tue, 26 Apr 2011 03:15:25 UTC in comp.os.os2.mail-news, "Barbara"

Post by Barbara
Do you still want that little debug.log file zipped and emailed to
you?

If you're still having trouble then, yes, why not.

OK, it turns out that the problem is that the mozilla news server silently
discards articles that it thinks have invalid message-ids. At least, Barbara was
changed her hostname or PNHOSTNAME= in pronews.env to something that started
@8113 does not.

Thanks Trevor!

All I can say is how grateful I am to the people/programmers who keep
our community going. This problem was rather subtle, and Trevor spent
quite a bit of time and effort finding it. It had nothing to do with
the Pronews/2 program, but with my inability to pick a proper
"hostname" that news.mozilla.org liked. Never affected other servers.

Wish I could send fresh fancy cupcakes to all OS/2 - eCS supporters!!!