Index :: BAM! Bug Report :: Inconsistent signing key from account manager - one more times

Pages: [1]
Author
Message
rroonnaalldd
PM
BAM!-ID: 15220
Joined: 2006-12-20
Posts: 207
Credits: 77,143,689
World-rank: 6,618
Posted 2012-03-30 18:23:15
I get this message on my Lubuntu64-11.10 box with client 6.10.56. The same client on my older DotschUX1.2-x64 box has no problems.
Does anybody know, which berkeley pre-v7 client works?

rroonnaalldd
PM
BAM!-ID: 15220
Joined: 2006-12-20
Posts: 207
Credits: 77,143,689
World-rank: 6,618
Posted 2012-03-31 15:58:07
I tested 6.12.34 and found:
<host_uhntiiccaator>1234567890</host_authentictoor> in "acct_mgr_login.xml" and "acct_mgr_request.xml"


[BOINCstats] Willy
PM Profile
Forum moderator - Administrator - Developer - Tester - Translator
BAM!-ID: 1
Joined: 2006-01-09
Posts: 8890
Credits: 342,073,175
World-rank: 2,105
Posted 2012-03-31 16:49:26
It's not a BAM! Bug, it's a BOINC manager bug.

Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.
rroonnaalldd
PM
BAM!-ID: 15220
Joined: 2006-12-20
Posts: 207
Credits: 77,143,689
World-rank: 6,618
Posted 2012-03-31 16:58:33
BOINCstats Willy wrote:
It's not a BAM! Bug, it's a BOINC manager bug.

Yeah, i know this but how can this be solved?

I tested the latest beta 7.0.23 and the tags seems to be correct now.
But this did not solve my problem, i got "[error] Inconsistent signing key from account manager"...

[BOINCstats] Willy
PM Profile
Forum moderator - Administrator - Developer - Tester - Translator
BAM!-ID: 1
Joined: 2006-01-09
Posts: 8890
Credits: 342,073,175
World-rank: 2,105
Posted 2012-03-31 17:06:11
There are already XML fixes in place at BAM! but if the XML is too messed up the auto-fix will fail.

Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.
rroonnaalldd
PM
BAM!-ID: 15220
Joined: 2006-12-20
Posts: 207
Credits: 77,143,689
World-rank: 6,618
Posted 2012-03-31 19:32:28
I checked all acct-mgr.xml-files and found no tag missmatch... To solve this again, i detached this host from BAM and deleted all acct_*.xml's one more times. After reattaching this host, it seems to work.

In the middletime i updated multiple times and got/get no signing key messages. This could be random because i saw the same all times before and the problem was back after 2, 3 days.
I keep you informed.

xmal
PM Profile
BAM!-ID: 1216
Joined: 2006-05-31
Posts: 9
Credits: 44,487,038
World-rank: 10,176
Posted 2012-04-06 07:19:31 , last modified: 2012-04-06 07:40:28
Hello!

I've this error too! :-( (boinc 6.12.34 on linux mageia)
Ok, I've readen it's not a BAM bug but... if I want to use still BAM (And I would like to!) what could I do ?

Thanx in advance!
rroonnaalldd
PM
BAM!-ID: 15220
Joined: 2006-12-20
Posts: 207
Credits: 77,143,689
World-rank: 6,618
Posted 2012-04-07 10:12:47
I will stay at v7.0.23 for the next time (months or years, we will see).
After the first "signing key message", i did the following. Detach from BAM, delete all acct_mgr-files manually and re-attach to BAM.
Since then no further "signing key messages" in the v7-log.
But you have to change the network preference "Computer is connected to the Internet about every, Leave blank or 0 if always connected. BOINC will try to maintain at least this much work." The meaning of this has been changed. Should be documented somewhere in the boinc-beta forums at berkeley.
If you let it at zero, no new work will be loaded as long as you have work on your host. Boinc will start ask for work, if absolutely no work is on the host. I use now the same setting for "Maintain enough work for an additional" and "Computer is connected to the Internet about every" without any problems.

Be aware that BOINC 7 is an one-way ticket. The syntax inside some xml-files has been changed and you need a complete backup of your BOINC installation.
If you want to stay at pre-v7, try another beta 6.13.12.

ebahapo
PM Profile
BAM!-ID: 239
Joined: 2006-05-12
Posts: 647
Credits: 15,489,899
World-rank: 23,884
Posted 2012-04-09 19:13:37
rroonnaalldd wrote:
I will stay at v7.0.23 for the next time (months or years, we will see).

I gave 7.0.2x a try, but it was rather buggy, having decided that my host was always in use and thus suspended all WUs. I'll wait until the release.

Thanks.

xmal
PM Profile
BAM!-ID: 1216
Joined: 2006-05-31
Posts: 9
Credits: 44,487,038
World-rank: 10,176
Posted 2012-04-14 20:02:22
rroonnaalldd wrote:
I will stay at v7.0.23 for the next time (months or years, we will see).
After the first "signing key message", i did the following. Detach from BAM, delete all acct_mgr-files manually and re-attach to BAM.
Since then no further "signing key messages" in the v7-log.


Thank you very much! It seems to work again, even if it seems to be not very "stable" because later, I had and error with signing. Same solution and again it's ok.

Thank you!
rroonnaalldd
PM
BAM!-ID: 15220
Joined: 2006-12-20
Posts: 207
Credits: 77,143,689
World-rank: 6,618
Posted 2012-04-14 20:57:50
Augustine wrote:
rroonnaalldd wrote:
I will stay at v7.0.23 for the next time (months or years, we will see).

I gave 7.0.2x a try, but it was rather buggy, having decided that my host was always in use and thus suspended all WUs. I'll wait until the release.

Thanks.

I had no problems on my dedicated cruncher with 7.0.23.
YoYo, the challenge at DistrRTgen and PG work without problems.
Perhaps we should talk about this in another thread...

ebahapo
PM Profile
BAM!-ID: 239
Joined: 2006-05-12
Posts: 647
Credits: 15,489,899
World-rank: 23,884
Posted 2012-04-15 20:30:39 , last modified: 2012-04-15 20:31:13
rroonnaalldd wrote:
I had no problems on my dedicated cruncher with 7.0.23.
YoYo, the challenge at DistrRTgen and PG work without problems.
Perhaps we should talk about this in another thread...

I configured a venue of hosts to suspend in case the user interacts with the computer. This has worked fine since BOINC 3.x, but 7.x thinks that my hosts are always in use, so I have to for to always run WUs, defeating my own preferences. I reported this issue here.

Pages: [1]

Index :: BAM! Bug Report :: Inconsistent signing key from account manager - one more times
Reason: