Author |
Message |
|
I can't attach a project boinc manager. I click attached project. I pick gpugrid.net. The url is https://www.gpugrid.net/. I click next. I click yes I am an existing user. Put in my email and username, Click next. And it freezes. The box says communicating with project. Please wait. What I am I do wrong here?
Here is my event, before I try attaching the project:
Fri 19 May 2023 10:15:49 PM EDT | | cc_config.xml not found - using defaults
Fri 19 May 2023 10:15:49 PM EDT | | Starting BOINC client version 7.22.1 for x86_64-pc-linux-gnu
Fri 19 May 2023 10:15:49 PM EDT | | log flags: file_xfer, sched_ops, task
Fri 19 May 2023 10:15:49 PM EDT | | Libraries: libcurl/7.86.0-DEV OpenSSL/3.0.8 zlib/1.2.13 nghttp2/1.52.0
Fri 19 May 2023 10:15:49 PM EDT | | Data directory: /home/bedrich
Fri 19 May 2023 10:15:50 PM EDT | | CUDA: NVIDIA GPU 0: NVIDIA GeForce RTX 2080 Ti (driver version 530.41, CUDA version 12.1, compute capability 7.5, 11010MB, 11010MB available, 14231 GFLOPS peak)
Fri 19 May 2023 10:15:50 PM EDT | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce RTX 2080 Ti (driver version 530.41.03, device version OpenCL 3.0 CUDA, 11010MB, 11010MB available, 14231 GFLOPS peak)
Fri 19 May 2023 10:15:50 PM EDT | | libc: version 2.35
Fri 19 May 2023 10:15:50 PM EDT | | Host name: bedrich-MS-7599
Fri 19 May 2023 10:15:50 PM EDT | | Processor: 6 AuthenticAMD AMD Phenom(tm) II X6 1090T Processor [Family 16 Model 10 Stepping 0]
Fri 19 May 2023 10:15:50 PM EDT | | 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 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt cpb hw_pstate vmmcall npt lbrv svm_lock nrip_save pausefilter
Fri 19 May 2023 10:15:50 PM EDT | | OS: Linux GNOME: GNOME 44 (Flatpak runtime) [5.15.0-72-generic|libc 2.35]
Fri 19 May 2023 10:15:50 PM EDT | | Memory: 7.76 GB physical, 2.00 GB virtual
Fri 19 May 2023 10:15:50 PM EDT | | Disk: 915.32 GB total, 840.82 GB free
Fri 19 May 2023 10:15:50 PM EDT | | Local time is UTC -4 hours
Fri 19 May 2023 10:15:50 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:15:50 PM EDT | | Preferences:
Fri 19 May 2023 10:15:50 PM EDT | | - When computer is in use
Fri 19 May 2023 10:15:50 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:15:50 PM EDT | | - don't use GPU
Fri 19 May 2023 10:15:50 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:15:50 PM EDT | | - suspend if non-BOINC CPU load exceeds 25%
Fri 19 May 2023 10:15:50 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:15:50 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:15:50 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:15:50 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:15:50 PM EDT | | - suspend if non-BOINC CPU load exceeds 50%
Fri 19 May 2023 10:15:50 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:15:50 PM EDT | | - Suspend if no input in last 60.000000 minutes
Fri 19 May 2023 10:15:50 PM EDT | | - Suspend if running on batteries
Fri 19 May 2023 10:15:50 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:15:50 PM EDT | | - Store up to an additional 0.50 days of work
Fri 19 May 2023 10:15:50 PM EDT | | - max disk usage: 823.79 GB
Fri 19 May 2023 10:15:50 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Fri 19 May 2023 10:15:50 PM EDT | | Setting up project and slot directories
Fri 19 May 2023 10:15:50 PM EDT | | Checking active tasks
Fri 19 May 2023 10:15:50 PM EDT | | Setting up GUI RPC socket
Fri 19 May 2023 10:15:50 PM EDT | | Checking presence of 0 project files
Fri 19 May 2023 10:15:50 PM EDT | | This computer is not attached to any projects
Fri 19 May 2023 10:15:50 PM EDT | | Suspending GPU computation - computer is in use
Fri 19 May 2023 10:19:11 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:19:11 PM EDT | | Reading preferences override file
Fri 19 May 2023 10:19:11 PM EDT | | Preferences:
Fri 19 May 2023 10:19:11 PM EDT | | - When computer is in use
Fri 19 May 2023 10:19:11 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:19:11 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:11 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:11 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:19:11 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:19:11 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:11 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:11 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:19:11 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:19:11 PM EDT | | - Store up to an additional 0.00 days of work
Fri 19 May 2023 10:19:11 PM EDT | | - max disk usage: 823.79 GB
Fri 19 May 2023 10:19:11 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Fri 19 May 2023 10:19:11 PM EDT | | Resuming GPU computation
Fri 19 May 2023 10:19:39 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:19:39 PM EDT | | Reading preferences override file
Fri 19 May 2023 10:19:39 PM EDT | | Preferences:
Fri 19 May 2023 10:19:39 PM EDT | | - When computer is in use
Fri 19 May 2023 10:19:39 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:19:39 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:39 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:39 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:19:39 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:19:39 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:39 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:39 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:19:39 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:19:39 PM EDT | | - Store up to an additional 0.00 days of work
Fri 19 May 2023 10:19:39 PM EDT | | - max disk usage: 100.00 GB
Fri 19 May 2023 10:19:39 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Fri 19 May 2023 10:21:07 PM EDT | | Running CPU benchmarks
Fri 19 May 2023 10:21:07 PM EDT | | Suspending computation - CPU benchmarks in progress
Fri 19 May 2023 10:21:38 PM EDT | | Benchmark results:
Fri 19 May 2023 10:21:38 PM EDT | | Number of CPUs: 6
Fri 19 May 2023 10:21:38 PM EDT | | 3651 floating point MIPS (Whetstone) per CPU
Fri 19 May 2023 10:21:38 PM EDT | | 14412 integer MIPS (Dhrystone) per CPU
Fri 19 May 2023 10:21:39 PM EDT | | Resuming computation
Fri 19 May 2023 10:25:36 PM EDT | | Fetching configuration file from https://www.gpugrid.net/get_project_config.php
Fri 19 May 2023 10:31:46 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:31:46 PM EDT | | Reading preferences override file
Fri 19 May 2023 10:31:46 PM EDT | | Preferences:
Fri 19 May 2023 10:31:46 PM EDT | | - When computer is in use
Fri 19 May 2023 10:31:46 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:31:46 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:31:46 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:31:46 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:31:46 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:31:46 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:31:46 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:31:46 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:31:46 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:31:46 PM EDT | | - Store up to an additional 0.00 days of work
Fri 19 May 2023 10:31:46 PM EDT | | - max disk usage: 100.00 GB
Fri 19 May 2023 10:31:46 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
|
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
You said you put in your email and username. Do you mean email and password?
Alternatively, you could try attaching the project using boinccmd.
boinccmd --project_attach https://www.gpugrid.net/ 'your weak account key' |
|
|
|
You said you put in your email and username. Do you mean email and password?
Alternatively, you could try attaching the project using boinccmd.
boinccmd --project_attach https://www.gpugrid.net/ 'your weak account key'
Yes, it was username and password. I had the same issue with Einstein and milkyway.
I try that later and let you know if it works.
And I thought Linux was suppose to be simply and straightforward.......
Anybody else run into problems like this?
Thanks for the suggestion.
|
|
|
|
You said you put in your email and username. Do you mean email and password?
Alternatively, you could try attaching the project using boinccmd.
boinccmd --project_attach https://www.gpugrid.net/ 'your weak account key'
Yes, it was username and password. I had the same issue with Einstein and milkyway.
I try that later and let you know if it works.
And I thought Linux was suppose to be simply and straightforward.......
Anybody else run into problems like this?
Thanks for the suggestion.
I did some reading on how to do this, but as a non programmer and a novice to linux, I am having trouble understanding this. Can someone explain this to me, in a step by step, elementary way, how to do this?
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
Open a Terminal and execute this command:
boinccmd --project_attach https://www.gpugrid.net/ 'your weak account key'
Where 'your weak account key' is your actual weak account key from your Account page here at GPUGrid.net
Without the quotes
Use copy and paste to paste the long hash into the command line.
https://www.gpugrid.net/myaccount.php
It's listed right under your User ID at the top of the page.
|
|
|
GregerSend message
Joined: 6 Jan 15 Posts: 76 Credit: 24,000,702,249 RAC: 12,961,970 Level
Scientific publications
|
Is this BOINC client version 7.22.1 from flatpak? It is new build and only 13 days old. I dont know if it been tested fully and don't know who build it.
I would suggest to get into discord for this if you have this.
invite to #help https://discord.gg/9m4WAfND
The issues that i see is that it is stored in main user home diectory and it can cause some problems like permission to create subfolder and read/write to it. It needs this to make boinc to create folder in /boinc/projects/
This indicate that boinc was started in wrong way or build choose that for you.
Package could be setup with wrong datadir and permissions could be mess along with that. It could cause issues that boinc-client does not have permission to create subfolder and operate with read and write permission when add project.
It should add user boinc and main user should be in boincgroups.
If the applications boinc-client was started from main user or in root at first start it could cause this. Therefor it is better to start from as service like systemd. To add it as a service use sudo systemctl enable boinc-client
To start it sudo systemctl start boinc-client
To get status sudo systemctl status boinc-client
To edit service nano /lib/systemd/system/boinc-client.service
It should be started from /var/lib/boinc like in debian based linux but gentoo probably have another directory for it.
You can try set user boinc to folder for read and write sudo usermod -a -G boinc $USER and restart computer (re-login should be enough but from experience in past it is forced to restart for this).
If that did not help you can start boinc in root (debugging only) and try add project then change permission after. But i would be careful doing it as i would be security risk.
We need better guidelines to package maintainers and guide users to avoid set data folder to user /home/ and add service enable as default to solve issues like this. |
|
|
|
I can't attach a project boinc manager. I click attached project. I pick gpugrid.net. The url is https://www.gpugrid.net/. I click next. I click yes I am an existing user. Put in my email and username, Click next. And it freezes. The box says communicating with project. Please wait. What I am I do wrong here?
Here is my event, before I try attaching the project:
Fri 19 May 2023 10:15:49 PM EDT | | cc_config.xml not found - using defaults
Fri 19 May 2023 10:15:49 PM EDT | | Starting BOINC client version 7.22.1 for x86_64-pc-linux-gnu
Fri 19 May 2023 10:15:49 PM EDT | | log flags: file_xfer, sched_ops, task
Fri 19 May 2023 10:15:49 PM EDT | | Libraries: libcurl/7.86.0-DEV OpenSSL/3.0.8 zlib/1.2.13 nghttp2/1.52.0
Fri 19 May 2023 10:15:49 PM EDT | | Data directory: /home/bedrich
Fri 19 May 2023 10:15:50 PM EDT | | CUDA: NVIDIA GPU 0: NVIDIA GeForce RTX 2080 Ti (driver version 530.41, CUDA version 12.1, compute capability 7.5, 11010MB, 11010MB available, 14231 GFLOPS peak)
Fri 19 May 2023 10:15:50 PM EDT | | OpenCL: NVIDIA GPU 0: NVIDIA GeForce RTX 2080 Ti (driver version 530.41.03, device version OpenCL 3.0 CUDA, 11010MB, 11010MB available, 14231 GFLOPS peak)
Fri 19 May 2023 10:15:50 PM EDT | | libc: version 2.35
Fri 19 May 2023 10:15:50 PM EDT | | Host name: bedrich-MS-7599
Fri 19 May 2023 10:15:50 PM EDT | | Processor: 6 AuthenticAMD AMD Phenom(tm) II X6 1090T Processor [Family 16 Model 10 Stepping 0]
Fri 19 May 2023 10:15:50 PM EDT | | 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 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt cpb hw_pstate vmmcall npt lbrv svm_lock nrip_save pausefilter
Fri 19 May 2023 10:15:50 PM EDT | | OS: Linux GNOME: GNOME 44 (Flatpak runtime) [5.15.0-72-generic|libc 2.35]
Fri 19 May 2023 10:15:50 PM EDT | | Memory: 7.76 GB physical, 2.00 GB virtual
Fri 19 May 2023 10:15:50 PM EDT | | Disk: 915.32 GB total, 840.82 GB free
Fri 19 May 2023 10:15:50 PM EDT | | Local time is UTC -4 hours
Fri 19 May 2023 10:15:50 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:15:50 PM EDT | | Preferences:
Fri 19 May 2023 10:15:50 PM EDT | | - When computer is in use
Fri 19 May 2023 10:15:50 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:15:50 PM EDT | | - don't use GPU
Fri 19 May 2023 10:15:50 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:15:50 PM EDT | | - suspend if non-BOINC CPU load exceeds 25%
Fri 19 May 2023 10:15:50 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:15:50 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:15:50 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:15:50 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:15:50 PM EDT | | - suspend if non-BOINC CPU load exceeds 50%
Fri 19 May 2023 10:15:50 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:15:50 PM EDT | | - Suspend if no input in last 60.000000 minutes
Fri 19 May 2023 10:15:50 PM EDT | | - Suspend if running on batteries
Fri 19 May 2023 10:15:50 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:15:50 PM EDT | | - Store up to an additional 0.50 days of work
Fri 19 May 2023 10:15:50 PM EDT | | - max disk usage: 823.79 GB
Fri 19 May 2023 10:15:50 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Fri 19 May 2023 10:15:50 PM EDT | | Setting up project and slot directories
Fri 19 May 2023 10:15:50 PM EDT | | Checking active tasks
Fri 19 May 2023 10:15:50 PM EDT | | Setting up GUI RPC socket
Fri 19 May 2023 10:15:50 PM EDT | | Checking presence of 0 project files
Fri 19 May 2023 10:15:50 PM EDT | | This computer is not attached to any projects
Fri 19 May 2023 10:15:50 PM EDT | | Suspending GPU computation - computer is in use
Fri 19 May 2023 10:19:11 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:19:11 PM EDT | | Reading preferences override file
Fri 19 May 2023 10:19:11 PM EDT | | Preferences:
Fri 19 May 2023 10:19:11 PM EDT | | - When computer is in use
Fri 19 May 2023 10:19:11 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:19:11 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:11 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:11 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:19:11 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:19:11 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:11 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:11 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:19:11 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:19:11 PM EDT | | - Store up to an additional 0.00 days of work
Fri 19 May 2023 10:19:11 PM EDT | | - max disk usage: 823.79 GB
Fri 19 May 2023 10:19:11 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Fri 19 May 2023 10:19:11 PM EDT | | Resuming GPU computation
Fri 19 May 2023 10:19:39 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:19:39 PM EDT | | Reading preferences override file
Fri 19 May 2023 10:19:39 PM EDT | | Preferences:
Fri 19 May 2023 10:19:39 PM EDT | | - When computer is in use
Fri 19 May 2023 10:19:39 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:19:39 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:39 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:39 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:19:39 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:19:39 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:19:39 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:19:39 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:19:39 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:19:39 PM EDT | | - Store up to an additional 0.00 days of work
Fri 19 May 2023 10:19:39 PM EDT | | - max disk usage: 100.00 GB
Fri 19 May 2023 10:19:39 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Fri 19 May 2023 10:21:07 PM EDT | | Running CPU benchmarks
Fri 19 May 2023 10:21:07 PM EDT | | Suspending computation - CPU benchmarks in progress
Fri 19 May 2023 10:21:38 PM EDT | | Benchmark results:
Fri 19 May 2023 10:21:38 PM EDT | | Number of CPUs: 6
Fri 19 May 2023 10:21:38 PM EDT | | 3651 floating point MIPS (Whetstone) per CPU
Fri 19 May 2023 10:21:38 PM EDT | | 14412 integer MIPS (Dhrystone) per CPU
Fri 19 May 2023 10:21:39 PM EDT | | Resuming computation
Fri 19 May 2023 10:25:36 PM EDT | | Fetching configuration file from https://www.gpugrid.net/get_project_config.php
Fri 19 May 2023 10:31:46 PM EDT | | No general preferences found - using defaults
Fri 19 May 2023 10:31:46 PM EDT | | Reading preferences override file
Fri 19 May 2023 10:31:46 PM EDT | | Preferences:
Fri 19 May 2023 10:31:46 PM EDT | | - When computer is in use
Fri 19 May 2023 10:31:46 PM EDT | | - 'In use' means mouse/keyboard input in last 3.0 minutes
Fri 19 May 2023 10:31:46 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:31:46 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:31:46 PM EDT | | - max memory usage: 3.88 GB
Fri 19 May 2023 10:31:46 PM EDT | | - When computer is not in use
Fri 19 May 2023 10:31:46 PM EDT | | - max CPUs used: 6
Fri 19 May 2023 10:31:46 PM EDT | | - Use at most 100% of the CPU time
Fri 19 May 2023 10:31:46 PM EDT | | - max memory usage: 6.99 GB
Fri 19 May 2023 10:31:46 PM EDT | | - Store at least 0.10 days of work
Fri 19 May 2023 10:31:46 PM EDT | | - Store up to an additional 0.00 days of work
Fri 19 May 2023 10:31:46 PM EDT | | - max disk usage: 100.00 GB
Fri 19 May 2023 10:31:46 PM EDT | | - (to change preferences, visit a project web site or select Preferences in the Manager)
Did you try to add another project? I remember Flatpack previously was tested and was working fine. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
I missed the OP had the data directory in /home. So navigate to the data directory and see if the main /boinc directory is located there and if that is where all the binaries are located also.
This seems more like the original Berkeley installer than any of the recent Boinc and distro packages.
I use the Berkeley installation path myself along with all of my Team. Simplifies everything to have all parts of Boinc in one location with the user having permissions to do whatever they need to any file.
In the main /Boinc directory do a ls -ail to see the permissions and ownerships of all the files. You should own all the files as $USER.
If this is the case, then the command to use boinccmd to project attach gpugrid.net with the weak key should work. |
|
|
|
Thanks for all the feedback.
Here is what I did. I copied and pasted this into the terminal to the right of the $:
bedrich@bedrich-MS-7599:~$ boinccmd --project_attach https://www.gpugrid.net/19(rest of my weak key)
I pressed enter and the next line was:
Illegal instruction (core dumped)
To answer some of your questions;
It is BOINC client version 7.22.1 from flatpak.
I am able to attach new projects. It is attaching existing projects(gpugrid, Einstein, milkyway, asteroids) that causes boinc manager to freeze.
I was able to attach milkyway as a new project under another email(xxx@gmail.com) and it worked fine. I removed the project, and then reattached under that same email as existing project. I repeat this couple of times. I do have a caveat to milkyway. I lost the password to the new account, and I click on the lost password link and I didn't reset that password,yet.
I also did this and yes I did put in my user password when prompted:
bedrich@bedrich-MS-7599:~$ sudo systemctl enable boinc-client
[sudo] password for bedrich:
Synchronizing state of boinc-client.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable boinc-client
Created symlink /etc/systemd/system/multi-user.target.wants/boinc-client.service → /lib/systemd/system/boinc-client.service.
bedrich@bedrich-MS-7599:~$ sudo systemctl start boinc-client
bedrich@bedrich-MS-7599:~$ sudo systemctl status boinc-client
× boinc-client.service - Berkeley Open Infrastructure Network Computing Client
Loaded: loaded (/lib/systemd/system/boinc-client.service; enabled; vendor >
Active: failed (Result: core-dump) since Sat 2023-05-20 23:04:59 EDT; 56s >
Docs: man:boinc(1)
Process: 4611 ExecStart=/usr/bin/boinc (code=dumped, signal=ILL)
Process: 4616 ExecStopPost=/bin/rm -f lockfile (code=exited, status=0/SUCCE>
Main PID: 4611 (code=dumped, signal=ILL)
CPU: 83ms
May 20 23:04:59 bedrich-MS-7599 systemd[1]: Started Berkeley Open Infrastructur>
May 20 23:04:59 bedrich-MS-7599 systemd[1]: boinc-client.service: Main process >
May 20 23:04:59 bedrich-MS-7599 systemd[1]: boinc-client.service: Failed with r>
lines 1-12/12 (END)
And that's as far as I was able to get. The process was running and the only way to stop it was to close the terminal. I hope I didn't screwed anything. I really don't know what this means.
Thanks again for the help. Enough for tonight.
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
bedrich@bedrich-MS-7599:~$ boinccmd --project_attach https://www.gpugrid.net/19(rest of my weak key)
Where did the '19' come from? That is not the proper URL for the GPUGrid.net project.
It is simply https://www.gpugrid.net/ and a space followed by the weak account key
You first input the operator and then follow with a space and the operand.
The instruction was malformed and I assume generated the illegal instruction.
The instruction is:
boinccmd --project_attach https://www.gpugrid.net/ 19~~~(rest of your weak account key)
Assuming the '19 is the first part of your key.
|
|
|
|
bedrich@bedrich-MS-7599:~$ boinccmd --project_attach https://www.gpugrid.net/19(rest of my weak key)
Where did the '19' come from? That is not the proper URL for the GPUGrid.net project.
It is simply https://www.gpugrid.net/ and a space followed by the weak account key
You first input the operator and then follow with a space and the operand.
The instruction was malformed and I assume generated the illegal instruction.
The instruction is:
boinccmd --project_attach https://www.gpugrid.net/ 19~~~(rest of your weak account key)
Assuming the '19 is the first part of your key.
The 19 is part of the key. I tried it both with and without the space in front of the key. I did not put a space after the $.
|
|
|
|
you need a space between the URL and your weak key. the way you typed it boinccmd would interpret all of that to be the URL which is incorrect.
boinccmd[space]--project_attach[space][URL][space][weak key]
____________
|
|
|
|
you need a space between the URL and your weak key. the way you typed it boinccmd would interpret all of that to be the URL which is incorrect.
boinccmd[space]--project_attach[space][URL][space][weak key]
I did it exactly this way and it didn't work.
bedrich@bedrich-MS-7599:~$ boinccmd --project_attach https://www.gpugrid.net/ [space & weak key written out]
Illegal instruction (core dumped)
I even removed and reinstall boinc and that didn't work. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
Don't have an answer for you then. Something about the flatpak version of BOINC is very flawed I guess.
I used this very same boinccmd statement to add the GPUGrid project via the Terminal for the recent BOINC Pentathlon in which I participated.
Had no problems at all adding the GPUGrid project to one of my hosts. |
|
|
|
I posted my problem on the boinc message page. It seems other people are having the same or similar problems. You will have to scroll down to get to my post.
https://boinc.berkeley.edu/forum_thread.php?id=14956
Is there anything else I should do?
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
Probably better to post an issue on the BOINC Github instead. That way the issue is directly seen and assigned to a BOINC developer.
https://github.com/BOINC/boinc |
|
|
|
I posted it on github:
https://github.com/BOINC/boinc/issues/5247
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
I added some commentary. No idea of any of my insight is relevant or not.
The devs know the project attach code best. |
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
I have another question. Are you (your username) a member of the boinc group? To check open a terminal and type groups yourusername. For example my username is mark so I would type groups mark.
mark@x32-linux:~$ groups mark
mark : mark adm cdrom sudo dip plugdev lpadmin sambashare boinc
As you can see, I'm a member of the boinc group. If you are not a member then enter the following exact command in a terminal:
sudo usermod -a -G boinc $(whoami)
For it to take effect, you need to log out and log back in.
EDIT: I see this was already suggested by Gregor in a post above. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
I had the same exact problem adding GPUGrid as an existing user to a new remote host during the contest. Same with trying to add Universe.
Was able to use the weak account key just fine to add the project.
Discussion pointed to the change to https in the URLs of those projects not matching the all_projects_list.xml file.
But my situation is different because I use a custom client. Not relevant likely to the OP's problem with a stock client. |
|
|
|
I have another question. Are you (your username) a member of the boinc group? To check open a terminal and type groups yourusername. For example my username is mark so I would type groups mark.
mark@x32-linux:~$ groups mark
mark : mark adm cdrom sudo dip plugdev lpadmin sambashare boinc
As you can see, I'm a member of the boinc group. If you are not a member then enter the following exact command in a terminal:
sudo usermod -a -G boinc $(whoami)
For it to take effect, you need to log out and log back in.
EDIT: I see this was already suggested by Gregor in a post above.
Looks like I am.
bedrich@bedrich-MS-7599:~$ groups bedrich
bedrich : bedrich adm cdrom sudo dip plugdev lpadmin sambashare boinc
I signed up yesterday, to post my problem.
Hopefully, it can be solved.
|
|
|
|
I had the same exact problem adding GPUGrid as an existing user to a new remote host during the contest. Same with trying to add Universe.
Was able to use the weak account key just fine to add the project.
Discussion pointed to the change to https in the URLs of those projects not matching the all_projects_list.xml file.
But my situation is different because I use a custom client. Not relevant likely to the OP's problem with a stock client.
In my all_projects_list.xml file, gpugrid, Einstein and milkyway have the https in the url, asteroids has http and I was unable to attach to any of these projects using the weak key method.
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
I'd like to confirm from reading your original event log dump that you are running Gnome OS.
Is this the true case?
So this was installed as flatpak, correct?
How did you install Boinc? Was it also a flatpak from the Gnome OS distro?
From what I have been reading, Gnome OS is not a true Linux, full-fledged distro.
It is supposed to be nothing more than a testing environment for Gnome. It is not a fully functional Linux distro so probably not expected to behave as a normal distro and probably why you are having issues connecting as an existing project user.
I also believe you installed it in a VM under Windows since I see no indication of a Linux host in your computers list.
Is this the case? |
|
|
|
I'd like to confirm from reading your original event log dump that you are running Gnome OS.
Is this the true case?
So this was installed as flatpak, correct?
How did you install Boinc? Was it also a flatpak from the Gnome OS distro?
From what I have been reading, Gnome OS is not a true Linux, full-fledged distro.
It is supposed to be nothing more than a testing environment for Gnome. It is not a fully functional Linux distro so probably not expected to behave as a normal distro and probably why you are having issues connecting as an existing project user.
I also believe you installed it in a VM under Windows since I see no indication of a Linux host in your computers list.
Is this the case?
This is what I installed from this web site, as separate OS on its separate disc :
https://www.linuxmint.com/download.php
Following these instructions:
https://linuxmint-installation-guide.readthedocs.io/en/latest/
I installed boincs through its software manager.
Now, you are telling me that I installed the wrong OS?
What should have I installed instead?
|
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
I have not installed Mint in several years but it always identified itself as Mint, not Gnome OS.
Look at your original post of your Event Log. You can see the system identifies itself as Gnome OS. Gnome OS AFAIK is NOT Mint, unless everything has changed in the Mint distro which it probably hasn't.
This is my evidence from your post.
Fri 19 May 2023 10:15:50 PM EDT | | OS: Linux GNOME: GNOME 44 (Flatpak runtime) [5.15.0-72-generic|libc 2.35]
This is the article where I learned what exactly Gnome OS is.
https://itsfoss.com/gnome-os/
I would hope that some other GPUGrid cruncher that is running the Mint distro might chime in with how their Mint installation identifies itself to BOINC. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
I know that most often Mint is offered as the closest approximation to Windows UI, but I never had much success with it and went with the most popular distro which is Ubuntu.
Been on Ubuntu since the beginning of my transition from Windows and never had any issues with it. Been rock solid with all applications and projects. |
|
|
|
You can look at my two:
Host 132158: Linux Mint 21.1 [5.15.0-71-generic|libc 2.35]
Host 508381: Linux Mint 20.3 [5.4.0-148-generic|libc 2.31]
Both have regular success with both ATM and Python tasks. |
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
This is what I installed from this web site, as separate OS on its separate disc :
https://www.linuxmint.com/download.php
Following these instructions:
https://linuxmint-installation-guide.readthedocs.io/en/latest/
I installed boincs through its software manager.
Now, you are telling me that I installed the wrong OS?
What should have I installed instead?
Mint 21.1 is fine. I have it installed on 4 computers and am running boinc on all of them. I would uninstall the flatpak boinc package via the software manager. I would then suggest adding the Gianfranco Costamagna PPA to your software sources and then installing boinc 7.20.5 by running the following commands:
sudo add-apt-repository ppa:costamagnagianfranco/boinc
sudo apt update
sudo apt install boinc
reboot |
|
|
|
Mint 21.1 is fine. I have it installed on 4 computers and am running boinc on all of them. I would uninstall the flatpak boinc package via the software manager. I would then suggest adding the Gianfranco Costamagna PPA to your software sources and then installing boinc 7.20.5 by running the following commands:
sudo add-apt-repository ppa:costamagnagianfranco/boinc
sudo apt update
sudo apt install boinc
reboot
Mint 21.1 is fine, but it isn't (or wasn't?) compatible with PPAs. I installed the PPA on the Mint 20.3 machine, where it loaded properly, and copied the client binary to 21.1
One or other of them may have fixed it since - did you get the PPA to install cleanly on 21.1? |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
Thanks Richard and biodoc for confirming that Mint identifies as Mint.
I don't know if he actually installed the normal Mint and then installed the flatpak version of Boinc which seemingly changes the way the OS is identifed or what.
I would remove the flatpak version of Boinc and go with the distro's version of Boinc, or the PPA of Gianfranco's. |
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
Mint 21.1 is fine, but it isn't (or wasn't?) compatible with PPAs. I installed the PPA on the Mint 20.3 machine, where it loaded properly, and copied the client binary to 21.1
One or other of them may have fixed it since - did you get the PPA to install cleanly on 21.1?
Now that you mentioned it, I did see a apt-key deprecated warning when I ran apt update but I fixed it using instructions from this link. https://www.omgubuntu.co.uk/2022/06/fix-apt-key-deprecation-error-on-ubuntu
|
|
|
|
I spent the evening removing and reinstall linux mint. I attempt a manual reinstall of boinc, using the distro's version of Boinc. I believe. The items are in the correct directory. It doesn't seem to work.
Pictures are posted in the link. The OS in linux mint, in case anybody thinks I am making this up, because I am not.
https://github.com/BOINC/boinc/issues/5247
I will make another attempt tomorrow.
Thanks for your effort. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
No you are still using the Flatpak version if your posted image is AFTER you supposedly removed BOINC.
sudo apt remove --purge boinc-client boinc-manager
Reboot.
sudo apt install boinc-client boinc-manager |
|
|
|
No you are still using the Flatpak version if your posted image is AFTER you supposedly removed BOINC.
sudo apt remove --purge boinc-client boinc-manager
Reboot.
sudo apt install boinc-client boinc-manager
I followed your procedure. Pictures of the results are posted at this link:
https://github.com/BOINC/boinc/issues/5247
Since this site has no drag and drop options, I post the pictures over there. I hope they don't mind.
|
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
Therefor it is better to start from as service like systemd. To add it as a service use sudo systemctl enable boinc-client
To start it sudo systemctl start boinc-client
To get status sudo systemctl status boinc-client
You can try set user boinc to folder for read and write sudo usermod -a -G boinc $USER and restart computer (re-login should be enough but from experience in past it is forced to restart for this).
@Bedrich Hajek, It looks good so far from what you posted at Github. Now is the time to use the commands above as recommended by @Greger. |
|
|
|
Further to that, I would suggest using
sudo systemctl disable boinc-client
before undertaking any form of maintenance, such as kernel updates, that might require a system restart. This prevents BOINC restarting automatically too early in the reboot process, before the video drivers have fully loaded.
Then, when everything is stable, do
sudo systemctl enable boinc-client
sudo systemctl start boinc-client
(in that order) to get things going again. |
|
|
|
Now that you mentioned it, I did see a apt-key deprecated warning when I ran apt update but I fixed it using instructions from this link. https://www.omgubuntu.co.uk/2022/06/fix-apt-key-deprecation-error-on-ubuntu
Thanks for that. It seemed to go OK, but I haven't succeeded in getting it to install a refreshed version of the current PPA yet. I'll have another go next time there's something new to install (I'm running v7.20.5 already). |
|
|
|
I did this per this morning's post:
https://github.com/BOINC/boinc/issues/5247
Scroll down.
It doesn't seem have gone quite right.
What is the next?
|
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
I did this per this morning's post:
https://github.com/BOINC/boinc/issues/5247
Scroll down.
It doesn't seem have gone quite right.
What is the next?
The command you used for adding your username to the boinc group was incorrect. Remove the $ sign from in front of your username in the command you entered or enter the following exactly as typed. $USER is a variable that is your username.
sudo usermod -a -G boinc $USER
Then reboot |
|
|
|
I did this:
sudo usermod -a -G boinc bedrichhajek
groups bedrichhajek
rebooted
Then did this again:
sudo systemctl disable boinc-client
sudo systemctl enable boinc-client
sudo systemctl start boinc-client
cd /usr/bin
ls |grep boinc
ls -ail |grep boinc
./boinc
./boincmgr
It look good until the last two steps.
See link for pictures:
https://github.com/BOINC/boinc/issues/5247
|
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
I hate to suggest this but you might be better off installing Mint 20.3 rather than 21.1. The boinc version (7.18.1) that "ships" with 21.1 is known to have bugs. If you want to start over, Mint 20.3 can be downloaded at this link.
https://linuxmint.com/download_all.php |
|
|
|
I hate to suggest this but you might be better off installing Mint 20.3 rather than 21.1. The boinc version (7.18.1) that "ships" with 21.1 is known to have bugs. If you want to start over, Mint 20.3 can be downloaded at this link.
https://linuxmint.com/download_all.php
I was think along the same lines, that if this doesn't work, than I should pick another version of linux, and install that. I am glad you came up with a suggestion of which one. I will do that. This is just getting too aggravating. It shouldn't be like this.
Thanks again.
|
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
After installation of the system software:
Update and upgrade the system packages to the latest releases
sudo apt update
sudo apt upgrade
reboot
Install nvidia drivers (version 525). There are other versions available
sudo apt install nvidia-driver-525
reboot
Install boinc meta package (includes boinc and boinc manager):
sudo apt install boinc
sudo usermod -a -G boinc $USER
reboot
|
|
|
|
I hate to suggest this but you might be better off installing Mint 20.3 rather than 21.1. The boinc version (7.18.1) that "ships" with 21.1 is known to have bugs.
My journey with Linux started with Linux Mint 20, after 25 years or so of being exclusively a Windows user - and MSDOS and CP/M before that. It took a few false starts, but after a while I got it all running, and switched to the PPA, because I'm an active member of the BOINC development community, and I wanted to keep up to date with new test releases.
I installed Mint 21 (initially 21.0) as an upgrade over 20 (by that time 20.3). During the upgrade process, Mint rejected the PPA because of the security key problem, and installed the repository version of v7.18.1 in its place. And it ran. (rendering null and void my plan to explore what was really wrong with v7.18.1)
The PPA uses the systemd launch process to run BOINC. I'm speculating that it's really the meta-framework surrounding BOINC that's broken in v7.18.1 (the responsibility of the repository maintainers), rather than BOINC itself. But alternative explanations are invited. |
|
|
biodocSend message
Joined: 26 Aug 08 Posts: 183 Credit: 10,085,929,375 RAC: 12,386,313 Level
Scientific publications
|
The PPA uses the systemd launch process to run BOINC. I'm speculating that it's really the meta-framework surrounding BOINC that's broken in v7.18.1 (the responsibility of the repository maintainers), rather than BOINC itself. But alternative explanations are invited.
I found this bug report that suggests the v7.18.1 client crashes with a core dump on processors without the avx instruction set. https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1970521
The flatpak boinc v7.22.1 is available on flathub.org. I do have another computer on which I could give this a try to see if it's fully functional. Is there a downside to running boinc in a container? https://flathub.org/apps/edu.berkeley.BOINC |
|
|
|
That launchpad bug report looks interesting. BOINC detects CPU capabilities via a single long string, and it's been getting longer over time as more instruction sets have been added. There have been times in the past when the string has overflowed and/or been truncated, and has needed extending. I'll have a look through the v7.18.1 source tree, to see the status of that string in that release. v7.18.1 was primarily targeted at Android, so some other elements may have got left behind. But it'll take me some time, though.
We've already explored flatpak earlier in this conversation, and it didn't help - I don't think it's worth revisiting.
@ Bedrich Hajek: because you haven't succeeded in attaching to the project yet, we can't see the details of the CPU in this host. Could you let us know the make/model of the CPU, or - if you've successfully attached it to another BOINC project in the past - post a link to the host details at that project? |
|
|
|
That launchpad bug report looks interesting. BOINC detects CPU capabilities via a single long string, and it's been getting longer over time as more instruction sets have been added. There have been times in the past when the string has overflowed and/or been truncated, and has needed extending. I'll have a look through the v7.18.1 source tree, to see the status of that string in that release. v7.18.1 was primarily targeted at Android, so some other elements may have got left behind. But it'll take me some time, though.
We've already explored flatpak earlier in this conversation, and it didn't help - I don't think it's worth revisiting.
@ Bedrich Hajek: because you haven't succeeded in attaching to the project yet, we can't see the details of the CPU in this host. Could you let us know the make/model of the CPU, or - if you've successfully attached it to another BOINC project in the past - post a link to the host details at that project?
The computer in question is:
https://www.gpugrid.net/show_host_detail.php?hostid=544232
I installed a second hard drive on which I installed Mint. I can boot into either windows or Mint now. The machine does run well with either OS.
If I am going to experiment it's on an older model, not my primary one.
I did manage to attach from the boinc manager to new project accounts, but I wasn't able to attach to my existing project accounts. I think I mentioned that somewhere in one my message board post.
https://github.com/BOINC/boinc/issues/5247
Here is an example attaching to new project account:
https://sech.me/boinc/Amicable/show_host_detail.php?hostid=206613
Of course, I since delete the flatpak and reinstall Mint. The WU's were crunching well, at the time.
I plan to work on this, later today, I am actually away from from home now. I hope this helps. Thanks.
|
|
|
|
OK, got some basic background. The list of processor features is stored in <p_features>: until early 2020 (around BOINC v7.16.7), it was set at 256 bytes, but it was increased to 1024 following https://github.com/BOINC/boinc/issues/3431 - concern over, specifically, an AMD Ryzen R9 3900X CPU. That's in the v7.18 branch source. It's recently been increased again, to 8192 bytes, though that won't take effect until v7.22.x
Looking at my own machines, which are mostly Intel i5s, they report much shorter feature lists under Windows than under Linux: an old one running Windows has a list 242 bytes long, and on a newer one running Linux the list is 757 bytes. You can see the list in BOINC's Event Log in the top few lines after a restart.
This probably isn't the cause, then, but if anyone can capture any figures for an AMD Phenom II X6 1090T or similar, it would be interesting.
There was another bug - again involving avx, I think - which caused 64-bit versions of BOINC to fail on low power Intel CPUs running Windows - 32-bit versions worked OK. I'll have a look for that next.
Edit - that particular bug was in an SSL security library distributed with the Windows client. It won't affect the Linux client at all - red herring. But #2470 if you're interested. |
|
|
|
Looks like, I made some progress, but I am not there yet.
Click below and scroll down:
https://github.com/BOINC/boinc/issues/5247
|
|
|
|
I attached the projects by the weak method.
http://www.gpugrid.net/hosts_user.php?userid=19626
https://einsteinathome.org/host/13142147
It works on Einstein. It's pity gpugrid doesn't have any work, so I can test it. |
|
|
Keith Myers Send message
Joined: 13 Dec 17 Posts: 1335 Credit: 7,404,517,459 RAC: 13,217,405 Level
Scientific publications
|
The work is very low but some is still trickling out. I have done 8 tasks today. Still working on one currently for the 26th.
You just have to ask for the work and it shows up.
A script to ping them every 5-10 minutes is all it takes. |
|
|
|
After running boinc client flawlessly for several weeks, rebooting the computers on average everyday, without any issues. I reboot it today, and got this message:
"Boinc Manager - Daemon Start Fail"
'Boinc Manager is not able to start a Boinc client."
"Please run the client and try again"
BTW: Boinc manager is running in the background, but I can't access it.
This is happening on my GenuineIntel Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz [Family 6 Model 63 Stepping 2] (12 processors).
The other machine is running fine.
https://www.gpugrid.net/hosts_user.php?userid=19626
I have posted screenshot on this site, please scroll down:
https://github.com/BOINC/boinc/issues/5247
What is the solution? |
|
|
|
After running boinc client flawlessly for several weeks, rebooting the computers on average everyday, without any issues. I reboot it today, and got this message:
"Boinc Manager - Daemon Start Fail"
'Boinc Manager is not able to start a Boinc client."
"Please run the client and try again"
BTW: Boinc manager is running in the background, but I can't access it.
This is happening on my GenuineIntel Intel(R) Core(TM) i7-5820K CPU @ 3.30GHz [Family 6 Model 63 Stepping 2] (12 processors).
The other machine is running fine.
https://www.gpugrid.net/hosts_user.php?userid=19626
I have posted screenshot on this site, please scroll down:
https://github.com/BOINC/boinc/issues/5247
What is the solution?
Nevermind, I solved this problem myself.
In the Boinc window, I clicked file, then select computer, then typed in the host name.
I don't know how this happened, but it's fixed.
|
|
|