• 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.

S@H problems

J

Jojo7

Senior member
I'm having problems with this new BOINC seti client. Most of the time I try to run it, it errors and says it can't connect and other times it said it connected and something to the effect of "no new work, will try again in 1.5 hrs". Am I doing something wrong? Should I be using seti queue? I don't understand how everyone else can still show work units for the day if I can't connect.

Also, I can still use the normal s@h command line client right? I'm having problems with it connecting too.
 
The BOINC-site is being worked on, so therefore it's sometimes down. One of the problems has been they've not managed getting wu added fast enough, therefore "out of work". Some database-optimization and moving services to different machines has sped things up.

Still, there can be other reasons for no work, this mostly is listed in the lines before this message.
 
Originally posted by: Jojo7
Should I be using seti queue? I don't understand how everyone else can still show work units for the day if I can't connect.
Click to expand...
SETI Q only works with SETI "Classic", not the BOINC version.




Originally posted by: Jojo7
Also, I can still use the normal s@h command line client right? I'm having problems with it connecting too.
Click to expand...
Yes, if you want to still run the SETI "Classic" version they're still sending out WU's. For that project you might want to connect thru one of the team Q's if you're having problems.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top