Hi.
A slight variation noticed. I can do a project update. and the pop-up will happen -> sometimes <-.

What is weird about the 'hang' is that it only lasts for about 30 seconds - and then all is fine. And, it seems to happen randomly. It happens whether or nor
files are being uploaded.

I have 11.6 GiB of memory - so I do not think this is the problem...
I'm running 7 of 8 kernels - so there should be processing power left over.

I have seen this on fresh installs of both Ubuntu Mate and Ubuntu (Gnome).

I have done BOINC installs from the BOINC PPA. My version installed are:


sudo add-apt-repository ppa:costamagnagianfranco/locutusofborg-ppa
sudo aptitude update

and start with fglrx-updates as a base...
sudo aptitude install fglrx-updates=2:15.200-0ubuntu0.3

sudo aptitude install boinc=7.6.2+dfsg-0~1343~ubuntu14.04.1
sudo aptitude install boinc-client-fglrx=7.6.2+dfsg-0~1343~ubuntu14.04.1
sudo aptitude install boinc-client-opencl=7.6.2+dfsg-0~1343~ubuntu14.04.1
sudo aptitude install boinc-dev=7.6.2+dfsg-0~1343~ubuntu14.04.1
sudo aptitude install libboinc-app-dev=7.6.2+dfsg-0~1343~ubuntu14.04.1
sudo aptitude install libboinc-app7=7.6.2+dfsg-0~1343~ubuntu14.04.1

( had a GPU not found problem - so I did this to find the libOpenCL.so )

I haven't seen this before...

Question: Can I ignore this - or is it a problem?

Thanks in advance,
Jay

An update..
To rule out other possibilities:
Memory diagnostics - passes 2 loops through all tests
Disc check with the SMART tool - disk passes test
I/O general congestion - started a clamav scan of the partition,
obsered clamav an WU writing activity - but no hangs on switching tabs
and other activity.
Tried % cpu utilization of less than 100% - hang still occurs.
Nothing suspicious seen in /var/logs

Other historical stuff...
I have 2 disks, a SSD and a Spinning disk.
To avoid BOINC eventually wearing out the SSD, I put
/ and swap on the SSD
/var /home and another swap on the spinning disk.
I have not had the hang with this this configuration before.

Want some log tracing? which?

Stumped,
Jay

A slight variation noticed. I can do a project update. and the pop-up will happen -> sometimes <-.

What is weird about the 'hang' is that it only lasts for about 30 seconds - and then all is fine.

That 30 seconds might be the time host address lookup takes to time out. During the lookup BOINC client doesn't do GUI RPCs or other things.

Question: Can I ignore this - or is it a problem?

The RPC calls BOINC uses occasionally hang. Signals are not perfect. You can ignore it. http://poincare.matf.bg.ac.rs/~ivana/courses/tos/sistemi_knjige/pomocno/apue/APUE/0201433079/ch10lev1sec4.html

---

Ah-hah...

Thanks for the info.

Jay.

An update..

Found the problem.
I had used vacuum to get out dust.
Had knocked power cable partially loose.
Re-seated cables and now all works OK.

Jay

I have 11.6 GiB of memory - so I do not think this is the problem.

Depends on the speed of the memory and the time it takes to load a huge file in. I just noticed a long "communicating with client" box on my BOINC Manager due to an Einstein Gamma-ray pulsar search loading into memory. It's 410MB big.

---

Just installed BOINC 7.6.11 on Mac OS X 10.10.5 and I am receiving the pop-up "Communicating with BOINC client. Please wait ..." with a Quit BOINC Manager button and a Cancel button. It hangs there for at least an hour before I gave up on it. When I click the Cancel button, the pop-up goes away for a few seconds then reappears. When I click on the Quit BOINC Manager it does in fact quits.

This problem occurs on a Standard account. This problem does NOT occur on an Admin account only if the system has just been re-booted and Admin account is the 1st to log in. BOINC 7.6.11 was installed in an Admin account.

What are the causes for this pop-up? How do I get around this issue?

--
Craig

What are the causes for this pop-up? How do I get around this issue?

Your account doesn't have permission to operate BOINC Manager.
See http://boinc.berkeley.edu/wiki/Tools_for_Mac_OS_X#Selecting_which_users_may_run_BOINC_Manager on how to fix that.

---