Hello.

I have FreeBSD in my computer:

$ uname -a
FreeBSD x 14.2-RELEASE FreeBSD 14.2-RELEASE releng/14.2-n269506-c8918d6c7412 GENERIC amd64

I installed the boinc-client package. This is the information about what it is installed:

$ pkg info boinc-client
boinc-client-8.0.2_1
Name           : boinc-client
Version        : 8.0.2_1
...

"Boinc Manager" icon was created too, but when I click it then the next pop-up appears over the manager:

BOINC Manager - Daemon Start Failed
BOINC Manager is not able to start a BOINC client.
Please run the client and try again.

If I run "boincmgr" with a terminal then the same message appears.

Apparently, the Boinc client is running:

$ ps -ax | grep boinc
2320  -  INs    0:00,00 daemon: /usr/local/bin/boinc_client[2321] (daemon)
2321  -  SN     0:00,75 /usr/local/bin/boinc_client --redirectio --dir /var/db/boinc
2564  -  S      0:01,34 /usr/local/bin/boincmgr
2584  1  S+     0:00,00 grep boinc

$ ps -aux | grep boinc
root       2320   0,0  0,0      13856   2232  -  INs  23:23     0:00,00 daemon: /usr/local/bin/boinc_cl
boinc      2321   0,0  0,1      32740  15728  -  SN   23:23     0:00,72 /usr/local/bin/boinc_client --r
ptony      2564   0,0  0,7     256012 116768  -  S    00:07     0:01,15 /usr/local/bin/boincmgr
ptony      2570   0,0  0,0      13916   2444  1  S+   00:09     0:00,00 grep boinc

Any help would be appreciated.

Pedro.

I haven't used BSD but if starting from command line, try doing it from the directory where the client resides.

In reply to Dave's message of 25 Mar 2025:

I haven't used BSD but if starting from command line, try doing it from the directory where the client resides.

I tried that, no success, always the same pop-up in the boinc manager with the same error message (related before).

If I run the client (killing it previously) from the command line then the next appears (no errors, except maybe that "getaddrinfo: Name does not resolve"):

# boinc_client
25-Mar-2025 20:38:09 [---] cc_config.xml not found - using defaults
25-Mar-2025 20:38:09 [---] Starting BOINC client version 8.0.2 for x86_64-pc-freebsd
25-Mar-2025 20:38:09 [---] log flags: file_xfer, sched_ops, task
25-Mar-2025 20:38:09 [---] Libraries: libcurl/8.11.1 OpenSSL/3.0.15 zlib/1.3.1 brotli/1.1.0 zstd/1.5.6 libidn2/2.3.7 libpsl/0.21.5 libssh2/1.11.1 nghttp2/1.64.0
25-Mar-2025 20:38:09 [---] Data directory: /usr/local/bin
25-Mar-2025 20:38:10 [---] No usable GPUs found
25-Mar-2025 20:38:10 getaddrinfo(x): Name does not resolve
25-Mar-2025 20:38:10 [---] Host name: x
25-Mar-2025 20:38:10 [---] Processor: 2  Intel(R) Celeron(R) CPU 1007U @ 1.50GHz [Family 6 Model 58 Stepping 9]
25-Mar-2025 20:38:10 [---] Processor features: sse sse2 pni mmx
25-Mar-2025 20:38:10 [---] OS: FreeBSD: 14.2-RELEASE
25-Mar-2025 20:38:10 [---] Memory: 15.86 GB physical, 0 bytes virtual
25-Mar-2025 20:38:10 [---] Disk: 81.36 GB total, 51.54 GB free
25-Mar-2025 20:38:10 [---] Local time is UTC +1 hours
25-Mar-2025 20:38:10 [---] No general preferences found - using defaults
25-Mar-2025 20:38:10 [---] Preferences:
...
25-Mar-2025 20:38:10 [---] Setting up project and slot directories
25-Mar-2025 20:38:10 [---] Checking active tasks
25-Mar-2025 20:38:10 [---] Setting up GUI RPC socket
25-Mar-2025 20:38:10 [---] Checking presence of 0 project files
25-Mar-2025 20:38:10 [---] This computer is not attached to any projects
25-Mar-2025 20:38:10 Initialization completed

I modified the /etc/hosts file adding the line:

127.0.0.1     x

("x" is my hostname)

then the error "getaddrinfo(x): Name does not resolve" does not appear anymore in the boinc client.

