[Support] Linuxserver.io - Boinc


Recommended Posts

3 hours ago, Squid said:

Depending upon your point of view, the reason is that its either an error you made or an error LSIO made in the template.  To run it in bridge mode, you need to explicitly enter in a port in the entry that states WebGUI Port:8080 default

We have never ever made a mistake 😎

  • Haha 1
Link to comment
  • 3 weeks later...
  • 7 months later...

Hello, i try to crunch cosmology@home with virtualbox-workunits.

I found the svm argument for amd virtualization in the boinc log. I installed virtualbox and the extension manually, but boinc didn't recognize it.

How can i crunch vbox workunits? In the unraid apps descrition is written "It supports virtualized, parallel, and GPU-based applications." But how to use the virtualized ones?

Maybe it's possible that you include virtualbox in the unraid docker script?

Thanks for creating this great docker! Every other projekt works fine for me! 🙂

Link to comment
  • 3 months later...

Anyone else having any problems with this BOINC container? I think the container updated a couple of days ago.

 

I wondered into the WebUI today and all I see is a black screen. I usually get a BOINC manager screen.

I see that Openbox is running and a right mouse click gives me a menu. I checked the processes with "ps -aux" and don't see boinc running.

I tried running boincmgr manually and get an error (see attachment).

 

Any ideas?

 

1435490242_boincmgrerrorunRaid.thumb.png.47ad22b89857d3ebcba5639e63050178.png

Link to comment
On 2/4/2022 at 3:07 PM, nraygun said:

Anyone else having any problems with this BOINC container? I think the container updated a couple of days ago.

 

I wondered into the WebUI today and all I see is a black screen. I usually get a BOINC manager screen.

I see that Openbox is running and a right mouse click gives me a menu. I checked the processes with "ps -aux" and don't see boinc running.

I tried running boincmgr manually and get an error (see attachment).

 

Any ideas?

 

1435490242_boincmgrerrorunRaid.thumb.png.47ad22b89857d3ebcba5639e63050178.png

 

Nevermind. The latest update seems to have resolved the problem. I now get a BOINC Manager interface.

Edited by nraygun
Link to comment
  • 4 weeks later...
On 2/8/2022 at 3:54 AM, nraygun said:

 

Nevermind. The latest update seems to have resolved the problem. I know get a BOINC Manager interface.

 

I updated to the latest version (and uninstalled from CA/Apps, then installed again), but I am still getting a black screen. BOINC seems to start ok from the logs, but the X server seems to not be working correctly.

 

Log snippet shows:

 

X.Org X Server 1.20.13
X Protocol Version 11, Revision 0

Build Operating System: linux Ubuntu
Current Operating System: Linux 2bc7a65a4633 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64
Kernel command line: BOOT_IMAGE=/bzimage isolcpus=0-3 initrd=/bzroot

Build Date: 14 December 2021 02:14:13PM
xorg-server 2:1.20.13-1ubuntu1~20.04.2 (For technical support please see http://www.ubuntu.com/support)
Current version of pixman: 0.38.4

Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.

Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.

(++) Log file: ".xorgxrdp.10.log", Time: Wed Mar 2 13:36:53 2022
(++) Using config file: "/etc/X11/xrdp/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
xorgxrdpSetup:
xrdpdevSetup:
rdpmousePlug:
rdpkeybPlug:
rdpIdentify:
rdpDriverFunc: op 10

:
rdpProbe: found DRMDevice xorg.conf value [/dev/dri/renderD128]
rdpProbe: found DRI3 xorg.conf value [1]
rdpPreInit:
rdpPreInit: /dev/dri/renderD128 open failed

rdpScreenInit: virtualX 800 virtualY 600 rgbBits 8 depth 24
rdpScreenInit: pfbMemory bytes 1920000
rdpScreenInit: pfbMemory 0x1528d4def010
rdpSimdInit: assigning yuv functions
rdpSimdInit: cpuid ax 1 cx 0 return ax 0x00800f82 bx 0x1e200800 cx 0x7ed8320b dx 0x178bfbff
rdpSimdInit: sse2 amd64 yuv functions assigned
rdpClientConInit: disconnect idle session after [0] sec
rdpClientConInit: kill disconnected [0] timeout [0] sec

rdpXvInit: depth 24
rdpScreenInit: out
[20220302-13:36:20] [INFO ] starting xrdp with pid 485
[20220302-13:36:20] [INFO ] address [0.0.0.0] port [3389] mode 1
[20220302-13:36:20] [INFO ] listening to port 3389 on 0.0.0.0
[20220302-13:36:20] [INFO ] xrdp_listen_pp done
[20220302-13:36:52] [INFO ] Socket 11: AF_INET6 connection received from ::ffff:127.0.0.1 port 51584
[20220302-13:36:52] [DEBUG] Closed socket 10 (AF_INET6 :: port 3389)
[20220302-13:36:52] [INFO ] Using default X.509 certificate: /etc/xrdp/cert.pem
[20220302-13:36:52] [INFO ] Using default X.509 key file: /etc/xrdp/key.pem
[20220302-13:36:52] [DEBUG] TLSv1.3 enabled
[20220302-13:36:52] [DEBUG] TLSv1.2 enabled
[20220302-13:36:52] [DEBUG] Security layer: requested 3, selected 1
ssl_tls_accept: TLS connection accepted
colorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp)
[20220302-13:36:52] [INFO ] connected client computer name: Guacamole RDP
postBeta2ColorDepth 0xca01 (0xca00 4bpp 0xca01 8bpp 0xca02 15bpp 0xca03 16bpp 0xca04 24bpp)
highColorDepth 0x0010 (0x0004 4bpp 0x0008 8bpp 0x000f 15bpp 0x0010 16 bpp 0x0018 24bpp)
supportedColorDepths 0x0007 (0x0001 24bpp 0x0002 16bpp 0x0004 15bpp 0x0008 32bpp)
earlyCapabilityFlags 0x0421 (0x0002 want32)
got client client connection type 0x00000006
xrdp_sec_process_mcs_data_CS_SECURITY:
client and server support none crypt, using none crypt
[20220302-13:36:52] [INFO ] adding channel item name cliprdr chan_id 1004 flags 0xc0a00000
[20220302-13:36:52] [INFO ] adding channel item name rdpdr chan_id 1005 flags 0xc0800000
[20220302-13:36:52] [INFO ] adding channel item name rdpsnd chan_id 1006 flags 0xc0000000
error unknown xrdp_sec_process_mcs_data tag 0xc006 size 8

