I have multiple hosts that are under BOINCstats/BAM's wing that are not receiving any credit for several days straight. I have tried different things for several weeks as BOINCStats have dropped my hosts, including posting.

The most straight forward message is "Host doesn't exist in BOINC combined or doesn't have any credit" from the "host_list.php" page. But don't understand why some days it displays this message and other days it does not.

From a Host's subpage I generally get valid data, but even that is not always true.

So what have I done:
-dropped BAM as controller from the client and issued "Attach to project or account manager" command sequence at the BOINC manager to re-initialize my connection -- no change
-installed old, current and beta versions of BOINC Manager -- no change
-changed projects (dumped Climate Predition for Einstein), have three active projects. -- no change
-monitored my local network to maintain consistent addressing -- no change
-visitied Project websites (Rosetta, Einstein, Seti) to verify their are collecting credits -- and they are
__Well Rosetta scheduling is not always giving out work, so there are some holes
-manually issued a Synchronize with BOINCstats BAM! command at client -- alway get success responses -- no change in behavior.
-refreshed my CPID -- no change
-added brand new host -- well some days it see it, other days it doesn't

I have not "deleted" a host yet. Pretty sure that changes the BAM ID. Kinda dire to do this, but since BOINCstat/BAM is busted, this just might work. Of course I lose any bragging rights about how long a host has been involved (and the converse of inflating the number of hosts I have)

WHINE ALERT: I have "lost" well over 200,000 credits in the past couple weeks, dropping more than a hundred places.

Thanks in advance
Carla


PS: I guess I should start another thread that BAM not being able to control the resource allocation of the BOINC manager. Ask for 1000 and idle (stop gap for Rosetta's lack of work) and get 50 / 50. Need to experiment some more first.

So I did the deed, and deleted a host using BOINCstat. And with in moments issued a Synchronize with BOINCstats BAM! command at client. A new host BAM host id was created. And there was credit.

Now nearly a day later, there is lots of credit. And other hosts appeared with credit.

So I will wait another day and see if any other host sshow up. If not, I will delete and add again.

Carla

At which project have you lost credits? As I stated in the other thread, BAM has nothing to do with credits; if you have lost any at BOINCstats it's because there was a change at one of the projects. Occasionally, there are errors in the stats on either side of the equation that are usually solved at the next update; if you are still missing credits after 24 hours or so (or whatever the update interval for the project is) you should direct your attention towards the project itself. Sometimes, this is caused on purpose by the projects when they reallocate credits issued.

Regarding hosts not showing up in your host list; go to one of the hosts that's not currently shown and do a "Synchronize with BOINCstats" from the Tools menu of the BOINC client. Note any errors on the Messages tab; if you are getting the "inconsistent signing key" message you might be able to solve it simply by detaching from BAM and then re-attaching.


This message should not be coming from "host_list.php" since that is a BAM page and does not display any credit information. If you are refering to the host list shown through "My detailed stats" (boinc_host_stats.php) you will have likely solved the problem when you got one of your hosts to work properly with BAM again. Even though BAM itself does not manage credits, it does grab your CPID, which is the primary key for finding you on the stats side of things and linking the two for the detailed stats and forum. If your hosts were not syncing with BAM for a while and the projects renewed your CPID for some reason, the link between your BAM account and the stats is lost. Thus, the "Host doesn't exist in BOINC combined or doesn't have any credit" error.

to continue my saga

So host_list.php displays a list of known hosts.
For this example we will use Host "workaround" We see that this host was in contact with BAM within the last 24 hour, but no Credit .
Click the right most "stats" button and your get: "Host doesn't exist in BOINC combined or doesn't have any credit." from stats/boinc_host_graph.php?pr=bo&id=a57439d700b209f38208eb052839f5bd. Sigh No credit and if the grand total did not increase, then it is easy to make the statement of "lost" credit. Noderaser is sorta right that the underlying system will count, by not aways.

So back to host_list.php
click on "workaround" and we get a nice page from bam/account_host.php?host_id=148335 So we know BAM is aware of us Good.

click on the "stats" for a project. Rosetta -- http://boincstats.com/stats/host_graph.php?pr=rosetta&id=972704. Well we all know that Rosetta had a hardware crash and has been struggling all week. I have a couple of dozen completed tasks that will not upload, therefore a plateau. And with Rosetta's various scheduling droughts, I have added Einstien.

I am not anal enough to keep track of how many credits I submit everyday for every host. When this issue arose I was breaking through the 8700 level and rising a couple ranks every day. So for the past 30-45 days I have lost ranks falling back into the 8800s. My ClimatePrediction tasks would complete successfull, but the Climatepredicition site has a fault and can't display a user' contribution <being Family Friendly PC> So I dumped them. There is definetely lost credit, but not a BAM issue.

So BOINCstats/BAM work on XML -- there are bugs in rececption of the from the projects. So my grand total has not increase as expected.

So is there a solution to all of this. YES!!! the fix is to delete your host that BOINCstat/BAM is not counting and then do an update from the client. Works like a charm.

As my Boss says frequently -- Databases are never trustworthy -- Slam them as needed....

Also this database slam also fixed the Resource Share allocation issue I was having.

Bye everyone
Carla