Repositroy Speed Test - Failures [ Solved ]

[txm0523]

Have been trying the Repository Speed test and all repositories come up failing.
Are the repositories locked or frozen that you can't connect to them and update ?

Thanks

[Hootiegibbon]

They are probably mid-sync

Jase

[YouCanToo]

The majority are working for me.

[Linuzoid]

The majority are working for me.

Me too.

[mikkl]

What did you select as your desired sync delay?  When I set this choice from the default of 5 days to 2 days, I too had most repositories fail.  Setting at 3 days, all repositories worked.

mikkl

[txm0523]

I had mine intially set at 2 days and then I changed it to 1 day. Seemed to work fine until the last couple of days.
Just saw on the main PCLOS website that 2010.1 is now out. Hootiegibbon might be right. But, mikkl could be right too.
If they're right and I'm wrong, won't be the first time. Will test it out during the day both ways.

Thanks all

[parnote]

I am also wondering about this, since I have never gotten Repo Speed Test to do anything but report failures. I tried changing the sync delay from 5 days (all repos fail at this setting) to 3 days (all fail), 2 days (all fail), but at 10 days, only pclosusers.com is successful (all others fail). It doesn't matter what time of day I attempt to run Repo Speed Test.

Obviously, I'm connected to the 'net (I'm typing from the same computer that reports all the failures). Nothing I do will make Repo Speed Test work. Does it not like wifi connections? That's the only thing I haven't tried.

parnote

[Mark342]

I had the same problem, but I found the solution.
When running Repository speed test you need to start it with the -t <amount> option
This specifies the timeout in seconds before the repository is condemned to failure.
Some connections have higher latencies than the default timeout setting, so all repository's fail.
My setting is 7, and it works perfectly.

[GoustiFruit]

I posted the exact same question a few hours before so I guess there was some problem anyway:
http://www.pclinuxos.com/forum/index.php/topic,72091.0.html

[txm0523]

I used to have no problems using the Speed Test, it worked beautifully until last week when failures started to show up.
Might be because of updating last week. Also have noticed that after updating, certain settings you have made, change and then you have to go back in and change them back again to where you had them before. Hmmmm.

=> Mark342  where exactly do you set the timeout for Speed Test ?

=> parnote   judging form your profile picture I'd say you are an RT, correct ?

[parnote]

txm0523,

Yes, I'm an RT. What gave it away?

parnote

[parnote]

I had the same problem, but I found the solution.
When running Repository speed test you need to start it with the -t <amount> option
This specifies the timeout in seconds before the repository is condemned to failure.
Some connections have higher latencies than the default timeout setting, so all repository's fail.
My setting is 7, and it works perfectly.

Thank you, Mark342!

For the first time, Repo Speed Test has finally worked. I added the -t7 option, and almost every repo succeeded in the tests. Those that didn't succeed, I suspect that they were mid-sync.

parnote

[txm0523]

=> parnote  the lab coat and stethescope for one and the hidden look of " Oh man, not another new start "  you can't hide it  LOL
                    I am an RT also

also, where do you add the -t option ?

[parnote]

=> parnote  the lab coat and stethescope for one and the hidden look of " Oh man, not another new start "  you can't hide it  LOL
                    I am an RT also

also, where do you add the -t option ?

txm0523,

I'm in Independence, Missouri, at Centerpoint Medical Center. You?

Also, I added the -t option by editing the PC Menu ... right click on it, select "Menu Editor," find Repo Speed Test in the list of apps on the left, highlight it, and add the -t7 option to the command line that starts Repo Speed Test.

FWIW, I haven't tried any other delay setting ... just the 7 second one.

parnote

[txm0523]

=> parnote   thanks for the info about where to do the -t option.
                  I'm at Kishwaukee Hospital  DeKalb, Illinois. Nice to meet a fellow RT enjoying Linux.

txm0523