Posts by Jean-David

1) Message boards : Projects : connecting to CPDN. (Message 112049)
Posted 11 Jun 2023 by Jean-David
Post:
How much credit do you have?

Total credit 	      16,166,961
Recent average credit 30,619.600


Niotice that these numbers do not agree with the stuff in my signature box. The box is many weeks (months?) behind, and I do not know why.
2) Message boards : Projects : Anything and Everything to do with (WCG) World Community Grid (Message 111821)
Posted 16 May 2023 by Jean-David
Post:
Ooh! ARP Uploads all going through as fast as my bored band can cope with!

Not here. My machine has run out of WCG work.

Tue 16 May 2023 07:45:51 AM EDT | World Community Grid | Sending scheduler request: To fetch work.
Tue 16 May 2023 07:45:51 AM EDT | World Community Grid | Requesting new tasks for CPU
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | Scheduler request completed: got 0 new tasks
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | No tasks sent
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | No tasks are available for OpenPandemics - COVID 19
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | No tasks are available for OpenPandemics - COVID-19 - GPU
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | No tasks are available for Africa Rainfall Project
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | No tasks are available for Help Stop TB
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | No tasks are available for Mapping Cancer Markers
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | Tasks are committed to other platforms
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | Tasks for NVIDIA GPU are available, but your preferences are set to not accept them
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | Tasks for AMD/ATI GPU are available, but your preferences are set to not accept them
Tue 16 May 2023 07:45:53 AM EDT | World Community Grid | Tasks for Intel GPU are available, but your preferences are set to not accept them
3) Message boards : Projects : connecting to CPDN. (Message 111815)
Posted 15 May 2023 by Jean-David
Post:
The update process now seems to work normally on Lunar with 7.23.0. Also at least one other user has reported it working on the CPDN fora with Arch Linux.


And here on Red Hat Enterprise Linux release 8.7 (Ootpa) with 7.20.2.
4) Message boards : Projects : connecting to CPDN. (Message 111802)
Posted 14 May 2023 by Jean-David
Post:
I raised my RAM to 128 GBytes so I would have enough room to do the larger Oifs work units, and now I am not getting any, Sigh!

There aren't any to be had even if the CPDN servers were working.


I know. I am sorry I did not make that clear.

But I cannot even get the Projects tab of the Boinc manager to display the current up-to-date results for climateprediction.net on my Linux machine. My Windows machine has that right.
5) Message boards : Projects : connecting to CPDN. (Message 111800)
Posted 14 May 2023 by Jean-David
Post:
As Jean-David Beyer pointed out on the CPDN site, these certificate files are actually incredibly simple: just chunks of plain ASCII, concatenated one after the other. If you break the[m] up into single certificate files, even a home version of Windows (sorry!) will decode and display the details - provider, period of validity, and so on.

Some months ago, the Rosetta project could not download anything to my Red Hat Enterprise Linux release 8.7 (Ootpa) machine (it may have been a slightly earlier release at the time). I updated all the certificate stuff on my machine, but nothing actually changed other than the dates of some of the files were made the current date. But the content was unchanged and it did not cure the problem.

I then did a Reset Project on Rosetta on the theory that something was wrong on my machine, but that did not work either. Doing that, Rosetta created the files that were needed, but they were all empty.

I posted on the Rosetta board where complaints should go, but nothing came of it. I wondered if any human was running Rosetta at all. They sure did not read their Crunching board. Then several months later, Rosetta started working again with no action on my part. I hope it does not take months to solve this here. My guess is that Rosetta did not update their certificate when the existing one expired.

It all works just fine on my Windows 10 machine (other than lack of work units, which is no big deal).

I raised my RAM to 128 GBytes so I would have enough room to do the larger Oifs work units, and now I am not getting any, Sigh!

CPU type  Intel(R) Xeon(R) W-2245 CPU @ 3.90GHz [Family 6 Model 85 Stepping 7]
Number of processors 	16
Operating System 	Linux Red Hat Enterprise Linux
Red Hat Enterprise Linux 8.7 (Ootpa) [4.18.0-425.13.1.el8_7.x86_64|libc 2.28]
BOINC version 	7.20.2
Memory 	125.34 GB
Cache 	 16896 KB
Total disk space 	488.04 GB
Free Disk Space 	475.73 GB
Measured floating point speed 6.05 billion ops/sec
Measured integer speed 	     25.61 billion ops/sec
6) Message boards : Projects : News on Project Outages (Message 111739)
Posted 7 May 2023 by Jean-David
Post:
Some Charlie getting a new hat