error unknown xrdp_sec_process_mcs_data tag 0xc00a size 8

 

Feels like I need to delete or reset something - any ideas?

 

Cheers,

 

Xav.

Link to comment
  • 5 weeks later...
  • 1 month later...
12 hours ago, xavierda said:

No, I ended up switching to cheesemarathon's app and managing remotely the BOINC instance using BOINC Manager from a Windows host. Works for me.

 

Xav.

 

I got on a Discord channel with the developers of the container and found that they had a parameter defaulting to a value that was causing my problem.

 

To resolve it, just remove the /dev/dri: parameter in the container.

Link to comment
  • 4 months later...

Hi!

Since I've added a GPU I've occasionally have had problems accessing BOINC through the incorporated Guacamole in the Docker.

Since last update, on the 24th of September, It never works.

I can access BOINC through the console and I can see it is working.

The errors that appear on the log are the following:


 

Quote

 

(EE) Failed to open authorization file ".Xauthority": No such file or directory

(...)

rdpClientConRecv: g_sck_recv failed(returned 0)
rdpClientConRecvMsg: error
rdpClientConCheck: rdpClientConGotData failed

 

 

Any idea on what could I do about it.

 

I would use the Official Unraid docker, but including the GPU looks cumbersome, and this one has been working fine for me for a long time.

 

Thank you

Link to comment
18 hours ago, acastellab said:

Hi!

Since I've added a GPU I've occasionally have had problems accessing BOINC through the incorporated Guacamole in the Docker.

Since last update, on the 24th of September, It never works.

I can access BOINC through the console and I can see it is working.

The errors that appear on the log are the following:


 

 

Any idea on what could I do about it.

 

I would use the Official Unraid docker, but including the GPU looks cumbersome, and this one has been working fine for me for a long time.

 

Thank you

 

Did you try removing the /dev/dri: parameter from your container? Stop the container, go to settings, remove /dev/dri, then restart the container and see if that helps. If it does, you'll have to do this every time the container is updated.

Link to comment
5 hours ago, nraygun said:

 

Did you try removing the /dev/dri: parameter from your container? Stop the container, go to settings, remove /dev/dri, then restart the container and see if that helps. If it does, you'll have to do this every time the container is updated.

 

I uninstalled the complete docker, deleted the image and reinstalled it from scratch.

 

Anyone trying to do the same, not only you have to remove /der/dri: parameter but also:

 

add the following parameter:

 

--runtime=nvidia 

 

and add an environment variable 

 

-e NVIDIA_VISIBLE_DEVICES=[GPU ID you find in the NVIDIA plugin]

 

And it works

  • Like 1
Link to comment

After 45 minutes it stopped working.

 

I read everything in the Nvidia Plugin support and tried different solutions to no avail.

 

In the end I extracted the GPU from the Unraid machine and inserted it to a bare metal ubuntu machine with BOINC and it worked fine.

 

Perhaps the plugin is not yet up to the workload BOINC puts on it, and I don't want it to break up my unraid machine with all my stuff on it.

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.