After Seti beeing up again i´ve noticed a strange behavior of two host of mine.

Everytime they connect to the sheduler or returning WU´s they get a new host id. Nothing has changed on both machines and detaching /reataching doesn´t solve the problem.

All other machines are running just fine with no such problems the only difference is that these two machines are running linux (boinc 4.32 and 4.19).

I´ve no idea what´s going on there maybe someone else noticed something similar or could help me solving the problem.

Greetz from Germany
Crunch3r

As you know you should get a new ID either when you first bring a system on, or when the system changes in terms of CPU or operating system.

Since this isn't being reported by others, it is unlikely that it is related to the outage.

Unfortunately your computers are hidden, so it is not possible to see what, if anything is changing in the system descriptions.

What messages are you getting in the log?

The Host id is stored on your system in 'client_state_prev.xml' ('hostid'), in the BOINC folder. Is this file present, and does it contain the id you expect?
There may be more than one 'hostid' entry, one per project you arte attached to.

I suspect the answer may lie with BOINCs' access to this file and/or client_state.xml.

---

Although not with SETI, I have noted exactly the same for other Projects (EAH, PAH), the phenomenon lasted for about last week.

Seems to have stopped now; no changes whatsoever were done to the affected Hosts...

Anyway, came out of nowhere and vanished like there never was anything (apart from some affected Hosts ID now naturally being changed to a higher ID after having to merge Hosts about half a dozen times)

---

the only "strange" thing that i've had happen recently was with this wu: 14059629

i think the first one i got after the outage was a noisy one...

[edit] - tried to fix my link, must be rusty html - [endedit]

---

No matter where you go, there you are...

> Although not with SETI, I have noted exactly the same for other Projects (EAH,
> PAH), the phenomenon lasted for about last week.
>
> Seems to have stopped now; no changes whatsoever were done to the affected
> Hosts...
>
> Anyway, came out of nowhere and vanished like there never was anything (apart
> from some affected Hosts ID now naturally being changed to a higher ID after
> having to merge Hosts about half a dozen times)
>

Well seems like the affected host stoped getting new host id´s... now the other ones ( windows clients) are affected...

I guess the only thing that helps ist to merge these host into the new id... same as falconfly did. %-(

---

Join BOINC United now!