Weird stuff

[Logan[TeamX]]

Had a weird bug in 3 of my 4 SETI boxes here at work... only did 1 WU each last night, and my workstation (slowest of the lot!) had a weird memory exception error - I guess that's the exploit that SETI@Home was talking about? All it did was crash SETI, and I rebooted my box, and now it's fine. Did the same for 2 of the 3 new 2.4GHz Northwoods I got... but no error message. They just did 1 WU each overnight (about a 16 hour period between leaving for home and coming in the next morning). They all get WUs from my SETIQueue server here at the office (my workstation again), so I'se a little confused, but everything appears to be back up and running again.

Oh well... the Northwood that DID run all night did 5 WUs in 16 hours, not bad I suppose! I'll check the average time later on today, I have a ton to do here this morning. Have a good day everyone!

[Logan[TeamX]]

Hmmm... I downloaded a WU checker from one of the well-known guys on the S@H message boards... I checked all 4 stacks of WUs on all 4 machines (after writing a long script to check the folders, that was fun :rolleyes: ), and all WUs came out ok. I guess I got whacked once or twice, and that was it. At least I have a script now that will check it for me :D

If anyone wants the program and script I created, email me off my site: http://www.one87.net/~teamx

It checks to make sure that there are no over-length lines in the WU, and saves you from having to run the 3.08 CLI client. If you find one, just delete the folder that the faulty WU resides in.

The new P4 Northwoods are nice and quick... I'll show you what I mean :)


http://www.one87.net/~teamx/sitepics/SETIWatch.jpg

[EDIT] - oh, Webby... I tried to email you that I'd like to be on the Links page at the SETITEAM.com site, but Cogeco just relayed back to me that your address can't be found. Still having site problems?

Logan

[Logan[TeamX]]

Hmmm... found the massive memory leak I was having... it was SETIWatch! :mad:

Came in this morning, checked my Task Manager and found SETIWatch using an ungodly 42MB of RAM, and who knows what else in swap file! I went from 330MB to 140 by simply shutting down SETIWatch. Now I know where my massive slowdown and memory errors were coming from. :mad:

[RampageIII]

Yeah, I don't run setiwatch all the time, just open to check what's running.

If you have to run all the time, set the refresh rate to zero and refresh manually.

:)

[Logan[TeamX]]

Thanks for the tip RampageIII!

I think it was even messing with my SETI processing, cause I have SETI Driver running the CLI on the new Northwoods, and one of em only did two WUs last night. Either I'm setting them to normal priority for the night and dropping it down to low in the morning, or I'll just KICK IT! MUAHAHAHA. Sorry. Just annoyed is all. :rolleyes:

[genesound]

I found i had to set it to over like 1 minute with it set for several machines on the network or I couldn't even get it to respond to input, i.e changing tabs etc. :rolleyes:

I just run it once a day or so to check all the machines are runnin ;)