uraid
-
Posts
40 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by uraid
-
-
42 minutes ago, Djoss said:
Somehow permission on the first 2 files have changed. They should not have the execute permission...
Removing and re-installing the image is probably not working because these files are part of the baseimage. So you also need to remove all images that depend on the same baseimage (e.g. MakeMKV, MKVToolNix).
Removing all images that depend on the baseimage and reinstalling fixed that
Thank you for the help!!
-
5 minutes ago, Djoss said:
Can you try to run and report the output of the following command, replacing "<DIR>" by your data-root directory ?
find <DIR> -type f -name XDG_CONFIG_HOME -exec ls -l {} ';'> find /mnt/user/system/docker -type f -name XDG_CONFIG_HOME -exec ls -l {} ';' -rwxr-xr-x 1 root root 19 Mar 4 00:41 /mnt/user/system/docker/docker/overlay2/1b4c1a6ce7c69003987c594a5c290aadc8bffb182520255ac0437467d8d0e296/diff/etc/cont-env.d/XDG_CONFIG_HOME -rwxr-xr-x 1 root root 19 Mar 4 00:41 /mnt/user/system/docker/docker/overlay2/43e0ae77fc00c2938365c254110c931a887d5081f804135b462180553d366b2a/diff/etc/cont-env.d/XDG_CONFIG_HOME -rw-r--r-- 1 root root 15 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/9dea0516110d7786064b03a3d40baf3dc5c33c025b60e09722ac19393e99a443/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 15 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/9dea0516110d7786064b03a3d40baf3dc5c33c025b60e09722ac19393e99a443/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/3773e9a5770523a0d13e0333e1dc26f0e8fa2c66599458a46d6eed46fbba79a2/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/3773e9a5770523a0d13e0333e1dc26f0e8fa2c66599458a46d6eed46fbba79a2/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/24692c298fd3025a60186296661d0a75f584e7ab7fed986afdb45dcf1b15a686/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:18 /mnt/user/system/docker/docker/overlay2/24692c298fd3025a60186296661d0a75f584e7ab7fed986afdb45dcf1b15a686/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/52a704cda63af32cff7eda72a87a90ceebcb8a5b68e56c4696550c275297be63/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/52a704cda63af32cff7eda72a87a90ceebcb8a5b68e56c4696550c275297be63/merged/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 7 Apr 24 06:01 /mnt/user/system/docker/docker/overlay2/4f22de215505b404c4efdd239d47729e5076bdfb642f855ef5c2de9e4fd12851/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/8332619b68ec53c3d0ac9a664723c4ea3788f8ffcaeae9a745998ecf0c64d508/diff/run/s6/container_environment/XDG_CONFIG_HOME -rw-r--r-- 1 root root 11 Apr 25 18:24 /mnt/user/system/docker/docker/overlay2/8332619b68ec53c3d0ac9a664723c4ea3788f8ffcaeae9a745998ecf0c64d508/merged/run/s6/container_environment/XDG_CONFIG_HOME -
Unraid 6.12rc2, Docker data-root as directory on Nvme SSD
-
Nothing has changed unfortunately
-
On 4/15/2023 at 11:19 PM, Exes said:
Randomly starting to get this for jdownloader2. It used to work fine but crashes on startup every time now
04/15/2023 4:17:38 PM [init ] container is starting... 04/15/2023 4:17:38 PM [cont-env ] loading container environment variables... 04/15/2023 4:17:38 PM [cont-env ] APP_NAME: loading... 04/15/2023 4:17:38 PM [cont-env ] DISPLAY: executing... 04/15/2023 4:17:38 PM [cont-env ] DISPLAY: terminated successfully. 04/15/2023 4:17:38 PM [cont-env ] DISPLAY: loading... 04/15/2023 4:17:38 PM [cont-env ] DOCKER_IMAGE_PLATFORM: executing... 04/15/2023 4:17:38 PM [cont-env ] DOCKER_IMAGE_PLATFORM: /etc/cont-env.d/DOCKER_IMAGE_PLATFORM: line 1: linux/amd64: not found 04/15/2023 4:17:38 PM [cont-env ] DOCKER_IMAGE_PLATFORM: terminated successfully. 04/15/2023 4:17:38 PM [cont-env ] DOCKER_IMAGE_PLATFORM: loading... 04/15/2023 4:17:38 PM [cont-env ] DOCKER_IMAGE_VERSION: loading... 04/15/2023 4:17:38 PM [cont-env ] GTK2_RC_FILES: executing... 04/15/2023 4:17:38 PM [cont-env ] GTK2_RC_FILES: terminated successfully. 04/15/2023 4:17:38 PM [cont-env ] GTK2_RC_FILES: loading... 04/15/2023 4:17:38 PM [cont-env ] GTK_THEME: executing... 04/15/2023 4:17:38 PM [cont-env ] GTK_THEME: terminated successfully. 04/15/2023 4:17:38 PM [cont-env ] GTK_THEME: loading... 04/15/2023 4:17:38 PM [cont-env ] HOME: executing... 04/15/2023 4:17:39 PM [cont-env ] HOME: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] HOME: loading... 04/15/2023 4:17:39 PM [cont-env ] INSTALL_PACKAGES_INTERNAL: executing... 04/15/2023 4:17:39 PM [cont-env ] INSTALL_PACKAGES_INTERNAL: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] INSTALL_PACKAGES_INTERNAL: loading... 04/15/2023 4:17:39 PM [cont-env ] QT_STYLE_OVERRIDE: executing... 04/15/2023 4:17:39 PM [cont-env ] QT_STYLE_OVERRIDE: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] QT_STYLE_OVERRIDE: loading... 04/15/2023 4:17:39 PM [cont-env ] TAKE_CONFIG_OWNERSHIP: executing... 04/15/2023 4:17:39 PM [cont-env ] TAKE_CONFIG_OWNERSHIP: /etc/cont-env.d/TAKE_CONFIG_OWNERSHIP: line 1: 1: not found 04/15/2023 4:17:39 PM [cont-env ] TAKE_CONFIG_OWNERSHIP: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] TAKE_CONFIG_OWNERSHIP: loading... 04/15/2023 4:17:39 PM [cont-env ] XDG_CACHE_HOME: executing... 04/15/2023 4:17:39 PM [cont-env ] XDG_CACHE_HOME: /etc/cont-env.d/XDG_CACHE_HOME: line 1: /config/xdg/cache: not found 04/15/2023 4:17:39 PM [cont-env ] XDG_CACHE_HOME: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] XDG_CACHE_HOME: loading... 04/15/2023 4:17:39 PM [cont-env ] XDG_CONFIG_HOME: executing... 04/15/2023 4:17:39 PM [cont-env ] XDG_CONFIG_HOME: /etc/cont-env.d/XDG_CONFIG_HOME: line 1: /config/xdg/config: not found 04/15/2023 4:17:39 PM [cont-env ] XDG_CONFIG_HOME: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] XDG_CONFIG_HOME: loading... 04/15/2023 4:17:39 PM [cont-env ] XDG_DATA_HOME: executing... 04/15/2023 4:17:39 PM [cont-env ] XDG_DATA_HOME: /etc/cont-env.d/XDG_DATA_HOME: line 1: /config/xdg/data: not found 04/15/2023 4:17:39 PM [cont-env ] XDG_DATA_HOME: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] XDG_DATA_HOME: loading... 04/15/2023 4:17:39 PM [cont-env ] XDG_RUNTIME_DIR: executing... 04/15/2023 4:17:39 PM [cont-env ] XDG_RUNTIME_DIR: /etc/cont-env.d/XDG_RUNTIME_DIR: line 1: /tmp/run/user/app: not found 04/15/2023 4:17:39 PM [cont-env ] XDG_RUNTIME_DIR: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] XDG_RUNTIME_DIR: loading... 04/15/2023 4:17:39 PM [cont-env ] XDG_STATE_HOME: executing... 04/15/2023 4:17:39 PM [cont-env ] XDG_STATE_HOME: /etc/cont-env.d/XDG_STATE_HOME: line 1: /config/xdg/state: not found 04/15/2023 4:17:39 PM [cont-env ] XDG_STATE_HOME: terminated successfully. 04/15/2023 4:17:39 PM [cont-env ] XDG_STATE_HOME: loading... 04/15/2023 4:17:39 PM [cont-env ] container environment variables initialized. 04/15/2023 4:17:39 PM [cont-secrets] loading container secrets... 04/15/2023 4:17:39 PM [cont-secrets] container secrets loaded. 04/15/2023 4:17:39 PM [cont-init ] executing container initialization scripts... 04/15/2023 4:17:39 PM [cont-init ] 10-certs.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-certs.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-check-app-niceness.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-check-app-niceness.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-cjk-font.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-cjk-font.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-clean-logmonitor-states.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-clean-logmonitor-states.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-clean-tmp-dir.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-clean-tmp-dir.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-fontconfig-cache-dir.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-fontconfig-cache-dir.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-init-users.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-init-users.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-nginx.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-nginx.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-openbox.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-openbox.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-set-tmp-dir-perms.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-set-tmp-dir-perms.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-vnc-password.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-vnc-password.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-web-data.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-web-data.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-x11-unix.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-x11-unix.sh: terminated successfully. 04/15/2023 4:17:39 PM [cont-init ] 10-xdg-runtime-dir.sh: executing... 04/15/2023 4:17:39 PM [cont-init ] 10-xdg-runtime-dir.sh: mkdir: can't create directory '': No such file or directory 04/15/2023 4:17:39 PM [cont-init ] 10-xdg-runtime-dir.sh: terminated with error 1.Same here. Also for any docker that uses VNC (MakeMKV + MKVToolNix).
Tried reinstalling those containers and resetting their data, but didn't help -
Doesn't matter what I do, I cannot boot a 7.0.1 with ARPL loader. Tried v1.1 beta 2 and even old v1.0 beta 3.
Tried virtio-net + e1000 network card type.Nothing helps. I can ping it after booting for like 3-4 seconds and then it gets stuck.
How do I get the logs?
EDIT: logs can be read using `cat /dev/pts/1`. Change ID to yours (from unraid vm logs)
-
3 hours ago, dlandon said:
I don't see anywhere in your log where you tried to change the disk name. There should be an entry like this:
Mar 11 10:41:27 BackupServer unassigned.devices: Set Disk Name on 'WDC_WD20EARX-00PASB0_WD-WCAZAC192391 (sdg)' to 'MusicBk'Click "Save" to change the disk name, not "Done".
Missed this button
Zoomed in too much, and the main confusion was having the top Done button (and I see there is a bottom Done button as well?).
Will report back by editing in a couple of hours.EDIT: That was it. Thank you for the help!
-
-
I encountered a problem on a fresh install of 6.11.5 with zfs drives.
Whenever I try to assign an alias on a disk, it isn't applied.
I tried: pool1, Pool1, Pool_1 but whenever I click the Done button I see it didn't change anything. Clicking on the drive settings again - I see its name reset.
Am I missing something?
-
-
I have forked the plugin repository and commited a fix for the stray warning.
May you check if you still have the warning after a restart so I'll make a Pull Request?
@mrslaw @Snowman @Mat W @GigaTech
Can't restart my server to test this unfortunately.
https://github.com/uraid/unraid-theme-engine/raw/fix-stray-dash/plugins/theme.engine.plg
The only change I've made is this:
-
1
-
-
On 12/30/2022 at 4:48 AM, doubleopinter said:
For all who are running this as a container via docker, are you just pulling from docker hub or are you building it locally from source? The docker hub version is pretty old by now.
Just built locally from source to get new rutorrent v4.0 and works great.
Had to replace the `root/install.sh` file line 102 with this one (to get around `git://` deprecation) https://github.com/pyroscope/pyrocore/pull/117/:git clone -b update-to-head-patch "https://github.com/stevezau/pyrocore.git" "/opt/pyrocore" && cd "/opt/pyrocore"
-------------------------------------------------------------------------------------------------------------------
EDIT: If someone encounters an error with the `autodl-irssi` plugin:
autodl-irssi: __init2: ex: Exception info: No content elem with id autodl-prefs-contents-upload
Change the code inside the container in the folder `/usr/share/webapps/rutorrent/plugins/autodl-irssi/` to this pull request:
https://github.com/autodl-community/autodl-rutorrent/pull/58
-------------------------------------------------------------------------------------------------------------------
EDIT2: If you encounter an error with the `throttle` plugin like so:
throttle: Plugin failed to start.It's because of this commit: https://github.com/Novik/ruTorrent/commit/06222a00375bdd0f1f1b5b58bda29e7025316428
It means the first part of the commit (editing `/usr/share/webapps/rutorrent/conf/config.php`) wasn't applied.
Simply add the line:
$throttleMaxSpeed = 327625*1024;to your `/usr/share/webapps/rutorrent/conf/config.php` file and enjoy!
-
On 1/11/2023 at 1:40 AM, xaositek said:
Ran into an odd issue where websites would get a 502 Gateway error after today's rebase to Alpine 3.17. The following error will fill the logs:
nginx: [emerg] "stream" directive is not allowed here in /etc/nginx/conf.d/stream.conf:3
Ending up figuring out you can do the following, then restart your Container and it'll fix it.
ls -al /etc/nginx/conf.d/ /etc/nginx/stream.d/
mv -v /etc/nginx/conf.d/stream.conf /etc/nginx/stream.d/
I did open https://github.com/linuxserver/docker-nginx/issues/87
Thanks for the help! It worked for me.
Seems that the images were rebuilt on Thursday, but saw it only after applying your fix.
-
On 9/23/2022 at 10:05 PM, xlelx said:
Glad you got something useful from my post!
Another update...
The container restarted successfully after last weeks appdata backup. I thought I had this beat, but there was an update last night which broke this again. Same errors. On a whim I reinstalled python2 from the container console (docker exec -it nzbget bash, then apk update, and finally apk add python2) and also deleted the custom-services.d folder. I then restarted the container and it worked like a charm. Dunno if this fix will work for everyone. Someone may want to just try deleting the README file in the custom-services.d folder rather than the whole folder to see if that makes things happy as well. I am not until it breaks the next time, if it breaks a next time
Thank you!
Deleting the 'README.txt' file from the 'cont-init.d' folder fixed it for me.
Python 2 was installed automatically in latest version.
-
1 hour ago, NeoDude said:
I'm assuming that this is the reason that none of my websites are accessible today. Any ideas how to fix it?
*EDIT* Disregard. Fixed it. Appears that the new version of Nginx requires Conf files to have the .conf extension or it won't load them.Thank you!
Adding '.conf' extension to the configuration files helped me solve it quickly.
-
Thank you for the hard work!
Been using this container for a few years now, so very much appreciated
Is there any chance to compile a separate beta tag with ruTorrent v4.0-beta 1 release 10 days ago?
https://github.com/Novik/ruTorrent/releases
A lot of interesting changes and wanted to try it out.
Thanks again!
-
On 7/14/2021 at 11:54 AM, Skylinar said:
I have also had the problem a few times that the Docker service did not stop because a container did not want to kill itself. I have also tried to do this manually and have never been able to successfully kill a Docker container manually. I have also used docker kill containername with no success. I then had to manually unplug my Unraid server, which is really suboptimal. It's good that rebooting worked around the problem for you, however it's not a real solution.
Has anyone else experienced this and can either confirm that docker kill worked for them or what the correct solution was? Because I would like to know if it is a problem on my machine or a general unraid problem.
I managed to kill 2 docker containers that just won't get stopped using this method:
The `docker kill` command didn't work either :/
-
2
-
-
On 8/25/2021 at 5:07 PM, keiser said:
Hey thanks for this, I just got this setup as I've been pretty unhappy with Photoprism's mobile app not getting updated/working with some new backend changes and only being accessible from a constantly broken Testflight link. Also I don't feel warm and fuzzy it will keep getting updated when it specifically states it's just a hobby.
Some notes:
- Steps 1,4,9 you call the network 'private' but later use it as 'privnet'. Personally I just called it 'photonix'.
- For the postgres container I suggest changing the data storage path because it's just something like /mnt/disk1/appdata/postgres/ by default and could conflict with other containers if you use more than one DB. I set it to /mnt/disk1/appdata/photonix_postgres11/
Not an issue with any of this process per se, but I tried adding an additional mount point (photos_photonix_import) and letting Photonix have a separate import folder as it asked me during the initial setup page, but it seems to just ignore that folder entirely and not import from it.
Thanks again! So far this seems a bit early in the life of the app, but I like how responsive the devs are, it's got a mobile app, and some neat features. A lot of promise here.
Just wanted to let you know that I've made a PR that fixes the 'manage.py create_library' command to let it create a custom path library and it got pushed to the latest v0.22.0 release
On 9/4/2021 at 6:10 PM, Alphahelix said:I can't seem to get it to work.
I followed your guide, and I can log in.
But once I log in I can't see any photos at all, not even JPEG.
via console I can see data has photos in it, but still no luck.
Any suggestions?
This seems to be a problem with the initial scanning of a library. Just restart the docker container and it'll start processing the images.
@cedev - Thank you for posting this template! Really appreciate it and also made a PR to fix object and face recognition for rotated photos (like selfies), so should pick up even more photos.
For anyone who tries to run a second Redis instance on unraid and can't figure out how to change ports like I encountered, just run inside the container the following command after switching ports: `redis-cli -p {port}`
-
3 minutes ago, hundsboog said:
Besides the upcoming security issues (if there are any): Is it by security means accaptable just to stay on that working version the next time till the docker gets a new maintainer?
I intend to ultimately move to wireguard as well, so that's a no for me, but everyone is free to make their choice.
Openvpn is more mature and peer reviewed, but seems to be that wireguard has all the attention nowadays
-
9 minutes ago, lakr said:
Forgive me - but how do you do that?
Click on the openvpn-as docker icon -> edit and add to the repository value ":{Version}" .
Just don't forget that version is the one I wrote above.
Excuse my brevity I'm on mobile
-
For those that want a workaround to get it working again after last update broke it:
Pull the version before the last (6 days earlier than it) - 2.8.8-cbf850a0-Ubuntu18-ls122
Worked for me in the meantime
-
1
-
-
Hi there,
I tried to add another vdisk to my W10 VM, and in the process also delete another vdisk not being used.
The result of that was that my W10 now sees my qcow2 vdisk as corrupted.
The image is RAW id diskmgmt.msc.
Can someone help me out?
Using 'fdisk -l' on it:
Disk /mnt/user/hddvms/Windows 10/LinuxISOs.img: 457.1 GiB, 490840203264 bytes, 958672272 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: 42365025-0A58-4DC7-8C48-A53D01E03B36 Device Start End Sectors Size Type /mnt/user/hddvms/Windows 10/LinuxISOs.img1 34 32767 32734 16M Microsoft reserved /mnt/user/hddvms/Windows 10/LinuxISOs.img2 32768 958668799 958636032 457.1G Microsoft basic data
Tried mounting it with 'mount -r -t ntfs -o loop,offset=16777216 /mnt/user/hddvms/Windows\ 10/LinuxISOs.img /mnt/test' but got:
NTFS signature is missing. Failed to mount '/dev/loop4': Invalid argument The device '/dev/loop4' doesn't seem to have a valid NTFS. Maybe the wrong device is used? Or the whole disk instead of a partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Can someone help me recover the data please?
-
Hi Peter,
Great plugin! Thanks for your work.
Is there an easy way to block LAN access without using iptables?
-
Had problems with faulty HDMI cable, but after doing a proper boot it has worked flawlessly and the issue is resolved.
Thanks a lot sir!
[Plugin] Docker Folder
in Plugin Support
Posted
Just after uninstalled this old plugin that I realized the whole Web UI slowness was due to it!
Definitely recommend using the new one, even though it requires Unraid >=6.12.3. Worth it