So I'm using 6.10.58 64-bit in Linux on my Ubuntu 18.04.2 LTS machine and started having a problem a week ago, on Sunday the 15th. The last successful contact was 6:48am local time.

It took me two days to figure out that the problem was something to do with an SSL failure:


Someone pointed me to some others who were having problems with SSL as well earlier in the 'Panic Mode' thread and basically, a minimum of 0.9.8o is needed, and I have 0.9.8g that is statically-linked into BOINC.

On my Windows machine, I dropped the .dll's for 1.0.2t into place and it took those just fine:

2019-09-19 17:12:47		Starting BOINC client version 6.10.58 for windows_x86_64
2019-09-19 17:12:47		Libraries: libcurl/7.19.7 OpenSSL/1.0.2t zlib/1.2.3
2019-09-19 17:12:47		Data directory: C:\ProgramData\BOINC

2019-09-19 17:13:47	SETI@home	[sched_op_debug] Starting scheduler request
2019-09-19 17:13:47	SETI@home	Sending scheduler request: Requested by user.
2019-09-19 17:13:47	SETI@home	Requesting new tasks
2019-09-19 17:13:49	SETI@home	Scheduler request completed: got 0 new tasks
2019-09-19 17:13:49	SETI@home	[sched_op_debug] Server version 709
2019-09-19 17:13:49	SETI@home	Message from server: No tasks sent
2019-09-19 17:13:49	SETI@home	Project requested delay of 303 seconds

So it worked in Windows. I've been trying to get the same thing to be able to happen in Linux, but that's when it became apparent that the libraries BOINC needs in Linux are static-linked instead of dynamic.

The specific problem is this, during a scheduler contact:

2019-09-20 22:47:27		Starting BOINC client version 6.10.58 for x86_64-pc-linux-gnu
2019-09-20 22:47:27		Libraries: libcurl/7.18.0 OpenSSL/0.9.8g zlib/1.2.11 c-ares/1.5.1
2019-09-20 22:47:27		Data directory: /var/lib/boinc-client

