After upgrading Ubuntu from 20.10 to 21.04, I keep getting these messages from /usr/bin/boinc about once per second, totally spamming journalctl. They come even when no computing is scheduled.
The BOINC event log itself does not contain anything that looks like an error.
Does anyone have a clue regarding what has happened or which flags I should enable for further debugging?

I am waiting till the work I have downloaded is finished before doing the upgrade. I will see if I get the same then. (That will be about a week or just over till last task finishes.

Just upgraded to 21.04 Decided to risk running tasks. (Lost one out of 8) but all seems to work just as it did before. I am running a self compiled version of BOINC 7.17.0

I have no idea if that makes any difference or not.

In fact nothing in journalctl from BOINC since August last year. Nice how much more quickly the upgrade runs with an nvme ssd disk as well.

After upgrading Ubuntu from 20.10 to 21.04, I keep getting these messages from /usr/bin/boinc about once per second, totally spamming journalctl. They come even when no computing is scheduled.
The BOINC event log itself does not contain anything that looks like an error.
Does anyone have a clue regarding what has happened or which flags I should enable for further debugging?

Would be helpful if you actually post one of the messages in the journal log you are complaining about. No clue otherwise.

Hello,
Since Ubuntu 21.04 upgrade, I've got same messages in /var/log/syslog:

Apr 28 10:16:02 Computer boinc[1820]: Authorization required, but no authorization protocol specified
Apr 28 10:16:02 Computer boinc[1820]: Authorization required, but no authorization protocol specified

Hello,
Since Ubuntu 21.04 upgrade, I've got same messages in /var/log/syslog:

Apr 28 10:16:02 Computer boinc[1820]: Authorization required, but no authorization protocol specified
Apr 28 10:16:02 Computer boinc[1820]: Authorization required, but no authorization protocol specified

On my XUbuntu box, nothing untoward at all in /var/log/syslog Probably going to need a bit more detail about your setup to track this one down. I know I have had problems before with the manager though very different problems after a version upgrade but this one has gone perfectly. Apart from the messages, is boinc running? If it is, is the message to do with communication between the manager and the client? It may be worth starting the client and manager from a terminal and seeing what messages appear there if any.

If I start the client by "systemctl start boinc-client" I get the messages in the journal:

maj 06 23:26:54 Bullen boinc[11266]: Authorization required, but no authorization protocol specified

It was suggested that I start the client manually in order to see the output.
Instead I filtered on the PID and got the following messages from the client startup:

tony@Bullen:/var/lib/boinc-client$ tail -90000 /var/log/syslog | grep 13943 | head -50

May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Starting BOINC client version 7.16.16 for x86_64-pc-linux-gnu
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] log flags: file_xfer, sched_ops, task, gui_rpc_debug
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Libraries: libcurl/7.74.0 OpenSSL/1.1.1j zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh/0.9.5/openssl/zlib nghttp2/1.43.0 librtmp/2.3
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Data directory: /var/lib/boinc-client
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] No usable GPUs found
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] libc: Ubuntu GLIBC 2.33-0ubuntu5 version 2.33
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Host name: Bullen
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Processor: 24 AuthenticAMD AMD Ryzen 9 3900X 12-Core Processor [Family 23 Model 113 Stepping 0]
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb cat_l3 cdp_l3 hw_pstate sme ssbd mba sev ibpb stibp vmmcall sev_es fsgsbase bmi1 avx2 smep bmi2 cqm rdt_a rdseed adx smap clflushopt clwb sha_ni xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local clzero irperf xsaveerptr rdpru wbnoinvd arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif umip rdpid overflow_recov succor smca
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] OS: Linux Ubuntu: Ubuntu 21.04 [5.11.0-16-generic|libc 2.33 (Ubuntu GLIBC 2.33-0ubuntu5)]
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Memory: 31.36 GB physical, 2.00 GB virtual
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Disk: 456.96 GB total, 230.06 GB free
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Local time is UTC +2 hours
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] VirtualBox version: 6.1.18_Ubuntur142142
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Config: GUI RPCs allowed from:
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] General prefs: from http://setiathome.berkeley.edu/ (last modified 18-Mar-2013 23:05:31)
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Computer location: home
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] General prefs: no separate prefs for home; using your defaults
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Reading preferences override file
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Preferences:
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---]    max memory usage when active: 16058.30 MB
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---]    max memory usage when idle: 30510.77 MB
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---]    max disk usage: 231.21 GB
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---]    don't use GPU while active
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---]    (to change preferences, visit a project web site or select Preferences in the Manager)
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Setting up project and slot directories
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Checking active tasks
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [Asteroids@home] URL http://asteroidsathome.net/boinc/; Computer ID 661334; resource share 100
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [Einstein@Home] URL http://einstein.phys.uwm.edu/; Computer ID 12813799; resource share 100
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [Milkyway@Home] URL http://milkyway.cs.rpi.edu/milkyway/; Computer ID 834319; resource share 100
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Setting up GUI RPC socket
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] [gui_rpc] found allowed hosts list
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] [gui_rpc] Local control only allowed
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] [gui_rpc] Listening on port 31416
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 [---] Checking presence of 463 project files
May  7 00:10:46 Bullen boinc[13943]: 07-May-2021 00:10:46 Initialization completed
May  7 00:10:46 Bullen boinc[13943]: Authorization required, but no authorization protocol specified
May  7 00:10:46 Bullen boinc[13943]: Authorization required, but no authorization protocol specified
May  7 00:10:53 Bullen boinc[13943]: Authorization required, but no authorization protocol specified