However, the problem launching the boinc manager remains (the same pop-up with the same message).

I think this is the problem...

getaddrinfo isn't resolving hostnames
http://stackoverflow.com/questions/32338919/ddg#73758984

In reply to ptony's message of 24 Mar 2025:

...
If I run "boincmgr" with a terminal then ...
...
Any help would be appreciated.

Double check that everything is installed correctly.
I described the installation procedure in CLI mode on the page:
https://setiathome.berkeley.edu/forum_thread.php?id=81107&postid=1856389#1856389
The old version of FreeBSD is listed there, but I don't think it has changed much.

In reply to Dr Who Fan's message of 27 Mar 2025:

I think this is the problem...

getaddrinfo isn't resolving hostnames
http://stackoverflow.com/questions/32338919/ddg#73758984

Sorry, but I'm not an expert in networking or communications, and I can't clearly deduce what I must do from that link.

I changed the line (see my previous post) in /etc/hosts, now is:

192.168.1.1		x

but the problem told in my first post remains. In addition, I did a couple of things more (but without really knowing what I was doing) without success. The changes were then reverted.

I would be very grateful if you (or someone else) could explain what I must do in an easier way.

Besides, the "getaddrinfo(x): Name does not resolve" error message might not be the cause of my problem.

In reply to Demis's message of 27 Mar 2025:

In reply to ptony's message of 24 Mar 2025:

...
If I run "boincmgr" with a terminal then ...
...
Any help would be appreciated.

Double check that everything is installed correctly.
I described the installation procedure in CLI mode on the page:
https://setiathome.berkeley.edu/forum_thread.php?id=81107&postid=1856389#1856389
The old version of FreeBSD is listed there, but I don't think it has changed much.

Thank you. That link seems very technical but I will study it.

I installed the package, not the port. Maybe the next step is to install the port, but I was reluctant because of the probable very long compilation time.

In reply to ptony's message of 27 Mar 2025:

In reply to Dr Who Fan's message of 27 Mar 2025:

I think this is the problem...

getaddrinfo isn't resolving hostnames
http://stackoverflow.com/questions/32338919/ddg#73758984

Sorry, but I'm not an expert in networking or communications, and I can't clearly deduce what I must do from that link.

I can ask you to show the output of two commands:
1. hostname -f
2. ping -c 3 www.google.com

If you do not want to show the host name, then replace the symbols with x
(for example, if the real host name is my.super.host, then write here as xx.xxxxx.xxxx)

I can ask you to show the output of two commands:
1. hostname -f
2. ping -c 3 www.google.com

If you do not want to show the host name, then replace the symbols with x
(for example, if the real host name is my.super.host, then write here as xx.xxxxx.xxxx)

$ hostname -f
x

I didn't hide the hostname, "x" is my actual hostname. I could change it without any problem.

$ ping -c 3 www.google.com
PING www.google.com (142.250.185.4): 56 data bytes
64 bytes from 142.250.185.4: icmp_seq=0 ttl=115 time=7.217 ms
64 bytes from 142.250.185.4: icmp_seq=1 ttl=115 time=11.039 ms
64 bytes from 142.250.185.4: icmp_seq=2 ttl=115 time=5.688 ms

--- www.google.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.688/7.981/11.039/2.250 ms

In reply to ptony's message of 27 Mar 2025:

I can ask you to show the output of two commands:
1. hostname -f
2. ping -c 3 www.google.com

If you do not want to show the host name, then replace the symbols with x
(for example, if the real host name is my.super.host, then write here as xx.xxxxx.xxxx)

$ hostname -f
x

I didn't hide the hostname, "x" is my actual hostname. I could change it without any problem.

Ok.
For a computer connected to a network, it is better to have a name like this "x.simple.loc"

ee /etc/rc.conf
hostname="x.simple.loc"

And it's better to reboot the host after that.

$ ping -c 3 www.google.com
PING www.google.com (142.250.185.4): 56 data bytes
64 bytes from 142.250.185.4: icmp_seq=0 ttl=115 time=7.217 ms
64 bytes from 142.250.185.4: icmp_seq=1 ttl=115 time=11.039 ms
64 bytes from 142.250.185.4: icmp_seq=2 ttl=115 time=5.688 ms

--- www.google.com ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 5.688/7.981/11.039/2.250 ms

Great, name resolving works fine.

