» Search forum


Index :: BAM! Bug Report :: Activating BAM! on my host does not recognize my existing BAM!-Account


Pages: [1]
TeeVeeEss
  Donator
Tester - Translator - BOINCstats SOFA member
BAM!ID: 2648
Joined: 2006-06-27
Posts: 814
Credits: 12,643,033,529
World-rank: 344

2025-06-28 14:51:54

When executing this commands on a new host (Linux with BOINC 8.3.0):
Code:
boinccmd --acct_mgr attach bam.boincstats.com [emailaddress] [weak authenticator]
boinccmd --acct_mgr sync
The reponse is:
28-6-2025 16:23:23 |  | Account manager: BAM! User: 158923,

28-6-2025 16:23:23 |  | Account manager: BAM! Host: 1384200
This is odd, looks like a new BAM!-user is created. The host is also not shown in my list of hosts.

On another BAM!-connected host (Windows with BOINC version 8.2.1) the correct response for the sync with BAM! is:
28 jun 2025 16:33:42	Account manager: BAM! Host: 1372810

28 jun 2025 16:33:42	Account manager: BAM! User: 2648, TeeVeeEss
Switching the Linux host to the latest stable version BOINC 7.24.1 did not change the response from BAM!

Not sure if and how I can fix this on the client side. Any thoughts?
gemini8
Forum moderator - Tester - Volunteer tester
BAM!ID: 101557
Joined: 2011-06-14
Posts: 127
Credits: 5,583,810,181
World-rank: 646

2025-06-30 11:33:47

The command should be:
Code:
boinccmd --acct_mgr attach bam.boincstats.com [username] [passwd]
or
Code:
boinccmd --acct_mgr attach bam.boincstats.com [weak authenticator]

Please try again.
I'm not absolutely certain if the WAK has to be used once or twice in the second example.
- - - - - - - - - - -
Greetings, Jens
TeeVeeEss
  Donator
Tester - Translator - BOINCstats SOFA member
BAM!ID: 2648
Joined: 2006-06-27
Posts: 814
Credits: 12,643,033,529
World-rank: 344

2025-06-30 19:51:38

Very strange. After:
Code:
boinccmd --acct_mgr detach
boinccmd --acctmgr [username] [password]
the respons is now correct:
Account manager: BAM! User: 2648, TeeVeeEss

Account manager: BAM! Host: 1385220

Account manager: Number of BAM! connections for this host: 3
Case solved, cause unknown
Pages: [1]

Index :: BAM! Bug Report :: Activating BAM! on my host does not recognize my existing BAM!-Account
Reason: