-
Unraid server intermittently crashes.
Hi JorgeB, Can't seem to find a folder call /boot/logs as describe in the document from the link you posted. I think I will have to start the server up which will over write syslog file and then go through checking the setup of the syslog server. I have now setup a remote syslog server using an old QNAP NAS and also been through all the required setting as per the documentation on the UNRAID server, it is logging as I write this. All that's left to do is wait for the crash and hopefully we will have a usable syslog file.....
-
Unraid server intermittently crashes.
Thanks JorgeB, Please find log files from my boot usb as requested. This contains the folder called logs. UNRAID logs.zip
-
-
Unraid server intermittently crashes.
Hi, Yesterday I attempted to log on to my server but could not as the server had crashed, this is a persistent issue I have been having and most likely the reason my docker image became corrupted. I've had to remake the docker image several times now... Unfortunately it's intermittent and you can't predict when it will crash, JorgB has helped me recover more than a few times which only started after I moved the file system from XFS to ZFS. Stated the week of the 2nd December I will be in hospital for 3 week so that means coming out just before Christmas. I do intend to fix all issue so will keep in contact as soon as I can. The server is currently switch off, I do copy the system logs to the flash drive may be there is some thing there.
-
Docker containers on custom network don't have an IP address
Sorry for not keeping in contact to let you know how things are going, but real life has gotten in the way and I have been very busy. I have read through your post and watch the youtube video, very informative it's a shame he moves so quickly through each network but I can watch it again to make it stick. I did attempted to take a look yesterday but could not log on as the server had crashed, this is a persistent issue I have been having and most likely the reason the docker image became corrupted in the first place. I've had to remake the docker image several times now... Unfortunately it's intermittent and you can't predict when it will crash, JorgB has helped me recover more than a few times so thinking about that it's probably best to fix the crashing first which only started after I moved the file system from XFS to ZFS. Stated the week of the 2nd December I will be in hospital for 3 week so that means coming out just before Christmas. I do entend to fix all issue so will keep in contact.
-
Docker containers on custom network don't have an IP address
Hi bmartino1, After very carefully following your guide to step 6 this is the situation I find my self in. With the containers running even though the network is now appearing the containers are not getting an IP. I've attached my cli output showing the steps I took. binhex-sabnzbd is still having a problem with the network despite the config having the correct network, strange. root@Locutus:~# docker network disconnect the-arrs prowlarr root@Locutus:~# docker network disconnect the-arrs radarr root@Locutus:~# docker network disconnect the-arrs lidarr root@Locutus:~# docker network inspect the-arrs [ { "Name": "the-arrs", "Id": "781daf242b174d8022d621313fdf7343d7b63a93e5b8de2aa790c2e1eccb28a8", "Created": "2024-11-16T13:23:48.915916839Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.19.0.0/16", "Gateway": "172.19.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ] root@Locutus:~# docker network rm the-arrs the-arrs root@Locutus:~# docker network ls NETWORK ID NAME DRIVER SCOPE 4eb6e48fe60b br0 ipvlan local 4974d5e68b6a bridge bridge local c23f590356ad host host local 9d85fee46172 none null local root@Locutus:~# docker network create \ > --driver bridge \ > --subnet=172.19.0.0/16 \ > the-arrs ff54bf2796fe949fcc49124e6259b89caa3a9ef31c3aa9f26af6a4e4d16f0b8f root@Locutus:~# docker network inspect the-arrs [ { "Name": "the-arrs", "Id": "ff54bf2796fe949fcc49124e6259b89caa3a9ef31c3aa9f26af6a4e4d16f0b8f", "Created": "2024-11-21T11:35:26.223788051Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.19.0.0/16" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": {}, "Options": {}, "Labels": {} } ] root@Locutus:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bb703c44083a amir20/dozzle "/dozzle" 31 hours ago Up 10 hours 0.0.0.0:8085->8080/tcp, :::8085->8080/tcp Dozzle 7c6c0b758afa lscr.io/linuxserver/homeassistant "/init" 31 hours ago Up 10 hours Home-Assistant 3fabd2296c29 jlesage/mediainfo "/init" 2 days ago Up 10 hours 0.0.0.0:7817->5800/tcp, :::7817->5800/tcp, 0.0.0.0:7917->5900/tcp, :::7917->5900/tcp MediaInfo 0e8f497546bc mikenye/picard "/init" 3 days ago Up 7 minutes 0.0.0.0:5800->5800/tcp, :::5800->5800/tcp, 5900/tcp MusicBrainz-Picard d1c398636e7b clamav/clamav "/init" 3 days ago Up 10 hours (healthy) 0.0.0.0:3310->3310/tcp, :::3310->3310/tcp, 7357/tcp ClamAV 2fb3c6591525 plexinc/pms-docker "/init" 4 days ago Up 3 days Plex-Media-Server 001aa28cca90 securecompliance/gvm:11.0.1-r3 "/bin/sh -c '/start.…" 4 days ago Up 10 hours 0.0.0.0:8088->9392/tcp, :::8088->9392/tcp frak-gvm 24458a4d2933 binhex/arch-krusader "/usr/bin/dumb-init …" 4 days ago Up 10 hours 5900/tcp, 0.0.0.0:6080->6080/tcp, :::6080->6080/tcp binhex-krusader d11a68f18fe2 ghcr.io/recyclarr/recyclarr:latest "/sbin/tini -- /entr…" 4 days ago Up 10 hours recyclarr 1fc6c5bc70e1 jlesage/qdirstat "/init" 4 days ago Up 10 hours 0.0.0.0:7815->5800/tcp, :::7815->5800/tcp, 0.0.0.0:7915->5900/tcp, :::7915->5900/tcp QDirStat 9ed27c22c1df ghcr.io/home-assistant-libs/python-matter-server:stable "matter-server --sto…" 4 days ago Up 10 hours matter-server 3023f45d5b67 ich777/luckybackup "/opt/scripts/start.…" 4 days ago Up 10 hours 0.0.0.0:8086->8080/tcp, :::8086->8080/tcp luckyBackup 5109a81c570d jbartlett777/diskspeed "catalina.sh run" 4 days ago Up 10 hours 8080/tcp, 0.0.0.0:18888->8888/tcp, :::18888->8888/tcp DiskSpeed 763aeb21b35c jlesage/czkawka "/init" 4 days ago Up 10 hours 0.0.0.0:7821->5800/tcp, :::7821->5800/tcp, 0.0.0.0:7921->5900/tcp, :::7921->5900/tcp Czkawka 93aae5cb1024 lscr.io/linuxserver/airsonic-advanced "/init" 4 days ago Up 10 hours 0.0.0.0:4040->4040/tcp, :::4040->4040/tcp airsonic-advanced root@Locutus:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES bb703c44083a amir20/dozzle "/dozzle" 31 hours ago Up 10 hours 0.0.0.0:8085->8080/tcp, :::8085->8080/tcp Dozzle 9209317f760a ghcr.io/hotio/radarr:latest "/init" 31 hours ago Up 3 minutes radarr 337973fe3bac ghcr.io/hotio/prowlarr "/init" 31 hours ago Up 5 minutes prowlarr 7c6c0b758afa lscr.io/linuxserver/homeassistant "/init" 31 hours ago Up 10 hours Home-Assistant 3fabd2296c29 jlesage/mediainfo "/init" 2 days ago Up 10 hours 0.0.0.0:7817->5800/tcp, :::7817->5800/tcp, 0.0.0.0:7917->5900/tcp, :::7917->5900/tcp MediaInfo 0e8f497546bc mikenye/picard "/init" 3 days ago Up 14 minutes 0.0.0.0:5800->5800/tcp, :::5800->5800/tcp, 5900/tcp MusicBrainz-Picard d1c398636e7b clamav/clamav "/init" 3 days ago Up 10 hours (healthy) 0.0.0.0:3310->3310/tcp, :::3310->3310/tcp, 7357/tcp ClamAV 2fb3c6591525 plexinc/pms-docker "/init" 4 days ago Up 3 days Plex-Media-Server c7172ee53700 ghcr.io/hotio/lidarr:latest "/init" 4 days ago Up 4 minutes lidarr 001aa28cca90 securecompliance/gvm:11.0.1-r3 "/bin/sh -c '/start.…" 4 days ago Up 10 hours 0.0.0.0:8088->9392/tcp, :::8088->9392/tcp frak-gvm 24458a4d2933 binhex/arch-krusader "/usr/bin/dumb-init …" 4 days ago Up 10 hours 5900/tcp, 0.0.0.0:6080->6080/tcp, :::6080->6080/tcp binhex-krusader f3790ad35636 ghcr.io/hotio/sonarr:latest "/init" 4 days ago Up 3 minutes sonarr d11a68f18fe2 ghcr.io/recyclarr/recyclarr:latest "/sbin/tini -- /entr…" 4 days ago Up 10 hours recyclarr 1fc6c5bc70e1 jlesage/qdirstat "/init" 4 days ago Up 10 hours 0.0.0.0:7815->5800/tcp, :::7815->5800/tcp, 0.0.0.0:7915->5900/tcp, :::7915->5900/tcp QDirStat 9ed27c22c1df ghcr.io/home-assistant-libs/python-matter-server:stable "matter-server --sto…" 4 days ago Up 10 hours matter-server 3023f45d5b67 ich777/luckybackup "/opt/scripts/start.…" 4 days ago Up 10 hours 0.0.0.0:8086->8080/tcp, :::8086->8080/tcp luckyBackup 5109a81c570d jbartlett777/diskspeed "catalina.sh run" 4 days ago Up 10 hours 8080/tcp, 0.0.0.0:18888->8888/tcp, :::18888->8888/tcp DiskSpeed 763aeb21b35c jlesage/czkawka "/init" 4 days ago Up 10 hours 0.0.0.0:7821->5800/tcp, :::7821->5800/tcp, 0.0.0.0:7921->5900/tcp, :::7921->5900/tcp Czkawka 93aae5cb1024 lscr.io/linuxserver/airsonic-advanced "/init" 4 days ago Up 10 hours 0.0.0.0:4040->4040/tcp, :::4040->4040/tcp airsonic-advanced root@Locutus:~#
-
Docker containers on custom network don't have an IP address
Hi bartino, the result of running docker network ls root@Locutus:~# docker network ls NETWORK ID NAME DRIVER SCOPE 4eb6e48fe60b br0 ipvlan local 4974d5e68b6a bridge bridge local c23f590356ad host host local 9d85fee46172 none null local 781daf242b17 the-arrs bridge local root@Locutus:~# and now docker inspect network the-arrs root@Locutus:~# docker inspect network the-arrs [ { "Name": "the-arrs", "Id": "781daf242b174d8022d621313fdf7343d7b63a93e5b8de2aa790c2e1eccb28a8", "Created": "2024-11-16T13:23:48.915916839Z", "Scope": "local", "Driver": "bridge", "EnableIPv6": false, "IPAM": { "Driver": "default", "Options": {}, "Config": [ { "Subnet": "172.19.0.0/16", "Gateway": "172.19.0.1" } ] }, "Internal": false, "Attachable": false, "Ingress": false, "ConfigFrom": { "Network": "" }, "ConfigOnly": false, "Containers": { "337973fe3bac029155e79631848b04dee6ae3d441a5fabbea187f24ce11c0aec": { "Name": "prowlarr", "EndpointID": "1ba201437c5be293706424bb4fb67e60dcd7bc17a84987ea35c4a0baae61aa63", "MacAddress": "02:42:ac:13:00:03", "IPv4Address": "172.19.0.3/16", "IPv6Address": "" }, "9209317f760a9aa9fd69e8b1aab73472bd71ac8ce499c896f89843e555bbfe29": { "Name": "radarr", "EndpointID": "1686a7f67091ace56dfbf03a3968eda60ad9766b4d508ed2bb1cd37e2d1b8248", "MacAddress": "02:42:ac:13:00:04", "IPv4Address": "172.19.0.4/16", "IPv6Address": "" }, "c7172ee53700618f540ed19859ff07635ffa1c3e42ed198467647052035c8bbb": { "Name": "lidarr", "EndpointID": "ff85813ae4d9bc1e8d0d760ccc9caa1c3bde582d79a6502bd96e0ae94f593aa2", "MacAddress": "02:42:ac:13:00:02", "IPv4Address": "172.19.0.2/16", "IPv6Address": "" } }, "Options": {}, "Labels": {} } ] Error: No such object: network Thanks for your help with this.
-
Docker containers on custom network don't have an IP address
Hi all, JorgeB help me get my docker image rebuilt but now I have a different issue. Before installing al my applications I made a custom docker network called the-arrs that I use to run my media applications so they run in there own network. Now that the containers are running all but one or two have an IP address and I can't connect to them. Anyone have any ideas whats going on and how I can fix this.
-
A number of issues with docker
Thanks JorgB, As all the containers are now running I will start a new topic and hopfully someone will pick up the issue. Mirrormir
-
A number of issues with docker
Hi GorgB, Docker Image recreated and a application installed as per the links in your last post. All dockers container are running but strangely there is no network for Prowarr, Sonarr, Radarr, binhex-sabnzbd but Lidarr does. This has completely confused me to what has happen as it was all aging very well. I do run a custom docker network for above media application which I created before in stalling any application. I've attached a net diag but I guess as the server has been running a while won't show the detail requyired.locutus-diagnostics-20241117-0923.ziplocutus-diagnostics-20241117-0923.zip
-
A number of issues with docker
Hi GorgB, As requested a new diag locutus-diagnostics-20241114-0940.zip
-
A number of issues with docker
Hi GorgeB, I've taken a fresh diag but attched both todays and yesterdays with the hope you can see them. locutus-diagnostics-20241113-0823.ziplocutus-diagnostics-20241114-0743.zip
-
A number of issues with docker
Hi Gorge, Second try with the diags locutus-diagnostics-20241113-0823.zip
-
A number of issues with docker
Hi Support, I keep getting an issue with docker that once fixed comes back after a few weeks that the docker stops running and I have to restart my server. Most of the time this is okay as all seems to be fine except that a few containers don't start with the reboot and I have to start them manually, they seem to fine. But a short while later we have the same issue, back in August GorgB fixed this for me and since then I just restart the server this has happen about 4 time. This morning thing have moved on and the situation seems to be getting worst. It all started when I tryed to open sonaar and recieved a message saying "unable connect" so I checked docker thinking all I would need to do was restart sonaar, not so. I noticed that a couple of container titles were in orange. I ran a scrub on the docker image and there were a number of errors in the summary: read=28 csum=4 Corrected: 0 Uncorrectable: 32 Unverified: 0. Currently only 5 of the containers are running out of 26. I've done a diagnostic capture and attached the file if you require any further information let me know. locutus-diagnostics-20241113-0823.zip
-
UNRAID 6.12.11 Docker Service failed to start.
Thx Jorge that was it al back up and running as usual.
-
UNRAID 6.12.11 Docker Service failed to start.
Hi, Woke up this morning to find this error message on the docker tab. "Docker Service failed to start." Took a quick look around the system to see if I could find and clues but so far I have not. I've attached the diagnostics file I did this morning. I do run a plugin to auto update docker so it must have been during the docker restart that it had a problem and failed to start. locutus-diagnostics-20240828-0836.zip