jaybird2203

It is supported, keep in mind it's the holidays and the people who maintain this may be busy with other things.

I got mine working finally. I pointed it directly to an array disk then keeping both config and data in the same folder. Finally I generated a new key and it pulled last night. Only change between the previous installs was the new key. @chrono, what's the output of docker logs musicbrainz?

So tried the root of the cache drive, root of the SSD outside of the array that's mounted with Unassigned devices both with the same results. Finally I dropped it directly on one of the data disks in my array and finally it's pulling data as described. Both the drives above had 100+GB free but both were SSD's, one in the array, the other outside, any idea why the docker isn't able to be properly mapped to either of the devices? Update: Spoke too soon. Docker stopped with the below details, specifically curl: (78) RETR response: 550 *** /etc/my_init.d/40_initialise.sh failed with status 78 *** Running /etc/my_init.d/005_set_time.sh... Current default time zone: 'America/New_York' Local time is now: Fri Dec 25 23:48:43 EST 2015. Universal Time is now: Sat Dec 26 04:48:43 UTC 2015. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/10_add_user_abc.sh... ----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- *** Running /etc/my_init.d/20_apt_update.sh... We are now refreshing packages from apt repositorys, this *may* take a while (Reading database ... 27044 files and directories currently installed.) Preparing to unpack .../git-core_1%3a1.9.1-1ubuntu0.2_all.deb ... Unpacking git-core (1:1.9.1-1ubuntu0.2) over (1:1.9.1-1ubuntu0.1) ... Setting up git-core (1:1.9.1-1ubuntu0.2) ... *** Running /etc/my_init.d/30_set_config.sh... *** Running /etc/my_init.d/40_initialise.sh... initialising empty databases completed postgres initialise BEGINNING INITIAL DATABASE IMPORT ROUTINE, THIS COULD TAKE SEVERAL HOURS AND THE DOCKER MAY LOOK UNRESPONSIVE DO NOT STOP DOCKER UNTIL IT IS COMPLETED % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 64.5M 100 64.5M 0 0 4738k 0 0:00:13 0:00:13 --:--:-- 7804k % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 18.0M 100 18.0M 0 0 2407k 0 0:00:07 0:00:07 --:--:-- 3906k % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 115M 100 115M 0 0 5910k 0 0:00:20 0:00:20 --:--:-- 7791k % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- 0:00:01 --:--:-- 0 curl: (78) RETR response: 550 *** /etc/my_init.d/40_initialise.sh failed with status 78 *** Killing all processes...

I've tried the cache drive as well which has well over 90GB free with the same results. I'll try not nesting and report back. Again, it's only this docker that I'm having these issues with on the ssd that's mounted with unassigned devices.

docker logs musicbrainz as requested. *** Running /etc/my_init.d/005_set_time.sh... Current default time zone: 'America/New_York' Local time is now: Wed Dec 23 22:17:03 EST 2015. Universal Time is now: Thu Dec 24 03:17:03 UTC 2015. *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/10_add_user_abc.sh... ----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- *** Running /etc/my_init.d/20_apt_update.sh... We are now refreshing packages from apt repositorys, this *may* take a while (Reading database ... 27044 files and directories currently installed.) Preparing to unpack .../git-core_1%3a1.9.1-1ubuntu0.2_all.deb ... Unpacking git-core (1:1.9.1-1ubuntu0.2) over (1:1.9.1-1ubuntu0.1) ... Setting up git-core (1:1.9.1-1ubuntu0.2) ... *** Running /etc/my_init.d/30_set_config.sh... *** Running /etc/my_init.d/40_initialise.sh... initialising empty databases *** /etc/my_init.d/40_initialise.sh failed with status 1 *** Killing all processes... *** Running /etc/my_init.d/005_set_time.sh... *** Running /etc/my_init.d/00_regen_ssh_host_keys.sh... *** Running /etc/my_init.d/10_add_user_abc.sh... ----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- *** Running /etc/my_init.d/20_apt_update.sh... We are now refreshing packages from apt repositorys, this *may* take a while *** Running /etc/my_init.d/30_set_config.sh... *** Running /etc/my_init.d/40_initialise.sh... initialising empty databases *** /etc/my_init.d/40_initialise.sh failed with status 1 *** Killing all processes... root@Tower:~# @Splnut This was found by ssh into the unraid tower, typing 'docker logs musicbrainz' without quote

