CHBMB
-
Posts
10620 -
Joined
-
Days Won
51
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by CHBMB
-
-
What's that got to do with Calibre-web?I can't seem to get LL to connect to my SABnzbd install on my unRaid server. Sonarr and Radarr and others have no problem. I "save" my config in LL before testing, but nothing that I do manages to actually get LL to connect to SAB.
Any ideas? Thanks!
You've mentioned several different containers, none of which are related to this support thread.....
Sent from my Mi A1 using Tapatalk
-
8 hours ago, xxlbug said:
1. The unraid machine is running for 99 days without problems, since I’m not home i don’t want to upgrade to unraid 6.8 currently
2. I don’t know how to get to debug logs for the Container/Sabnzbd, the normal log just says “opening browser at x.x.x.x:8080”... which is not helpful.
Have you looked in the logs folder in the appdata directory.
8 hours ago, xxlbug said:3. Is sab using files other than in the appdata dir which could still be corrupted?
No, although the docker.img file being full can give some pretty weird errors. Might be worth a look.
8 hours ago, xxlbug said:4. Could i see something in the unraid logs and not in the docker logs?
No, that's very unlikely, containers are isolated.
-
18 hours ago, Iceman24 said:
For this and any Docker, if the app has a shutdown feature within the app itself, should I do that before updating the Docker from unRAID?
No, I've never known that to be necessary and due to the init system used in the container, it's probably futile.
-
1
-
-
The settings page just reads a record of what cards were present at boot, it isn't dynamically loaded at each page load.Occasionally my GPU seemingly 'disappears' from Unraid/Docker. Running nvidia-smi produces:
but if I check Settings/Unraid Nvidia the device is still present:
The server log is filled with some nvidia driver errors:
A server reboot usually fixes the issue but it's rather annoying. How would I go about debugging this?
Running 6.8.0
EDIT: Just after I posted this nvidia-smi showed the card correctly and the docker containers that use the GPU were working correctly, I did not reboot. It basically just showed back up again.
Your card is dropping out on occasion. The cause could be anything.
Try a different slot, BIOS up to date.
Different Unraid version and/or associated Nvidia version, but ultimately there's not much I can do to help unless you conclusively identify a driver issue and even then you're probably going to have to wait until a new upstream driver is released.
Sent from my Mi A1 using Tapatalk
-
3 minutes ago, tylaw1011 said:I tried latest again just now and experience the same issue.
Try a force update as it's definitely working here. If that doesn't do it, then provide your docker run command and container logs.
-
The thing I like the most about Unraid is the community, I've been here longer than any other forum I've ever frequented, "met" some people who I consider good friends, some of whom I've now met in real life, and continue to speak to in one form or another on pretty much a daily basis and have shared our tales or marriages, births, highs and lows, some of whom I'd love to meet in the future, and undoubtedly will.
From a diehard Windows guy back in 2011 when I first came to Unraid, it's been the gentle introduction to Linux I needed after playing around with Ubuntu a few years previously and sucked me into the virtues of a Linux based server operating system and ultimately converted my house to a fully Linux based household, (OK my wife still has a Windows laptop, but that's used for nothing more than Chrome (another sore point) and MS Office (yet another sore point).
With the support of some prominent community members help over the years I've developed skills and knowledge I never thought I had in me, and continue to do so on a daily basis.
I came to Unraid in the v4.7 days because it was "easy" to maintain, now in our third major version which continues to develop and become more and more impressive I stay because in my opinion, there just isn't a better home server solution out there. Sure you can roll your own, and I don't shy away from a terminal, but even the solutions that are sometimes named, just don't compare with Unraid.
Notice above I use the words "our third major version" this was without thinking, but on reflection, shows how I view Unraid, yes it's a (remarkably good value) paid product produced by LimeTech, but there are so many other contributors over the years that give it a community and sense of joint ownership that nurtures it, extols it's virtues and enables it to continue to flourish!
The one thing I'd like to see in 2020 is a tricky one, for me Unraid does everything I need it to do right now. I could see myself using multiple arrays if that feature was added.
-
On 12/29/2019 at 2:48 AM, BRiT said:
Hell no, no SystemD at all.
That was exactly the response I predicted from you! I've been hanging around here for too many years 🤣
-
1
-
-
1 hour ago, Rokk said:
Do you know how I can compile unraid 6.8.0 with nvidia and dvb (Libreelec) drivers?
Or do you know someone, who has the needed skills and whould be so kind to do that for me?
That would be a yes from me, as I maintain both. As I've mentioned before I don't have the free time to develop this at the moment, due to work commitments and an impending new baby.
FWIW, I've bought an external ethernet DVB device, so no longer use the DVB plugin, although I still maintain it. You're getting sound advice from @BRiT
To put it in perspective, the $60 you paid for your hardware is nowhere near going to cover the cost in time if I were to charge for developing a dual DVB/Nvidia build. (not that I do charge, but just to give you an idea of what you're asking for)
It would have been prudent to ask some questions before paying out for hardware. Remember that neither Nvidia or DVB are developed by LimeTech, they are maintained by the community (well me for DVB & me & @bass_rock, in the case of the Nvidia plugin)
-
30 minutes ago, dockerPolice said:
Doesn't appear to be
Since there's been zero traction on this thread and @dexn hasn't posted in 2.5 years and there looks to be far better alternatives on a quick search in dockerHub, I'm going to be removing this from CA unless there are any objections
I think the police have the wrong guy in custody.......
dexn has an alibi, you mean McCloud
-
Not tried it myself, but if I were to, that'd be how I'd do it.Hi,
Do to very slow loading of pictures I've added Redis to Nextcloud by putting this into the config.php
'memcache.local' => '\\OC\\Memcache\\Redis',
'memcache.locking' => '\\OC\\Memcache\\Redis',
'redis' => array(
'host' => 'MY SERVER IP',
'port' => 6379,
),
I've then added the Prieveiw Generator app.
Ran this command inside the Nextcloud docker console:
sudo -u abc php7 /config/www/nextcloud/occ preview:pre-generate
Then added this to a cron job to run weekly:
docker exec -i nextcloud sudo -u abc php7 /config/www/nextcloud/occ preview:pre-generate
So, basically I would like to know if this all correct and no other steps are needed?
Thanks!
Sent from my Mi A1 using Tapatalk
-
My two cents.
Docker compose is a simple cli way to manage containers.
I personally don't see the value in including it in Unraid if people actually want a GUI to manage it, for Unraid that would be like reinventing the wheel and also require every XML template to be rewritten, as well as Dockerman, neither are an attractive proposition.
If however people want to manage containers using compose then there is easy access to the terminal from the GUI.
I haven't checked if Slackware current has a more recent docker compose version but wouldn't be surprised if it does, in which case someone could submit a PR to NerdPack.
Sent from my Mi A1 using Tapatalk -
That command shouldn't work as you need to use php7 instead of phpi have a huge issue... i went ahead and updated to the latest version of nextcloud and now i cant access my web application at all. i just keep getting the following error:
Any idea how to fix this? i dont think i will ever update this application again... but i need access to my files and this is driving me crazy. PLEASE HELP!
FIXED IT: Had to run this in the nextcloud terminal : sudo -u user php /config/www/nextcloud/occ upgrade
after i had to go and re-add a bunch of "apps" in nextcloud and update them... once done everything was back to normal on the latest version.
These commands are linked to from the first post.
Sent from my Mi A1 using Tapatalk
-
2 hours ago, DZMM said:
1. Should I use linuxserver/sonarr:preview now?
Yes
2 hours ago, DZMM said:2. Was it safe to just switch the repository in docker? It worked, but I kept a backup just in case
Yes, albeit, running a preview build, stuff goes wrong, you're on your own.
-
1
-
-
@hernandito This is being discussed here https://github.com/linuxserver/docker-nzbget/issues/91
-
15 hours ago, hernandito said:
Hi Gang,
I am now getting Post Processing errors when using NZBtoSickbeard. This was properly working before. The error I am getting is:
Fri Jan 03 2020 12:57:47 INFO Executing post-process-script nzbToSickBeard.py for Messiah.2020.S01E02.MULTi.1080p.WEBRip.x264.1-S0CKET-Obfuscated Fri Jan 03 2020 12:57:47 INFO nzbToSickBeard: Please use a newer version of Python. Fri Jan 03 2020 12:57:47 INFO nzbToSickBeard: Python End-of-Life for current versions: Fri Jan 03 2020 12:57:47 INFO nzbToSickBeard: v3.5 in 254 days Fri Jan 03 2020 12:57:47 INFO nzbToSickBeard: v3.6 in 720 days Fri Jan 03 2020 12:57:47 INFO nzbToSickBeard: v3.7 in 1271 days Fri Jan 03 2020 12:57:47 INFO nzbToSickBeard: v3.8 in 1746 days Fri Jan 03 2020 12:57:47 INFO nzbToSickBeard: Python 2.7 is no longer supported. Fri Jan 03 2020 12:57:47 ERROR Post-process-script nzbToSickBeard.py for Messiah.2020.S01E02.MULTi.1080p.WEBRip.x264.1-S0CKET-Obfuscated failed (terminated with unknown status) Fri Jan 03 2020 12:57:47 INFO Collection Messiah.2020.S01E02.MULTi.1080p.WEBRip.x264.1-S0CKET-Obfuscated added to historyI can see that NZBGet is using Python 2.7... but it wants a new version. I am not sure if this will solve my issue.
Any advise is greatly appreciated.
Thanks,
H.
UPDATE:
So It is the fault of Python being an older version. I tried the following commands inside the docker container:
apk update && apk add --no-cache python3 rm /usr/bin/python ln -s /usr/bin/python3 /usr/bin/python python --versionI can certainly certainly a script that runs the above... But shouldn't the Docker be updated for this?
Thanks,
H.
Python is a bit of a mess at the moment, some projects have been updated to python 3, some are still in the midst of migration, the approach we're currently taking is to include python2 and python3 if the underlying project and it's common plugins/scripts.
https://github.com/linuxserver/docker-nzbget/commit/c87dc842020ee2b0f018c6f16cf15b1ff9d41c53
Looks like nzbtomedia has done some backtracking from it's python2 to python3 migration. New release 5 mins ago adds back python2 compatibility
https://github.com/clinton-hall/nzbToMedia/releases
So, bottom line, container already has python 3 now, and the scripts causing the issue have been reverted to continue to support python 2.
So, if you wish to migrate to python 3 I wonder if the shell override is the way forward to avoid getting down and dirty with the terminal.
-
15 hours ago, tylaw1011 said:
With Booksonic being deprecated in favor of Booksonic Bridge according to the dev, are there going to be any more updates to this container?
Yeah, even if the underlying Booksonic code isn't updated. the container still receives updates. If/when he releases another project to replace Booksonic in it's current guise then we'll obviously reassess things, but from your point of view at the moment, nothing has changed.
It's not really as though booksonic has seen much dev over the last few years anyway.
-
15 hours ago, tylaw1011 said:
Will the 404 error that's holding us at ls46 be resolved at least?
That was fixed a while ago
-
Memory leak in Plex is not something I can do much about with this plugin....Hi guys,
posted this in the plex forum (lnio) but thought I should place here as well. Installed a quadro p2200 and unraid 6.8 stable and have a crazy memory leak in plex. Never had this before installing this plugin and the p2200 being added. Anyway, I'm attaching the diagnostic file here as well. Any help would greatly be appreciated.
ps. I had a sata error but have fixed that by moving cable to another sata connector on the motherboard..no errors with this anymore
unraid-diagnostics-20200101-0804.zip
Sent from my Mi A1 using Tapatalk
-
1
-
-
If you scroll up to the last few of my posts this sort of thing has been discussed.I have a similar problem, the P5000 and P4000 (one in my server) are supported by this driver version (see snip)?
My 710GT and 1080 both showed up in the Info page, and the 1080 disappeared when it was being used as pass through for my VM, but the Quadro P4000 does not show up on the Info page even tho it is showing up in the system devices page.
Is there a way to get the UUID in a another manor and still try passing it through to the docker? Or will it not work at all if its not detected on the Unraid Nvidia page?
Sent from my Mi A1 using Tapatalk
-
You can't passthrough a card you are using for transcoding in Plex, it's one or the other.Hello,
Am I missing something as I do not see my Nvidia quadro p2000 card in the IOMMU list even though Unraid Nvidia works with no issues and transcodes for plex.
I do have HVM and IOMMU enabled.
I wanted to pass this through to a VM and I did do a search first, but the thread is 60 pages long so i do apologize if I missed something blatantly obvious.
Any help is appreciated. Thanks!
Sent from my Mi A1 using Tapatalk
-
Uninstall the plugin to remove the nvidia-smi line, that's part of the plugin install at boot to parse the cards.I can boot into safe mode and looking at boot the plugin seems to build a new kernel with the nvidia drivers.bzfirmwarebzimagebzmodulesbzrootbzroot-gui
Does this plugin back the previous kernel up somewhere before overwriting? Is there some way just to pass a kernel param to stop the drivers from loading?
Thanks again for any help that can be provided. I realize I put myself in quite the pickle and am relying on others to help fix my screw up.
Update: I managed to get it booted after a hard shutdown and start. I used the plugin to install the stock version of 6.8.0 and everything boots fine.
There is one thing on the startup staying that:/bin/bash: line 14: nvidia-smi: command not found
I know this will not affect anything but is there a way to fix this?
The plugin is merely a conduit to download a different version of Unraid with the drivers built in. It doesn't compile anything at boot time.
Sent from my Mi A1 using Tapatalk
-
I haven't done this for a few years, but iirc I hosed everything except my user data and then used occ to scan everything back in after afterwards.What is the correct way to "remove" the nextcloud, leaving MariaDB and Letsencrypt intact, and not compromising the nextcloud data? I hope that reinstalling the docker afterwards may fix the problem.
Sent from my Mi A1 using Tapatalk
-
2 minutes ago, levster said:
17.0.1
If it were me, I'd first make sure stuff is backed up then try running the full upgrade from the CLI
-
@levster What version were you on? Because if you were on 15 and trying to upgrade to 17 that would explain the error.
[Plugin] Linuxserver.io - Unraid Nvidia
in Plugin Support
Posted
You've obviously got some ideas, why not do it?
Problem is I see time and time again, is people keep telling us what we should be doing and how quick we should be doing it, now, don't be offended because this is a general observation, rather than personal.
It's ten to one in the morning, I've just got back from work, I have a toddler that is going to get up in about five hours, my wife is heavily pregnant, Unraid Nvidia and beta testing just isn't up there in my list of priorities at this point.
I've already looked at it and I need to look at compiling the newly added WireGuard out of tree driver.
I will get around to it, but when I can. And if that means some Unraid users have to stick on v6.8.0 for a week or two then so be it, or, alternatively, forfeit GPU transcoding for a week or two, then so be it.
I've tried every way I could when I was developing this to avoid completely repacking Unraid, I really did, nobody wanted to do that less than me. But, if we didn't do it this way, then we just saw loads of seg faults.
I get a bit annoyed by criticism of turnaround time, because, as this forum approaches 100,000 users, how many actually give anything back? And of all the people who tell us how we should be quicker, how many step up and do it themselves?
TL:DR It'll be ready when it's ready, not a moment sooner, and if my wife goes into labour, well, probably going to get delayed.
My life priority order:
1. Wife/kids
2. Family
3. Work (Pays the mortgage and puts food on the table)
@Marshalleq The one big criticism I have is comparing this to ZFS plugin, no disrespect, that's like comparing apples to oranges. Until you understand, and my last lengthy post on this thread might give you some insight. Please refrain from complaining. ZFS installs a package at boot, we replace every single file that makes up Unraid other than bzroot-gui.
I've said it before, I'll say it again. WE ARE VOLUNTEERS
Want enterprise level turnaround times, pay my wages.