I thunk chuckie got his new hat yesterday...
7) Message boards : Projects : News on Project Outages (Message 111733)
Posted 6 May 2023 by Jean-David
Post:
The way I see it, it's better if Andy gets it right first time rather than rushes and makes silly mistakes.


I entirely agree.
8) Message boards : Projects : News on Project Outages (Message 111731)
Posted 6 May 2023 by Jean-David
Post:
I anticipate that this will take a few days to complete during which time the project will be offline. -- Posted: 2 May 2023, 15:23:30 UTC


Any idea how long a few days is? It is now late May 5.
9) Message boards : Projects : News on Project Outages (Message 111493)
Posted 3 Apr 2023 by Jean-David
Post:
For me, the "Home Page" resolves to www.climateprediction.net and everything of interest is at www.cpdn,org. And www.cpdn.org is down. The link to the real home page seems to resolve to the www.climateprediction.net now, but that is not where my browser wants to go. It wants to go to www.cpdn.org. So perhaps this home page is a fall-back address in the DNS somewhere.

https://downforeveryoneorjustme.com/cpdn.org?www=1

Is Cpdn.org down?
Checking if cpdn.org is down or it is just you...
It's not just you! cpdn.org is down.
10) Message boards : Questions and problems : Is there a way to get BOINC to give priority to Tasks with short "time to deadline"? (Message 107785)
Posted 10 Apr 2022 by Jean-David
Post:
Pore example, only CPDN set absurd deadline


CPDN deadlines were not absurd. They may be a little long these days with faster machines, and shorter work-units, so perhaps they could be cut in half, or even to 25%. Mine currently take 4 to 8 days, depending on what work units I get. But a new set of work units (OpenIFS -- not yet available) might take a long time. I am told they are RAM hogs.

In the past, there were many CPDN tasks (most of them) that took several months to complete on the machine I had. It had two Xeon processors that ran at 3.06 GHz, which was as fast as I could get at the time. It had 8GBytes of RAM that was considered a lot in those days.
11) Message boards : Questions and problems : boinc cliend does not start correctly (Message 106586)
Posted 28 Dec 2021 by Jean-David
Post:
Whatta mess!

After a lot of spinning wheels, splitting hairs, and so on, I gave up and removed the boinc-client and boinc-manager and replaced them with the same thing I already had. I had the rpms on hand. Then I could get the boinc-client and boinc manager up, with no tasks in the machine (as I had left it) with no new tasks for anything. The system still got mad at me with errors every second or two.

This system runs with systemd and SELinux (security enhanced Linux) and it is very fussy. Even the super-user cannot do things. So I cleaned up a few rules and got it going. I then enabled new tasks for universe (because I do not care what happens to it) and it failed to download any, though it acquired a nice list trying to download. I then set the system to check and relabel all the files with SELinux (which involves a reboot), and that helped a lot more. So now I have it running. If it does all right with those, I may let another project run next. WCG, probably.

Then I have to remember how to tell systemd to start the boinc client on boot. But I have done that before, so I suspect I will be able to do it again. But a day wasted on a 15-minute job.
12) Message boards : Questions and problems : boinc cliend does not start correctly (Message 106552)
Posted 27 Dec 2021 by Jean-David
Post:
P.S.:

ps -ef reveals nothing with .boinc in it except the grep ps -ef | grep boinc

jeandav+ 470157 469956 0 11:15 pts/0 00:00:00 grep --color=auto boinc

So there is no boinc client running.
13) Message boards : Questions and problems : boinc cliend does not start correctly (Message 106549)
Posted 27 Dec 2021 by Jean-David
Post:
I run Red Hat Enterprise Linux release 8.5 (Ootpa) and have been running BOINC for years.
Today I had to reorganize my hard drives and moved the boinc stuff from one partition to another. That looked OK.
First, I stopped the boinc client, and that worked.
# systemctl stop boinc-client.service

Then I moved the files.
When I try to start the client, I do this

# systemctl start boinc-client

Dec 27 10:02:58 localhost systemd[1]: Started Berkeley Open Infrastructure Network Computing Client.
Dec 27 10:03:08 localhost boinc[465491]: 27-Dec-2021 10:03:08 Another instance of BOINC is running.
Dec 27 10:03:09 localhost systemd[1]: boinc-client.service: Main process exited, code=exited, status=108/n/a
Dec 27 10:03:09 localhost systemd[1]: boinc-client.service: Failed with result 'exit-code'.

