Posting problems in 6.73 B3:

[saintsinner]

Hi all, with the latest beta (and at least B2) there seems to be a problem posting, below is my verbose logs from my most recent test post (roughly half of my posted data shows up)
Before the log, here's what I received from the provider when I asked them about it (note there are no places that I've found in newsbin pro to change yEnc lines per segment.


I asked my provider about it and received:

Is there a reason why the amount of "340 Start posting" occurs 272 times, while "240 message received" only occurs 136 times in your previous reply?

This would explan why your post are only for 50% on our servers whenever you create a post. This could be due to your posting settings, espescially the yEnc lines per segment. If this is set too high, your post "340 Start posting" will indeed fail. A stanard setting for yEnc lines per segment is 3000.

----------------------------------------------
[01:17:05] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:05] HIGH usenetbucket |340 start posting.
[01:17:06] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:06] HIGH usenetbucket |340 start posting.
[01:17:06] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:06] HIGH usenetbucket |340 start posting.
[01:17:06] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:06] HIGH usenetbucket |340 start posting.
[01:17:06] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:06] HIGH usenetbucket |340 start posting.
[01:17:06] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:06] HIGH usenetbucket |340 start posting.
[01:17:07] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:07] HIGH usenetbucket |340 start posting.
[01:17:07] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:07] HIGH usenetbucket |340 start posting.
[01:17:07] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:07] HIGH usenetbucket |340 start posting.
[01:17:07] HIGH usenetbucket None |240 message received.
[01:17:07] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:07] HIGH usenetbucket |340 start posting.
[01:17:07] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:07] HIGH usenetbucket |340 start posting.
[01:17:07] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:07] HIGH usenetbucket |340 start posting.
[01:17:08] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:08] HIGH usenetbucket |340 start posting.
[01:17:14] HIGH usenetbucket None |240 message received.
[01:17:14] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:14] HIGH usenetbucket |340 start posting.
[01:17:15] HIGH usenetbucket None |240 message received.
[01:17:15] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:15] HIGH usenetbucket |340 start posting.
[01:17:15] HIGH usenetbucket None |240 message received.
[01:17:16] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:16] HIGH usenetbucket |340 start posting.
[01:17:16] HIGH usenetbucket None |240 message received.
[01:17:16] HIGH usenetbucket None |240 message received.
[01:17:16] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:16] HIGH usenetbucket |340 start posting.
[01:17:16] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:16] HIGH usenetbucket |340 start posting.
[01:17:16] HIGH usenetbucket None |240 message received.
[01:17:16] ALWAYS usenetbucket POST | 340 Start posting.
[01:17:16] HIGH usenetbucket |340 start posting.
[01:17:18] HIGH usenetbucket None |240 message received.
[01:17:18] HIGH usenetbucket None |240 message received.
[01:17:18] ALWAYS usenetbucket POST | 340 Start posting.
(SNIP can give full report, but really, you shouldn't need it as this is very much reproducible with multiple servers as long as you post ~400 megs+ for tests)
[01:19:01] HIGH usenetbucket None |240 message received.
[01:19:01] HIGH usenetbucket None |240 message received.
[01:19:02] HIGH usenetbucket None |240 message received.
-------------------------------------------------

[saintsinner]

just for a data point, I also tried posting the same item to the same group using the oldest version of newsbin I could (6.62) with ssl disabled completely successfully. I'll run a test on if the new beta with ssl disabled works or not next.

Edit: actually, staying with 6.62 as I reported this problem previously in 6.70B3 as well and I'm not sure if it was ever fixed, or just carried over to the latest version (and again I noticed in the 3rd beta?) Either way, in 6.62 with ssl enabled or disabled posting the exact same files to the exact same group works flawlessly, it's just in 6.73B3 that posting is a problem (and 6.70B3, perhaps also in everything since 6.62?)

viewtopic.php?f=44&t=39769

[saintsinner]

Had a bit of downtime so here's another data point: I just upgraded from 6.62 to 6.72 (4776) and you guessed it, uploading doesn't work. Only a fraction of my post shows up so 6.62 was in fact the final version where posting worked.....

[Quade]

I'll see if I can re-produce it. Thanks.

[saintsinner]

Cool, fingers crossed you can track it down. there are no issues at all with posting text, but binary posts (at least in multiple 50M parts) are clipping horrendously (if you want to exactly reproduce it I've sent you the nzb for the files that failed)

[Quade]

Just looking at the code. It sort of acts like some of the chunks of the post are missing from disk. They get stored in a folder in the data folder.

I'm still investigating though.

[Quade]

Ok think I have a fix. It'll basically never give up on an upload now even when exposed to connection or other errors.

Because posting is essentially single-server, it would fail if the server returned errors. Now it won't.

[PCZ]

I had the same issues with 6.73 and have gone back to 6.62 as that seems to be the last version were posting works correctly for me.

The latest beta has made the problem worse, NB just waits forever for a server response.
I cant even post text messages let alone binary attachments.

[Quade]

I'll check it again before the release.