WU's not uploading.

[blcjr]

My wu's are not uploading. I've got 200 wu's in the "results" queue of SetiQ. I don't see any indication of a problem with the Berkeley server. Is anyone else having problems? Any tips on how to troubleshoot the problem? Specifically, what is the ip address of the server that results get uploaded to by setiqueue?

 

[Freewolf]

Hi Baz, I just checked our q and we haven't any results waiting. Have you tried rebooting the machine your q is on or restarting your q ?

 

[blcjr]

I'm running Q as a service. I just stop and restarted it, and the wu's are starting to upload again.

Weird. The SetiQ client log is full of errors which don't mean much to me...lines like:


3:57pm: Passthrough: Seti@home status: ErrorCode 0x00000064 100
3:57pm: Passing through request send_result_get_user_stats
3:57pm: Returning passing through request response
3:57pm: Queued passthrough request

over and over.

I'm still getting these errors, but at least wu's are flowing out again. I've dumped 40 wu's in the time it took to compose this message. I'm feeling much better now. 😀

 

[networkman]

Hmm.. 3 of my rigs were reporting "Unknown error 100" when they'd completed a WU and were ready to flush to the queue I run at home; I tried pointing them directly to Berkeley, but got the same message. I finally just deleted *.sah files, dl'd new WUs through my queue and they're working fine.

 

[Freewolf]

There seems to be some bad work units out now. There is another thread on the first page about the problem with the same error message, you have some clients with bad work units out there.

 

[Freewolf]

Check out the post by Doomer

 

[Orange Kid]

Problems continue..............

Wasting too much time..............

Going to something else.....................

Bad WU's bad bad bad WU's
:brokenheart:😕:disgust::frown::|🙁

 

[Spacehead]

Just saw this on the S@H page:

? October 27, 2003 ?
If you are unable to connect due to "100" errors (or perhaps "41") you may need to exit SETI@home, remove the files "result.sah" and "user_info.sah" from your system, and then restart SETI@home. This is probably fallout from the user database crash a few days ago. Sorry for the inconvenience.

 

[blcjr]

It happened again, and my queue backed up. But stopping and restarting the service got it going again.

Weird.

 

[networkman]

Here too.. more machines with bad WUs. 🙁 Anybody else using SetiSpy? Possibly related to these bad WUs is that my SetiSpy doesn't seem to "see" that the client is running and just turns to the yellow "idle" mode in the System tray. 😕 I've deleted it, re-downloaded and re-installed it, but still keep getting the same thing.

I'm thinking perhaps I should flush the whole queue and refill? I'm gonna try that and see what happens. In the mean time, the few machines that're having problem with SetiSpy will just have to run the CLI in a DOS window.

 

[Robor]

I had 109 WU's waiting in my SetiQ at work. Stopped and restarted the Q and they appear to be slowly uploading now. Still have 12 of my clients that have no WU pending though. I dunno what happened at Berkeley but this sucks. The SETI client has stable for so long and now this. Some of these clients have been running for several years without any maintenance.

 

[Assimilator1]

Repost!😉

🙁

 

[Smoke]

Yeah, there is more than one of these threads but the problems remain.

I've just spent some time with my Q and this is what I found.

There seems to be an unusual number of PASSTHROUGH REQUESTS and these don't seem to make it to Berkeley and the Q times out. In an attempt to avoid these errors I have DISABLED both the OVERRIDE FOR PASS-THROUGH OPERATIONS and DOWNLOAD NEW WUs.

Upon a restart it appeared WUs were being sent in but then the following happened:

Queued passthrough request
Passing through request send_result_get_user_stats
Pass: Seti@home status: Error 0x00000064 100
Returning passing through request response

Then 3 or 4 completed WUs are sent in and the above entires in the LOG appear again?

I thought by disabling PASS-THROUGHs and not DOWNLOADING WUs, this would not happen? Any thoughts?

 

[blcjr]

I don't understand what is happening. What I do know is that when I find completed wu's backing up, starting and restopping the service gets them flowing again. Just did it for a third time, "dumping" 76 wu's in a matter of minutes. Right this minute, the results q is empty.

Call me 😕 .