Attached are my mappings etc as requested from the other thread. This drive is mounted with unassigned devices and works for the other dockers I have, it was just this one docker that fails after grabbing. even tried mapping the files to the cache drive with the below log messages. Refresh the dashboard page and the docker is shown as off. ----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- We are now refreshing packages from apt repositorys, this *may* take a while (Reading database ... 27044 files and directories currently installed.) Preparing to unpack .../git-core_1%3a1.9.1-1ubuntu0.2_all.deb ... Unpacking git-core (1:1.9.1-1ubuntu0.2) over (1:1.9.1-1ubuntu0.1) ... Setting up git-core (1:1.9.1-1ubuntu0.2) ... initialising empty databases completed postgres initialise BEGINNING INITIAL DATABASE IMPORT ROUTINE, THIS COULD TAKE SEVERAL HOURS AND THE DOCKER MAY LOOK UNRESPONSIVE DO NOT STOP DOCKER UNTIL IT IS COMPLETED

It's going to have to wait, tapatalk isn't allowing me to post images from my mobile.

Even with the docker itself giving the option to start? Just want to make sure things are in motion.

Of course not, I use the same directories but delete all contents. After I pull the data for the docker, the docker itself is stopped with the below in the logs with the docker stopped. ----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| Brought to you by linuxserver.io ----------------------------------- GID/UID ----------------------------------- User uid: 99 User gid: 100 ----------------------------------- We are now refreshing packages from apt repositorys, this *may* take a while (Reading database ... 27044 files and directories currently installed.) Preparing to unpack .../git-core_1%3a1.9.1-1ubuntu0.2_all.deb ... Unpacking git-core (1:1.9.1-1ubuntu0.2) over (1:1.9.1-1ubuntu0.1) ... Setting up git-core (1:1.9.1-1ubuntu0.2) ... initialising empty databases

For some odd reason when I run the recommended version it doesn't stay started. I'll swap the dockers and post the logs again.

So this is what I get in the logs right from when the first import was happening. The lines at the end (copied below) were repeating every hour. Dec 22 00:00:01 9bc372c1b5a3 /USR/SBIN/CRON[1195]: (root) CMD (/bin/bash /root/update-script.sh) Dec 22 00:00:02 9bc372c1b5a3 /USR/SBIN/CRON[1194]: (CRON) info (No MTA installed, discarding output) The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale "en_US.UTF-8". The default database encoding has accordingly been set to "UTF8". The default text search configuration will be set to "english". Data page checksums are disabled. fixing permissions on existing directory /data/main ... 2015-12-21 23:15:36,131 CRIT Supervisor running as root (no user in config file) 2015-12-21 23:15:36,133 INFO supervisord started with pid 39 2015-12-21 23:15:37,136 INFO spawned: 'redis-server' with pid 43 2015-12-21 23:15:37,137 INFO spawned: 'postgres' with pid 44 2015-12-21 23:15:37,149 INFO exited: postgres (exit status 2; not expected) 2015-12-21 23:15:38,153 INFO success: redis-server entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2015-12-21 23:15:38,154 INFO spawned: 'postgres' with pid 47 2015-12-21 23:15:38,165 INFO exited: postgres (exit status 2; not expected) 2015-12-21 23:15:40,169 INFO spawned: 'postgres' with pid 48 2015-12-21 23:15:40,179 INFO exited: postgres (exit status 2; not expected) 2015-12-21 23:15:43,184 INFO spawned: 'postgres' with pid 49 2015-12-21 23:15:43,195 INFO exited: postgres (exit status 2; not expected) 2015-12-21 23:15:44,196 INFO gave up: postgres entered FATAL state, too many start retries too quickly BEGINNING INITIAL DATABASE IMPORT ROUTINE, THIS COULD TAKE SEVERAL HOURS AND THE DOCKER MAY LOOK UNRESPONSIVE DO NOT STOP DOCKER UNTIL IT IS COMPLETED /data/import / mbdump-cdstubs.tar.bz2: OK mbdump-cover-art-archive.tar.bz2: OK mbdump-derived.tar.bz2: OK mbdump-documentation.tar.bz2: FAILED open or read mbdump-edit.tar.bz2: FAILED open or read mbdump-editor.tar.bz2: OK mbdump-sitemaps.tar.bz2: FAILED open or read mbdump-stats.tar.bz2: OK mbdump-wikidocs.tar.bz2: OK mbdump.tar.bz2: OK IMPORT IS COMPLETE, MOVING TO NEXT PHASE Dec 21 23:22:17 9bc372c1b5a3 syslog-ng[77]: syslog-ng starting up; version='3.5.3' Dec 21 23:59:01 9bc372c1b5a3 /USR/SBIN/CRON[1158]: (root) CMD (/bin/bash /root/update-script.sh) Dec 21 23:59:02 9bc372c1b5a3 /USR/SBIN/CRON[1157]: (CRON) info (No MTA installed, discarding output) Dec 22 00:00:01 9bc372c1b5a3 /USR/SBIN/CRON[1195]: (root) CMD (/bin/bash /root/update-script.sh) Dec 22 00:00:02 9bc372c1b5a3 /USR/SBIN/CRON[1194]: (CRON) info (No MTA installed, discarding output)

