Rosetta@home website unreachable fot at least 3.5 hours now.

It is almost as if Dr Millea doesn't care about the people who are crunching his data for him, so long as we continue to crunch it.

There are of course other possible explanations that projects heavily dependent on one person can suffer from such as illness. or worse. Just as many people do not prepare their personal lives for their death/illness, many especially if they do not expect problems do not prepare their professional lives for such events.

Cosmology@home is down for at least 2 weeks now. Can't access website to find what is wrong.
Any1 knows anything?

Scientists in China have succeeded in teleporting information between photons further than ever before. They transported quantum information over a free space distance of 16 km (10 miles), much further than the few hundred meters previously achieved, which brings us closer to transmitting information over long distances without the need for a traditional signal.

You can thank the distro devs for that. Boinc runs as a service and can't be killed by the user. With your version the only way to stop the client is to invoke superuser.

sudo systemctl stop boinc-client

I run an older client that still has the ability to stop the client and all processes through the Manager interface.

To restart the client if you aren't going to reboot use this.

sudo systemctl start boinc-client

If he's using systemd, the old logs will be in the system journal, not a text file.

I installed BOINC from the ubuntu repos.

When i want to start form the menu i get an error window:

"Impossible d'exécuter boinc manager
le changement de répertoire /var/lib/boinc-client a échoué (permission non accodrée)"

That suggest a permissions problem.

Ok, i managed to changes the permission of the folder. Now i get a boinc manager window that tells me:

"Boinc manager (pre release) ne peut pas démarrer un client BOINC. Merci d'exécuter le client et de réessayer."

Ok, i searched the net and found a workaround: i type in a terminal:

sudo systemctl start boinc-client

Before relaunching the boinc manager. And it finally works; With the GPU enabled. I leave this here in case someone would be in trouble like i was. But what a shoddy work by canonical !

It's all good now.
https://asteroidsathome.net/boinc/

Took 6 hours for all my completed tasks to finally upload. I had a huge queue when the cert expired.
Problem was exacerbated by the WGC tasks that cannot upload yet. BOINC tried and failed each upload of WCG before going on to Asteroids.
I should have requested a restart of the transfers for just Asteroids.

I suspect all my WCG have passed their deadline.

I've found a new (?) page, which may assist readers and save them wading through this whole thread.

Accessing BOINC on Linux

The final suggestion on that page is

exec su $USER

That only works if you want to launch BOINC Manager from the command line in terminal. If you want to use a graphical launch icon on your desktop, or a menu item created by your distribution, you'll need to reboot the machine.

The Linux tools for ensuring that the Manager can read - and thus supply - the requisite password from gui_rpc_auth.cfg are woefully inadequate.

No, the Manager should not need, and not be able, to read that file at all. The user has to provide the password to prove they're authorised to control the Client. To make that work the password has to be secret, enforcing a password and then allowing everybody to look it up is just absurd. You could add authorised users to the boinc group as you suggested and then allow only those to read the password file. In fact that's what I do, but I'm sure that's still not how it was intended to work. The Manager has the ability to read the password from a file but I don't think that was meant to read the Client's password file but one provided by the user. Correct me if I'm wrong. For me the whole concept of someone else reading the Client's private file is only added by the Linux packagers and it's another case where the convenience vs security decision goes in the wrong direction.

I'm running a large server with 192 cores. Consequently, /var/log/messages gets cluttered with messages of started and finished tasks.

Is there a setting somewhere which would use a different file for this output, or suppress it altogether?

I tried opening the website in an incognito window. It opened i-n-c-r-e-d-i-b-l-y slowly, especially the photographs - but it looked as if it was all there.

Then, I clicked for the latest news. And the latest news is ...

{"errors":[{"error":"An unexpected error occurred: Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.GenericJDBCException: Unable to acquire JDBC Connection"}]}

But I still haven't got a clue why other people are having so much trouble. The keys seem to be:

• Learn the systemctl commands for systemd (stop, start, enable, disable)
  
• Add your user account to the boinc group
  
• reboot
  

Learn the systemctl commands
Add your user account to group boinc, and if using VirtualBox add user boinc to group vbox-users
Log out/log in to complete your user's addition to group boinc (in openSUSE at least, this does not appear to be necessary if you use YaST's user manager to do this task -- try it with your distro's equivalent to see if it works for you)
Instead of rebooting, simply enable boinc-client service: sudo systemctl enable boinc-client
And now start boinc-client: sudo systemctl start boinc-client

I've installed BOINC, but I get an error message when starting the BOINC manager:
BOINC Manager (Pre-release) - Daemon Start Failed
BOINC Manager (Pre-release) is not able to start a BOINC client. Please run the client and try again.

How does one run the client?

BOINC Version: 7.18.1 (x64)
wxWidgets Version: 3.0.5