6 or more identities were were assigned today according to my Seti account data. I performed a merge operation and all but 2 merged. The reason given for the failure to merge the remaining 2 was overlapping lifetimes. I forced the computer to report completed projects and returned to "computers on this account" to find that both received a portion of the credit. There have been no changes to the computer in several months. i7 24GB RAM and 1 Nvidia Tesla. Windows XP Pro x64 & Seti 6.10.60 with Lunatics Win64 v0.38. Never seen this kind of behavior before. Any ideas?

---

Delta-V

I've seen this several times & have one machine that tends to do it often. I decided the last time that it did it I wouldn't merge in the event the issues is some error in the db for that computer ID. So far so good, but sometimes it could be months between occurrences or just a few hours. So I will just have to sit and wait to find out if it worked or not. :/

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I presently have 1 machine in this condition exactly.

I have not been able to figure out how to fix it.

---

Dave

I think a full uninstall including registry entries followed by a reinstall would temporarily cure the problem but whats to prevent it from re-occurring? Besides dealing with removing orphaned work units and downloading more can be a hassle especially with recent download, upload and reporting problems.

---

Delta-V

I think a full uninstall including registry entries followed by a reinstall would temporarily cure the problem but whats to prevent it from re-occurring? Besides dealing with removing orphaned work units and downloading more can be a hassle especially with recent download, upload and reporting problems.

I have a feeling this is a server side SNAFU. That is why I decided not to merge the machines the last time it occurred.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

Did your "clones" eventually go away? Except for 1 with credit all others had zero credit and merged with no problem. Did any of yours continue to run concurrently and share in earning credit?

---

Delta-V

Did your "clones" eventually go away? Except for 1 with credit all others had zero credit and merged with no problem. Did any of yours continue to run concurrently and share in earning credit?

Machine never go away automatically. After 30 days you will have to hit the All Computers link to see the old ones, but they will remain until you delete them. Which requires all of the tasks on that ID to go away.

What I have seen is that all of the tasks that the machine processed that were assigned under the old ID were completed validated on the old ID. That might be what you are seeing when you say they are sharing credit. Unless the same task is assigned to both IDs.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I presently have 1 machine in this condition exactly.

I have not been able to figure out how to fix it.

If the "ghost" has not been allocated tasks you can just delete it. The link to do so is at the bottom of the ghost's "Details" link.

If it has tasks allocated I wait for them to time out and get validated by the new wingman. Once they've disappeared from its task list you can then delete it as per above.

I refuse to merge them as I got sick of loosing my "historical" low cruncher numbers to a(nother) server problem.

T.A.

I think a full uninstall including registry entries followed by a reinstall would temporarily cure the problem but whats to prevent it from re-occurring? Besides dealing with removing orphaned work units and downloading more can be a hassle especially with recent download, upload and reporting problems.

I have a feeling this is a server side SNAFU. That is why I decided not to merge the machines the last time it occurred.

Well my guess as to this being a server issue may not be correct. My machine that keeps doing this did it again on the 26th. So I went ahead and merged all 3 of them. If it isn't a server issue then I am really confused. A few months ago I replace the HD, installed a new OS (changed from XP x86 to 7 x64), & blew away everything to start BOINC from scratch. I did name the machine the same... maybe they just don't like my machine name. Who knows. /me screams in silence.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[