It seems the problem is solved by detaching from BAM! and attaching again. It's however not a perfect solution. There are now numerous hosts which are duplicated in the database on every connection because their CPID changed between connections. And if the opaque is missing and the CPID changed there is no way to match the host to an existing host in the DB.
Shouldn't the opaque send to the client by the last BAM! rpc be used in the next request to BAM!? Willy. On Sun, Jul 1, 2012 at 5:04 PM, Willy <[email protected]> wrote: > The opaque section of AMS RPC from BOINC v7 hosts is no longer containing > the data send to the host by BAM! It's just an empy line. This is causing > problems with hosts that change their CPID every connections. Older v6 > hosts do contain the data. > > v7 example: > <acct_mgr_login> > <login>[BOINCstats] Willy</login> > <password_hash>duh</password_hash> > > <previous_host_cpid>a152f0baac4907dafebd1ccc7335e2a7</previous_host_cpid> > <next_rpc_time>1341157151.659159</next_rpc_time> > <opaque> > > </opaque> > </acct_mgr_login> > > v6 example: > <acct_mgr_login> > <login>[BOINCstats] Willy</login> > <password_hash>duh</password_hash> > > <previous_host_cpid>70718f69af7772225df32529bfdf586f</previous_host_cpid> > <next_rpc_time>1341157176.408516</next_rpc_time> > <opaque> > <host_authenticator>32charactercode</host_authenticator> > </opaque> > </acct_mgr_login> > > These are both taken from hosts which are connected to BAM! for years now. > One of them was upgraded to 7.0.25 last week. The other one is 6.12.33. > > The data is also missing from acct_mgr_login.xml. > > Willy > _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
