my one win98 box keeps attaching itself to SETI over and over and over. I have merged it at least 20 times now, only losing/abandoning a few WUs overall, but if you look at my stats now you can see where it has attached itself 2 more times in just the last day!

including the relevant hosts here for future reference once the issue has been resolved

444220 10 67.45 3,281.28 GenuineIntel Pentium Microsoft Windows 98 SE, (04.10.2222.00)

444457 12 9.04 25.25 GenuineIntel Pentium Microsoft Windows 98 SE, (04.10.2222.00)

444456 13 0.00 0.00 GenuineIntel Pentium Microsoft Windows 98 SE, (04.10.2222.00)


i will have to abandon WUs this time (sorry ppl, some will go over deadline) but does anyone know how to keep it from doing this (or why it might be in the first place)?
i have tried everything i could think of short of doing a complete uninstall of BOINC or going to a beta release.

thanks in advance

---

S@h Berkeley's Staff Friends Club

looks like it keeps seeing your connected computer as having different IP addresses and keeps seeing it as a new host. not sure how to stop it though

---

I don't believe that a change in the IP would cause this. The following is a quote from Rom Walton about a month ago concerning a similar problem.

quote
The issue causing the host to be recreated with every RPC has been identified and a fix has been checked in.

Basically the problem was that BOINC couldn't write to the state file and so everytime BOINC was restarted on that machine, it would recreate a new host.

This mostly happened in schools where the administrator/teacher setup the software and then the students, with less premissioned accounts, started up the software but couldn't modify the state files or store the workunits.

For the short term we are just going to have BOINC shut itself down when it detects this condition, eventually we'll have a smart enough setup to allow the person settng up the software to configure BOINC to run as a service.
unquote

This is a more likely cause of the problem.

---

Boinc....Boinc....Boinc....Boinc....

> I don't believe that a change in the IP would cause this. The following is a
> quote from Rom Walton about a month ago concerning a similar problem.
>
Rom's statement is possible, as that machine is old (and an HP on top of that) it is very possible that the drive is just not responding to the BOINC client fast enough. i do not have that unit set to Static IP, but it has not been rebooted in at least 2 weeks and has continued this.
i have just in the past day been working on optimizing the disk, cleaning old crap off and running diskeeper numerous times.

any other ideas very welcome

thanks again!

---

S@h Berkeley's Staff Friends Club

when I added my wireless network card boinc saw my computers as a "new" host. Then when I tried to set up my network differently Boinc saw this puter as a "new" host. Each time it added the same puter under a different name.

---

Host # 444457 looks like it got caught at about the time of the power outage at SETI Central. Wonder if that's part of your problem?

All my SETI boxes are WIN98 (intel and amd, 500Mhz - 2.4GHz) and I have never experienced a problem like this one.

---

<img src="http://www.boincstats.com/stats/teambanner.php?teamname=GasBuddy"> <img src="http://www.boincstats.com/stats/banner.php?cpid=84c0cf7846cbf28338406e54b3eb8a83">

i seem to have resolved this. I am guessing that the issue was that BOINC was starting while the processor and HDD were too taxed. After a good bit of work on startup and getting more of the drive free (was down to like 9%) and running DisKeeper over and over and setting the smart scheduler to run all day everyday for a week, this has not happened.

quote
The issue causing the host to be recreated with every RPC has been identified and a fix has been checked in.

Basically the problem was that BOINC couldn't write to the state file and so everytime BOINC was restarted on that machine, it would recreate a new host.

thanks everyone!

---

S@h Berkeley's Staff Friends Club