are you mapping the /data volume to a large enough drive ? Yes, mapped to a 256gb ssd that I mapped my other dockers to which detect the full 235gb after format.

I get a similar situation, fresh install last night, let it run over night before checking any logs and the total file size is just over 2Gb I'll upload the logs and error messages in detail this evening.

For some reason when I formatted with unassigned devices previously it had saved a 7.1Gb partition, even though it wasn't showing as such. I just finished reformatting the complete drive first partitioning it with gdisk then formatting with unassigned devices, reinstalled SAB from scratch but program is still only detecting the 7.1GB free. This time in the SAB folder settings the folders stuck with the correct folder and not the /config/downloads folder. Last ditch effort is to rename the partition again without any kind of hyphens or underscores. In the mean time I'm installing it again to the cache drive to see what happens there. UPDATE:When installed to the cache drive (where the docker img is) the program reports the remaining ~90GB free space so next step is to try to remap to the new drive outside of the array. UPDATE 2: as soon as I map the folders to the unassigned device drive it drops back down to 7.1GB free. going to format again but not using the unassigned devices plugin to see if that is the cause. Didn't realize the time, I'll play with the system again tomorrow. It looks like some issue with the SSD I'm using outside of the array is formatted. I'm on the road so it's going to have to wait until I get back as I've tried formatting using unassigned devices (current situation) mkfs.xfs (won't format properly), even tried to preclear the drive with no difference. Every time it is mounted using unassigned devices and the sab install mapped to it sab reverts to 7.1Gb So finally got it sorted, for some reason everytime I reformatted the SSD unassigned devices would still see the original partition, I ended up removing unassigned devices, went into the flash drive and removed the folder for it as well. Restarted the unraid server then reinstalled unassigned devices. I put the original script in for using the unassigned devices as a docker/VM drive back in again and restarted the server once again. Finally the SAB docker was able to use all free space on the SSD.

Think I found the issue, going to confirm for certain.

Still no go. Renamed the partition to Samsung_SSD_850, just curious, do you have any underscores or hyphens in the folder structure at all? from /mnt/virtualisation down? Going to wipe everything and start from scratch as nothing has been set in stone as of yet. Just another thought, you know Linux is case sensitive right? Good practice to keep everything in lowercase to simplify stuff. Of course, this is from the person who spent over four hours today trying to work out why a variable in a script wouldn't work, then facepalmed when her realised it was a capitalisation issue.... Yeah, I know it's case sensitive, the odd thing is that I continually select the paths via the drop down which should remove any chance of the incorrect case/spelling in my eyes anyways.

Still no go. Renamed the partition to Samsung_SSD_850, just curious, do you have any underscores or hyphens in the folder structure at all? from /mnt/virtualisation down? Going to wipe everything and start from scratch as nothing has been set in stone as of yet.

I appreciate the detailed response, I'm pretty certain that I restarted the container with no change but I'll try again after work.

Another interesting situation occurred. I stopped the array to see if there was a simple way to move the docker image which was no real help since docker can only be managed when the array is running but when I restarted the array the newly added dockers (Couchpotato, SAB and Sonarr) all reverted back to fresh installs. I'm assuming that is due to the /config folders being blank as they're all mapped to the same drive.

Yes I do have a 10.7Gb docker image, located on the cache drive of the array but it's cache only so it won't be moved. So to recap, docker image is on the cache drive of my array, folders are mapped to folders outside of array. Would this be the issue? If so, is there a simple way to move the docker image from the cache drive to the unassigned drive as that's where I'll be keeping the additional folders. Here's the details.

Here you go. Aside from the full mapping being shown that is. Naming is too long to show all at once with the drop down. Should also mention that this does affect the ability to download files larger than the 7.1Gb that are showing as free.

First off, thank you greatly for the linuxserver.io dockers, each of the ones I've enabled are able to start without much configuration whatsoever. Although after running through this setup I have a quick question for the guru's about how I have my system setup with this docker. System is running unraid 6.1.6 , SAB 0.8.0Beta3 [0b6395f], I've mapped the folders to a 256Gb SSD formatted with xfs I've mounted using unassigned devices outside of my array with some basic folder structure in the root (/SAB/downloads/ and /SAB/incomplete/ etc for example) to keep each docker separate for basic house keeping. According to Unassigned devices the SSD has a total used of 9.1GB out of the 256Gb (for some reason it's also reporting that it has 253Tb free which I'm guessing has more to do with how the drive is reporting to unassigned devices but that's another issue to track down at a later time) My issue is that even when I've mapped the folders correctly, SAB is reporting only 7.1Gb free space, even though the SSD has more than that free. Is this something that I should be concerned with? I have yet to initiate a download but wanted to confirm if what SAB is reporting is the correct amount of free space for the download/temp folder.