Hi all,

I am sure there is a simple reason for this but on my Linux box, BOINC manager is loading at boot time but never connects to the client.

I have tried to uninstall but am not sure what files need to be taken out and aptitude doesn't recognise boinc or boincmgr so can't help me.

Is there an obvious reason for the Manager to not see the Seti app? It was all working fine but just suddenly stopped after a reboot. I'm assuming there's some lock file in place but am not sure where to look for it and it's just an assumption anyway.

TIA

S.

---

This will be because the client ('boinc') isn't running - there's nothing there for the manager to connect to. Review your startup options.

(I'll engage with this better in the morning - my pizza is getting cold!)

Hi all,

I am sure there is a simple reason for this but on my Linux box, BOINC manager is loading at boot time but never connects to the client.

I have tried to uninstall but am not sure what files need to be taken out and aptitude doesn't recognise boinc or boincmgr so can't help me.

Is there an obvious reason for the Manager to not see the Seti app? It was all working fine but just suddenly stopped after a reboot. I'm assuming there's some lock file in place but am not sure where to look for it and it's just an assumption anyway.

TIA

S.

Look for posts from Ageless.

---

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

A proud member of the OFA (Old Farts Association)

my pizza is getting cold!)

Hope it was good - that's what I'll be having tonight!

I located the boinc file in "usr/bin" and ran it. I checked with "ps aux | grep boinc" to see what was running; I got:

root     16240  0.1  0.1  40804 13536 pts/0    Sl+  17:25   0:00 boinc
root     16297  1.6  1.0 102851176 86348 tty2  Sl+  17:25   0:01 boincmgr

I killed the "boincmgr" process and restarted it but I still get no connection. Starting "boinc" gives this:

13-Sep-2019 17:25:17 [---] cc_config.xml not found - using defaults
13-Sep-2019 17:25:17 [---] Starting BOINC client version 7.16.1 for x86_64-pc-linux-gnu
13-Sep-2019 17:25:17 [---] log flags: file_xfer, sched_ops, task
13-Sep-2019 17:25:17 [---] Libraries: libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.39.2 librtmp/2.3
13-Sep-2019 17:25:17 [---] Data directory: /usr/bin
13-Sep-2019 17:25:17 [---] No usable GPUs found
13-Sep-2019 17:25:17 [---] [libc detection] gathered: 2.28, Debian GLIBC 2.28-10
13-Sep-2019 17:25:17 [---] Host name: KALI
13-Sep-2019 17:25:17 [---] Processor: 4 GenuineIntel Intel(R) Core(TM) i5-7400 CPU @ 3.00GHz [Family 6 Model 158 Stepping 9]
13-Sep-2019 17:25:17 [---] Processor features: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb invpcid_single pti ssbd ibrs ibpb stibp tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid mpx rdseed adx smap clflushopt intel_pt xsaveopt xsavec xgetbv1 xsaves dtherm ida arat pln pts hwp hwp_notify hwp_act_window hwp_epp md_clear flush_l1d
13-Sep-2019 17:25:17 [---] OS: Linux Kali: Kali GNU/Linux Rolling [5.2.0-kali2-amd64|libc 2.28 (Debian GLIBC 2.28-10)]
13-Sep-2019 17:25:17 [---] Memory: 7.76 GB physical, 15.75 GB virtual
13-Sep-2019 17:25:17 [---] Disk: 264.80 GB total, 221.03 GB free
13-Sep-2019 17:25:17 [---] Local time is UTC +1 hours
13-Sep-2019 17:25:17 [---] Last benchmark was 18152 days 16:25:17 ago
13-Sep-2019 17:25:17 [---] No general preferences found - using defaults
13-Sep-2019 17:25:17 [---] Preferences:
13-Sep-2019 17:25:17 [---]    max memory usage when active: 3975.46 MB
13-Sep-2019 17:25:17 [---]    max memory usage when idle: 7155.82 MB
13-Sep-2019 17:25:17 [---]    max disk usage: 221.71 GB
13-Sep-2019 17:25:17 [---]    don't use GPU while active
13-Sep-2019 17:25:17 [---]    suspend work if non-BOINC CPU load exceeds 25%
13-Sep-2019 17:25:17 [---]    (to change preferences, visit a project web site or select Preferences in the Manager)
13-Sep-2019 17:25:17 [---] Setting up project and slot directories
dir_open: Could not open directory 'slots' from '/usr/bin'.
13-Sep-2019 17:25:17 [---] Checking active tasks
13-Sep-2019 17:25:17 [---] Setting up GUI RPC socket
13-Sep-2019 17:25:17 [---] Checking presence of 0 project files
13-Sep-2019 17:25:17 [---] This computer is not attached to any projects
13-Sep-2019 17:25:17 Initialization completed

