theothermatt_b

Monitor shows an endless list of the following message: crond[1942]: exit status 126 from user root /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null With one or two of these: crond[2967834]: unable to exac /usr/sbin/sendmail: cron output for user root /usr/bin/run-parts /etc/cron.hourly 1> /dev/null to /dev/null I tried to log in and got this: Last login: (timestamp) on tty1 -bash: /usr/share/bash-completion/bash-completion: Input/Output error Unraid Server OS version: 7.2.3 IPV4 Address: (ip address) IPv6 Address: not set and then it just prompts for the login again. I'm going to hard reboot it and then look for those diags and logs. EDIT: I see that hard rebooting has cleared the syslog file. I should have expected this. I did some reading and turned on the syslog server, so hopefully if/when this happens again, I can go get the log after the fact.

I do now!

My server did this about a week ago too. I figure its probably a plugin or something. I can't get to the web UI for Unraid. There is also one docker image that is down (no webUI, no other responses). The other images seem to be working fine. I know I can hard-reboot the box, by physically pressing the power button, but I'm wondering if there's anything else I could/should do instead? Another way into the machine? To at least do an Unraid-commanded reboot instead of pressing the power button? Also, once it's back up, where if anywhere can I look to help narrow down wtf happened? Thanks everyone.

I've been seeing this odd issue the last few weeks, but haven't taken the time to post about it. I do a weekly appdata backup. The backup works great (thank you!), updating the containers works great (thank you again!), and then all the containers start back up as they should (thanks yet again lol), however, about half the containers report that they fail the first start up attempt, but then report that the second attempt is skipped because they're already running. It's like the first attempt DID work, it just didn't wait long enough to check? Log looks like this (but with a lot more containers) [01.09.2025 01:15:43][ℹ️][Main] Set containers to previous state [01.09.2025 01:15:43][ℹ️][mariadb] Starting mariadb... (try #1) done! [01.09.2025 01:15:56][ℹ️][nextcloud] Starting nextcloud... (try #1) done! [01.09.2025 01:16:25][ℹ️][plex] Starting plex... (try #1) done! [01.09.2025 01:16:54][ℹ️][radarr] Starting radarr... (try #1) done! [01.09.2025 01:17:54][ℹ️][sonarr] Starting sonarr... (try #1) Container did not started! - Code: [01.09.2025 01:19:02][ℹ️][sonarr] Starting sonarr... (try #2) Hmm - container is already started! [01.09.2025 01:19:04][ℹ️][bazarr] Starting bazarr... (try #1) Container did not started! - Code: [01.09.2025 01:20:53][ℹ️][bazarr] Starting bazarr... (try #2) Hmm - container is already started! [01.09.2025 01:20:55][ℹ️][ddns-updater] Starting ddns-updater... (try #1) Container did not started! - Code: [01.09.2025 01:22:43][ℹ️][ddns-updater] Starting ddns-updater... (try #2) Hmm - container is already started! [01.09.2025 01:22:45][ℹ️][immich] Starting immich... (try #1) Container did not started! - Code: [01.09.2025 01:25:05][ℹ️][immich] Starting immich... (try #2) Hmm - container is already started!

That nailed it. Thank you SO MUCH!

That didn't end up being the fix I used, but you pushed me in the right direction (a lot of times its just like, i don't even know what to search for). I ended up changing -it to -d -t and removing anything after the image name at all. Also I removed the ENTRYPOINT line entirely from the dockerfile Thank you!! (Assuming none of the above was a stupid thing to do for any reason...) The only trick left is if I could have the console default to the /app directory instead of /

Hi everyone, I've got a python app that can take a small variety of of launch parameters. Currently I've built a docker image that works in Unraid, that will run it with default parameters, and output stuff to the log. That's great, but what I'd love is to launch the image and just have it sit there. Then you go into the console for it, and actually run the python program from there, with whatever launch parameters you want that time. I'm sure this is a case of me not knowing much about docker/unraid yet and dabbling in things I don't fully understand. dockerfile: FROM python:3.11-alpine3.20 WORKDIR / RUN apk update && apk add git (needed programs) RUN adduser -D (username) && mkdir /config /data /app RUN chown (username):(username)-R /config /data /app USER (username) ENV HOME=/config \ TZ=Etc/UTC \ HOSTNAME=(image name) RUN pip install --upgrade pip COPY /app/requirements.txt requirements.txt RUN pip install --no-cache-dir -r requirements.txt ENTRYPOINT ["/bin/sh", "-c"] image run command: docker run -it --name='ImageName' --net='bridge' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Unraid" -e HOST_CONTAINERNAME="ImageName" -l net.unraid.docker.managed=dockerman -v '/mnt/user/appdata/omb/':'/config/.omb':'rw' -v '/mnt/user/omb/monitored':'/monitored':'rw' -v '/mnt/user/omb/app':'/app':'rw' -v '/mnt/user/omb/init':'/init':'rw' omb -c "bin/sh /init/init.sh" init.sh: cd /app python -u omb # the -u switch makes all print statements go to the log, which we can see in Unraid Is there a way to modify this to make it not actually fire off a script but just wait, so I can launch the Console for that docker and run it manually?