I have no idea what to do next.
14) Message boards : Projects : News on Project Outages (Message 89996)
Posted 10 Feb 2019 by Jean-David
Post:
$ dig climateprediction.net

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.1 <<>> climateprediction.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 42232
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 4, ADDITIONAL: 5

;; QUESTION SECTION:
;climateprediction.net. IN A

;; ANSWER SECTION:
climateprediction.net. 14400 IN CNAME mehet-weret.oerc.ox.ac.uk.
mehet-weret.oerc.ox.ac.uk. 300 IN A 129.67.242.70

;; AUTHORITY SECTION:
ox.ac.uk. 85518 IN NS ns2.ja.net.
ox.ac.uk. 85518 IN NS dns2.ox.ac.uk.
ox.ac.uk. 85518 IN NS dns1.ox.ac.uk.
ox.ac.uk. 85518 IN NS dns0.ox.ac.uk.

;; ADDITIONAL SECTION:
dns2.ox.ac.uk. 85518 IN A 163.1.2.190
dns0.ox.ac.uk. 85518 IN A 129.67.1.190
dns1.ox.ac.uk. 85518 IN A 129.67.1.191
ns2.ja.net. 85518 IN A 193.63.105.17
ns2.ja.net. 85518 IN AAAA 2001:630:0:45::11

;; Query time: 205 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Feb 10 15:23:09 2019
;; MSG SIZE rcvd: 264



$ dig climateprediction.org

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.1 <<>> climateprediction.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47943
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;climateprediction.org. IN A

;; ANSWER SECTION:
climateprediction.org. 3600 IN A 184.168.221.104

;; AUTHORITY SECTION:
climateprediction.org. 3600 IN NS ns1.namefind.com.
climateprediction.org. 3600 IN NS ns2.namefind.com.

;; Query time: 45 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Sun Feb 10 15:23:16 2019
;; MSG SIZE rcvd: 103
15) Message boards : Projects : News on Project Outages (Message 89995)
Posted 10 Feb 2019 by Jean-David
Post:
It seems to be down because it cannot do a TLS handshake.

The connection has timed out

The server at www.cpdn.org is taking too long to respond.

The site could be temporarily unavailable or too busy. Try again in a few moments.
If you are unable to load any pages, check your computer’s network connection.
If your computer or network is protected by a firewall or proxy, make sure that Firefox is permitted to access the Web.


It also complained the web site was using a security certificate for .net instead of .org.
16) Message boards : Projects : News on Project Outages (Message 89864)
Posted 30 Jan 2019 by Jean-David
Post:
Hmm. We’re having trouble finding that site.

We can’t connect to the server at www.cpdn.org.

$ dig www.cpdn.org

; <<>> DiG 9.8.2rc1-RedHat-9.8.2-0.68.rc1.el6_10.1 <<>> www.cpdn.org
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 54142
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;www.cpdn.org. IN A

;; Query time: 0 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Wed Jan 30 08:52:27 2019
;; MSG SIZE rcvd: 30
17) Message boards : Projects : CPDN project offline again (Message 86577)
Posted 16 Jun 2018 by Jean-David
Post:
Not really wasting my time. I run World Community Grid(30), Rosetta@home(13), Seti@home(13) too. But I am really disappointed because I feel CPDN is the most important thing I could run. If they all had work units, 44% of my spare resources would go to CPDN. (Actually, those resource shares result in CPDN getting 50% of my spare CPU time.)
18) Message boards : Projects : CPDN project offline again (Message 86572)
Posted 16 Jun 2018 by Jean-David
Post:
I have received no work in months (Linux machine), so my back-off must be at maximum. But it seems nowhere near a week
My recent experience for the last week has been:

