joshstrange

I'll start by saying I have 2 other unraid boxes that are working perfectly fine but on my new server I'm having some issues. Whenever I try to copy data to the array it crashes the server. I've tried tailing syslog on the box while doing this but nothing pops in. I've tried both a local copy from an external hard drive and a copy over the network and both resulted in the same crash. Sometimes the box comes back up (with the array not mounted) and sometimes I have to shut off the machine manually and restart it to be able to ping it again. I'm not sure what else I can do. I've attached the diagnostic log. Unraid version: 6.2.4 Array: 1 5TB hard drive, no cache, no parity. tower-diagnostics-20170101-0914.zip

I can't seem to access the the WebUI. I get a Connection refused and I've let the docker run for quite a long time. There is nothing in the logs past: 160118 12:48:21 mysqld_safe Logging to '/var/lib/mysql/96c0209c5475.err'. 160118 12:48:21 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql And the folders that are mounted are empty. I've tried restarting it multiple times but nothing seems to be happening.

Thank you very much for the suggestion and proposed fix. I guess I'm just going to have to run Sonarr in my debian VM instead of trying to get the docker container to work. Also thank you for informing me that docker image and unraid host OS share the same kernel as I did not know that before!

Let me start off by saying I am loving docker in unRaid 6 and I am using it heavily. I am currently having a problem with one of my containers which I *think* is related to a bug in the docker image kernel (https://forums.sonarr.tv/t/native-mono-crashes-kernel-fix-released/4985/136). If I understand correctly containers share the host kernel and so the bug must exist in the docker image that all the containers run in. How would I go about checking what version of kernel it is running and updating it if it turns out that is the culprit. I've done a ton of searching both on google and these forums but I've come up with nothing. Am I crazy or is this possible?

Thanks! Restarting the array fixed the messages. If they happen again I'll track them back to the start in syslog.

Filesystem Size Used Avail Use% Mounted on tmpfs 128M 79M 50M 62% /var/log /dev/sda1 7.5G 208M 7.3G 3% /boot /dev/md1 4.6T 3.8T 776G 84% /mnt/disk1 /dev/md2 4.6T 3.8T 841G 82% /mnt/disk2 /dev/md3 4.6T 3.7T 918G 81% /mnt/disk3 /dev/md4 4.6T 4.2T 428G 91% /mnt/disk4 /dev/md5 4.6T 2.6T 2.1T 56% /mnt/disk5 /dev/md6 4.6T 2.8T 1.8T 62% /mnt/disk6 /dev/sdb1 236G 45G 187G 20% /mnt/cache shfs 28T 21T 6.7T 76% /mnt/user0 shfs 28T 21T 6.9T 76% /mnt/user /dev/loop0 10G 5.1G 3.8G 58% /var/lib/docker /dev/loop1 1.8M 85K 1.6M 6% /etc/libvirt

If I click the "Log" button in the web UI I see a ton of these messages: Jul 18 00:01:46 Tower shfs/user: share cache full Jul 18 00:01:48 Tower shfs/user: share cache full Jul 18 00:01:48 Tower shfs/user: share cache full Jul 18 00:01:49 Tower shfs/user: share cache full Jul 18 00:01:49 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:50 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:53 Tower shfs/user: share cache full Jul 18 00:01:54 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Jul 18 00:01:55 Tower shfs/user: share cache full Both googling and searching the forums didn't bring up anything. Should I be worried about this? What does it mean? Thanks!

There was a slight change in Kode's application feed which caused that. The system was working correctly with the feed as it was on 7/15. Sometime on 7/16 the feed changed (The notice that the feed was changing probably got lost in a PM along the line) Since you were running in the appFeed mode, you could have reverted back to the old template mode and it would have worked correctly. (Or, with the update 7/16, hit Update Applications, and the error would have fixed itself) Thanks for this! I didn't see the error but when I went to add an application the add container page would be empty instead of prefilled. Clicking the "Update Applications" on the Docker tab for CA worked and now I can add applications again.

I'm having the same problem. I did a "docker attach $containerId" to get the url (didn't think to look in the logs) to do oauth with and then restarted the container after I got it linked and now all I can get is that message. EDIT: It would appear this is the issue it's a pull request on gfjardim's github for the dropbox container. It was post 15 days ago and it's a 1 line (ok technically 2 line) fix and hopefully gfjardim will merge it soon and trigger a rebuild of the container so we can update. EDIT 2: Ok if you are getting the error above causing your container to die 2 seconds after starting then until gfjardim accepts the pull request you can just edit the docker container (from web UI), toggle Advanced View, and change the repository to "joshstrange/unraid-dropbox", then press Save. I am not planning on providing any support whatsoever and offer no guarantees it will work for you but it works for me. Know that this is only a stopgap until the pull request is merged then you can go back to using gfjardim's repo.