» Search forum


Index :: BAM! Bug Report :: My hosts sync with BAM! constantly


Pages: [1]
Tuna Ertemalp
 
Tester
BAM!ID: 37744
Joined: 2007-10-31
Posts: 535
Credits: 20,799,048,922
World-rank: 239

2017-10-01 21:05:17

Since the beginning of time, I have had my BAM settings set so that hosts connect every 1 hour. But I just noticed, by mistake, while looking at a live EventLog window, that 4 of my 11 hosts are constantly connecting to BAM! Like connect, done, connect, done, ...

I have no clue as to why. And how long this has been happening. They all run the latest BOINCMgr 7.8.2. Not much else has changed that I can think of.

The hosts are:

https://boincstats.com/en/bam/host/568156
https://boincstats.com/en/bam/host/568142
https://boincstats.com/en/bam/host/696757
https://boincstats.com/en/bam/host/634443

What can I do to stop these 4 hosts from spamming the BAM server?

Tuna

[BOINCstats] Willy
 
Forum moderator - Administrator - Developer - Tester - Translator
BAM!ID: 1
Joined: 2006-01-09
Posts: 9442
Credits: 353,172,950
World-rank: 4,870

2017-10-02 09:04:54
last modified: 2017-10-02 09:17:03

It's a BOINC manager bug introduced in one of the latest versions. You can check the value for repeat_sec in the acct_mgr_reply xml file. This is the amount of time BAM! tells the host to wait before a reconnect.

Tuna Ertemalp wrote:
What can I do to stop these 4 hosts from spamming the BAM server?

At the moment the only fix is a downgrade of the client software.

I reported the bug to the BOINC developers.
Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.
Tuna Ertemalp
 
Tester
BAM!ID: 37744
Joined: 2007-10-31
Posts: 535
Credits: 20,799,048,922
World-rank: 239

2017-10-02 16:29:56
last modified: 2017-10-02 16:30:24

Ouch.

Is there a link to your bug report so I can follow any discussion about it?

Tuna
Tuna Ertemalp
 
Tester
BAM!ID: 37744
Joined: 2007-10-31
Posts: 535
Credits: 20,799,048,922
World-rank: 239

2017-10-02 20:01:10

Also confirmed that repeat_sec=3600 on these machines. And, there is nothing common and remarkable between these 4 hosts compared to the other 7 hosts where this doesn't happen. Would love to see if there are any details about what the mechanics of the bug is. I am tempted to set the time to something other than 60mins on BAM!, but then also afraid if that change would kick the remaining 7 hosts into the bad state, making things worse for you...

Is this actually creating undue load on your server that it cannot handle?

Tuna
[BOINCstats] Willy
 
Forum moderator - Administrator - Developer - Tester - Translator
BAM!ID: 1
Joined: 2006-01-09
Posts: 9442
Credits: 353,172,950
World-rank: 4,870

2017-10-03 12:34:16

Tuna Ertemalp wrote:
Is there a link to your bug report so I can follow any discussion about it?

https://lists.ssl.berkeley.edu/pipermail/boinc_dev/2017-October/022992.html
Please do not PM, IM or email me for support (they will go unread/ignored). Use the forum for support.
Tuna Ertemalp
 
Tester
BAM!ID: 37744
Joined: 2007-10-31
Posts: 535
Credits: 20,799,048,922
World-rank: 239

2017-10-03 21:50:28

Ah! Thanks! With a little reading there and here, I found out how to fix it WITHOUT rolling back to a previous version of the BOINCMgr.

The insight is buried in the The Projects :: Einstein@Home - Updated URL - https://einsteinathome.org/ thread where there is this gem:

Jacob Klein wrote:

That's a good question.

I believe BOINC 7.8.2 has a bug where delayed detach doesn't work, and BOINC gets stuck in a loop, attempting it every 10 seconds and contacting BAM! every 10 seconds. David Anderson, who is owner of the BOINC code, has reproduced the problem and is working on a fix.

For now, a workaround is to:
- Use Tools > Stop using BOINCstats BAM!...
- Remove the project that was stuck in the delayed-detach-loop.
- Use Tools > Use account manager, to setup BAM! again.

In the end, this "mess" helped bring to light 2 issues that the BOINC community needs to solve:
1) The delayed-detach-loop (a real immediate problem)
2) URL redirection when being added by an account manager (a nuisance that prevents the account manager from using redirect URLs)

Jacob


