FLK Posted March 25, 2015 Share Posted March 25, 2015 Hi, I'm trying to setup miniDLNA... but I have some errors : On the /config I have two logs files : [2015/03/26 00:27:20] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf [2015/03/26 00:27:21] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf [2015/03/26 00:27:23] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf [2015/03/26 00:27:26] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf 2015-03-26 00:27:19,696 CRIT Set uid to user 0 2015-03-26 00:27:19,696 WARN Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2015-03-26 00:27:19,702 INFO supervisord started with pid 1 2015-03-26 00:27:20,703 INFO spawnerr: can't find command '/run/minidlna/start.sh' 2015-03-26 00:27:20,709 INFO spawned: 'minidlna' with pid 8 2015-03-26 00:27:20,736 DEBG 'minidlna' stdout output: [2015/03/26 00:27:20] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf 2015-03-26 00:27:20,738 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47356028119952 for <Subprocess at 47356028119376 with name minidlna in state STARTING> (stdout)> 2015-03-26 00:27:20,738 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 00:27:20,738 DEBG received SIGCLD indicating a child quit 2015-03-26 00:27:21,740 INFO spawnerr: can't find command '/run/minidlna/start.sh' 2015-03-26 00:27:21,746 INFO spawned: 'minidlna' with pid 9 2015-03-26 00:27:21,775 DEBG 'minidlna' stdout output: [2015/03/26 00:27:21] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf 2015-03-26 00:27:21,776 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47356028120096 for <Subprocess at 47356028119376 with name minidlna in state STARTING> (stdout)> 2015-03-26 00:27:21,776 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 00:27:21,777 DEBG received SIGCLD indicating a child quit 2015-03-26 00:27:23,779 INFO spawnerr: can't find command '/run/minidlna/start.sh' 2015-03-26 00:27:23,785 INFO spawned: 'minidlna' with pid 10 2015-03-26 00:27:23,814 DEBG 'minidlna' stdout output: [2015/03/26 00:27:23] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf 2015-03-26 00:27:23,816 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47356028119880 for <Subprocess at 47356028119376 with name minidlna in state STARTING> (stdout)> 2015-03-26 00:27:23,816 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 00:27:23,816 DEBG received SIGCLD indicating a child quit 2015-03-26 00:27:26,820 INFO spawnerr: can't find command '/run/minidlna/start.sh' 2015-03-26 00:27:26,820 INFO gave up: start entered FATAL state, too many start retries too quickly 2015-03-26 00:27:26,826 INFO spawned: 'minidlna' with pid 11 2015-03-26 00:27:26,855 DEBG 'minidlna' stdout output: [2015/03/26 00:27:26] minidlna.c:541: fatal: Error reading configuration file /config/minidlna.conf 2015-03-26 00:27:26,856 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47356028120096 for <Subprocess at 47356028119376 with name minidlna in state STARTING> (stdout)> 2015-03-26 00:27:26,857 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 00:27:26,857 DEBG received SIGCLD indicating a child quit 2015-03-26 00:27:27,858 INFO gave up: minidlna entered FATAL state, too many start retries too quickly So he can't write to my /config dir... but logs are here... so? My config dir is /mnt/cache/docker/dlna the dlna folder is created by the installation script, and dir rights looks OK : drwxrwxrwx 1 nobody users 92 Mar 26 00:27 dlna/ Maybe the main problem come from that error : can't find command '/run/minidlna/start.sh' ? any idea ? thanks ! EDIT: If i manually create the minidlna.conf file in /config (from https://github.com/binhex/arch-minidlna/blob/master/minidlna.conf) 2015-03-26 00:55:01,179 CRIT Set uid to user 0 2015-03-26 00:55:01,179 WARN Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2015-03-26 00:55:01,182 INFO supervisord started with pid 1 2015-03-26 00:55:02,183 INFO spawnerr: can't find command '/run/minidlna/start.sh' 2015-03-26 00:55:02,189 INFO spawned: 'minidlna' with pid 8 2015-03-26 00:55:02,217 DEBG 'minidlna' stdout output: parsing error file /config/minidlna.conf line 1 : [program:start] parsing error file /config/minidlna.conf line 3 : startsecs=0 parsing error file /config/minidlna.conf line 4 : autorestart=False parsing error file /config/minidlna.conf line 5 : command=/run/minidlna/start.sh parsing error file /config/minidlna.conf line 7 : [program:minidlna] parsing error file /config/minidlna.conf line 8 : stdout_logfile=/config/supervisord-minidlna-stdout.log parsing error file /config/minidlna.conf line 9 : stdout_logfile_maxbytes=10MB parsing error file /config/minidlna.conf line 10 : stdout_logfile_backups=5 parsing error file /config/minidlna.conf line 11 : redirect_stderr=true parsing error file /config/minidlna.conf line 13 : command=/usr/bin/minidlnad -S -R -f /config/minidlna.conf 2015-03-26 00:55:02,227 DEBG 'minidlna' stdout output: minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/var/cache/minidlna] ownership to 99: Operation not permitted minidlna.c:1026: warn: Starting MiniDLNA version 1.1.4. 2015-03-26 00:55:02,227 DEBG 'minidlna' stdout output: minidlna.c:294: fatal: ERROR: Failed to open sqlite database! Exiting... 2015-03-26 00:55:02,229 DEBG fd 6 closed, stopped monitoring (stdout)> 2015-03-26 00:55:02,229 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 00:55:02,229 DEBG received SIGCLD indicating a child quit 2015-03-26 00:55:03,231 INFO spawnerr: can't find command '/run/minidlna/start.sh' 2015-03-26 00:55:03,237 INFO spawned: 'minidlna' with pid 10 2015-03-26 00:55:03,267 DEBG 'minidlna' stdout output: parsing error file /config/minidlna.conf line 1 : [program:start] parsing error file /config/minidlna.conf line 3 : startsecs=0 parsing error file /config/minidlna.conf line 4 : autorestart=False parsing error file /config/minidlna.conf line 5 : command=/run/minidlna/start.sh parsing error file /config/minidlna.conf line 7 : [program:minidlna] parsing error file /config/minidlna.conf line 8 : stdout_logfile=/config/supervisord-minidlna-stdout.log parsing error file /config/minidlna.conf line 9 : stdout_logfile_maxbytes=10MB parsing error file /config/minidlna.conf line 10 : stdout_logfile_backups=5 parsing error file /config/minidlna.conf line 11 : redirect_stderr=true parsing error file /config/minidlna.conf line 13 : command=/usr/bin/minidlnad -S -R -f /config/minidlna.conf 2015-03-26 00:55:03,278 DEBG 'minidlna' stdout output: minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/var/cache/minidlna] ownership to 99: Operation not permitted minidlna.c:1026: warn: Starting MiniDLNA version 1.1.4. 2015-03-26 00:55:03,278 DEBG 'minidlna' stdout output: minidlna.c:294: fatal: ERROR: Failed to open sqlite database! Exiting... 2015-03-26 00:55:03,281 DEBG fd 6 closed, stopped monitoring (stdout)> 2015-03-26 00:55:03,281 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 00:55:03,282 DEBG received SIGCLD indicating a child quit Link to comment
binhex Posted March 26, 2015 Author Share Posted March 26, 2015 Maybe the main problem come from that error : can't find command '/run/minidlna/start.sh' that was the issue, i did a mass tidy up a while ago and didn't change the path in the supervisor conf file for minidlna, its now fixed and a new image created, please do an update and see if it fixes the issue. Link to comment
gswarriorfan Posted March 26, 2015 Share Posted March 26, 2015 Is it possible to use the delugeVPN docker and openvpn server plugin simultaneously? I just upgraded to unraid 6 beta14 last night and I'm researching using dockers instead of plugins. My goal is to have deluge download behind my PIA VPN, and have the ability to VPN into my unraid box with my Android phone/tablet for remote access. just thought of another question: Does the extract feature of deluge work in a docker? Some files I torrent come zipped as rar. I would like it to automatically unrar after download. Thanks! Link to comment
HarryRosen Posted March 26, 2015 Share Posted March 26, 2015 I run the OpenVPN server and delugeVPN at the same time no problems Link to comment
FLK Posted March 26, 2015 Share Posted March 26, 2015 Maybe the main problem come from that error : can't find command '/run/minidlna/start.sh' that was the issue, i did a mass tidy up a while ago and didn't change the path in the supervisor conf file for minidlna, its now fixed and a new image created, please do an update and see if it fixes the issue. Looks like another permissions issue Sorry I can't help you more... Both logs : (conf file is OK now) minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. 2015-03-26 17:32:07,656 CRIT Set uid to user 0 2015-03-26 17:32:07,656 WARN Included extra file "/etc/supervisor/conf.d/minidlna.conf" during parsing 2015-03-26 17:32:07,661 INFO supervisord started with pid 1 2015-03-26 17:32:08,668 INFO spawned: 'start' with pid 8 2015-03-26 17:32:08,671 INFO spawned: 'minidlna' with pid 9 2015-03-26 17:32:08,684 DEBG 'start' stderr output: chown: changing ownership of ‘/config/supervisord.log’: Operation not permitted chown: changing ownership of ‘/config/supervisord-minidlna-stdout.log’: Operation not permitted chown: changing ownership of ‘/config/minidlna.conf’: Operation not permitted 2015-03-26 17:32:08,684 INFO success: start entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2015-03-26 17:32:08,684 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47310157347800 for <Subprocess at 47310157347368 with name start in state RUNNING> (stderr)> 2015-03-26 17:32:08,684 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47310157347440 for <Subprocess at 47310157347368 with name start in state RUNNING> (stdout)> 2015-03-26 17:32:08,684 INFO exited: start (exit status 1; not expected) 2015-03-26 17:32:08,685 DEBG received SIGCLD indicating a child quit 2015-03-26 17:32:08,717 DEBG 'minidlna' stdout output: minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. 2015-03-26 17:32:08,722 DEBG fd 9 closed, stopped monitoring <POutputDispatcher at 47310157348232 for <Subprocess at 47310157347152 with name minidlna in state STARTING> (stdout)> 2015-03-26 17:32:08,722 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 17:32:08,722 DEBG received SIGCLD indicating a child quit 2015-03-26 17:32:09,728 INFO spawned: 'minidlna' with pid 13 2015-03-26 17:32:09,770 DEBG 'minidlna' stdout output: minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. 2015-03-26 17:32:09,774 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47310157348664 for <Subprocess at 47310157347152 with name minidlna in state STARTING> (stdout)> 2015-03-26 17:32:09,774 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 17:32:09,774 DEBG received SIGCLD indicating a child quit 2015-03-26 17:32:11,782 INFO spawned: 'minidlna' with pid 15 2015-03-26 17:32:11,819 DEBG 'minidlna' stdout output: minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. 2015-03-26 17:32:11,821 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47310157348088 for <Subprocess at 47310157347152 with name minidlna in state STARTING> (stdout)> 2015-03-26 17:32:11,822 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 17:32:11,822 DEBG received SIGCLD indicating a child quit 2015-03-26 17:32:14,829 INFO spawned: 'minidlna' with pid 17 2015-03-26 17:32:14,871 DEBG 'minidlna' stdout output: minidlna.c:438: error: Unable to open pidfile for writing /var/run/minidlna/minidlna.pid: Permission denied minidlna.c:975: error: Unable to set db_path [/config] ownership to 997: Operation not permitted minidlna.c:980: fatal: Failed to switch to uid '997'. [Operation not permitted] EXITING. 2015-03-26 17:32:14,875 DEBG fd 6 closed, stopped monitoring <POutputDispatcher at 47310157347800 for <Subprocess at 47310157347152 with name minidlna in state STARTING> (stdout)> 2015-03-26 17:32:14,875 INFO exited: minidlna (exit status 255; not expected) 2015-03-26 17:32:14,875 DEBG received SIGCLD indicating a child quit 2015-03-26 17:32:15,876 INFO gave up: minidlna entered FATAL state, too many start retries too quickly Link to comment
FLK Posted March 27, 2015 Share Posted March 27, 2015 @binhex: looks like you updated the miniDLNA container, everything is working now! Thanks a lot Link to comment
djstabby Posted March 28, 2015 Share Posted March 28, 2015 Hey binhex, I have been using the delugevpn, and it has been working great. I was wondering if you are still looking into access to the daemon via local network. The webui works OK, but you can't create any uploads with it, and it runs fairly slow with a lot loaded into it. Another thing I noticed is it does not get a new port to forward once the one goes down. With PIA that seems to happen about every 24 hours. Any thoughts on just grabbing a new port every 12 or 24 hours? Thanks again for all the great dockers and all the work you put in. Link to comment
gswarriorfan Posted March 30, 2015 Share Posted March 30, 2015 Sorry, I am a Deluge noob. Quick question. I just set up the docker with my pia username and password, and I believe everything is working fine. I am able to access the Deluge webui, but when I add a torrent, it doesn't start downloading. It just sits there at 0.0%. I'm downloading the torrent from iptorrents to my computer and uploading via the Deluge webui. Bonus question: Should I use the same directory that I set for /data in the docker setup as my downloads folder? Link to comment
binhex Posted March 30, 2015 Author Share Posted March 30, 2015 @binhex: looks like you updated the miniDLNA container, everything is working now! Thanks a lot FLK no probs :-), your a little quick on the trigger, i made some further improvements to this, so at your leisure, do another pull down Link to comment
binhex Posted March 30, 2015 Author Share Posted March 30, 2015 Hey binhex, I have been using the delugevpn, and it has been working great. I was wondering if you are still looking into access to the daemon via local network. The webui works OK, but you can't create any uploads with it, and it runs fairly slow with a lot loaded into it. Another thing I noticed is it does not get a new port to forward once the one goes down. With PIA that seems to happen about every 24 hours. Any thoughts on just grabbing a new port every 12 or 24 hours? Thanks again for all the great dockers and all the work you put in. indeed i am still looking into daemon access, i am just flat out at the moment at work, so not having much time at present. i did have a stab at this but didnt get anywhere with it, but i havent forgotten about the issue and will try and get time to take a look. with regards to your comment about the "new port to forward", this shouldn't be happening every 24 hours, the only time you should get a new port is when your tunnel drops and re-establishes, when this happens you will typically get a dynamically assigned new incoming port, i have code built into this docker to deal with this based on current ip, if it detects a new ip it will reconfigure the incoming port. i have had delugevpn running for several days now and the incoming port is still the same as it was and i still have fast download speeds so the port is still active, not sure why/how you are seeing the need to reconfigure the port every 24 hours?. Link to comment
binhex Posted March 30, 2015 Author Share Posted March 30, 2015 Sorry, I am a Deluge noob. Quick question. I just set up the docker with my pia username and password, and I believe everything is working fine. I am able to access the Deluge webui, but when I add a torrent, it doesn't start downloading. It just sits there at 0.0%. I'm downloading the torrent from iptorrents to my computer and uploading via the Deluge webui. Bonus question: Should I use the same directory that I set for /data in the docker setup as my downloads folder? hi, that sounds like the tunnel isnt up correctly, can you please post the output of your supervisord.log file, please make sure you strip out any sensitive info. bonus answer is you should ALWAYS be pointing deluge to save incomplete/completed in the /data volume, if you dont do this then all downloads will be saved inside the docker container, which means you will run out of space in your docker img file (which may explain why it cant download anything??) and also means you wont be able to access the files downloaded. Link to comment
death.hilarious Posted March 31, 2015 Share Posted March 31, 2015 Thanks for the awesome work binhex! 1. Just a quick suggestion to help complete noobs like me: 6. Click the Advanced View toggle on the top right and Ffill in required fields e.g. volume data, environment variables etc Seems the Environment Variables are hidden by default (at least in 6.0-beta14b) and it took me far far too long to figure where to put the PIA user information for the DelugeVPN docker app. edit: spoke too soon about port-forwarding. You're awesome. Link to comment
gswarriorfan Posted March 31, 2015 Share Posted March 31, 2015 Sorry, I am a Deluge noob. Quick question. I just set up the docker with my pia username and password, and I believe everything is working fine. I am able to access the Deluge webui, but when I add a torrent, it doesn't start downloading. It just sits there at 0.0%. I'm downloading the torrent from iptorrents to my computer and uploading via the Deluge webui. Bonus question: Should I use the same directory that I set for /data in the docker setup as my downloads folder? hi, that sounds like the tunnel isnt up correctly, can you please post the output of your supervisord.log file, please make sure you strip out any sensitive info. bonus answer is you should ALWAYS be pointing deluge to save incomplete/completed in the /data volume, if you dont do this then all downloads will be saved inside the docker container, which means you will run out of space in your docker img file (which may explain why it cant download anything??) and also means you wont be able to access the files downloaded. Thanks binhex! I think I'm getting a hang of using the docker system. Instead of using /data, I was trying /mnt/cache/delugevpn/data. Now I know better. Link to comment
binhex Posted April 1, 2015 Author Share Posted April 1, 2015 Thanks for the awesome work binhex! 1. Just a quick suggestion to help complete noobs like me: 6. Click the Advanced View toggle on the top right and Ffill in required fields e.g. volume data, environment variables etc Seems the Environment Variables are hidden by default (at least in 6.0-beta14b) and it took me far far too long to figure where to put the PIA user information for the DelugeVPN docker app. edit: spoke too soon about port-forwarding. You're awesome. thanks for this, appreciate you taking the time to post, im actually still running b12 at the mo, so i haven't seen the new docker ui yet so wasn't aware of requiring the toggle to see the env variables, will add it in to OP. Link to comment
gswarriorfan Posted April 1, 2015 Share Posted April 1, 2015 Thanks for the awesome work binhex! 1. Just a quick suggestion to help complete noobs like me: 6. Click the Advanced View toggle on the top right and Ffill in required fields e.g. volume data, environment variables etc Seems the Environment Variables are hidden by default (at least in 6.0-beta14b) and it took me far far too long to figure where to put the PIA user information for the DelugeVPN docker app. edit: spoke too soon about port-forwarding. You're awesome. thanks for this, appreciate you taking the time to post, im actually still running b12 at the mo, so i haven't seen the new docker ui yet so wasn't aware of requiring the toggle to see the env variables, will add it in to OP. It took me far too long to figure this out on my own. I was going a little crazy looking for config files to edit. Link to comment
gswarriorfan Posted April 1, 2015 Share Posted April 1, 2015 OK, can someone please do a mini-guide how they successfully got sonarr to automatically download with deluge using a private tracker RSS? I am having a hard time getting things working. Link to comment
death.hilarious Posted April 1, 2015 Share Posted April 1, 2015 with regards to your comment about the "new port to forward", this shouldn't be happening every 24 hours [...] not sure why/how you are seeing the need to reconfigure the port every 24 hours?. PIA recommends making the port forwarding call every hour: "Please make the call to this API at least once every hour" (first post). From my experience port-forwarding stops around every 24 hours or so, even if you stay connected and IP doesn't change (which is a pain because I was doing the call manually on my QNAP). It may depend on port activity and it may even be different for different servers (most of my experience is with the Toronto gateway). I think calling every 24 hours is a good idea. Link to comment
djstabby Posted April 2, 2015 Share Posted April 2, 2015 with regards to your comment about the "new port to forward", this shouldn't be happening every 24 hours [...] not sure why/how you are seeing the need to reconfigure the port every 24 hours?. PIA recommends making the port forwarding call every hour: "Please make the call to this API at least once every hour" (first post). From my experience port-forwarding stops around every 24 hours or so, even if you stay connected and IP doesn't change (which is a pain because I was doing the call manually on my QNAP). It may depend on port activity and it may even be different for different servers (most of my experience is with the Toronto gateway). I think calling every 24 hours is a good idea. Beat me to it death.hilarious. Also, you can use any port check tool to see that the port does close on you usually after about 24 hours but sometimes sooner. I just restart the docker nightly and that does the trick. Link to comment
gswarriorfan Posted April 2, 2015 Share Posted April 2, 2015 OK, I just restarted my server today, and it seems like my delugevpn settings have reset. My sonarr docker settings remained intact. It's like my delugevpn docker is a fresh setup. I also had some torrents seeding and now they're gone. Weird. Link to comment
binhex Posted April 2, 2015 Author Share Posted April 2, 2015 thanks djstabby and death.hilarious, was not aware that PIA requires you to keep querying the api AT LEAST every hour to check the port, bit crap to be honest, esp in comparison to airvpn where you can choose the port you want and its yours for the duration of your account, but hey i can work with that. ive now created an additional script to check the currently assigned port against the port pia has assigned you, if different it will re-configure deluge, it runs every 50 mins, as its less than an hour which is their minimum, if they want hammer time on their api then they are gonna get it :-), let me know how it works for you guys. im going to be AFK for the next few days so dont worry if i dont respond, will be back next tuesday. Link to comment
binhex Posted April 2, 2015 Author Share Posted April 2, 2015 OK, I just restarted my server today, and it seems like my delugevpn settings have reset. My sonarr docker settings remained intact. It's like my delugevpn docker is a fresh setup. I also had some torrents seeding and now they're gone. Weird. this sounds to me like the folder you specified for /config on the host for delugevpn (i.e. unraid) got either deleted or moved, can you confirm the share you are saving your config files to is marked as "use cache disk = only", if its not marked as such then the mover script will move the files/folders to the array, and thus next time you start the docker it will create a brand new config folder. Link to comment
gswarriorfan Posted April 2, 2015 Share Posted April 2, 2015 OK, I just restarted my server today, and it seems like my delugevpn settings have reset. My sonarr docker settings remained intact. It's like my delugevpn docker is a fresh setup. I also had some torrents seeding and now they're gone. Weird. this sounds to me like the folder you specified for /config on the host for delugevpn (i.e. unraid) got either deleted or moved, can you confirm the share you are saving your config files to is marked as "use cache disk = only", if its not marked as such then the mover script will move the files/folders to the array, and thus next time you start the docker it will create a brand new config folder. This was it. I didn't have it on "use cache disk = only". Doh!! Link to comment
Dephcon Posted April 6, 2015 Share Posted April 6, 2015 Hey binhex, does your sab package include multicore par2, and if not is there a way for me to add it? thanks *edit* just wanted to add some props for your repo. I've just upgraded to 6.x last night and converting from my usenet VM to your docker containers was pretty damn easy Link to comment
binhex Posted April 7, 2015 Author Share Posted April 7, 2015 Hey binhex, does your sab package include multicore par2, and if not is there a way for me to add it? thanks *edit* just wanted to add some props for your repo. I've just upgraded to 6.x last night and converting from my usenet VM to your docker containers was pretty damn easy hi Dephcon, no it wasnt the multi threaded version of par2, reason being i had a package conflict that was causing me a headache a while back and just gave up in the end, just revisited it with renewed vigour and worked around the issue, so if you now do an update you should then have the multi threaded par2 included good to hear you had such a smooth transition over to dockers Link to comment
Recommended Posts