Anyway, the message is clearly related to the X server, and since Ubuntu 21.04 runs Wayland, that's probably the reason something got broken. BOINC is using "GUI RPC sockets", and if I enable debuging to the BOINC event log by ticking the option for "gui_rpc_debug" I get more logging. What's an "ams_password_error"?

Is it possible that BOINC is relying "too much" on X, and are using some deeper X functionality that Wayland in it's current state on Ubuntu 21.04 can't handle?

maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: <get_cc_status/>
maj 07 00:21:45 Bullen boinc[13943]: </boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: [2B blob data]
maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
maj 07 00:21:45 Bullen boinc[13943]: <cc_status>
maj 07 00:21:45 Bullen boinc[13943]:    <network_status>2</network_status>
maj 07 00:21:45 Bullen boinc[13943]:    <ams_password_error>0</ams_password_error>
maj 07 00:21:45 Bullen boinc[13943]:    <task_s'
maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: <get_messages>
maj 07 00:21:45 Bullen boinc[13943]:   <seqno>3606</seqno>
maj 07 00:21:45 Bullen boinc[13943]:   <translatable/>
maj 07 00:21:45 Bullen boinc[13943]: </get_messages>
maj 07 00:21:45 Bullen boinc[13943]: </boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: [2B blob data]
maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
maj 07 00:21:45 Bullen boinc[13943]: <msgs>
maj 07 00:21:45 Bullen boinc[13943]: <msg>
maj 07 00:21:45 Bullen boinc[13943]:  <project></project>
maj 07 00:21:45 Bullen boinc[13943]:  <pri>1</pri>
maj 07 00:21:45 Bullen boinc[13943]:  <seqno>3607</seqno>
maj 07 00:21:45 Bullen boinc[13943]:  <body><![CDATA[
maj 07 00:21:45 Bullen boinc[13943]: [gui_rpc] GUI RPC re'
maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: <get_notices>
maj 07 00:21:45 Bullen boinc[13943]:    <seqno>0</seqno>
maj 07 00:21:45 Bullen boinc[13943]: </get_notices>
maj 07 00:21:45 Bullen boinc[13943]: </boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: [2B blob data]
maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
maj 07 00:21:45 Bullen boinc[13943]: <notices>
maj 07 00:21:45 Bullen boinc[13943]: </notices>
maj 07 00:21:45 Bullen boinc[13943]: </boinc_gui_rpc_reply>
maj 07 00:21:45 Bullen boinc[13943]: '
maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC Command = '<boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: <get_results>
maj 07 00:21:45 Bullen boinc[13943]: <active_only>1</active_only>
maj 07 00:21:45 Bullen boinc[13943]: </get_results>
maj 07 00:21:45 Bullen boinc[13943]: </boinc_gui_rpc_request>
maj 07 00:21:45 Bullen boinc[13943]: [2B blob data]
maj 07 00:21:45 Bullen boinc[13943]: 07-May-2021 00:21:45 [---] [gui_rpc] GUI RPC reply: '<boinc_gui_rpc_reply>
maj 07 00:21:45 Bullen boinc[13943]: <results>
maj 07 00:21:45 Bullen boinc[13943]: <result>
maj 07 00:21:45 Bullen boinc[13943]:     <name>h1_0981.85_O2C02Cl5In0__O2MD1S3_Spotlight_982.70Hz_1341_0</name>
maj 07 00:21:45 Bullen boinc[13943]:     <wu_name'
maj 07 00:21:45 Bullen boinc[13943]: Authorization required, but no authorization protocol specified
maj 07 00:21:45 Bullen boinc[13943]: Authorization required, but no authorization protocol specified

X.org is ancient. BOINC is ancient. They get along really well. Trying to get BOINC to cooperate with a new WDM is going to be troublesome.

I've been hearing about XWayland as a solution for older programs dependent on the X.server to run under Wayland. Have you tried that?

I wonder if the <ams_password_error> might have ams standing for an account manager?

I have yet to try Wayland. XUbuntu seems to let BOINC work without any problems at least on my machine that I updated from what was a clean install of 20.10 to 21.04

Yes. X is doomed. Wayland has been around for quite some time in phones and embedded systems. Now it's mainstream.
If BOINC doesn't work with Wayland, then BOINC has a problem.
But here is also the possibility that the Ubuntu upgrade process is at fault. It would be interesting to know if BOINC works better on a fresh Ubuntu 21.04 with Wayland installation.

I found a post elsewhere where this message appeared when someone was starting an X program as root. The answer was:

"The slightly more detailed answer is those programs require X windows features but there's no configuration available in the root account for that to happen."

Clearly boinc is not running as root, but there maybe the boinc user has the same problem.
Another post mentioned:

When you start XLaunch you may want to choose to Disable access control. Otherwise you may get errors like this:
$ xeyes
Authorization required, but no authorization protocol specified

I'm not sure what all this means, but it looks like the boinc user needs some kind of configuration that is now missing.