-
Posts
10,620 -
Joined
-
Days Won
51
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by CHBMB
-
-
1 hour ago, OOmatrixOO said:
Ok now i understand what's going on. Thanks.
So i have to change abc to my user and then it should be working. Will try it.
The only thing I'd caution against that approach is a location inside the container is on your docker.img so a session of error log spamming will fill up your docker image. I'd suggest moving it to somewhere in /config so at least it's on your cache disk.
-
1 hour ago, gweari said:
I have the docker pointing to where everything needs to be. It is set up the same way as Radarr and Radarr works perfectly.
The issue I am running into is that Sonarr isn't moving my completed shows from the completed folder.
My /downloads path is: /mnt/user/MyMedia/ which is where my completed folder is and
My /tv path is: /mnt/user/MyMedia/Tv Shows/
I am using the linuxserver Sonarr
Any help is greatly appreciated. I have been having this issue for a long time now and have tried almost everything I have seen on forums and google.
Sonarr is creating the folders but nothing ever gets populated so i get 2-4x of the same show.
Not an Unraid support issue, use the dedicated support threads created for Sonarr.
-
13 minutes ago, jonathanm said:
Isn't docker compose command line?
Yup....
And as far as I'm aware there is no GUI tools for docker compose.
-
On 5/7/2019 at 9:17 AM, ICDeadPpl said:
Just curious, when is this going to be merged in template repo? It's been over a week since the announcement.
This has been merged now. Should be in CA within an hour or so.
-
It's not a ls.io issue. It doesn't break anything, it just requires a direct address to disk.
As to whether the actual issue is kernel, Unraid, Docker, Sqlite or Sonarr/${Application} I have no idea and to be honest, I don't see it as a significant issue.
Why you would want all your appdata for Sonarr spread across an array anyway is beyond me, and I would recommend keeping it all on one disk for that very reason.
I think you see this as a bigger deal than it actually is
Also, for some reason it doesn't seem to affect everyone, some people get away with it with no problems at all, others don't, hence you could probably throw hardware into the mix as a possible cause.
If you wish to go down the rabbit hole to try and get to the bottom of it, feel free.
Sent from my Mi A1 using Tapatalk -
Also, the problem seems to be isolated to sqlite databases.
Sent from my Mi A1 using Tapatalk- 1
-
It's not our issue to fix and by design appdata is meant to reside on cache. It makes far more sense to have appdata localised to one disk anyway and no real sense to write it directly to the array as that slows things down considerably and causes issues.Wow, really, that seems like a major problem for any code that relies on file system locking to work like a local fs?
If I am now forced to use a single disk for any app that relies on fs locking, it also breaks the intent of a resilient filesystem, i.e. my app dies when the disk dies, vs. my app dies when disk plus parity dies?
If I did add a cache, would BTRFS be impacted by fuse, I assume not?
Any pointers to docs about the issue with fuse and locking, or plans to address the issue?
Also, protected array is not the same as backups, appdata should be backed up, not relying on parity protection.
Sent from my Mi A1 using Tapatalk
-
8 hours ago, fr05ty said:
tonight my plex app crashed caused my unraid server to need a reboot upon doing so i had a problem loading plex and emby up, I looked in the logs to see
and when i went in to my nvidia plugin my p2000 does not show up but it is listed in iommu group 28 under system devices, I'm on ver 6.7
Here's your error here, as we've mentioned several times in the thread, there's a bug in the forums that pastes extra (invisible characters) to your command.
unknown device id: GPU-cc63faa0-8033-52ac-dad4-79279b371033\\\\n\\\"\"": unknown
This bit looks very suspicious of that.
\\\\n\\\"\""
Try typing the GPU id in manually.
-
-
Turn off all autostarting VMs if possible and reboot Unraid.tonight my plex app crashed caused my unraid server to need a reboot upon doing so i had a problem loading plex and emby up, I looked in the logs to seekernel: nvidia-uvm: Loaded the UVM driver in 8 mode, major device number 245kernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)kernel: NVRM: rm_init_adapter failed for device bearing minor number 0iceberg kernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)kernel: NVRM: rm_init_adapter failed for device bearing minor number 0rc.docker: PlexMediaServer: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:407: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/local/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-runtime-hook.log --ldcache=/etc/ld.so.cache configure --ldconfig=@/sbin/ldconfig --device=GPU-cc63faa0-8033-52ac-dad4-79279b371033 --compute --compat32 --graphics --utility --video --display --pid=31670 /var/lib/docker/btrfs/subvolumes/4787b541f516ce4d01faa8f10f4dfed05c53589f0b299ae78d883bc14cdc346d]\\\\nnvidia-container-cli: device error: unknown device id: GPU-cc63faa0-8033-52ac-dad4-79279b371033\\\\n\\\"\"": unknownrc.docker: Error: failed to start containers: PlexMediaServerkernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)kernel: NVRM: rm_init_adapter failed for device bearing minor number 0kernel: NVRM: RmInitAdapter failed! (0x31:0xffff:834)kernel: NVRM: rm_init_adapter failed for device bearing minor number 0rc.docker: EmbyServer: Error response from daemon: OCI runtime create failed: container_linux.go:344: starting container process caused "process_linux.go:424: container init caused \"process_linux.go:407: running prestart hook 0 caused \\\"error running hook: exit status 1, stdout: , stderr: exec command: [/usr/local/bin/nvidia-container-cli --load-kmods --debug=/var/log/nvidia-container-runtime-hook.log --ldcache=/etc/ld.so.cache configure --ldconfig=@/sbin/ldconfig --device=GPU-cc63faa0-8033-52ac-dad4-79279b371033 --compute --compat32 --graphics --utility --video --display --pid=32044 /var/lib/docker/btrfs/subvolumes/6ea3c2c0c5428be0afad1d23b1f459f821776f1dcf923641c55aae2b4acdd312]\\\\nnvidia-container-cli: device error: unknown device id: GPU-cc63faa0-8033-52ac-dad4-79279b371033\\\\n\\\"\"": unknownrc.docker: Error: failed to start containers: EmbyServer
and when i went in to my nvidia plugin my p2000 does not show up but it is listed in iommu group 28 under system devices, I'm on ver 6.7
Sent from my Mi A1 using Tapatalk
-
I'm starting to suspect this is a Plex issue. No Emby users have reported an issue, and three similar reports recently.
Are any of you or all of you using the decoding patch for Plex?
Sent from my Mi A1 using Tapatalk -
Ignore it, discussed elsewhere in this thread and on GitHub. Harmless error if you're not using Lua and is a problem with the upstream project.Reinstalled Letsencrypt and add some of the Conf files but am still getting.
nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)
nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:
no field package.preload['resty.core']
no file './resty/core.lua'
no file '/usr/share/luajit-2.1.0-beta3/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core.lua'
no file '/usr/local/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/5.1/resty/core.lua'
no file '/usr/share/lua/5.1/resty/core/init.lua'
no file '/usr/share/lua/common/resty/core.lua'
no file '/usr/share/lua/common/resty/core/init.lua'
no file './resty/core.so'
no file '/usr/local/lib/lua/5.1/resty/core.so'
no file '/usr/lib/lua/5.1/resty/core.so'
no file '/usr/local/lib/lua/5.1/loadall.so'
no file './resty.so'
no file '/usr/local/lib/lua/5.1/resty.so'
no file '/usr/lib/lua/5.1/resty.so'
no file '/usr/local/lib/lua/5.1/loadall.so')
As I am pretty new to all this any help would be gratefully appreciate.
Sent from my Mi A1 using Tapatalk
-
Screenshot of the plugin page please. This is strange, we know v6.7.0 is working, so it must be something specific to you.No VMs have ever run on this hardware.
Sent from my Mi A1 using Tapatalk
-
And the card isn't being used by a VM?The fields were all typed, not copied and pasted. I've tried multiple times.
Version is 6.7.0
Im using a GTX1050, which I can see from nvidia-smi so not a hardware issue.
Sent from my Mi A1 using Tapatalk
-
Might be nice if you told us what version of Unraid you're using too.
All the releases other than v6.7.1rc1 are tested.
Not sure I've seen any reports of that yet.
Sent from my Mi A1 using Tapatalk -
This is now in CA
-
6 minutes ago, Der_Eine said:
No, it is not. I copied the pw directly from the mariadb edit window.
Run this to check:
docker exec -it mariadb bash msyql -uroot -p
If that works then paste a screenshot of the settings before you submit them on the Nextcloud setup page
-
2 hours ago, Der_Eine said:
Hello,
I got a problem while trying to install nextcloud with the mariadb database docker. I can connect to the nextcloud webui but when I completed anything i got the following message:
Error while trying to create admin user: Failed to connect to the database: An exception occurred in driver: SQLSTATE[HY000] [1045] Access denied for user 'root'@'172.17.0.1' (using password: YES)
Do anyone knows what I can do to fix that? Sorry for my bad english Im from Germany...
Thank you
Looks like the root password for your database is wrong
-
17 minutes ago, monogoat said:
I can reinstall the container and provide you with any information you need to help fix, if it doesn't appear isolated to my configuration
Fix has been merged, so if you try again it should work now.
-
1 minute ago, monogoat said:
I can reinstall the container and provide you with any information you need to help fix, if it doesn't appear isolated to my configuration
It's OK thanks, I think I've isolated it and have submitted a PR to fix it.
-
3 minutes ago, monogoat said:
I'm sorry for any confusion, I have it working with the NginxProxyManager so I didn't want to bother using up anyone's time trying to troubleshoot this problem. Thanks for everything you guys do.
Actually I'm already looking at it, I *think* it's a problem with a python package.
-
4 minutes ago, monogoat said:
Well all I did when adding it from CA was add in the ports, 80 and 443, the email and the domain. In the mean time I installed NginxProxyManager and it is working fine, so I'll stick with it for now.
Thanks
If you don't provide us with the information, we can't help.
-
v6.7.1rc1 just uploading.
- 1
-
Just uploading v6.7.1rc1 for all versions.
- 1
- 2
Add a module for full Docker Swarm please?
in Feature Requests
Posted
@bonienl This topic has been bumped in three different places this morning, here, here, and here.
I would suggest the topic here is the most appropriate one as it actually defines the kernel requirements to run swarm, although I haven't tested (and am not going to as I have zero interest in swarm on Unraid.)
From an Unraid-Nvidia plugin I can state that my position is we won't add it. The project was never designed to modify Unraid any more than add drivers and enable the ability to utilise them in containers, and I'm not modifying .config every time I build a new release as I have to do that with the DVB kernel releases and it's a PITA.
If @limetech wish to include the module in the kernel then Unraid-Nvidia will naturally follow being downstream.