• 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 Driver won't send WU

sswingle

Diamond Member
I checked my main system this morning, to see that it was hording 5 WU's instead of sending them. I noticed that my proxy/socks setting had somehow changed itself from proxy to socks, therefore not allowing it to connect. I changed it back and transmitted. It sent all but 1 WU. When I click transmit, it doesn't even try to send it. I figured it would go when another WU finished, but one just finished and sent, leaving the loner behind again.

Anyone know what is going on?
 
Originally posted by: pwddesign
I checked my main system this morning, to see that it was hording 5 WU's instead of sending them. I noticed that my proxy/socks setting had somehow changed itself from proxy to socks, therefore not allowing it to connect. I changed it back and transmitted. It sent all but 1 WU. When I click transmit, it doesn't even try to send it. I figured it would go when another WU finished, but one just finished and sent, leaving the loner behind again.

Anyone know what is going on?


Did you "stop" and then "restart" SETIDriver?
 
my seti driver has been doing this to me over the past week as well. i dont know what the hell the deal is so what im doing to safeguard against it is to queue up at least 10-15 units on the machines that are doing them so that will at least give me 1 days worth of units to crunch if for some reason it stalls before i can check on it. its only been happening recently and never occured for me with the old version of seti driver but has just started with the newest edition...
 
Originally posted by: plankton
my seti driver has been doing this to me over the past week as well. i dont know what the hell the deal is so what im doing to safeguard against it is to queue up at least 10-15 units on the machines that are doing them so that will at least give me 1 days worth of units to crunch if for some reason it stalls before i can check on it. its only been happening recently and never occured for me with the old version of seti driver but has just started with the newest edition...

Better to have a 7dy cache! So if ever the Q or Berkeley's server are down for awhile you won't run out of WUs !! 🙂

@Ray , I don't think there's any more bad wus, but O/Cling to much seems to do this on my work fleet!😕 don't know why every other programs still run ok.:evil:


Paf
 
im running a seti queue as well so if i throw down 10 on each machine plus have 3 days worth in my queue then i have plenty to get by. 🙂
 
Originally posted by: plankton
im running a seti queue as well so if i throw down 10 on each machine plus have 3 days worth in my queue then i have plenty to get by. 🙂

Best set you Q to min 10days and max to 20!! You konw what I mean?? 🙂🙂

Paf
 
You can manually send yoru work units if there are any, by putting the client in the directory that containd the wu, ie if the completed wu is in \setiathome\1\ put the cmd line client in 1 and start it up, it will take care of the rest....

~Ryan
 
i've seen something happen like this. auto-transmit would be unchecked for some reason, i'd click it back, restart the prog., then find it un-clicked again. doh😱, i forgot to ever save my settings in the first place. after everything is running, i tend to assume things are fine.

easily dealing with this, of course like everyone else already mentioned, is to use a seti queue. I have a couple new setups runnings on a 50 queue bank for the week until i find the right hardware to connect them all. not having to constantly unplug & plug my only network cable to send results & check up on them would be great(anyone got a good deal on a switch?🙂)
 
Back
Top