Hi,

I used to run the seti at home classic (I started in 1999). However I stopped running this at about the time BOINC started to be used.

Anyway a few days ago I installed BOINC on some of my machines to run SETI but I seem to be having some issues.

The first machine, command line linux CentOS, no problems what so ever. It happily goes through the units pretty quickly and I haven't even bothered checking its status because it is showing as having credits on my account page on the seti.berkeley.edu website.

The next machine, command line linux CentOS, I ran exactly the same commands and it has done a work unit (started on its second), but its units are not showing on the webpage. Also, when I run "./boinc_cmd --get_state" it says that there is a unit ready to report. However, it doesn't seem to be making any effort to report it despite the fact that it has got a second unit from somewhere.

Machine number three, Ubuntu GUI, has finished a work unit. Hasn't reported it or bothered to get a new one.

Machine number four, windows xp GUI, has finished a work unit, started on another one but not submitted the first result.

I'm wondering if the SETI servers are currently down or something? Or am I doing something stupid?

I simply ran "./boinc" in a screen, then outside of the screen ran "./boinc --project_attach http://setiathome.berkeley.edu/ MYCODE". Then when I go back to the screen it says it has work and is getting on with it.

Also, 'grep "fraction_done" client_state.xml' shows that stuff is going on on all the machines that have work.

All these machines are servers so the internet is always on, no proxies or anything that would get in the way. On the GUI ones if I press "update" I get "Scheduler request pending, Requested by user, Communication deffered (a count down goes here)".

I wonder if I need to pass more arguments to the command line ones, I tried stopping boinc and running "./boinc --return_results_immediately" but it didnt seem to do anything.

Confused! Any help appreciated! Normally I'd take a guess and say the seti servers are temporarily down but as Ive only just started with boinc and im having this issue straight away im not so sure.

Well, it seems to work now

---

Reporting is done if one of a few things are done.
1: BOINC determines it needs more work
2: 24 hours
3: Manual Update (not recommended)

The database gets hit hard, and each report causes a database open, write, close. If you report 2-3 units at a time, instead of 1, this saves database time as it can be done just as fast, and gives a lesser chance of corruption.

So, it queues the reports until one of the above conditions have been established. This was on older versions of BOINC, was removed for a while, but has returned.

---

My movie https://vimeo.com/manage/videos/502242

Thanks for clearing that up :)

---