It then repeatedly outputs:

Invalid MIT-MAGIC-COOKIE-1 key Invalid MIT-MAGIC-COOKIE-1

I am (was) attached to projects and the 'Add project' option in the Tools dropdown is greyed out. No idea what a MIT-MAGIC-COOKIE is!!

Not sure how to proceed.

S.

---

Pasting 'MIT-MAGIC-COOKIE-1' into Google brings up all sort of references to Linux X-server (video output) problems and techniques. At which point, it stops being a BOINC problem within my knowledge, so I'll bow out.

Only to mention in passing that 'dir_open: Could not open directory 'slots' from '/usr/bin'.' sounds like possibly serious disk corruption: the 'slots' directory is pretty fundamental to BOINC's operation, and would have been created during or immediately after your first BOINC installation.

Pasting 'MIT-MAGIC-COOKIE-1' into Google brings up all sort of references to Linux X-server (video output) problems and techniques. At which point, it stops being a BOINC problem within my knowledge, so I'll bow out.

Agree, I think this is ancillary to the actual issue at hand and should be disregarded. It's a server problem that's unrelated. (DVWA has been playing up - now fixed). It's just noise in a live terminal output.

Only to mention in passing that 'dir_open: Could not open directory 'slots' from '/usr/bin'.' sounds like possibly serious disk corruption: the 'slots' directory is pretty fundamental to BOINC's operation, and would have been created during or immediately after your first BOINC installation.

The folder exists, but not in /usr/bin. The drive isn't corrupted at all - I just tested it. The 'slots' directory is in 'var/lib/boinc/slots'
This setup was running fine and has recently stopped so it isn't an installation issue, unless KALI Linux introduced some fundamental changes, which they haven't as far as I am aware.
I've tried a fresh install but don't think I managed to delete everything so might try again tomorrow. It's takeaway time ...
Steve.

---

I killed the "boincmgr" process and restarted it but I still get no connection. Starting "boinc" gives this:
[code]

I have experience only with Ubuntu, not sure what you are running. However I have found that attempting to "kill" or "start" tasks manually causes ownership problems when the tasks try to talk to one another. if you start or stop the client be sure to use the designated service call.

Except for the links to the xml files, all the boinc files (var/lib/boinc-client) should be owned as "boinc:boinc"

I have found that attempting to "kill" or "start" tasks manually causes ownership problems when the tasks try to talk to one another. if you start or stop the client be sure to use the designated service call.

OK - do you know what the designated calls are? I'll use those.

Steve.

---

Assuming you are asking how to stop and start the client?

sudo /etc/init.d/boinc-client start

sudo /etc/init.d/boinc-client stop

Also helpful.
https://boinc.berkeley.edu/wiki/Boinccmd_tool

---

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

A proud member of the OFA (Old Farts Association)

Keith,
Thank you. I'll try those tomorrow.
Steve.

---

Assuming you are asking how to stop and start the client?

sudo /etc/init.d/boinc-client start

sudo /etc/init.d/boinc-client stop

Also helpful.
https://boinc.berkeley.edu/wiki/Boinccmd_tool

Hi Keith,

Those will only work on the repository installs. What about for us that run BOINC from our /home/BOINC directories? ;)

Have a great day! :)

Siran

---

CAPT Siran d'Vel'nahr - L L & P _\\//
Winders 11 OS? "What a piece of junk!" - L. Skywalker
"Logic is the cement of our civilization with which we ascend from chaos using reason as our guide." - T'Plana-hath

boinccmd - especially 'boinccmd --quit' - will still be useful. See the link.

Editing from my Linux Mint box.

The 'repository' installation (LocutusOfBorg PPA) has placed:

The binaries in /usr/bin
The data in /var/lib/boinc-client (with a softlink from /var/lib/boinc, just in case)

Since the OP has mentioned a failed attempt to open the 'slots' directory in /usr/bin (it should be in the data area), this feels like a repository installation which has lost the (hidden) configuration files which define the locations which should be active, or possibly the startup script has become corrupted or outdated. I haven't explored Linux that deeply yet.

But the systemctl commands may still be helpful to the OP, depending which repository was used for the original installation.

Edit again - couldn't see Keith's command lines while editing. The PPA commands are

sudo systemctl stop boinc-client
sudo systemctl start boinc-client

sudo systemctl stop boinc-client
sudo systemctl start boinc-client

Fixed!!
Thanks for your help!
Steve.

---