• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

error -34 (SETI), any ideas ????

C

ColinP

Golden Member
Getting lots of error -34 back from SETI on my SETIQ server.
This happens when it's trying to send results.
If I get rid of the particular result it's trying to send, it will be OK for a few results, then repeat the error.

I suspect it's got something to do with the transition to V.3.
I'm not sure all of the Sparcs are using V.3 yet, if 1 was still on V2.x, and SETI wouldn't accept the result, you might see something like this...

Mind you, that could be a load of bollocks, it's just a thought...

Anybody else seen this / knows what error -34 is ????

Update...

SETIQ tries 6 times to send the result then drops it to /dropped and carries on. It also gives a message along the lines of result stuck...

cheers,

Col
 
getting it here too... i think its definitely a 2.x to 3.x issue, as i know some of my clients are still using v2.

Looks like ive lost about 1 week of results from whilst i was away..

D
 
I uploaded some results with no problem about 7 hours ago. Now I have four more and was going to send em, but SetiQ cant connect to server. I only wish I had told it to save more than 3 days worth, cause it looks like another seti server outage boys and girls.


setiQ says: "Failed to connect: timedout"

bummers.🙁

Just checked the seti server status page. It does not indicate any problems. 🙁
 
Weird! I just restarted setiQ and it is acting normally again and sending its results as i type this. Maybe the servers are just overloaded.
 
I believe a lot of the v2.x clients were killed on Saturday, so that might be why you guys are having problems.
 
All of my clients are the 3.0 CLI. I have only had intermittant connection troubles. Setiq reports that the server is timeing out when trying to connect. But that error -34 could be related to the 2.0 client being phased out. I havn't checked it out though.
 
Just checked the SETI website and on their front page, they were reporting a 1 hour scheduled outage for today at 21:00 UTC (which would have been around 4pm EST)... Maybe the 2.x windoze cutoff is now in effect!
 
error 34 is definatley a message refering to the v2.x clients being blocked, there's a thread at Arstechs forum abtout it.The Linux v2.x clients were killed last night ,upgrade quickly!.

 
You must log in or register to reply here.

TRENDING THREADS

Back
Top