(By default FreeBSD now has a name resolution service called "unbound".
I don't know why, but this service can glitch quite often. Perhaps in the release version of FreeBSD 14.2 this already works fine. The glitch was that name resolution stopped working once a week or two. Restarting the service didn't help. Only restarting the computer helped. When I removed "unbound" and installed and configured the old classic service "named" - all the glitches ended. But setting up "named" is not trivial. This is just my comment, not a call to action.)

Please check that the gui_rpc_auth.cfg file is 32 bytes in size.

ls -l /var/db/boinc/gui_rpc_auth.cfg
-rw-------  1 boinc  boinc  32 Mar 28  2017 /var/db/boinc/gui_rpc_auth.cfg

cat /var/db/boinc/gui_rpc_auth.cfg
6badc0922db7ed5c31179c4105354f01

Your code will be different (no need to publish it here).
Just check its structure, that it is approximately the same.

And one more thing.
Your log shows:

25-Mar-2025 20:38:10 [---] Processor: 2  Intel(R) Celeron(R) CPU 1007U @ 1.50GHz [Family 6 Model 58 Stepping 9]

You installed from the pkg.
The pkg contains a precompiled version.

It is quite possible that the binary code is not suitable for this processor.
Only a local build from the port will help here.

(I have encountered the fact that binary versions of programs may not work or work with glitches on Celeron.
Regardless of the system Windows, Unix, Linux, etc.)

Thanks Demis for your advice.

The gui_rpc_auth.cfg file looks ok.

I changed the hostname to "x.simple.loc" (modifying /etc/rc.conf and rebooting) and the problem with boinc persisted. Additionally, I couldn't launch the Chromium browser (no error messages in /var/log, no core, simply didn't start). The same happened when I chose another hostname (one word, without dots), and only when I returned to "x" as my hostname then the Chromium browser started again (but the boinc problem persists).

In any case, it seems that "x" was not a good choice as my hostname when I installed the OS. I have to find out how to change the hostname properly (without additional problems) and maybe all will get fixed, or maybe I should uninstall the package and build the port.

If I make any progress I'll write it here, and of course any additional help is welcome.

In reply to ptony's message of 28 Mar 2025:

I changed the hostname to "x.simple.loc" (modifying /etc/rc.conf and rebooting) and the problem with boinc persisted. Additionally, I couldn't launch the Chromium browser (no error messages in /var/log, no core, simply didn't start). The same happened when I chose another hostname (one word, without dots), and only when I returned to "x" as my hostname then the Chromium browser started again (but the boinc problem persists).

To run Chromium correctly, I think you just need the correct entry in the host file:

ee /etc/hosts
::1			localhost localhost.my.domain
127.0.0.1		localhost localhost.my.domain
#
192.168.1.1		x x.simple.loc

And of course in

ee /etc/rc.conf
hostname="x.simple.loc"

