CHBMB
-
Posts
10620 -
Joined
-
Days Won
51
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by CHBMB
-
-
-
Nextcloud is an exception for technical reasons.I had always thought we were supposed to update an application outside of the docker. Thank you!
Sent from my Mi A1 using Tapatalk
-
1
-
-
If you read the first post, this is discussed with links.How do you upgrade to 17? I have updated my docker and it is still on v16.
Sent from my Mi A1 using Tapatalk
-
You haven't mentioned your card. Probably hardware restriction on Nvidias part.y emby only transcodes two streams in paralell via nvenc ?
Try and include relevant information next time you post and it'll help get a better answer.
Sent from my Mi A1 using Tapatalk
-
Here's the commands to run. Please try this those of you that are seeing the nvidia-smi stuff and let me know if it fixes it, my suspicion is it will.
-
3 hours ago, eds said:
I was afraid you would write that...
Yes, the desktop client is the issue. I should have been clearer. It's when I reboot the windows machines I need to re authenticate, not rebooting the server. That link appeared to be saying the missing file was on the server side.
Anyway, is there a way to debug this?
There probably is, but I don't know how. I still think it's a client side issue tbh.
-
Yeah, if the plugin is installed but you haven't
1. Downloaded the custom Nvidia build &
2. Rebooted
You will see nvidia-smi errors as the plugin parses the installed cards at boot using nvidia-smi then writes that info to a temp file which is then utilised from then on.
Problem is, for everyone posting that nvidia-smi error it doesn't really mean anything as all it says to me is
"At the time of boot, when nvidia-smi was run, a card wasn't able to be found"
That's not to say the card didn't load the kernel drivers later in the boot cycle and would work perfectly regardless
I'll put the beast to bed then post a command for people to test the theory.
Why this is suddenly an issue, no idea....
Sent from my Mi A1 using Tapatalk -
That's very kind of you, thank you.I will perform the update during the holidays and report back to you.
In the meantime I have sent a donation your way. Thanks to everybody contributing to this project! Your work truly has improved my quality of life.
Since the donate link is buried in this thread, I’m posting it below, in case other people feel compelled to donate as well.
https://www.linuxserver.io/donate
Sent from my Mi A1 using Tapatalk
-
6 hours ago, Pokey said:
Hello, I really need help with nextcloud i get everything with mariadb and nextcloud just the letsencrypt part is messing me up.Heres the error i am getting.
Challenge failed for domain pokey.ddns.net
http-01 challenge for pokey.ddns.net
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: pokey.ddns.net
Type: connection
Detail: Fetching
http://pokey.ddns.net/.well-known/acme-challenge/KrfzfxBK7A7T_X35-D_D_gnPHHDOfO8GKK2yVPKkqdA:
Timeout during connect (likely firewall problem)
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
ERROR: Cert does not exist! Please see the validation error above. The issue may be due to incorrect dns or port forwarding settings. Please fix your settings and recreate the containerThat's an error with LetsEncrypt, nothing to do with Nextcloud. You're not going to be able to get any further until you sort that out. Suggest you post in the LetsEncrypt support thread, including the above log and with your docker run command (see the docker faq to find out how to get that) and screenshots of your port forwards in your router/firewall.
-
10 hours ago, phasetwo said:
I have been using a Quadro P600 from the earliest Nvidia Unraid builds with nvidia-smi and am currently running 6.8.0-rc7 without any issues regarding transcoding and using nvidia-smi commands.
Hope this helps.
I would also like send my heartfelt thanks to everybody involved with the plugin and the builds! Your work is truly appreciated!
Thanks for confirming, I'll be interested to see your findings on v6.8.0 final.
-
So it's working?when I run the update command
sudo -u abc php7 /config/www/nextcloud/occ upgrade
Nextcloud is already latest version
I'm in 17.0.1...
Sent from my Mi A1 using Tapatalk
-
Then it may just be nvidia-smi isn't supported. Try to transcode with it anyway. Nvidia-smi is a CLI tool for interacting with the card, not necessary for it's use.According to the compatibility list at https://www.nvidia.com/download/driverResults.aspx/154997/en-us it is.
Have you used previous versions of the Unraid plugin without issue?
Or is this the first time you've tried?
Sent from my Mi A1 using Tapatalk
-
Is the P600 supported by this driver version?I have installed 6.8.0, but my P600 isn't recognised. I get the following:-
I have tried the following:-$ nvidia-smiNVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running.
I'm not sure where to go from here. Can anyone suggest what I should try next? Thanks.
Sent from my Mi A1 using Tapatalk
-
14 minutes ago, eds said:
I'm still running Nextcloud 16 and I have been having the annoying task of re authenticating my windows client machines to access nextcloud docker after each reboot.
According to this thread, some servers seem to require libgnome-keyring.
Is that true of the nexcloud docker and if show, how to add?
That thread is in reference to the desktop client. libgnome-keyring is a Linux desktop package for the Gnome desktop. So basically nothing related to your problem with Windows clients
-
37 minutes ago, Nosirus said:
how to update?
I have the error
"Check for expected files
Parsing response failed. File not found."
in nextcloud.
Try the terminal, it's more reliable in general.
-
Docker run command for both is required.I'm currently "drinking from the fire hose" and setting up my first Unraid server. I've found what appears to be a conflict between this docker and this same groups Unifi controller docker. I can't have them both running at the same time without losing access to NZBGet. The log fills with "[ERROR] Binding socket failed for 0.0.0.0: ErrNo 98, Address in use".
I think I understand what the error signifies but Unraid shows no port conflicts between the two dockers. It also doesn't matter which order I start them in, if both are running at the same time, NZBGet loses. While the log is flooding with the error I cannot connect to NZBGet's GUI - the browser tab just hangs.
Both dockers are fresh installations as this entire server is a new build.
Thanks in advance for any assistance.
You can see how by either turning on signatures in the forum, and the link is in mine, or by reading the docker faq.
Sent from my Mi A1 using Tapatalk
-
32 minutes ago, frakman1 said:
In their infinite wisdom, the creators of this app made the password field be the md5 hash of your actual password. See my earlier post here for details on how to set it.
You could always submit a pull request to change it.
-
11 hours ago, Nimrad said:
I tried that now. Still the same problem. I save my settings and everything is fine. Quit the webUI and restart the docker container and now it’s unreachable.
You're not changing the port in the webui are you?
Otherwise as @trurl says, post your docker run command.
-
11 hours ago, tmchow said:
This isn’t updating the driver by itself this is updating unraid which I know how to do
I was understanding that post I quoted to mean we could update the drivers independently (which others have corrected me saying you can’t)
Technically you can.
1. Install all the required dependencies.
2. Recompile the Linux kernel including any OOT drivers
3. Install more dependencies, including compiling some Nvidia dependencies from source like Go, which takes an age.
4. Compile the Nvidia drivers, there's a tiny bit of hackery here as there's no desktop environment by default in Unraid so it fails without (iirc it's something to do with the GTK toolkit, I can't remember how I fixed it in the end, I think I removed part of the Slackbuild to skip that bit as we don't need it)
5. Compile the Nvidia docker runtime and libseccomp
6. Change the docker daemon json config
7. Pull apart Unraid to it's component files, install all the bits and bobs then put it back together.
Before we made this everyone was asking for the Nvidia drivers, problem is, that doesn't solve the problem of utilising them in the docker containers, actually compiling the drivers and making Slackware packages is the easy bit of the whole thing, problem is if you install at boot time like many other slackware packages you get a kernel panic. (Probably because it's too late in the boot process) In fact, when I started this process, that was the approach I initially took, install everything at boot time.
To put it into perspective, we have scripted this whole process and using 24 threads on my server, with 32GB of RAM, it still takes ~ 30-40 minutes to get through the whole thing.
-
3
-
1
-
-
2 hours ago, reggierat said:
Now i realise this is probably outside the bounds of what is supportable, but i have noticed since moving to unraid nvidia that the sleep plugin causes an unclean shutdown when attempting to put the server to sleep.
I have tested this with unraid nvidia 6.7.2 and 6.8, stock unraid the sleep plugin correctly puts the server into s3 sleep and i'm able to easily wake it.
Is this worth investigating or do i just give up on s3_sleep?
The decision is down to you, but I doubt many of us use s3 sleep so you're probably going to be by yourself figuring it out.....
-
1
-
-
-
Look on docker hub, probably your best bet.
-
You might want to add those lines to a user.scripts script to be run on array start.Correct. All seems well again. Thanks for all the hard work you guys do.
Sent from my Mi A1 using Tapatalk
-
So you 100% sure that RC9 works and v6.8.0 doesn't, that's weird as I used the same config.i upgraded to 6.8 rc9 libreelec and it pulls down the dvb folder, all is good with this one
Sent from my Mi A1 using Tapatalk
I was understanding that post I quoted to mean we could update the drivers independently (which others have corrected me saying you can’t)
[Support] Linuxserver.io - Sickchill
in Docker Containers
Posted
If you're sure you're running the latest version of our container then it must be a sickchill issue as we're building from master and it's up to date.
https://github.com/SickChill/SickChill/commits/master
https://github.com/linuxserver/docker-sickchill/releases/tag/2c72459d-ls28