I'm going to assume this falls under "I still don't really know what I'm doing," but here's my issue: I'm trying to set up this docker image in Unraid 7. https://hub.docker.com/r/starkayc/orpheusbetter https://github.com/starkayc/orpheusbetter-crawler (those links are both to the same project). I went into the Docker tab and added a new container. I put starkayc/orpheusbetter:latest as the Repository I added paths for config, data, torrent, app Extra parameters: starkayc/orpheusbetter -c "/app/orpheusbetter --threads 4" Here's what Unraid ran: docker run -d --name='OrpheusBetter' --net='bridge' --pids-limit 2048 -e TZ="America/New_York" -e HOST_OS="Unraid" -e HOST_HOSTNAME="Unraid" -e HOST_CONTAINERNAME="OrpheusBetter" -l net.unraid.docker.managed=dockerman -v '/mnt/user/appdata/orpheusbetter/':'/config/.orpheusbetter':'rw' -v '/mnt/user/orpheusbetter/data':'/data':'rw' -v '/mnt/user/orpheusbetter/torrent':'/torrent':'rw' -v '/mnt/user/orpheusbetter/':'/app':'rw' starkayc/orpheusbetter -c "/app/orpheusbetter --threads 4" 'starkayc/orpheusbetter:latest' This "finished successfully" but when I check the log it just says: starkayc/orpheusbetter:latest: line 0: /app/orpheusbetter: not found And that's where I'm stuck. Whenever I run the docker image, it just spits out that line, and stops. Again, I assume this is a "I don't know enough" problem. Can anyone point me in the right direction? It seems like it's not doing all the setup its supposed to do? Downloading python packages and whatnot?

Hi all, I can write mediocre python, but I'm still very new to things like virtual environments and things like that. I have a python discord bot running in a python docker container. To be clear: it's working. But I've been reading about venv's due to getting this message whenever I start the container: I see that I can suppress the message but... should i? Should i be running python in a venv instead? Is that... better somehow? I don't intend on distributing this container, running multiple bots, or anything fancy, if that helps. It also appears to be the case that every time i start the container, it needs to re-download all the extra libraries (discord.py, and about a dozen others) every single time. That seems less than efficient. Would a venv resolve that as well? My init.sh looks like this: python -m pip install --upgrade pip python -m pip install -r app/requirements.txt python /app/mombot.py If I comment out those first two lines, it won't start because its missing discord and the rest. So it seems like they have to install every time.

They said in "Extra Params or something like that" you can just "drop in all the docker CLI stuff" which is helpful if you know exactly what that means. I'm unclear what the docker command line stuff would be, but I believe they're referring to the Extra Parameters section. This section (for this container) already has a few parameters there, in the format: --param=VALUE --secondparam=SECOND_VALUE I have no idea what precisely to put here to add a healthcheck.

I have a docker image (qbittorrent) with a vpn built in that I use. It works great, EXCEPT that every couple of days, the vpn dies. The WebUI still works fine, but you can't curl to any address from the command line, and i get a notice from some sites that i'm no longer seeding. I did some digging on this and found a thing people can add to their docker image called a healthcheck? Sorry if this is obvious, i'm very new to docker and unraid. Basically you'd add something like: healthcheck: test: ["CMD-SHELL", "curl -f http://google.com || exit 1"] interval: 10s timeout: 5s retries: 5 I have no idea how to add that to a docker image i got from the community. Plus, if I add it, will it get wiped out the next time I go into the docker settings and re-apply? Searching here and elsewhere hasn't provided much help. Is this an option for me?

I just found this thread and was having the same issue. I have my docker apps on a custom network created by the command line. All of them seem to work with it fine, but the WebGUI for Photoprism only loads if i change it to Host.

Thank you for all of that! So it sounds like the "you should have been doing this ahead of time" things are: 1) have your flash drive getting backed up routinely either by a plugin or through Unraid Connect 2) backup your appdata folder regularly through a plugin Other than that, the system has fail-safes already in place for most other single-piece-of-hardware failures.

It feels like answers to these questions are in a dozen different places, some older than others and may not apply. I don't want to be scared of hardware failure due to lack of knowledge, so I'd like to just ask about the different scenarios here. Flash drive dies I believe the solution here is to already have a backup of your flash drive, either through Unraid Connect (according to Unraid, this should backup any flash drive changes within a minute or two of them happening, so your backup should ideally be current), through manually backing it up, or through a backup plugin like Appdata Backup (which backs up your flash drive onto your array, although without a working flash drive i'm not sure how you get to the backup... hm.) ' What's the best solution here? Array drive dies Get a new drive of the same size or larger, and let the parity drive rebuild the data. I believe any data on the dead drive is completely inaccessible until you replace the drive. Is this accurate? Parity drive dies I believe you can get to all your data, but it's not "safe" until you get a new parity drive and rebuild it. Accurate? Cache drive dies Assuming you don't have two cache drives in a raid setup, you should be using a backup plugin like Appdata Backup to backup your appdata folder, otherwise you've just lost your appdata folder and with it all or most settings in any docker containers. The docker container settings that you can get to through Unraid are fine, but things like movie collections in plex, or indexer lists in jackett, are all potentially gone. (This is the one that happened to me, that made me want to make this thread) Is this correct? Motherboard dies If you can't (or don't want to) get the same motherboard... can you just plug all your hard drives and flash drive into a new motherboard, and everything will boot up just fine? That seems too simple. I feel like Unraid wouldn't get the drives in the right order or something? What's the solution here?

Same (or at least very similar) here: It was working fine an hour ago (I think?), but after a reboot, i'm getting this.