( https://man.freebsd.org/cgi/man.cgi?rc.conf find hostname in man )
Above I showed two parts "x" and "x.simple.loc".
Short name and space separated FQDN.

As of now, I know for sure that in CLI mode on FreeBSD 14.2, the BOINC-client (boinc-client-8.0.2_1) installed from the PKG works fine.
About the graphic part - I don't know. Need to check. (What do you use for the graphic part?)
You may need to reinstall some package.

Thanks again.

Sorry, but I changed again the hostname to "x.simple.loc" (modifying /etc/rc.conf as you said), and I added the exact line you showed in /etc/hosts (I copied and pasted it, using the vi editor that I know how to use) and then reboot and then Chromium does not start, Iridium neither (a similar browser). Nevertheless, I can start Firefox and apparently functions properly, and I can start the Otter browser and the Web browser (the one included in Gnome)

About the graphic part - I don't know. Need to check. (What do you use for the graphic part?)
You may need to reinstall some package.

I deleted (again) the boinc-client package and reinstalled it (with the new hostname "x.simple.loc"), the terminal said this:

New packages to be INSTALLED:
	boinc-client: 8.0.2_1

Number of packages to be installed: 1

The process will require 12 MiB more space.

Proceed with this action? [y/N]: y

[1/1] Installing boinc-client-8.0.2_1...
===> Creating groups
Using existing group 'boinc'
===> Creating users
Using existing user 'boinc'
===> Creating homedir(s)
[1/1] Extracting boinc-client-8.0.2_1: 100%
Adjusting file ownership in "/var/db/boinc" to boinc:boinc
==> Running trigger: desktop-file-utils.ucl
Building cache database of MIME types
=====
Message from boinc-client-8.0.2_1:

--
The BOINC client is now installed.

Then the problem "BOINC Manager is not able to start a BOINC client" when I open the manager persists.

Now I'm going to reboot again, but I'm afraid there won't be good news. Otherwise, I'll tell you.

Edit: after rebooting all continues the same.

Did you add a line allowing the client to run?

 ee /etc/rc.conf

boinc_client_enable="YES"

And start like:

/usr/local/etc/rc.d/boinc-client start

And recheck

192.168.1.1[There_Tabulation_Symbol_Like_Separator]x x.simple.loc

On my VM I'm see:

uname -a
FreeBSD test.simple.loc 14.2-RELEASE FreeBSD 14.2-RELEASE releng/14.2-n269506-c8918d6c7412 GENERIC amd64

cd /var/db/boinc
ls -l
total 136
-rw-r--r--  1 boinc boinc   196 Mar 29 12:26 account_boinc.progger.info_odlk.xml
-rw-r--r--  1 boinc boinc 51604 Mar 29 11:55 all_projects_list.xml
lrwxr-xr-x  1 boinc boinc    38 Mar 29 11:50 ca-bundle.crt -> /usr/local/share/certs/ca-root-nss.crt
-rw-r--r--  1 boinc boinc  4631 Mar 29 13:16 client_state.xml
-rw-r--r--  1 boinc boinc  4622 Mar 29 13:14 client_state_prev.xml
-rw-r--r--  1 boinc boinc   310 Mar 29 12:15 coproc_info.xml
-rw-r--r--  1 boinc boinc   113 Mar 29 13:18 daily_xfer_history.xml
-rw-r-----  1 boinc boinc    32 Mar 29 11:55 gui_rpc_auth.cfg
-rw-r--r--  1 boinc boinc     0 Mar 29 11:55 lockfile
-rw-r--r--  1 boinc boinc     0 Mar 29 12:23 lookup_account.xml
-rw-r--r--  1 boinc boinc 19492 Mar 29 13:18 lookup_website.html
-rw-r--r--  1 boinc boinc     0 Mar 29 13:14 master_boinc.progger.info_odlk.xml
drwxrwx--x  2 boinc boinc   512 Mar 29 11:55 notices
drwxrwx--x  3 boinc boinc   512 Mar 29 12:26 projects
lrwxr-xr-x  1 boinc boinc    28 Mar 29 11:50 skins -> /usr/local/share/boinc/skins
-rw-r--r--  1 boinc boinc     0 Mar 29 11:55 stderrdae.txt
-rw-r--r--  1 boinc boinc   672 Mar 29 12:15 stderrgpudetect.txt
-rw-r--r--  1 boinc boinc  9934 Mar 29 13:18 stdoutdae.txt
-rw-r--r--  1 boinc boinc   204 Mar 29 12:15 stdoutgpudetect.txt
-rw-r--r--  1 boinc boinc   389 Mar 29 12:15 time_stats_log

In reply to Demis's message of 29 Mar 2025:

Did you add a line allowing the client to run?

 ee /etc/rc.conf

boinc_client_enable="YES"

Yes, that line is in /etc/rc.conf, I can't remember if I added it at the beginning (when I first installed boinc-client), but the line is there, and the client starts when the computer boots.

And start like:

/usr/local/etc/rc.d/boinc-client start

I killed the boinc_client (two processes, see my first post) and started it as you said. Then I started the boinc manager, from the icon in desktop and from the command line. In both cases, as always: "BOINC Manager is not able to start a BOINC client".
Sorry.

And recheck

192.168.1.1[There_Tabulation_Symbol_Like_Separator]x x.simple.loc

Yes, I used the tab as separator.

These are the lines (not beginning with "#") in my /etc/hosts :

::1               localhost localhost.my.domain
127.0.0.1         localhost localhost.my.domain
192.168.1.1       x x.simple.loc

"from the icon in desktop" - What kind of desktop is installed?
https://docs.freebsd.org/en/books/handbook/desktop/

In reply to Demis's message of 29 Mar 2025:

"from the icon in desktop" - What kind of desktop is installed?
https://docs.freebsd.org/en/books/handbook/desktop/

I first installed GNOME, later I installed LXQT. Now I'm in gnome, I start it from GDM (GNOME Display Manager).

I'll try to install gnome on VM.
To check.
But it won't be fast.
Try to look for errors in the message file (/var/log/messages).