wth is up with my client?

[gpcola]

Just got in from a night out to find 1 failed 110 credit WU and 4 others in a perpetual state of 'uploading' on my X2 rig. In addition boincview is showing no buffered work whilst boinc manager is still showing 10 days of buffered WUs.

What is this 'uploading' state indicating, anyone know?

[DeltZ]

is cpu oc'ed or stock?

[gpcola]

It's oc'd but I reckon the WU that failed might have been a bad one - out of the 80ish WUs this rig has completed only 3 have failed to date.

It looks like boincview has totally lost contact with the client - not seeing any work at all in there now and the host icon has a red question mark over it.

On the plus side one of the WUs in 'uploading' state has finally managed to update to 'ready to report' so hopefully the other 3 will do the same given time.

[DeltZ]

i had same problem with boinc view...so i decided i could be bothered to fix it...but try the method which doesn't retrieve data from the boinc files

Read kaptainblazzed's post in the Boincview topic saying how to manage global computers remotely while staying pretty secure...because if you can also see yourself in real time.. using that method to connect to boinc

http://www.xtremesystems.org/forums/showthread.php?t=85255 (about half way down)

and it sounds like you're cpu is very slightly unstable for R@H which then causes it to just stop and die

seems to be happening if you read the other topics...

so decrease the clocks about 10-50 mhz and you should be ok...

[gpcola]

Yeah it's KaptBlazzed's method I have been using to connect to the client and it has been working for a couple of day's using the client name 'X2'. I just changed that to 'localhost' and successfully connected to the client once again (odd that still works whilst the client name doesn't :confused: ) but it's still not showing any buffered work :stick:

[Rodzilla]

Yeah it's KaptBlazzed's method I have been using to connect to the client and it has been working for a couple of day's using the client name 'X2'. I just changed that to 'localhost' and successfully connected to the client once again (odd that still works whilst the client name doesn't :confused: ) but it's still not showing any buffered work :stick:
I bet we can figure this out if we know what's in your "messages" tab. If there is a problem you will have an error or warning in there.

[gpcola]

Thanks rod - As it happens I no longer have a problem with WUs stuck in an uploading state as they all eventually progressed to 'ready to report' and were accepted when I updated the client. I hadn't realised that, when there is no network connection, WUs stay in this state following completion until a connection is made available and even then it takes a while for this to happen...

The problem with boincview not showing buffered work remains but I have a feeling that when the client next requests work that situation will change too.