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

SETI CLASSIC: Something strange

RaySun2Be

RaySun2Be

Lifer
I've got some crunchers running SETIHIDE, and some running SETIDRIVER.

Lately, the crunchers running SETIDRIVER seem to have problems uploading to Bezerkley, and I have to do manual transmits, sometimes several times.

However, the SETIHIDE crunchers don't seem to be having a problem at all. Everytime I check the cache, there are no WUs waiting to be uploaded.

Just thought it was strange, and why SETIDRIVER would be having issues and not SETIHIDE.

😕

Ah well, in 11 days it won't matter anymore anyway. :Q

 
I'm using Setidriver also, and have been having the same issues. Oh well, at least with manual transmits they eventually go through. Oh well, only 11 more days to go!
 
Using SETI Driver also but i'm on dial-up so i always have to manually transmit. But once i hit the transmit button everthing seems to upload OK.

Probably just jinxed myself though.
 
I've been having a lot of issues with setidriver the last couple of days. I have to exit and restart it after nearly every submitted WU, assuming that it even goes through. It's only been going on the last few days, so I think it is pretty obvious bezerkley has done something. I think they've put an extra delay in the submittal/retrival process and that is screwing with setidriver.
 
I should of stated i'm uploading only. I had enough cached that i don't need to download any more, at least on this comp.
If you're trying to upload & download then i think you will get the "Can't connect to server, will retry in one hour" message when the server isn't working, which is almost always the last week or so.
Check the SETI@home server status page the next time you want to transmit. If it isn't working adjust you cache size before transmitting so it only uploads.


They didn't add any delay. The communication between server & client isn't completing anymore. That's why everyones getting the duplicate errors.
 
Having no problems with sending from SETIDriver through my queue, but the queue itself is having fun with the dupe results problem :/
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top