0.6.0Beta2: warning: none -> Unknown encoding

[sander]

My stdout says "missing from all servers, discarding",
but http://localhost:8085/sabnzbd/connections/ -> Latest Warnings says "Unknown encoding" and " Unknown encoding - Error importing

[sander]

Afterwards, SAB is reporting "» Download failed - Out of your server's retention? ". Better than the "Unknown encoding" error.

However, wouldn't it be more correct / informative if the message was:


» Download failed - Post not available on your newsserver(s). Out of your server's retention, or removed?

Reason: in this case the post was within the server's retention, but I guess a DMCA order made it disappear. ;-)

[premiso]

@sander: Did you even look through the thread completely? I took the liberty to quote a post that should help you. If you want more information, I suggest reading through this whole thread, as it should have everything you need.

Sent the information via email.

To completely fix the issue, I just generate a brand new .ini file and then rebuild it from the ground up. That seems to have worked, I am thinking it could be a category issue, but not 100% sure, but that has fixed my issues completely.

So in the end, when you upgrade just regenerate the sabnzbd.ini file and that should work fix the issue.

[sander]

@sander: Did you even look through the thread completely? I took the liberty to quote a post that should help you. If you want more information, I suggest reading through this whole thread, as it should have everything you need.

Sent the information via email.

To completely fix the issue, I just generate a brand new .ini file and then rebuild it from the ground up. That seems to have worked, I am thinking it could be a category issue, but not 100% sure, but that has fixed my issues completely.

So in the end, when you upgrade just regenerate the sabnzbd.ini file and that should work fix the issue.

Yes, I read the complete thread, and creating a fresh sabnzbd.ini resulted in the same errors: None -> Unknown encoding on the GUI while the stdout says "missing from all servers, discarding".

[sander]

Now running 0.5.6, with a fresh sabnzbd.ini, empty queue, with the same NZB, and it just says "... => missing from all servers, discarding" under Connections. Which is OK and probably correct.

So it's my guess 060b2 does some mis-interpretation of the status / error message. Or it starts working on the failed post, and then thinks it has an incorrect encoding?

@shypike, could that be it? I'll send you the .NZB

[Rezzar]

I had this issue and the resolution for me seemed to be to disabling the "Send Group" option under switches. before figuring that out I also created a new virgin configuration ini so that might have had something to do with it as well, but not until i unticked Send Group did it stop the constant errors.

Thx for this Info   z3r0z !

the same Setting was ticked in my switches option, I upgraded from Version 5.6 to  6 Beta 2.
I will test if it works now...

[shypike]

Upgrading an existing queue and INI file can be screwed up.
I'm still looking at the details and a remedy.
At least, creating a fresh INI file and starting with an empty queue will solve most problems.

[shypike]

So it's my guess 060b2 does some mis-interpretation of the status / error message. Or it starts working on the failed post, and then thinks it has an incorrect encoding?
@shypike, could that be it? I'll send you the .NZB

What is your complaint exactly?
Does 0.6.0 behave different from 0.5.6 or is it just the wording of the messages?
Both 0.5.6 and 0.6.0 show "WARNING: None -> Unknown encoding".
0.6.0 doesn't show a warning for every missing article, like 0.5.6 does.
Instead it summarizes the amount of missing articles.

I agree that the "encoding" warning should be removed.

[sander]

So it's my guess 060b2 does some mis-interpretation of the status / error message. Or it starts working on the failed post, and then thinks it has an incorrect encoding?
@shypike, could that be it? I'll send you the .NZB

What is your complaint exactly?
Does 0.6.0 behave different from 0.5.6 or is it just the wording of the messages?
Both 0.5.6 and 0.6.0 show "WARNING: None -> Unknown encoding".
0.6.0 doesn't show a warning for every missing article, like 0.5.6 does.
Instead it summarizes the amount of missing articles.

I agree that the "encoding" warning should be removed.

Do you mean the message means to say "WARNING: (a lot of) articles missing on newsserver(s)"? If so, I would understand it completely.

If not, I still wonder what "None -> Unknown encoding" means. It makes me think SAB is complaining about the encoding of the .NZB (no correct XML) or the communication with the newsserver (wrong response) or the posts retrieved (incorrect rar or par format) .

FWIW:  I've never seen "WARNING: None -> Unknown encoding", but maybe it's lost in all the "missing on server"-messages?

EDIT: in the above line, I meant to say "... in SAB 0.5.x".

[shypike]

The "None -> Unknown" warning is an anomaly that I have just removed.
It was given for any file that has no downloaded articles at all.

0.6.0 says in the History summary how many articles are missing.
Together with the "out of your server's retention" message, it should make things clear.
The wording might be slightly improved.
We are a bit careful to do that in this stage, because it will cause new work for the translators.

[shypike]

I think some different types of complaints are mixed in this thread
and I'm still looking at the materials emailed to me.
It may take a while, but I'll dig into this deeper.
The stuff I fixed so far is only the confusing message "None - Unknown encoding".

[shypike]

I found the culprit for premiso's problem.
The "Send Group" feature in Config->Switches has a bug that will prevent downloads.
premiso happened to have it on.
Keep it off, it's needed for only very few Usenet servers (if any).
Beta3 will contain a fix.