In all my four hosts showing this issue, some project (Einstein & Citizen Science Grid) was stuck in the Won't get new tasks, Will remove when tasks done state, even though there were no tasks left. So, disconnecting from BAM! made the problem project to get deleted automatically (without even needing me to remove it), and reconnecting to BAM! made everything to go back to normal as far as the sync frequency, and also added the problem project back in, if need be.

Tuna
Yavanius
BAM!ID: 180363
Joined: 2015-01-26
Posts: 297
Credits: 27,725,263
World-rank: 27,394

2017-10-04 05:04:58

On the Alpha list there is discussion of releasing a new version with the fix soon. There's been some talk about waiting and incorporating some other bug fixes. I suggested they release a hotfix because this is impacting the projects who are having to field these reports (which is no issue of theirs).

That was a few days ago... maybe chime in your thoughts too? Squeaky wheel et al.
Yavanius
BAM!ID: 180363
Joined: 2015-01-26
Posts: 297
Credits: 27,725,263
World-rank: 27,394

2017-10-04 05:08:17

Tuna Ertemalp wrote:

For now, a workaround is to:
- Use Tools > Stop using BOINCstats BAM!...
- Remove the project that was stuck in the delayed-detach-loop.
- Use Tools > Use account manager, to setup BAM! again.



Actually, as Willy noted, you just have to go back to the previous 7.6.33 version and all works fine again including removing the project if you want to. That's what I did on Windows. Not sure if this is an issue on Linux too...
Tuna Ertemalp
 
Tester
BAM!ID: 37744
Joined: 2007-10-31
Posts: 535
Credits: 20,799,048,922
World-rank: 239

2017-10-04 15:34:09

Yavanius wrote:

you just have to go back to the previous 7.6.33 version


But I didn't want to downgrade my machines. So, I am glad there was a simple way to alleviate the problem without doing something as drastic as uninstalling the newest version and then reinstalling the old, just to install the next new version when it came out.

Tuna
Tuna Ertemalp
 
Tester
BAM!ID: 37744
Joined: 2007-10-31
Posts: 535
Credits: 20,799,048,922
World-rank: 239

2017-10-04 15:36:29

Yavanius wrote:

maybe chime in your thoughts too? Squeaky wheel et al.


I don't know where the alpha list is. If you could be kind enough to post a link, I will see what I can do. But I am pretty sure David Anderson will be looking at creating a quick 7.8.3 before a lengthy 7.10, given that there are even more pressing serious bugs in 7.8.2 with no easy/available workarounds.

Tuna
Tuna Ertemalp
 
Tester
BAM!ID: 37744
Joined: 2007-10-31
Posts: 535
Credits: 20,799,048,922
World-rank: 239

2017-10-04 16:38:00
last modified: 2017-10-04 16:45:50

Tuna Ertemalp wrote:

But I am pretty sure David Anderson will be looking at creating a quick 7.8.3 before a lengthy 7.10, given that there are even more pressing serious bugs in 7.8.2 with no easy/available workarounds.


And, right on cue: Version 7.8.3 Released for Alpha testing, today, including this fix... (http://boinc.berkeley.edu/download_all.php)


BOINC version history
Version 7.8.3

released: 4 October 2017


  • client: extensions, fixes to account manager functionality
  • client: eliminate possible buffer overflow in reporting result errors
  • lib: fix boinc_file_exists() on Windows
  • Mac: Changes to Xcode project to support screensaver changes for Mac OS 10.13.
  • Screensaver: Changes for screensaver to support Mac OS 10.13
  • api: BOINC graphics library changes to support Mac OS 10.13
  • client library: inconsistent terminology for intel_gpu
  • update project list
  • Locale: Update french localization files
  • update installshield files

Yavanius
BAM!ID: 180363
Joined: 2015-01-26
Posts: 297
Credits: 27,725,263
World-rank: 27,394

2017-10-05 02:49:07
last modified: 2017-10-05 02:52:49

Tuna Ertemalp wrote:

Yavanius wrote:

you just have to go back to the previous 7.6.33 version


But I didn't want to downgrade my machines. So, I am glad there was a simple way to alleviate the problem without doing something as drastic as uninstalling the newest version and then reinstalling the old, just to install the next new version when it came out.

Tuna



Actually, on my system, I did try detaching from BAM too with no luck. But, it seems we got a new version out...although being a development version nobody knows about it unless they read about it or follow along development.
Pages: [1]

Index :: BAM! Bug Report :: My hosts sync with BAM! constantly
Reason: