Hello!

Since yesterday I get the following message when I try to add a PC to Boincstats:

"Account manager error: 0 Unable to add host to BAM!. Please try again later."

The Computer was until a week or two "member of Boincstats". Now I will "readd" him, but I doesn´t work...

Any hints?

Bye

Andy

Uhm, how is this related to CPID's?

Sorry - I didn´t find the forum which title is related to my problem (bug report)...

Bye

Andy

Did you detach the client from BAM! and are now trying to reattach it? Then you should first delete the host from you BAM! host list.

Otherwise I need more information about what you did with the host.

I was just looking into why my credits weren't growing as fast any more. I have several hosts running.

I found that two of my hosts (LINUX based that have been running for a long time) had been detached from all projects in BAM without my approval. I was able to go into one PC and detach from the project manger then reattach then go into boincstats and attach the host to the projects and everything started up OK.

The other PC I was able to detach from BAM but when I try to attach it tells me:
Account manager error: 0 unable to add hosts to BAM!. Please try again later.

I even updated BOINC to the latest LINUX version without any improvement.

Also, in the lists of my hosts it shows a last contact at about the time I tried to re-attach.

Something is really FUBAR'd somewhere.

I would really rather not delete the host from BAM and have it create a new one unless there is some way to keep and merge the history instead of it always appearing as two separate systems.

What next?

The credit history is totally unrelated to the BAM! host list. Deleting it from BAM! (and reattaching it) does in no way affect the stats. What does affect the stats is if the host CPID changes, but that is controlled by the host itself, not by BAM!.

OK. I deleted the host from BAM! and then went to the host and it let me reattach it to BAM!.

And, as you said, it went back to the projects and picked up the host's history.

Not sure yet why it 1) detached the host from all the projects 2) wouldn't let me reattach it to BAM! without deleting it from within BAM! first.

Thanks.

[quote]...Then you should first delete the host from you BAM! host list.


THX!!!

That´s the solution!

bye

Andy

I'm getting a similar error message from some of my clients.

Only in my case the clients that are having the problem are all running Cruncher's modified BOINC client version 5.5.0 which reports wu's immediately after uploading.

All the 5.5.0 clients show last contact as 8/28 or 8/29. I have clients set to contact BAM once a day. All my hosts that are running newer clients are working fine with BAM.

Will deleting the hosts and reattaching work for me or do I need to update BOINC? I really like having the client report wu's right off.

Black Beard

If this is a way to get rid of the cheater client, it's fine imho
Use an official client with proper benchmarks and proper documentation, and everything will be fine.

Cheater Client? What are you talking about?

Correct me if I'm wrong but AFAIK the only mod to this client is that it reports results immediately on upload instead of letting a huge que of results pile up until the next update.

I never saw the purpose in not reporting when the result is uploaded. They claim it reduces network traffic but it actually causes more network traffic because the client has to make an additional connection to report the result after it has already made a connection earlier to upload the result. I also find it "aesthetically unpleasant"*.

I've also been burned out of credit because of results not being reported when a project goes down. I lost a lot of credit from RS and it looks like I might lose a bunch more from Cosmo because of this.

Black Beard

*It bugs me.

The main purpose of the 5.5.0 is to artificially increase the benchmarks to claim more credits on projects that ise benchmarks.
The tag <return_results_immediately> is considered evil by the developers, and I simply believe it. It was never claimed that it reduces network traffic, that's not the problem, the problem is server load at the projects database servers. Here is the article by Rom Walton about it.

And you won't lose any from Cosmo probably, at least not because of that missing feature. Upload is possible at the moment, but reporting not. This two steps are distinct things and result in a very different load on the project servers.

This thread seems to disagree with your statement that the 5.5.0 client artificially inflates benchmarks.
and I don't know who Rom Walton is but he should invest in a spell checker. I know nothing about running a DB server so I will have to defer to his 'expertise'.

The only way I won't lose credits for Cosmo is if they actually get the DB servers running again which at this point I'm not convinced they will. I'm downloading crunching and uploading wu's but can't report so no credit. I'm doing all the work but getting no 'return' on my investment.

Black Beard

Rom is one of the main BOINC developers.
For more information about the illegal cheater client 5.5.0 read this thread, Crunch3r retracted it, it's no longer GPL compatible, so it's (besides plain cheating) illegal.

In regard of Cosmo:
Why do you still DL work? I've set it to No New Work on the day they announced the DB-changes, even before the mess with the raid occured. I ahvn't changed them back yet as I know (and you know the same) it will probably be futile. I've even stopped the WUs not already started at the time of the crash, why possibly waste CPU-time on Cosmo if I can use it on other projects? I'll be back as soon as the server is up again (or at least as soon as I hear about that )

First off let me say I didn't read that entire thread (too long). But from what I did read the illegal thing is to redistribute the app without the source code. There is nothing illegal about using the app. And also from what I did read I didn't see any mention of the app cheating on benchmarks.

Regarding Cosmo, I didn't know ahead of time about the raid crash! I'm not psychic. [] and I don't check every projects homepage every day. Also I don't like deleting work I've already done. I like to get credit for the work I do if I can.

Black Beard

I have a similar problem ,when reconnecting a maschine which was offline for some time.
These get deleted in my host list. (At least not shown any more.

As soon as I try to sync again, I get this message.

Anyway I tried this workaround, but could not find the button to delete the host.
Could someone help me open my eyes?

Thanks

Achim

Click on the 'Host list' in your BAM menu. Click on the name of the host. On the bottom of the page with the host details you will see a red link "delete this host"

HTH

Thanks somehow I expected a button, but no simple link.
Found it.(You opened my eyes)

Hi Willy,

I ran into this problem yesterday when I detached from BAM. But, I just noticed that some of my hosts are detaching from BAM by theirselves or BAM is detaching them without my knowledge. I noticed a change in the Host List operations because it's not deleting host that haven't connected for 30 days like it use too. My Question is should I detach, delete hosts and reattach to BAM? Would that help stop the autodetaching?

Thanks

Bill


Edited: I got back attached, but all the projects were reset/detached and all my work was deleted of course. Very Confusing?

There is something wrong with the new way the host are being handled. My host are being detach by theirselves by BAM, then they get this message. Then when you delete the host and try to attach again it resets all the projects and detaches the host from all the projects. When you check host settings there aren't any boxes checked. Something is Broke.

I have ben havingthis issue as well. I did detach, delete the host, and then re-attached. That fixed the problem for a few days. Now it is happening again. On one host I have verified that the CPID listed in the xml files does not match up to the info on BAM. All other details are correct. This is not a new host...attached to BAM November of last year.

BAM is a great tool. And I would like to continue to use, but what choice do I have if I keep getting detached. The last major thing i remember changing was attaching to MalariaControl....could they have contributed to this issue?



Please help.

Host-ID??

For me it is hosts 988 and 131774. Both exhibited this error only today, after the DB reconnection.

[edit] Deleted and reattached hosts. They are now 135768 and 135769 respectively. This isn't going to happen every time the DB goes offline is it?

If the datacenter disconnects current to the server there is now way for me to have a grip on what's happening to the server/data.

Only during the last downtime the host table was corrupted and unexpected things happened to host that tried to connect BAM!.

For the new host that would not connect I deleted 2 acct_mgr_???.xml files from the BOINC directory and then was able to attach after that. One of the files was acct_mgr_reply.xml....I forgot to note the other one.

As far as "disconnected hosts" these are the ones I am sure of...
32236
58051
58055
134589 <- this host was one of the ones I manually disconnected and reconnected
135879 <- this is the other one but seems to be okay right now