Error handling and salvaging partial multiparts
Posted: Mon Dec 10, 2007 1:54 am
I have multipart binary messages which one of the parts is reporting "Error 430 No Such Article." That's OK though... that's not what my question is about.
I need to save that corrupt joined binary anyway so it can be used for par data. Unfortunately, it's sitting in my queue indefinitely with "Pending 97% completed 1 pending 39 bodies 0 errors".
Some settings:
Recoverable errors: too*many|limit|timeout
-That's default - and doesn't seem like it should include this 430 error... but why doesn't then take complete or error out after that error then?
Retry failed tasks every 1 minute.
Server Retries 1 (also, only one server is currently enabled)
All options in the Articles subbox "Saving Attachments" are checked (including "Ignore 'No such article' errors").
Am I doing something wrong? Not only am I unable to get these partial files for use in PAR, but they stay in my queue forever unless I manually cancel them.
Thanks.
I need to save that corrupt joined binary anyway so it can be used for par data. Unfortunately, it's sitting in my queue indefinitely with "Pending 97% completed 1 pending 39 bodies 0 errors".
Some settings:
Recoverable errors: too*many|limit|timeout
-That's default - and doesn't seem like it should include this 430 error... but why doesn't then take complete or error out after that error then?
Retry failed tasks every 1 minute.
Server Retries 1 (also, only one server is currently enabled)
All options in the Articles subbox "Saving Attachments" are checked (including "Ignore 'No such article' errors").
Am I doing something wrong? Not only am I unable to get these partial files for use in PAR, but they stay in my queue forever unless I manually cancel them.
Thanks.