2019-09-23 04:16:33		[http_debug] [ID#1] Info:  Connected to setiathome.berkeley.edu (208.68.240.110) port 443 (#0)
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  successfully set certificate verify locations:
2019-09-23 04:16:33		[http_debug] [ID#1] Info:    CAfile: ca-bundle.crt
2019-09-23 04:16:33		[http_debug] [ID#1] Info:    CApath: none
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  SSLv2, Client hello (1):
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  SSLv3, TLS handshake, Server hello (2):
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  SSLv3, TLS handshake, CERT (11):
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  SSLv3, TLS alert, Server hello (2):
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  error:0D0C50A1:asn1 encoding routines:ASN1_item_verify:unknown message digest algorithm
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  Expire cleared
2019-09-23 04:16:33		[http_debug] [ID#1] Info:  Connection #0 to host setiathome.berkeley.edu left intact
2019-09-23 04:16:33		[http_debug] HTTP error: SSL connect error
2019-09-23 04:16:34		Project communication failed: attempting access to reference site
2019-09-23 04:16:34	SETI@home	[sched_op_debug] Deferring communication for 1 days 0 hr 0 min 0 sec
2019-09-23 04:16:34	SETI@home	[sched_op_debug] Reason: 30 consecutive failures fetching scheduler list

There was a suggestion that maybe the ca-bundle.crt was bad, so I went to https://github.com/BOINC/boinc/blob/master/curl/ca-bundle.crt and copy&pasted as a text file of the same name, that didn't resolve it. Also tried the latest from http://curl.haxx.se/ and that didn't do it either.

That's when someone recognized the specific error in the log above and said that a minimum of 0.9.8o is required now.

On that system..

root@taurus:~# openssl version
OpenSSL 1.1.1  11 Sep 2018
root@taurus:~#

So the system has a modern openssl library on it, but BOINC refuses to use it because it is using the static-linked one. So that led me to asking if anyone had the source for the old 6.10.x branch to just.....recompile it on a modern system with modern libraries.

I was told about https://github.com/BOINC/boinc/tree/client_release/6/6.10, so I gave it a try. There were a few dependencies to resolve during '_autoconfig' and 'configure', but I finally got all the dependency issues resolved on those and went on to 'make', which lasted about 3 whole seconds before this error for a missing OSX (which I'm not using...so obviously it will be missing) localization file:

In file included from gui_rpc_client.cpp:50:0:
gui_rpc_client.h:762:10:fatal error: xlocale.h: No such file or directory
#include <xlocale.h>
         ^~~~~~~~~~~
compilation terminated.

I say it was for OSX because during '_autoconfig', it spewed out HUNDREDS of warnings about OSX things being missing or undefined, so I figure that's probably why it failed.

I'm not well-versed in compiling complex things in linux, I'll be honest. I know enough to do "config, make, make install" and resolve dependency issues that arise during 'config', such as when it needs some library, what i need to install is the -dev[el] package for it. I know that much, but I don't know what/if I need to be feeding a whole bunch of switches and options into the commands to build for a specific environment or what, since it complained a lot about missing OSX things.

Keith was nice enough to give compiling a try for me, but ran into too many issues and had to abandon.

So I guess my question is.. could/would somebody familiar with compiling in Linux be willing to take a stab at it? Maybe in an older version of Ubuntu, like say.. something from the 12.04 or 14.04 epoch? With a fully-current openssl-dev library?

I'd rather not move up beyond 6.10.x, as the connection problem isn't a BOINC issue, it's an SSL issue. But because the SSL library is static-linked, recompiling is the only way to update it. Maybe there's a flag that doesn't static-link and relies on shared libraries found in $PATH ?

Or is there some switch or flag I can put in cc_config.xml or something that will disable SSL?

Any insight on this would be greatly appreciated.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

I say it was for OSX because during '_autoconfig', it spewed out HUNDREDS of warnings about OSX things being missing or undefined, so I figure that's probably why it failed.

You wouldn't have seen that if you were just compiling the client I think. The OSX errors are for the Manager. What did you use for the configure? I would just compile the 6.10.58 client and skip the Manager.

./configure --disable-server --disable-manager

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Try this one. It works in My 18.04 with Libcurl3. The only problem I've found is when the Manager first launches you have to expand the top of the window a fraction of an inch to have the menu bar appear.
I couldn't get any 6.10.x versions to work with OpenSSL 1.1, they will all fail during compile with 'unexpected RSA functions'. So, you're stuck with Ubuntu 18.10 or lower which still uses OpenSSL 1.0.x.
http://www.arkayn.us/lunatics/BOINC-6.10.36.7z

BTW, what does your 6.10.58 version say for the version of wxWidgets being used?

You wouldn't have seen that if you were just compiling the client I think. The OSX errors are for the Manager. What did you use for the configure? I would just compile the 6.10.58 client and skip the Manager.

./configure --disable-server --disable-manager

Manager never did work for me on that machine, even when I used the current version that's in the package repo. I use Manager on the Windows machine to connect to it.

I didn't use any switches or options for _autoconfig or configure, so I'll give your suggestion a try and see how that goes.

I couldn't get any 6.10.x versions to work with OpenSSL 1.1, they will all fail during compile with 'unexpected RSA functions'. So, you're stuck with Ubuntu 18.10 or lower which still uses OpenSSL 1.0.x.

BTW, what does your 6.10.58 version say for the version of wxWidgets being used?

I have no idea what wxwidgets is.

And I'm on 18.04 with openssl 1.1.1 installed from the package repo.

But I guess I have the 1.0 libraries available...

root@taurus:~# ldconfig -pv | grep ssl
        libssl3.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl3.so
        libssl.so.1.1 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl.so.1.1
        libssl.so.1.0.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0
        libssl.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libssl.so
        libgsoapssl-2.8.60.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libgsoapssl-2.8.60.so
        libgsoapssl++-2.8.60.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libgsoapssl++-2.8.60.so
root@taurus:~#

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

And now I'm getting...

...
configure.ac:395: the top level
Done, now run ./configure
 ./configure -C                         to enable caching
root@taurus:~/boinc-client_release-6-6.10# ./configure --disable-server --disable-manager
checking for gcc... gcc
checking whether the Objective C++ compiler works... no
configure: error: in `/root/boinc-client_release-6-6.10':
configure: error: Objective C++ compiler cannot create executables
See `config.log' for more details
root@taurus:~/boinc-client_release-6-6.10#

It worked for me the other night, but now it doesn't want to play ball.

_autosetup complained that I didn't have 'AC_PROG_OBJCXX' nor 'OBJCXX' defined, and I did a quick google search and found that you can just put both of those into 'configure.ac' and it'll sort itself out.

That's what I did the other night, too, and it made it all the way through './configure' and even let me start doing 'make' before crashing-out.

But now it doesn't want to.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Go to the Manager, Help/About Boinc Manager
The wxWidgets version is there.
Yes everyone up to 18.10 has OpenSSL 1.0.x available.
You will Never get OpenSSL 1.1 to work with 6.10.xx in Ubuntu, but you can keep working at it if you wish.
I actually know what I'm doing. You won't get 6.10.60 to compile either, but 6.10.36 will compile in 12.04 and 14.04.

I have no idea what wxwidgets is.

Wxwidgets is the primitive graphics library that is used to build the elements of the Manager. It is only used or needed with the Manager. Don't need it to compile the client.

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

It looks as though the only one that will work is the one compiled in Ubuntu 12.04. The other ones seemed to work, but then started crashing. So, you'll need to compile in 12.04 with BOINC 6.10.36 & wxWidgets 2.8.12, and that one will need libcurl3 in Ubuntu 18.04. If I knew which wxWidgets 6.10.58 first used, I might be able to get it to work a little better.

http://www.arkayn.us/lunatics/BOINC-6.10.36.7z

It looks like the 6.10.xx series used wxWidgets version 2.6.0 from the wxWidgets.m4 file.
Minimum version is 2.3.4

---

Seti@Home classic workunits:20,676 CPU time:74,226 hours

A proud member of the OFA (Old Farts Association)

Well, 2.6.0 was one of the ones I had tried previously that doesn't compile. I've only found a couple below 2.8.12 that even compile by themselves. The 6.10.36 version calls for 2.6.0 or higher. I was able to compile 6.12.43 which calls for 2.8 or higher and it has the same partially hidden Menu bar on startup as 6.10.36. It must be something with wxWidgets 2.8.12, which is a shame because it's about the oldest version which actually works when compiled with BOINC. It seems BOINC 6.12.43 is also incompatible with openSSL 1.1, when the compiler starts on the SSL section it spews dozens of RSA errors and dies. SSL 1.0.x works fine. Oh well.

Thank you, TBar, for your knowledge and info on this subject. I grabbed the 7z for 6.10.36, but I guess I need to install a library for it to run.

root@taurus:/var/lib/boinc-client# ldd /usr/bin/boinc
/usr/bin/boinc: /usr/lib/x86_64-linux-gnu/libcurl.so.4: version `CURL_OPENSSL_3' not found (required by /usr/bin/boinc)
        linux-vdso.so.1 (0x00007ffd847c1000)
        libcurl.so.4 => /usr/lib/x86_64-linux-gnu/libcurl.so.4 (0x00007f365ae7e000)
        libssl.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libssl.so.1.0.0 (0x00007f365ac16000)
        libcrypto.so.1.0.0 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.0.0 (0x00007f365a7d3000)
        libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f365a5cf000)
        libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f365a3b2000)
        libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f365a193000)
        libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f3659e0a000)
        libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3659a6c000)
        libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f3659854000)
        libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3659463000)
        libnghttp2.so.14 => /usr/lib/x86_64-linux-gnu/libnghttp2.so.14 (0x00007f365923e000)
        libidn2.so.0 => /usr/lib/x86_64-linux-gnu/libidn2.so.0 (0x00007f3659021000)
        librtmp.so.1 => /usr/lib/x86_64-linux-gnu/librtmp.so.1 (0x00007f3658e05000)
        libpsl.so.5 => /usr/lib/x86_64-linux-gnu/libpsl.so.5 (0x00007f3658bf7000)
        libssl.so.1.1 => /usr/lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f365896a000)
        libcrypto.so.1.1 => /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f365849f000)
        libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f3658254000)
        libldap_r-2.4.so.2 => /usr/lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007f3658002000)
        liblber-2.4.so.2 => /usr/lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007f3657df4000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f365b0fd000)
        libunistring.so.2 => /usr/lib/x86_64-linux-gnu/libunistring.so.2 (0x00007f3657a76000)
        libgnutls.so.30 => /usr/lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007f3657711000)
        libhogweed.so.4 => /usr/lib/x86_64-linux-gnu/libhogweed.so.4 (0x00007f36574dd000)
        libnettle.so.6 => /usr/lib/x86_64-linux-gnu/libnettle.so.6 (0x00007f36572a7000)
        libgmp.so.10 => /usr/lib/x86_64-linux-gnu/libgmp.so.10 (0x00007f3657026000)
        libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f3656d50000)
        libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f3656b1e000)
        libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f365691a000)
        libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f365670f000)
        libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f36564f4000)
        libsasl2.so.2 => /usr/lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007f36562d9000)
        libgssapi.so.3 => /usr/lib/x86_64-linux-gnu/libgssapi.so.3 (0x00007f3656098000)
        libp11-kit.so.0 => /usr/lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007f3655d69000)
        libtasn1.so.6 => /usr/lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007f3655b56000)
        libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f3655952000)
        libheimntlm.so.0 => /usr/lib/x86_64-linux-gnu/libheimntlm.so.0 (0x00007f3655749000)
        libkrb5.so.26 => /usr/lib/x86_64-linux-gnu/libkrb5.so.26 (0x00007f36554bc000)
        libasn1.so.8 => /usr/lib/x86_64-linux-gnu/libasn1.so.8 (0x00007f365521a000)
        libhcrypto.so.4 => /usr/lib/x86_64-linux-gnu/libhcrypto.so.4 (0x00007f3654fe4000)
        libroken.so.18 => /usr/lib/x86_64-linux-gnu/libroken.so.18 (0x00007f3654dce000)
        libffi.so.6 => /usr/lib/x86_64-linux-gnu/libffi.so.6 (0x00007f3654bc6000)
        libwind.so.0 => /usr/lib/x86_64-linux-gnu/libwind.so.0 (0x00007f365499d000)
        libheimbase.so.1 => /usr/lib/x86_64-linux-gnu/libheimbase.so.1 (0x00007f365478e000)
        libhx509.so.5 => /usr/lib/x86_64-linux-gnu/libhx509.so.5 (0x00007f3654544000)
        libsqlite3.so.0 => /usr/lib/x86_64-linux-gnu/libsqlite3.so.0 (0x00007f365423b000)
        libcrypt.so.1 => /lib/x86_64-linux-gnu/libcrypt.so.1 (0x00007f3654003000)
root@taurus:/var/lib/boinc-client#

If I try to do libcurl3, it wants to uninstall the BOINC package from the repo, which I need to have installed so that it can be a service, even though I'm overwriting the new binaries with the old ones:

root@taurus:/var/lib/boinc-client# apt-get install libcurl3
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libboinc7 libllvm7 libssl1.0-dev
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  boinc-client libcurl4
The following NEW packages will be installed:
  libcurl3
0 upgraded, 1 newly installed, 2 to remove and 16 not upgraded.
Need to get 0 B/214 kB of archives.
After this operation, 1,456 kB disk space will be freed.
Do you want to continue? [Y/n]

I tried following all the instructions for manually creating a service, but it refused to work until I just went the package manager route.

I........guess I can try copying/saving the service definition file that systemctl uses, before removing the BOINC package, and then I should be able to maybe put that file back into place and re-insert it into the systemctl database..?

Like I said, I tried this back in May, completely manually, following instructions from all over the internet for how to do this by-hand.. and it didn't work. But once I installed the package, I went and looked at the file it made, and it was identical to what I had typed-up by hand. There's clearly a missing step somewhere that I'm not aware of.

But I'll give it a try.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

So I installed libcurl3, and now doing 'ldd /usr/bin/boinc' doesn't return any errors about dependencies. So that's good.

Saved the service definition file to replace it back into '/lib/systemd/system/boinc-client.service' and a soft-link in '/etc/systemd/system/multi-user.target.wants/boinc-client.service' just like there was.

The service got put in a masked state, so I unmasked it, enabled, and tried starting.

root@taurus:/etc/boinc-client# systemctl status boinc-client
â boinc-client.service - Berkeley Open Infrastructure Network Computing Client
   Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor pre
   Active: failed (Result: exit-code) since Tue 2019-09-24 17:19:06 EDT; 12s ago
     Docs: man:boinc(1)
  Process: 5466 ExecStopPost=/bin/rm -f lockfile (code=exited, status=200/CHDIR)
  Process: 5465 ExecStart=/usr/bin/boinc (code=exited, status=200/CHDIR)
 Main PID: 5465 (code=exited, status=200/CHDIR)

Sep 24 17:19:06 taurus systemd[1]: Started Berkeley Open Infrastructure Network
Sep 24 17:19:06 taurus systemd[5465]: boinc-client.service: Changing to the requ
Sep 24 17:19:06 taurus systemd[5465]: boinc-client.service: Failed at step CHDIR
Sep 24 17:19:06 taurus systemd[1]: boinc-client.service: Main process exited, co
Sep 24 17:19:06 taurus systemd[5466]: boinc-client.service: Changing to the requ
Sep 24 17:19:06 taurus systemd[5466]: boinc-client.service: Failed at step CHDIR
Sep 24 17:19:06 taurus systemd[1]: boinc-client.service: Control process exited,
Sep 24 17:19:06 taurus systemd[1]: boinc-client.service: Failed with result 'exi

So I referred to syslog, [omitting the non-relevant lines above it, since I asked for the last 30]

root@taurus:/etc/boinc-client# tail -30 /var/log/syslog
...
Sep 24 17:19:06 taurus systemd[1]: Started Berkeley Open Infrastructure Network Computing Client.
Sep 24 17:19:06 taurus systemd[5465]: boinc-client.service: Changing to the requested working directory failed: No such file or directory
Sep 24 17:19:06 taurus systemd[5465]: boinc-client.service: Failed at step CHDIR spawning /usr/bin/boinc: No such file or directory
Sep 24 17:19:06 taurus systemd[1]: boinc-client.service: Main process exited, code=exited, status=200/CHDIR
Sep 24 17:19:06 taurus systemd[5466]: boinc-client.service: Changing to the requested working directory failed: No such file or directory
Sep 24 17:19:06 taurus systemd[5466]: boinc-client.service: Failed at step CHDIR spawning /bin/rm: No such file or directory
Sep 24 17:19:06 taurus systemd[1]: boinc-client.service: Control process exited, code=exited status=200
Sep 24 17:19:06 taurus systemd[1]: boinc-client.service: Failed with result 'exit-code'.

OOP... dumb silly me, i just remembered... have to make another symbolic link.

ln -s /var/lib/boinc-client /var/lib/boinc
systemctl start boinc-client
systemctl status boinc-client

   Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor pre
   Active: active (running) since Tue 2019-09-24 17:26:26 EDT; 8s ago
     Docs: man:boinc(1)
  Process: 5466 ExecStopPost=/bin/rm -f lockfile (code=exited, status=200/CHDIR)
 Main PID: 5489 (boinc)

And reconnected with Manager on the Windows machine...

2019-09-24 17:26:27		Starting BOINC client version 6.10.37 for x86_64-pc-linux-gnu
2019-09-24 17:26:27		Libraries: libcurl/7.58.0 OpenSSL/1.0.2n zlib/1.2.11 libidn2/2.0.4 libpsl/0.19.1 (+libidn2/2.0.4) nghttp2/1.30.0 librtmp/2.3
2019-09-24 17:26:27		Data directory: /var/lib/boinc-client
2019-09-24 17:26:27		Version change (6.10.58 -> 6.10.37)
2019-09-24 17:26:30		[http_debug] [ID#0] Info:  Connected to boinc.berkeley.edu (208.68.240.115) port 443 (#1)
2019-09-24 17:26:30		[http_debug] [ID#0] Info:  Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
2019-09-24 17:26:30		[http_debug] [ID#0] Info:  SSL connection using TLSv1.2 / ECDHE-RSA-AES256-GCM-SHA384
2019-09-24 17:26:30		[http_debug] [ID#0] Info:   SSL certificate verify ok.

AWESOME

Thank you, TBar. I really appreciate it.

2019-09-24 17:36:59 SETI@home update requested by user
2019-09-24 17:37:00 SETI@home [sched_op_debug] Fetching master file
2019-09-24 17:37:00 SETI@home Fetching scheduler list
2019-09-24 17:37:05 SETI@home [sched_op_debug] Got master file; parsing
2019-09-24 17:37:05 SETI@home [sched_op_debug] Found 1 scheduler URLs in master file
2019-09-24 17:37:05 SETI@home Master file download succeeded
2019-09-24 17:37:10 SETI@home [sched_op_debug] Starting scheduler request
2019-09-24 17:37:10 SETI@home Sending scheduler request: Requested by user.
2019-09-24 17:37:10 SETI@home Reporting 100 completed tasks, requesting new tasks
2019-09-24 17:37:10 SETI@home [sched_op_debug] CPU work request: 1731456.00 seconds; 4.00 idle CPUs
2019-09-24 17:37:15 SETI@home Scheduler request completed: got 0 new tasks
2019-09-24 17:37:15 SETI@home [sched_op_debug] Server version 709
2019-09-24 17:37:15 SETI@home Message from server: No tasks sent
2019-09-24 17:37:15 SETI@home Message from server: SETI@home v8 needs 32.00MB more disk space. You currently have 0.00 MB available and it needs 32.00 MB.
2019-09-24 17:37:15 SETI@home Project requested delay of 303 seconds

Now to figure out what that's all about. I've allowed BOINC to use a full gig of space, and it currently says:


Soooo.................... ?????

edit2: Figured it out. stdoutdae.txt was pretty near the limit of 100MiB that I had set for it years ago, so I upped it a bit more to 1GiB instead.

Apparently that set value counts as "currently used"

So I scaled it back to 200MiB instead. Tasks are flowing again.

2019-09-24 17:57:52 SETI@home [sched_op_debug] Starting scheduler request
2019-09-24 17:57:52 SETI@home Sending scheduler request: To fetch work.
2019-09-24 17:57:52 SETI@home Requesting new tasks
2019-09-24 17:57:52 SETI@home [sched_op_debug] CPU work request: 1731456.00 seconds; 4.00 idle CPUs
2019-09-24 17:57:57 SETI@home Scheduler request completed: got 24 new tasks
2019-09-24 17:57:57 SETI@home [sched_op_debug] Server version 709
2019-09-24 17:57:57 SETI@home Project requested delay of 303 seconds
2019-09-24 17:57:57 SETI@home [sched_op_debug] estimated total CPU job duration: 102436 seconds
2019-09-24 17:57:57 SETI@home [sched_op_debug] Deferring communication for 5 min 3 sec
2019-09-24 17:57:57 SETI@home [sched_op_debug] Reason: requested by project

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)