Cstolworthy

Interesting, I changed the data drive to the cache drive and everything started working fine.

The run command is: /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker run -d --name="unifi" --net="bridge" -e TZ="America/Los_Angeles" -e HOST_OS="unRAID" -e "PUID"="99" -e "PGID"="100" -p 8080:8080/tcp -p 8081:8081/tcp -p 8443:8443/tcp -p 8843:8843/tcp -p 8880:8880/tcp -v "/mnt/user/appdata/unifi/config/":"/config":rw linuxserver/unifi 5a11219372e77d33f4313fc86afbbb608333d70324a10308329d869c2d798019

I just recently installed the Unifi docker via unraid. However whenever I have tried to access the Web UI, it would never respond. To ensure a cleaner state, I removed the container entirely and deleted the data directory. I then re-setup a container (didn't user the my-unifi option available in the interface, and went with defaults on everything except data directory.). I have attached the log files from that run to this post. From what I can gather, Mongo is failing to start which makes the controller fail to boot. This is where things start to die: 2017-02-01T23:18:18.577-0800 [initandlisten] journal dir=/usr/lib/unifi/data/db/journal 2017-02-01T23:18:18.578-0800 [initandlisten] recover : no journal files present, no recovery needed 2017-02-01T23:18:18.578-0800 [initandlisten] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes; b=0x3846000 errno:22 Invalid argument 2017-02-01T23:18:18.578-0800 [initandlisten] Fatal Assertion 13515 2017-02-01T23:18:18.580-0800 [initandlisten] 0xedb3e9 0xe6fb3f 0xe4a1c1 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2ba0ddfd3830 0x61a2d9 bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9] bin/mongod(_ZN5mongo10logContextEPKc+0x21f) [0xe6fb3f] bin/mongod(_ZN5mongo13fassertFailedEi+0x71) [0xe4a1c1] bin/mongod(_ZN5mongo7LogFile17synchronousAppendEPKvm+0x29b) [0xe7039b] bin/mongod(_ZN5mongo3dur20_preallocateIsFasterEv+0x22a) [0x8869fa] bin/mongod(_ZN5mongo3dur19preallocateIsFasterEv+0x2a) [0x886f3a] bin/mongod(_ZN5mongo3dur16preallocateFilesEv+0x966) [0x88ea86] bin/mongod(_ZN5mongo3dur7startupEv+0x74) [0x87d184] bin/mongod(_ZN5mongo14_initAndListenEi+0x76f) [0x61f92f] bin/mongod(_ZN5mongo13initAndListenEi+0x23) [0x620903] bin/mongod(main+0x23c) [0x5e943c] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x2ba0ddfd3830] bin/mongod(_start+0x29) [0x61a2d9] 2017-02-01T23:18:18.580-0800 [initandlisten] After this, it throws one more exception(below) before restarting the process: ***aborting after fassert() failure 2017-02-01T23:18:22.703-0800 [initandlisten] SEVERE: Got signal: 6 (Aborted). Backtrace:0xedb3e9 0xeda3a5 0x2ade19e344b0 0x2ade19e34428 0x2ade19e3602a 0xe4a213 0xe7039b 0x8869fa 0x886f3a 0x88ea86 0x87d184 0x61f92f 0x620903 0x5e943c 0x2ade19e1f830 0x61a2d9 bin/mongod(_ZN5mongo15printStackTraceERSo+0x39) [0xedb3e9] bin/mongod() [0xeda3a5] /lib/x86_64-linux-gnu/libc.so.6(+0x354b0) [0x2ade19e344b0] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x38) [0x2ade19e34428] /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x2ade19e3602a] bin/mongod(_ZN5mongo13fassertFailedEi+0xc3) [0xe4a213] bin/mongod(_ZN5mongo7LogFile17synchronousAppendEPKvm+0x29b) [0xe7039b] bin/mongod(_ZN5mongo3dur20_preallocateIsFasterEv+0x22a) [0x8869fa] bin/mongod(_ZN5mongo3dur19preallocateIsFasterEv+0x2a) [0x886f3a] bin/mongod(_ZN5mongo3dur16preallocateFilesEv+0x966) [0x88ea86] bin/mongod(_ZN5mongo3dur7startupEv+0x74) [0x87d184] bin/mongod(_ZN5mongo14_initAndListenEi+0x76f) [0x61f92f] bin/mongod(_ZN5mongo13initAndListenEi+0x23) [0x620903] bin/mongod(main+0x23c) [0x5e943c] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x2ade19e1f830] bin/mongod(_start+0x29) [0x61a2d9] Let me know if there is anything else I can provide. Thanks! mongod.txt server.txt

Change the configuration folder location to either a cache drive or if you don't have one, a disk location. /mnt/cache/blah /mnt/diskX/blah I deleted the container and image, added it fresh and changed /config to point to /mnt/cache/appdata/plexrequests I am still seeing the same issue Can you post a log? Also, how long did you wait? At container start, it updates meteor and a couple of times I noticed the meteor servers being ridiculously slow. It took 20 minutes for the update After 45 minutes, the docker started responding. It looks like the meteor servers were just really bogged down. Thanks for the help, and for the awesome docker containers!

Change the configuration folder location to either a cache drive or if you don't have one, a disk location. /mnt/cache/blah /mnt/diskX/blah I deleted the container and image, added it fresh and changed /config to point to /mnt/cache/appdata/plexrequests I am still seeing the same issue

I am having an issue with the plex requests docker. Everything appears to pull and install correctly, docker reports that the container is started. But when I attempt to browse to the service, it gives me a "Connection refused". I can't seem to find any logs, so I am not sure how to troubleshoot it at this point. Here is a screenshot of my configuration: http://i.imgur.com/WKXiZW3.png