problem with download list

[bloggs_&_co]

First let me say the program looks great, but there is, (what I would
consider a major bug in a multi server program) I would be surprised
if no one else has brought this up, but it would stop me from using
this program despite its many good features,the problem is in the
file queue being deleted if the file does not exist on the first
primary sever, it does not allow the file to remain for download by
other servers in the list. this results in many small fragments of
incomplete files.

[Rdl]

Define other servers as backup to your primary server

[bloggs_&_co]

In reply to other servers, well I had three servers loaded
into this program, I had downloaded the group file from the
first server entered, I did not download any groups but
got the file from one of the search engines,the first
server was the fastest on downloading and as I started to
download there was a 430 msg from my main server the file
parts were being deleted from the queue, and the slower
servers were downloading parts from the remaining files
before they were also deleted until al that remained was
the paused par files....I hope this helps oh! and this
was also observered in version 023.2

[Rdl]

As I said define one primary and others as backup to that primary or if you need all as primaries cause of speed then define others as the backups.

Code: [Select]


1) [x] Server 1
        |
         --[x] Server2
        |
         --[x] Server3

2) [x] Server 1
        |
         --[x] Server2
        |
         --[x] Server3
   [x] Server 2
        |
         --[x] Server1
        |
         --[x] Server3
   [x] Server 3
        |
         --[x] Server1
        |
         --[x] Server2


[bloggs_&_co]

Well in that case they were all primary, I sould say also add server
as backup server was dimmed out so could only add as primary.
the problem should be easy to observe, by loading an nzb which is out
of date and watching the file list being deleted, because unless I,ve missed
something in the settings the file list should remain in the queue until
manul deletion takes place... I hope this makes things clearer in the
way the program was setup

[bloggs_&_co]

Right I now see the reason for your question, in order to add as backup server you have to first click on the primary server and add it to that.

so if all servers are added as primary servers then the queue list will
vanish before your eyes if the first server does not have the article.

[Rdl]

Right I now see the reason for your question, in order to add as backup server you have to first click on the primary server and add it to that.

so if all servers are added as primary servers then the queue list will
vanish before your eyes if the first server does not have the article.

Exactly. Primary server must be selected in order to attack backup to it.

Well it will not vanish, but if you have 3 primaries and one of them doesn't have articles then approx. 1/3 of articles will be missing and all files will be corrupted.

[bloggs_&_co]

Which of course is just the point I was making, the way the program works will have exactly the same results even with backup servers if none
of them have the aricle leading too corrupted files, this  happen after I
tried it later this evening. it could also take place if one or two of your servers were down or even problems on the net.
I have been looking for a good multi server prog for sometime bnr2 has
the right sort of idea in that only once the segment has been downloaded
does that segment get deleted, even if all servers have tried to get it.
are there any plans to amend the way the queue currently works?.
other programs I have used such as newsleecher suffered from the same
problem although I have not used the latest version, dont like the way its
laid out....tks..

[Rdl]

Lol I don't see anything wrong with the way the program works. Stall download cause some articles are missing is nonsense. That's why par2 are there. You're obviously not aware of the setup->connection->articles not found options. You can set retry count to some high number with 5 minutes delay.

[bloggs_&_co]

Well I,m sorry to hear that, but the concept of a multi server program is to my way of thinking, in order to use server for bits which can be flaky, also if you now the server is off line you might untick the box in the server setup, it will be no good reticking it to try the server if the missing article part has vanished, and yes the queue will vanish before your eyes, I had the following setup 3 server 2 with download speeds of 15k and one with 4mbs, this did not have the group needed but was ticked, they were all prim servers I ended up with a few rars with lengths of 384kb as all the other segments were deleted as the 4mbs server raced down the queue.Now I think your program looks and feels great so don't get me wrong, but with the  queue being delete in the way it is, one can never be sure if the missing part is missing or just deleted from the queue you could have the situation that the file is some what new and still being uploaded, you can`t go back and finish without corrupting articles, I have been doing this from about 15 years now and have tried lots of programs, and to be blunt in my opinion the queue is a major problem if it can`t be relied upon to retain the article segments until ever thing has been tried, I am well aware that pars can repair files but if you have a fast link one wants to max it. This is intended as constructive criticism by the way, I would be interested in other peoples thoughts on this point.

[bloggs_&_co]

Ok, i have reset that option in setup/connections/article and will
give it a try and see what happens. could this be set so  the
article in effect never expires until a lower setting is reinstated?

[Rdl]

You could set 999 retries x 1440 minutes. That's 999 days. Enough?
So to be clear, files with missing articles will not be removed from download queue & decoded for next 999 days. I'll add option to reset retry & delay properties for selected files so you could force program to try downloading missing articles with current server properties.

[bloggs_&_co]

Right, thanks for that, you may already have had this reported but one other thing I have noticed is even if you set the backup server
for only 1 connection it uses the setting from the primary server
this is a problem becuse some serves will only accept 1 connection
otherwise theres a temp ban on your ip..

[bloggs_&_co]

I have made some more observations and find near the end of the article the program is cycling through connect disconnects because it checks the primary then the backup but in the mean time it has dropped the connection and needs to make a new one as the servers are a bit flaky this all takes time, whilst doing this I reset "connected while idle" box now with this ticked the program refused to shut down, but has been ok all the time this box was unticked. With the "connected while idle ticked" the problem with downloads was worse..by the way if you need the log how do i post it too you..tks