08-Jun-2018 02:52:30 Scheduler request failed: Couldn't connect to server
08-Jun-2018 06:43:37 Scheduler request failed: Couldn't connect to server
08-Jun-2018 12:11:38 Scheduler request failed: Couldn't connect to server
08-Jun-2018 17:15:14 Scheduler request failed: Couldn't connect to server
09-Jun-2018 02:11:38 Scheduler request failed: Couldn't connect to server
09-Jun-2018 06:48:27 Scheduler request failed: Couldn't connect to server
09-Jun-2018 10:38:09 Scheduler request failed: Couldn't connect to server
09-Jun-2018 15:04:30 Scheduler request failed: Couldn't connect to server
09-Jun-2018 18:32:13 Scheduler request failed: Couldn't connect to server
09-Jun-2018 23:39:00 Scheduler request failed: Couldn't connect to server
10-Jun-2018 00:52:25 Scheduler request failed: Couldn't connect to server
10-Jun-2018 05:14:38 Scheduler request failed: Couldn't connect to server
10-Jun-2018 10:13:41 Scheduler request failed: Couldn't connect to server
10-Jun-2018 18:34:00 Scheduler request failed: Couldn't connect to server
11-Jun-2018 01:16:15 Scheduler request failed: Couldn't connect to server
11-Jun-2018 06:10:27 Scheduler request failed: Couldn't connect to server
11-Jun-2018 10:47:09 Scheduler request failed: Couldn't connect to server
11-Jun-2018 15:15:29 Scheduler request failed: Couldn't connect to server
11-Jun-2018 20:56:30 Scheduler request failed: Couldn't resolve host name
12-Jun-2018 01:12:38 Scheduler request failed: Couldn't connect to server
12-Jun-2018 05:13:42 Scheduler request failed: Couldn't connect to server
12-Jun-2018 10:32:04 Scheduler request failed: Couldn't connect to server
12-Jun-2018 15:25:49 Scheduler request failed: Couldn't connect to server
12-Jun-2018 20:49:24 Scheduler request failed: Couldn't connect to server
13-Jun-2018 02:06:54 Scheduler request failed: Couldn't connect to server
13-Jun-2018 07:11:33 Scheduler request failed: Couldn't connect to server
13-Jun-2018 14:36:32 Scheduler request failed: Couldn't connect to server
13-Jun-2018 14:38:29 Fetching scheduler list
13-Jun-2018 14:38:32 Master file download succeeded
13-Jun-2018 19:33:30 Scheduler request failed: Couldn't connect to server
13-Jun-2018 20:13:45 Scheduler request failed: Couldn't connect to server
13-Jun-2018 23:54:30 Scheduler request failed: Couldn't connect to server
14-Jun-2018 02:39:36 Scheduler request failed: Couldn't connect to server
14-Jun-2018 07:48:25 Scheduler request failed: Couldn't connect to server
14-Jun-2018 12:38:24 Scheduler request failed: Couldn't connect to server
14-Jun-2018 18:25:26 Scheduler request failed: Couldn't connect to server
15-Jun-2018 00:39:47 Scheduler request failed: Couldn't connect to server
15-Jun-2018 07:53:30 Scheduler request failed: Couldn't connect to server
15-Jun-2018 12:57:33 Scheduler request failed: Couldn't connect to server
15-Jun-2018 18:36:10 Scheduler request failed: Couldn't connect to server
15-Jun-2018 18:38:05 Fetching scheduler list
15-Jun-2018 18:38:10 Master file download succeeded
19) Message boards : Questions and problems : boinc 7.0.28 on Linux 64bits error: libnotify.so.4: cannot open shared object file (Message 46517)
Posted 30 Nov 2012 by Jean-David
Post:
Now then, with that oud of the way, what is your output when you do ldd boincmgr (that's el dee dee)?


DellT7600:boinc[~/BOINC]$ ldd boincmgr
./boincmgr: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./boincmgr)
./boincmgr: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./boincmgr)
linux-vdso.so.1 => (0x00007fff09bb1000)
libwx_gtk2u_html-2.8.so.0 => /usr/lib64/libwx_gtk2u_html-2.8.so.0 (0x00007fc1a21c9000)
libwx_gtk2u_adv-2.8.so.0 => /usr/lib64/libwx_gtk2u_adv-2.8.so.0 (0x00007fc1a1ee4000)
libwx_gtk2u_core-2.8.so.0 => /usr/lib64/libwx_gtk2u_core-2.8.so.0 (0x00007fc1a18db000)
libwx_baseu_net-2.8.so.0 => /usr/lib64/libwx_baseu_net-2.8.so.0 (0x00007fc1a16ac000)
libwx_baseu-2.8.so.0 => /usr/lib64/libwx_baseu-2.8.so.0 (0x00007fc1a1350000)
libsqlite3.so.0 => /usr/lib64/libsqlite3.so.0 (0x000000322ea00000)
libdl.so.2 => /lib64/libdl.so.2 (0x0000003218a00000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003219200000)
libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x0000003e63800000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x000000321b200000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x000000321a200000)
libnotify.so.4 => not found
libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x0000003227a00000)
libm.so.6 => /lib64/libm.so.6 (0x0000003219a00000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003224600000)
libc.so.6 => /lib64/libc.so.6 (0x0000003218e00000)
libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x0000003e63000000)
libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x0000003220e00000)
libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x000000321ba00000)
libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x0000003e62c00000)
libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x000000321fe00000)
libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x0000003e64000000)
libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x000000321da00000)
libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x000000321e200000)
libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x000000321b600000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x000000321be00000)
librt.so.1 => /lib64/librt.so.1 (0x0000003219600000)
libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x000000321fa00000)
libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x0000003223e00000)
libSM.so.6 => /usr/lib64/libSM.so.6 (0x0000003227600000)
libpng12.so.0 => /usr/lib64/libpng12.so.0 (0x000000321ce00000)
libz.so.1 => /lib64/libz.so.1 (0x0000003219e00000)
libjpeg.so.62 => /usr/lib64/libjpeg.so.62 (0x000000322a200000)
libtiff.so.3 => /usr/lib64/libtiff.so.3 (0x0000003226600000)
libSDL-1.2.so.0 => /usr/lib64/libSDL-1.2.so.0 (0x00007fc1a10a8000)
/lib64/ld-linux-x86-64.so.2 (0x0000003218600000)
libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x0000003e63400000)
libX11.so.6 => /usr/lib64/libX11.so.6 (0x000000321c200000)
libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x000000321ee00000)
libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x0000003222a00000)
libXext.so.6 => /usr/lib64/libXext.so.6 (0x000000321d600000)
libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x000000321ea00000)
libXi.so.6 => /usr/lib64/libXi.so.6 (0x000000321e600000)
libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x0000003221a00000)
libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x0000003221200000)
libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x0000003220a00000)
libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x000000321f600000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x000000321aa00000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x000000321a600000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x000000321de00000)
libICE.so.6 => /usr/lib64/libICE.so.6 (0x0000003226a00000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x0000003223600000)
libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x000000321c600000)
libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x0000003221600000)
libXau.so.6 => /usr/lib64/libXau.so.6 (0x000000321ca00000)
DellT7600:boinc[~/BOINC]$

