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

Anyone seen this error in SetiQueue?

R

Robor

Elite Member
11/12 Sun 9:59am ERR reported cpu_time is bad
11/12 Sun 9:59am sah 192.168.1.101 -> qresult.3205 0h00m00s
11/12 Sun 9:59am sah 192.168.1.101 <- user_info
11/12 Sun 9:59am sah 192.168.1.101 <- qwork.3a0917a4

This is from my main box that I just did a fresh reinstall on. The CPU is a P3-550E and it is not overclocked. The only thing I noticed is I screwed up and had the wrong time/date in Windows. I corrected it now so I'll see if I get this error again.

Rob
 
Yes I had that error before(twice) ,that was also with a 0hr 00 result.
I'm guessing that there was corrupted WU (?)

Anyway ,it didn't happen again on that PC so I ignored it!😉
Let us know what happens with further WU's
 
So far so good. Hasn't happened since. The weird thing is I saw a WU in my results.log that was 304hr+ to complete. This is an error because I did WU's before and after this WU in the same day. Sucks to add a 304hr WU time to my average though. Takes a long time to make that back up if it's possible at all.

Rob
 
Rober,

Twice I have had WU's with UNREAL times: 175 and 148 hours. In both cases I had double-clicked on the time in the Systray to look at the calendar. I did not change anything. I sent screen shots of the error to the author of SetiDriver, and he responded that it was an error with the cli. At that time I was running cli v2.4. I no longer use Windows as a calendar. If I need to change the time I first stop S@H, then make the adjustment.

Recently I have had situations where the computer reports that it would take 100+ hours to complete a WU. In one case it had been running for 12+ hours and was less than 10% done. I stopped S@H and rebooted the system. The WU then completed in the normal time, but the time for the first 10% was of course included. The latest instance was with a Cel300a that I installed and set to run at 450. When I discovered it was taking toooo long (via Stats in Setiq) I reboot and reduced the FSB from 100 to 90 MHz. It was working fine when I left for work. I might have a melted mess when I return tonight.

Good luck! And, yes it really screws up the WU average times!
 
I would really love to know what this guy was running SETI on! ,that would take years to shed that high time!:Q

437) CmdrJoe......... 1....... 299 hr 24 min ......299 hr 24 min 49.4 sec
 
Probably an old 386 or 486. Notice that he only did one? If I was going to test a piece of junk system, just to see what it would do, I think I'd create a new account myself, just to avoid that nasty time on my average.. 🙂
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top