unRaide
-
Posts
108 -
Joined
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by unRaide
-
-
On 1/17/2024 at 12:22 AM, itimpi said:
That message does not explain why the system would stop responding.
I misspoke somewhat, the webui wouldn’t load but my dockers and VMs were still accessible.
On 1/17/2024 at 12:22 AM, itimpi said:It means that the cache has fallen below the minimum free space value allowed to write a new file to the cache, so the file will be written directly to the array instead. You have 100GB set as the minimum free for the cache so that is the value probably triggering it.
I had a hard time finding this setting initially, but I believe it’s the one in the screenshot below , which currently looks to have a minimum free setting of 100 kB vs 100 GB - is the wrong setting?
Additionally, I’m not sure how to change this value, perhaps I need to first stop the array?
On 1/17/2024 at 12:22 AM, itimpi said:I see that you have macvlan networking enabled for docker, but have not disabled bridging on eth0 as is recommended in the Unraid release notes to get maximum stability when using macvlan. Any reason for this?
No reason really – reading through the release notes iIt felt like this was an optional step but I’ll go back and reread it 😅.
-
Hi, I'm getting this error filling up my logs which caused my server to stop responding earlier today requiring a reboot. After doing some search it seems like this error is usually caused by one of the shares exceeding it's minimum free space however looking through my shares I'm not seeing one like this?
-
Does anyone have any tips or advice on why I wouldn’t be able to connect to my server on the local network? The server doesn’t show up in Friends and always gives me "Unable to connect to world" when trying to connect to the server manually.
-
Regarding Network Type, should I be using "Host" here or "Bridge" - I've tried both with no luck?
- I'm using 192.168.1.216 on port 19132 in minecraft
- All iPads are on the same network as the server so I'm assuming I don't need to forward any ports on my Unifi router if I'm only connecting locally?
Not seeing any errors in the logs so I'm not sure what else to try?
-
Regarding Network Type, should I be using "Host" here or "Bridge" - I've tried both with no luck?
-
Just when I think I've figured out how to setup my Cache / Shares I end up with some disk full...
Here's what I'm trying to figure out:
- I have a few shares (appdata, isos, downloads, system, domains) all set to Cache: Prefer with a minimum free space of 20GB except for downloads which is 120GB (I made this so high after running out of disk space when downloading a massive iso).
- I then have a 500GB cache pool with a minimum free space of 100GB (also had the same issue as above and set this high to avoid running out of disk space).
- My cache drive is currently sitting at 413GB used and 85GB free so my logs are getting spammed with `UnRaider shfs: cache disk full` messages
- I also have Mover setup to run every 8 hours
My question is how do I manage how much free space is available on the cache and which files are moved to it, especially seeing as the shares set to "Prefer" amount to way more than 500GB? Shouldn’t Mover move files off the cache to at least satisfy the 100GB minimum space requirement?
How should I setup this up to avoid future issues?
Also, looking at my mover logs I just see stuff like this:
-
Yea, i'll need to update that but it seems like I can't edit it while the array is online?
In any case the "share cache full" error has disappeared but I'm still seeing the "Unable to write to Docker Image" error.
Should I try restarting docker or the array - not sure the best way to resolve that issue?
-
Hi, woke up this morning to these two errors flooding the logs, especially the first one. I recently updated radarr to pull down 4k remux and I'm assuming some of those wreaked havoc on my cache and docker img.
shfs: share cache full Fix Common Problems: Error: Unable to write to Docker ImageAny ideas on how to resolve this?
-
Ok, thx for the reply! I’ve been struggling with crashing issues for ages but could never pin it down - this could be one of the reasons!
-
On 2/5/2023 at 7:06 AM, blaine07 said:
Is this container not kept updated with docker? I see this in logs; i have tried to run it but can't seem to figure out the proper way to handle this?
Any help?
Yea, seeing the same thing and wondering if any action is needed on my part?
-
On 2/21/2023 at 5:01 PM, robotdog said:
Since the middle of last week if my plex pass docker is running my server will run for about 11 hours or so and then freeze until a hard reboot is preformed. This docker had been running flawlessly since July and I can't figure out what I could have changed or what to do to fix it.
If I turn off plex pass, my server will run for days.
@robotdog, would be curious to know if you were able to resolve this as I've been experiencing the same issue for the last 5 days. My server is locking up / crashing every morning between 3-6pm and after eliminating different dockers my latest theory is that it could be Plex as turning that off prevented my server from crashing and led me here? Given the pattern it does seem plausible that it's something related to a scheduled task in plex.
-
For the past 5 days my unraid server keeps crashing every morning between 5am-8am. Yesterday it also crashed an additional 2 times throughout the day. The only thing recurring that happens every morning is the CA Auto Update Applications plugin runs.
The only major change I've made is upgrading rom 6.9.2 to 6.11.5 which I did 3 weeks ago. I've attached my diagnostics and I've enabled the syslog server but I don't see any major errors - the logs just stop before the crash and then pickup after boot.
Any help would be very much appreciated - my household basically comes to a crawl without my unraid server and hard restarting every day is bound to end badly
-
For the Homebridge docker: I've noticed that Homebridge UI says there is an update available and is stuck on homebridge-config-ui-x v4.41.4. When trying to manually update the plugin through the UI I get the message below. I usually stay away from updating anything like this and usually rely on a docker update but given how old the version I'm on is it doesn’t seem like that's going to happen.
Has anyone gone through this and updated Node.js?
-
I didn’t unfortunately. Just had the server lock up on me again earlier today.
Sad to say but I just hard reboot it every few days 😩
-
Hi, hoping someone can help me troubleshoot an issue I'm having with both Sonarr and Radarr. Everything was working fine until a couple of weeks back when the containers refused to start.
Now every time I try to start them they just exit immediately, with "Exited (10)".
Other things that have happened recently, that may be related, include:
- upgrading to Unraid 6.10 > running into permission issues with the .db files and needing to change everything to nobody/users
- downgrading back to 6.9.2 based on the issue above.
Logs below don't seem to have any helpful info either.
Any help would be appreciated as I'm not sure where to start even.
2022-07-24 15:48:12.610994 [info] System information Linux 6c60ea4c6872 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2022-07-24 15:48:12.637291 [info] OS_ARCH defined as 'x86-64' 2022-07-24 15:48:12.663228 [info] PUID defined as '99' 2022-07-24 15:48:12.691479 [info] PGID defined as '100' Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-07-24 16:00:50.515417 [info] System information Linux 6c60ea4c6872 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2022-07-24 16:00:50.537848 [info] OS_ARCH defined as 'x86-64' 2022-07-24 16:00:50.561804 [info] PUID defined as '99' 2022-07-24 16:00:50.587522 [info] PGID defined as '100' Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-08-03 20:18:22.221588 [info] System information Linux 6c60ea4c6872 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2022-08-03 20:18:22.247155 [info] OS_ARCH defined as 'x86-64' 2022-08-03 20:18:22.271985 [info] PUID defined as '99' 2022-08-03 20:18:22.298299 [info] PGID defined as '100' Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2022-08-13 14:45:27.645429 [info] System information Linux 6c60ea4c6872 5.10.28-Unraid #1 SMP Wed Apr 7 08:23:18 PDT 2021 x86_64 GNU/Linux 2022-08-13 14:45:27.670912 [info] OS_ARCH defined as 'x86-64' 2022-08-13 14:45:27.696122 [info] PUID defined as '99' 2022-08-13 14:45:27.722993 [info] PGID defined as '100' -
Hi, just upgraded from 6.9.3 and everything seems to be working fine so far except for what seems like a permissions issue with Sonarr.
Whenever I try searching I'm getting the following error:
[v3.0.4.1126] System.Data.SQLite.SQLiteException (0x80004005): attempt to write a readonly databaseLooking at the permissions in the appdata folder between Radarr and Sonnar I noticed that Sonarr has more files owned by root/root vs nobody/users (specifically the .db file which I'm assuming is the cause of the error)?
Searching led me to suggestions to use "Docker Safe New Perms" but that doesn’t appear to touch the appdata folder.
Should I just manually chmod the files/folders?
-
On 4/3/2021 at 7:36 PM, unRaide said:
Hi @binhex, any ideas on how to get this new setup working with a reverse proxy? I've added each of the ports above and couldn’t find any suggestions in the documentation or anywhere else in this thread.
Is it still possible to use a reverse proxy?
Just wanted to follow-up on this in case anyone else runs into this issue. I got this working by simply changing the app name below from binhex-radarr to binhex-sabnzbdvpn in my swag conf file.
location / { # auth_basic "Restricted"; # auth_basic_user_file /config/nginx/.htpasswd; include /config/nginx/proxy.conf; resolver 127.0.0.11 valid=30s; # set $upstream_radarr binhex-radarr; set $upstream_radarr binhex-sabnzbdvpn; proxy_pass http://$upstream_radarr:7878; } } -
On 3/21/2021 at 2:59 PM, unRaide said:
Hi @binhex, just finished updating my sabnzbdvpn, radarr, sonarr, nzbhydra2 setup to work with the latest changes and so far everything seems to be working well!
The only issue I’m still having is that I can no longer reach radarr (port 8989), sonarr (7878), nzbhydra2 (5076) outside my network using my reverse proxy. I used @SpaceInvaderOne tutorial to setup a reverse proxy using Swag and creating a proxynet and after the vpn updates I get a “502 bad gateway” error when trying to access those containers.I tried Q27 in the docs and added each of the ports above to VPN_OUTPUT_PORTS but no luck so far.
Any guidance on how to get to get this working again 🙏 ?
Thx
Hi @binhex, any ideas on how to get this new setup working with a reverse proxy? I've added each of the ports above and couldn’t find any suggestions in the documentation or anywhere else in this thread.
Is it still possible to use a reverse proxy?
-
Hi @binhex, just finished updating my sabnzbdvpn, radarr, sonarr, nzbhydra2 setup to work with the latest changes and so far everything seems to be working well!
The only issue I’m still having is that I can no longer reach radarr (port 8989), sonarr (7878), nzbhydra2 (5076) outside my network using my reverse proxy. I used @SpaceInvaderOne tutorial to setup a reverse proxy using Swag and creating a proxynet and after the vpn updates I get a “502 bad gateway” error when trying to access those containers.I tried Q27 in the docs and added each of the ports above to VPN_OUTPUT_PORTS but no luck so far.
Any guidance on how to get to get this working again 🙏 ?
Thx
-
Just had another lockup requiring a hard reboot and there doesn’t seem to be anything helpful in the logs as they also seemed to have locked up/stopping updating for a few hours?
Feb 20 16:47:01 UnRaider root: Fix Common Problems Version 2021.02.18 Feb 20 16:47:01 UnRaider root: Fix Common Problems: Warning: Share backup set to not use the cache, but files / folders exist on the cache drive ** Ignored Feb 20 16:47:05 UnRaider root: Fix Common Problems: Warning: Docker application duckdns2 has moderator comments listed ** Ignored Feb 20 16:47:05 UnRaider root: Fix Common Problems: Warning: Docker application letsencrypt has moderator comments listed ** Ignored Feb 20 17:47:01 UnRaider root: Fix Common Problems Version 2021.02.18 Feb 20 17:47:02 UnRaider root: Fix Common Problems: Warning: Share backup set to not use the cache, but files / folders exist on the cache drive ** Ignored Feb 20 17:47:06 UnRaider root: Fix Common Problems: Warning: Docker application duckdns2 has moderator comments listed ** Ignored Feb 20 17:47:06 UnRaider root: Fix Common Problems: Warning: Docker application letsencrypt has moderator comments listed ** Ignored Feb 20 18:47:01 UnRaider root: Fix Common Problems Version 2021.02.18 Feb 20 18:47:02 UnRaider root: Fix Common Problems: Warning: Share backup set to not use the cache, but files / folders exist on the cache drive ** Ignored Feb 20 18:47:06 UnRaider root: Fix Common Problems: Warning: Docker application duckdns2 has moderator comments listed ** Ignored Feb 20 18:47:06 UnRaider root: Fix Common Problems: Warning: Docker application letsencrypt has moderator comments listed ** Ignored Feb 20 19:47:01 UnRaider root: Fix Common Problems Version 2021.02.18 Feb 20 19:47:02 UnRaider root: Fix Common Problems: Warning: Share backup set to not use the cache, but files / folders exist on the cache drive ** Ignored Feb 20 19:47:06 UnRaider root: Fix Common Problems: Warning: Docker application duckdns2 has moderator comments listed ** Ignored Feb 20 19:47:06 UnRaider root: Fix Common Problems: Warning: Docker application letsencrypt has moderator comments listed ** Ignored Feb 20 20:47:01 UnRaider root: Fix Common Problems Version 2021.02.18 Feb 20 20:47:01 UnRaider root: Fix Common Problems: Warning: Share backup set to not use the cache, but files / folders exist on the cache drive ** Ignored Feb 20 20:47:06 UnRaider root: Fix Common Problems: Warning: Docker application duckdns2 has moderator comments listed ** Ignored Feb 20 20:47:06 UnRaider root: Fix Common Problems: Warning: Docker application letsencrypt has moderator comments listed ** Ignored Feb 20 21:47:01 UnRaider root: Fix Common Problems Version 2021.02.18 Feb 20 21:47:02 UnRaider root: Fix Common Problems: Warning: Share backup set to not use the cache, but files / folders exist on the cache drive ** Ignored Feb 20 21:47:06 UnRaider root: Fix Common Problems: Warning: Docker application duckdns2 has moderator comments listed ** Ignored Feb 20 21:47:06 UnRaider root: Fix Common Problems: Warning: Docker application letsencrypt has moderator comments listed ** Ignored Feb 20 23:39:43 UnRaider cache_dirs: Arguments=-i backup -i domains -i downloads -i files -i isos -i multimedia -i nextcloud -i sync -i sync-downloads -i windows Feb 20 23:39:43 UnRaider cache_dirs: Max Scan Secs=10, Min Scan Secs=1 Feb 20 23:39:43 UnRaider cache_dirs: Scan Type=adaptive Feb 20 23:39:43 UnRaider cache_dirs: Min Scan Depth=4 Feb 20 23:39:43 UnRaider cache_dirs: Max Scan Depth=none Feb 20 23:39:43 UnRaider cache_dirs: Use Command='find -noleaf' Feb 20 23:39:43 UnRaider cache_dirs: ---------- Caching Directories --------------- Feb 20 23:39:43 UnRaider cache_dirs: backup Feb 20 23:39:43 UnRaider cache_dirs: domains Feb 20 23:39:43 UnRaider cache_dirs: downloads Feb 20 23:39:43 UnRaider cache_dirs: files Feb 20 23:39:43 UnRaider cache_dirs: isos Feb 20 23:39:43 UnRaider cache_dirs: multimedia Feb 20 23:39:43 UnRaider cache_dirs: nextcloud Feb 20 23:39:43 UnRaider cache_dirs: sync Feb 20 23:39:43 UnRaider cache_dirs: sync-downloads Feb 20 23:39:43 UnRaider cache_dirs: windows Feb 20 23:39:43 UnRaider cache_dirs: ---------------------------------------------- Feb 20 23:39:43 UnRaider cache_dirs: Setting Included dirs: backup,domains,downloads,files,isos,multimedia,nextcloud,sync,sync-downloads,windows Feb 20 23:39:43 UnRaider cache_dirs: Setting Excluded dirs: Feb 20 23:39:43 UnRaider cache_dirs: min_disk_idle_before_restarting_scan_sec=60 Feb 20 23:39:43 UnRaider cache_dirs: scan_timeout_sec_idle=150 Feb 20 23:39:43 UnRaider cache_dirs: scan_timeout_sec_busy=30 Feb 20 23:39:43 UnRaider cache_dirs: scan_timeout_sec_stable=30 Feb 20 23:39:43 UnRaider cache_dirs: frequency_of_full_depth_scan_sec=604800 Feb 20 23:39:43 UnRaider cache_dirs: cache_dirs service rc.cachedirs: Started: '/usr/local/emhttp/plugins/dynamix.cache.dirs/scripts/cache_dirs -i "backup" -i "domains" -i "downloads" -i "files" -i "isos" -i "multimedia" -i "nextcloud" -i "sync" -i "sync-downloads" -i "windows" 2>/dev/null' Feb 20 23:39:43 UnRaider root: Delaying execution of fix common problems scan for 10 minutes Feb 20 23:39:43 UnRaider unassigned.devices: Mounting 'Auto Mount' Devices... Feb 20 23:39:43 UnRaider unassigned.devices: Adding disk '/dev/sdb1'... Feb 20 23:39:43 UnRaider unassigned.devices: Mount drive command: /sbin/mount -t xfs -o rw,noatime,nodiratime,discard '/dev/sdb1' '/mnt/disks/ssd' Feb 20 23:39:43 UnRaider kernel: XFS (sdb1): Mounting V5 Filesystem Feb 20 23:39:43 UnRaider kernel: XFS (sdb1): Starting recovery (logdev: internal) Feb 20 23:39:43 UnRaider kernel: XFS (sdb1): Ending recovery (logdev: internal) Feb 20 23:39:43 UnRaider unassigned.devices: Successfully mounted '/dev/sdb1' on '/mnt/disks/ssd'. Feb 20 23:39:43 UnRaider unassigned.devices: Disk with serial 'WDC_WD140EDFZ-11A0VA0_9LG83JPA', mountpoint 'easystore' is not set to auto mount. Feb 20 23:39:43 UnRaider emhttpd: Starting services... Feb 20 23:39:43 UnRaider emhttpd: shcmd (65): /etc/rc.d/rc.samba restart Feb 20 23:39:43 UnRaider rsyslogd: [origin software="rsyslogd" swVersion="8.1908.0" x-pid="6884" x-info="https://www.rsyslog.com"] start Feb 20 23:39:45 UnRaider root: Starting Samba: /usr/sbin/smbd -D Feb 20 23:39:45 UnRaider root: /usr/sbin/nmbd -D Feb 20 23:39:45 UnRaider root: /usr/sbin/wsdd Feb 20 23:39:45 UnRaider root: /usr/sbin/winbindd -D Feb 20 23:39:45 UnRaider emhttpd: shcmd (79): /usr/local/sbin/mount_image '/mnt/user/system/docker/docker.img' /var/lib/docker 50 Feb 20 23:39:45 UnRaider kernel: BTRFS: device fsid a8e1d964-f72d-42b6-a377-79a34367d3fd devid 1 transid 2223184 /dev/loop2 Feb 20 23:39:45 UnRaider kernel: BTRFS info (device loop2): disk space caching is enabled Feb 20 23:39:45 UnRaider kernel: BTRFS info (device loop2): has skinny extents Feb 20 23:39:45 UnRaider kernel: BTRFS info (device loop2): start tree-log replay Feb 20 23:39:45 UnRaider kernel: BTRFS info (device loop2): checking UUID tree Feb 20 23:39:45 UnRaider root: Resize '/var/lib/docker' of 'max' Feb 20 23:39:45 UnRaider kernel: BTRFS info (device loop2): new size for /dev/loop2 is 53687091200 Feb 20 23:39:45 UnRaider emhttpd: shcmd (81): /etc/rc.d/rc.docker start Feb 20 23:39:45 UnRaider root: starting dockerd ...
Really at a loss on how to stabilize my server 😩
Also attached the diagnostic taken after the server booted back up.
unraider-diagnostics-20210220-2347.zip
-
Thx, I just enabled the Local syslog sever and hopefully that will give me more info after the next lockup.
-
I'm having issues with my server locking up and becoming unresponsive.
What I know so far:
-
My server locks up consistently every 2- 3 days, just long enough to get through the Parity check
- When this happens I cannot ssh into the box and the UI/dockers/etc.. are unresponsive.
- I don't remember changing anything specific but it started happening a few weeks ago
- I've disabled all new dockers that were installed since then to try and isolate the issue with no luck
- I turned on the Method 1 recommend by @Squid in this forum post which I recently checked after the server rebooted and it didn’t show anything out of the ordinary other than a ton of "shfs: share cache full" msgs
Does anyone have any guidance on how to troubleshoot this issue.
Also attached my diagnostics.
Thx
-
My server locks up consistently every 2- 3 days, just long enough to get through the Parity check
-
Wow, what an amazing container... tku @testdasi!!!
I've been wanting to install these apps for ages but it always seemed to daunting to tackle... this container took me 10mins
I have a question around the disk paths... by default they're all set to "/mnt/user0/" or "/mnt/cache/" which seems right but didn’t work for me, just showed N/A. I am able to get them working by changing the path to "/rootfs/mnt/user0/" but before I change the numerous instances of them I'm wondering if there is something off about my config/container that I should fix and/or if there is a centralized place to change this once?
-
Another follow-up question while I'm here
I'm trying to figure out how to manually install this node for the Pocket app which isn't available through the Node-RED palette however I'm not sure how to do this within the docker?
-
5 hours ago, spants said:
What are you trying to do with nbrowser?
Hi @spants, thx for the response!
I'm trying to create a flow that periodically logs into a site (audible.com) and extracts one piece of data. nbrowser seems like a node that would allow me to handle this entire flow e.g. login to a site and handle the cookies, redirect, etc. but unfortunately it has the issues mentioned above :(.
Definitely open to other ideas on how to accomplish the same task.
-
Has anyone been able to successfully get the nbrowser node working in the Node-RED container? Whenever I try it it crashes Node-RED.
26 Dec 19:43:59 - Error: spawn /data/node_modules/electron/dist/electron ENOENT at Process.ChildProcess._handle.onexit (internal/child_process.js:240:19) at onErrorNT (internal/child_process.js:415:16) at process._tickCallback (internal/process/next_tick.js:63:19) npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! [email protected] start: `node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data"` npm ERR! Exit status 1 npm ERR! Failed at the [email protected] start script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above. npm ERR! A complete log of this run can be found in: npm ERR! /data/.npm/_logs/2020-12-27T03_43_59_278Z-debug.logPer this thread it seems like there may be some additional package needed although that’s the extent of my technical skills.
https://github.com/segmentio/nightmare/issues/224
**Out of Memory errors detected on your server**
in General Support
Posted
Hi, a couple of days ago I started noticing these errors from the Fix Common Problems plugin which suggested I post my diagnostics here to see if anyone could help troubleshoot. I haven't noticed anything too bad wrt my dockers/VMs but would love to figure it out if possible.
Any help would be greatly appreciated.
unraider-diagnostics-20240302-1314.zip