you can easily just run ./run_client (without the added --daemon), to see the output in the terminal window.


DellT7600:boinc[~/BOINC]$ ./run_client
./boinc: /usr/lib64/libssl.so.1.0.0: no version information available (required by ./boinc)
./boinc: /usr/lib64/libcurl.so.4: no version information available (required by ./boinc)
./boinc: /usr/lib64/libcrypto.so.1.0.0: no version information available (required by ./boinc)
./boinc: /lib64/libc.so.6: version `GLIBC_2.15' not found (required by ./boinc)
./boinc: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by ./boinc)
DellT7600:boinc[~/BOINC]$

I think I have 2.12 on my machine. So I guess I need an older version of the client.

I may have 2.11 or 2.12 on my achine
20) Message boards : Questions and problems : boinc 7.0.28 on Linux 64bits error: libnotify.so.4: cannot open shared object file (Message 46515)
Posted 30 Nov 2012 by Jean-David
Post:
I have the same problem. I installed Boinc on my new x86_64 machine using the following shell script: boinc_7.0.28_x86_64-pc-linux-gnu.sh

This machine is running Red Hat Enterprise Linux Server release 6.3 (Santiago). It has a 4-core Xeon processor and 8 GBytes of RAM, but that probably has nothing to do with this.

When I try to do the run_manager, I get this:

$ ./run_manager
./boincmgr: error while loading shared libraries: libnotify.so.4: cannot open shared object file: No such file or directory

Similarly, if I check, I get:

$ rpm -ql libnotify
/usr/bin/notify-send
/usr/lib64/libnotify.so.1
/usr/lib64/libnotify.so.1.2.3
/usr/share/doc/libnotify-0.5.0
/usr/share/doc/libnotify-0.5.0/AUTHORS
/usr/share/doc/libnotify-0.5.0/COPYING
/usr/share/doc/libnotify-0.5.0/NEWS

I hope there is an answer here because cycles are awasting.


Next 20

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.