SETI - Any decent working monitoring programs?

[Assimilator1]

I've tried SETIspy reloaded & SETI@BOINC watch & neither seem to work 🙁 ,SETIspy reloaded hasn't been updated in over 2yrs & SETI@BOINC watch in over 1yr.

Are their any others ? or has anyone got the above 2 to work?

I've got a load of WUs which finished much earlier than normal ,I want to know if I've got a bunch of VHAR WUs or my rig is currently unstable!:Q (I've done a 6hr P95 test & it was ok but I would of normally done a 24hr test ,I will do when time allows)

 

[bryanW1995]

are you getting client errors when you look at your WU's?

never mind, you are fine. you have had only one error on all of your reported WU's, and it was a validate error. trust me, if your oc is unstable your computer will let you know in no uncertain terms 😉 I have unfortunately, at one time or another, gotten too aggressive on just about every one of my rigs. This led to client errors out the wazoo. You have nothing to worry about except whether to oc a little bit more or not.

I believe that matt mentioned something about very short WU's the other day when they took the server down. We should have a day or two of these 15-20 credit WU's before getting back to the big ones.

 

[Assimilator1]

Thanks Bryan ,good to know my rig isn't spitting out bad WUs🙂

Btw you might want to run Prime 95 for 24hrs to avoid unstable overclocks & invalid results😉
Re quick WUs ,yes I remember now something about it in the news that RD delivers:thumbsup:

Oh I am still interested in finding a decent monitoring app btw😉

 

[Rattledagger]

BoincView should be a possibility...

 

[Assimilator1]

Thanks 🙂

Darn ,can't get it working🙁 .......wait a minute ,I've tried this before as I remember having this problem before!😛 ,can't remember how i fixed it though.....
It can't seem to see my PC ,tried local host & its LAN IP ,says no client detected on those ,on 127 etc it just says & does nothing!😕

 

[Rattledagger]

Have you remembered to configure the remote BOINC-client for external connections?

If not, place a remote_hosts.cfg in the BOINC-directory, and in this put-in the name or ip of the computer you're going to monitor from, one name or ip per line.

Also, make sure you knows the password in gui_rpc_auth.cfg

Re-start BOINC on remote computer(s), after adding/changing either of the files.

As for other things, BOINC uses port 31416, so make sure your lan isn't blocking this...

 

[Assimilator1]

Man what a lot of hassle to setup a little monitoring!:Q🙁 , bring back SETIspy reloaded!
Anyway ,thanks for the info 🙂 ,I'll give it a go.

Also, make sure you know the password for gui_rpc_auth.cfg

What the heck is that? lol [edit]ah the BOINC password

Btw I hadn't forgotten I just never knew in the 1st place.....unless I'd totally forgotten about it! 😉

It's working now 🙂 ,but I can't seem to check the WUs AR in it!🙁

 

[Assimilator1]

Just wondered if anything has turned up?