Is Mika's Down

[dvch]

Title says it all.

 

[dkappos]

I get this message:

[Jul 01 14:45:43 UTC] NetUpdate:: Perproxy does not have packets available.
[Jul 01 14:46:37 UTC] NetUpdate:: Perproxy does not have packets available.
[Jul 01 14:46:52 UTC] NetUpdate:: Perproxy does not have packets available.

I use the last client and my computer tries to get keys every 30 seconds. If the same happens to a lot of the users of Mika's pproxy then it is possible that you will have problems connecing to it. The proxy is not down... it just doesn't have keys to send you. I hope that none of us is checking randoms because of this.

 

[bonehead]

I have ten machines checking randoms now Hope Mika's up soon .

 

[BurntKooshie]

same here...

[Jul 03 03:13:33 UTC] Connection detected on 'My Connection'...
[Jul 03 03:13:36 UTC] Connected to teamanandtech.dhs.org:2064...
[Jul 03 03:13:36 UTC] NetUpdate:erproxy does not have packets available.
[Jul 03 03:13:40 UTC] Connected to distributed.net 128.104.18.148:2064...
[Jul 03 03:13:40 UTC] The keyserver says: "You cannot control me with a
smile. (bob)"

Guess I need to change it back to never fallback Oops.

 

[MWalkden]

is there a way to set the client to get packets from dnet but flush to Mika?

 

[Engineer]

Yes, just set keyserver to d.net and use the fetch command (not update - fetch and flush), just fetch....

Then set back to Mika's server..

You can also us clueless.2y.net since clueless' pproxy flushes through Mika....

 

[dvch]

You can also manually flush and it will go to Mika's.

 

[bonehead]

Bump one

 

[Camm]

I tried to flush to Mika's and could not. Guess I'll have to keep saving up

At least the client fetches first and you can shut it off to stop the flush to Dnet.............. Do not forget to start it back right away though.

Camm

 

[ViRGE]

I'll shoot an email off to Mika to see what can be done. Hopefully it can be fixed quickly even if it is a weekend.

 

[BoberFett]

My pproxy is flushing correctly to Mika's, but may not be getting blocks. The same thing happened a week or so ago. If anybody would like to, they can flush and fetch from my pproxy at 199.199.174.1 port 2064. I've got around 30K-35K blocks buffered so I can support several people without a problem.

 

[Clueless]

My pproxy has 28K blocks right now and I've started another pproxy to fetch another 100K directly from dnet so you can use mine if you want.

I have a question though. The second pproxy that I use to feed the public one is only sending packets every 20 seconds. I need for this to happen as fast as possible to minimize the disruption to everybody else. The closet thing I can see is the connectperiod setting but changing it did not seem to have any effects. Got any suggestions?

 

[Beefcake]

Clueless, I asked on Dnet for you.. the best that they could come up with was to either scrap the old buff in and replace it with the new one you just downloaded.

Or to set the maxkeysdone= option to a massive figure while you downloaded blocks from dnet with you main proxy.. and then change back to Mikas and reset the maxkeysdone= to a low number again. That way it shouldnt dump any blocks direct to Dnet just download from them! Worth a try!!

 

[Beefcake]

Oh yeh.. they also said.. make sure proxy one has finished downloading its blocks.. otherwise your second proxy wont get them as quick and set your connect period as low as you can!

 

[Viztech]

The Team Gamma proxy maybe in trouble as well.
BobberFett and I have been sending them to Mika via my Gamma proxy, but none have shown up on the stats since Friday.

viz

 

[imported_Thunder]

Grrrrrr,

Dang Win9x 2.8007 version client. :|

Somehow they broke the auto "fallback" feature in that client release (and of course all but two of my machines were on it).

I ran around for a while today and got all but the 4 really, really remote machines updated to the latest client release (which "falls back" just fine).

-Brian

 

[BoberFett]

Thunder

Moose just made mention of a new client release today. Sounds like this one might be a winner.

 

[Slacker]

I flushed a thousand blocks to mika's today, none showed up at dnet tonight

 

[ViRGE]

Usually, if Mika's isn't getting any blocks, then it can't send them either.

 

[dvch]

Do we know what the storage capacity of Mika's is? Since it may not be possible for it to flush could we "overload" it and lose wu's?

 

[ViRGE]

No, it has a nearly infinate storge capasity. It's only true limitation is disk space, which we won't be able to fill up any time soon.

 

[mindless]

Im missing almost 700 blocks, which may not be many to you but when you normally only flush about 1000 per day it is

Any chance of these showing up in todays stats run on dnet?

 

[ViRGE]

Well, I went through my email, and figured out where Mika is: gone for the long weekend since Saturday was Canada Day. So, we're SOL until at least tomorrow(or should I say today?).

 

[mindless]

So are mine and a few others gone forever? Or until the next stats run?

 

[Beefcake]

Yeh your blocks are safe, just need Mika to restart the proxy and they will all get dumped ok