ridge

Perfect! I couldn't get it to work using a subdirectory. Switched to using a subdomain as in your example and we're golden. Thanks!

Hey @realiesI just got this docker working, and I was wondering if you had a functioning reverse proxy going for it? I can't seem to get nginx to work on this novnc container. Thanks!

You guys were so fast with the ninja-update I didn’t even have chance to! Posted the above, went to bed, and woke up a few hours ago to an automatically updated and working Airsonic. Thank you!

New problem after this week's update: I can't access Airsonic at all. Without my reverse proxy (by accessing the docker via the internal IP and assigned port) I get this displayed in the browser: Error 404 - Not Found. No context on this server matched or handled this request. Contexts known to this server are: /music ---> o.e.j.w.WebAppContext@769c9116{/music,file:///tmp/jetty-0.0.0.0-4040-airsonic.war-_music-any-8871381388144330769.dir/webapp/,AVAILABLE}{file:///app/airsonic/airsonic.war} Powered by Jetty:// 9.3.14.v20161028 And with the reverse proxy in use (proxied to mydomain.com/music) I just get this displayed in the browser: Directory: /music/ I've tried forcing an update, but nothing has changed. Log: ------------------------------------- GID/UID ------------------------------------- User uid: 99 User gid: 100 ------------------------------------- [cont-init.d] 10-adduser: exited 0. [cont-init.d] 20-config: executing... [cont-init.d] 20-config: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. 2018-05-05 01:24:41.542:INFO::main: Logging initialized @317ms 2018-05-05 01:24:41.553:INFO:oejr.Runner:main: Runner 2018-05-05 01:24:41.854:INFO:oejs.Server:main: jetty-9.3.14.v20161028 2018-05-05 01:24:42.150:INFO:oeja.AnnotationConfiguration:main: Scanning elapsed time=1ms 2018-05-05 01:24:42.274:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@769c9116{/music,file:///tmp/jetty-0.0.0.0-4040-airsonic.war-_music-any-7774717693097823199.dir/webapp/,AVAILABLE}{file:///app/airsonic/airsonic.war} 2018-05-05 01:24:42.305:INFO:oejs.AbstractConnector:main: Started ServerConnector@71423665{HTTP/1.1,[http/1.1]}{0.0.0.0:4040} 2018-05-05 01:24:42.307:INFO:oejs.Server:main: Started @1089ms

Ah okay. Well, changing that up to -Xms256m -Xmx512m worked. Thanks!

Okay, after removing the new JAVA_OPTS optional field the container was able to start, and I'm back up and running. I have to assume it's somewhat important to keep it in, but for now it doesn't seem to do any harm to delete it.

Hey guys, Airsonic isn't working (for me) since the recent update. Got this error (repeating into infinity) today: Too small initial heap Error occurred during initialization of VM Restarted the container, no joy. Forced an update, no joy. What else can I provide you to help diagnose?

Perfect! Thanks! All set up and running now.

First of all, thank you for this docker. The instructions to move over from gfjardim's docker were clear and my migration went without a hitch. Secondly, I may have missed something in the settings but if not, I have a feature request...in gfjardim's Crashplan docker there's a field for Unassigned Devices - essentially to map a drive using that plugin to the container. Would it be possible to have a similar field added to your docker? My unassigned device is the only folder sitting in the cloud that has a red "Missing" next to it. I'm aware I could back up locally to the array and then back that new folder up to Crashplan, but if I can keep it simple I'd like to. Thanks!

Problems after the update for me too. 2017-04-27 10:56:59,954 WARN received SIGTERM indicating exit request 2017-04-27 10:56:59,954 INFO waiting for start-script, sabnzbd-script to die 2017-04-27 10:57:00,956 DEBG killing sabnzbd-script (pid 114) with signal SIGTERM 2017-04-27 10:57:00,957 DEBG fd 16 closed, stopped monitoring <POutputDispatcher at 47681140893960 for <Subprocess at 47681140892808 with name sabnzbd-script in state STOPPING> (stderr)> 2017-04-27 10:57:00,957 DEBG fd 11 closed, stopped monitoring <POutputDispatcher at 47681140894104 for <Subprocess at 47681140892808 with name sabnzbd-script in state STOPPING> (stdout)> 2017-04-27 10:57:00,957 INFO stopped: sabnzbd-script (terminated by SIGTERM) 2017-04-27 10:57:00,957 DEBG received SIGCLD indicating a child quit 2017-04-27 10:57:00,958 DEBG killing start-script (pid 113) with signal SIGTERM 2017-04-27 10:57:00,958 DEBG fd 8 closed, stopped monitoring <POutputDispatcher at 47681140893240 for <Subprocess at 47681140893096 with name start-script in state STOPPING> (stdout)> 2017-04-27 10:57:00,958 DEBG fd 10 closed, stopped monitoring <POutputDispatcher at 47681140893384 for <Subprocess at 47681140893096 with name start-script in state STOPPING> (stderr)> 2017-04-27 10:57:00,958 INFO stopped: start-script (terminated by SIGTERM) 2017-04-27 10:57:00,959 DEBG received SIGCLD indicating a child quit 2017-04-27 10:57:39.335455 [info] Starting Supervisor... 2017-04-27 10:57:39,683 CRIT Set uid to user 0 2017-04-27 10:57:39,683 INFO Included extra file "/etc/supervisor/conf.d/sabnzbdvpn.conf" during parsing 2017-04-27 10:57:39,686 INFO supervisord started with pid 7 2017-04-27 10:57:40,689 INFO spawned: 'start-script' with pid 113 2017-04-27 10:57:40,691 INFO spawned: 'sabnzbd-script' with pid 114 2017-04-27 10:57:40,692 INFO spawned: 'privoxy-script' with pid 115 2017-04-27 10:57:40,700 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2017-04-27 10:57:40,700 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-04-27 10:57:40,700 INFO success: sabnzbd-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-04-27 10:57:40,700 INFO success: privoxy-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2017-04-27 10:57:40,700 DEBG 'sabnzbd-script' stdout output: [info] VPN is enabled, checking VPN tunnel local ip is valid 2017-04-27 10:57:40,702 DEBG 'privoxy-script' stdout output: [info] Privoxy set to disabled 2017-04-27 10:57:40,703 DEBG fd 17 closed, stopped monitoring <POutputDispatcher at 47128651112960 for <Subprocess at 47128651116344 with name privoxy-script in state RUNNING> (stdout)> 2017-04-27 10:57:40,703 DEBG fd 21 closed, stopped monitoring <POutputDispatcher at 47128651114328 for <Subprocess at 47128651116344 with name privoxy-script in state RUNNING> (stderr)> 2017-04-27 10:57:40,703 INFO exited: privoxy-script (exit status 0; expected) 2017-04-27 10:57:40,703 DEBG received SIGCLD indicating a child quit 2017-04-27 10:57:40,706 DEBG 'start-script' stdout output: [info] VPN default certs defined, copying to /config/openvpn/... 2017-04-27 10:57:40,710 DEBG 'start-script' stdout output: [info] VPN config file (ovpn extension) is located at /config/openvpn/openvpn.ovpn 2017-04-27 10:57:40,711 DEBG 'start-script' stderr output: dos2unix: converting file /config/openvpn/openvpn.ovpn to Unix format... 2017-04-27 10:57:40,758 DEBG 'start-script' stdout output: [info] Default route for container is 172.17.0.1 2017-04-27 10:57:40,762 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2017-04-27 10:57:40,765 DEBG 'start-script' stdout output: [info] Adding 37.235.1.174 to /etc/resolv.conf 2017-04-27 10:57:40,769 DEBG 'start-script' stdout output: [info] Adding 8.8.4.4 to /etc/resolv.conf 2017-04-27 10:57:40,772 DEBG 'start-script' stdout output: [info] Adding 37.235.1.177 to /etc/resolv.conf 2017-04-27 10:57:40,779 DEBG 'start-script' stdout output: [info] Adding 192.168.1.0/24 as route via docker eth0 2017-04-27 10:57:40,780 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2017-04-27 10:57:40,780 DEBG 'start-script' stdout output: default via 172.17.0.1 dev eth0 172.17.0.0/16 dev eth0 proto kernel scope link src 172.17.0.2 192.168.1.0/24 via 172.17.0.1 dev eth0 2017-04-27 10:57:40,781 DEBG 'start-script' stdout output: -------------------- 2017-04-27 10:57:40,787 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2017-04-27 10:57:40,815 DEBG 'start-script' stdout output: [info] Docker network defined as 172.17.0.0/16 2017-04-27 10:57:40,882 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2017-04-27 10:57:40,884 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD ACCEPT -P OUTPUT DROP -A INPUT -i tun0 -j ACCEPT -A INPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 8090 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 8090 -j ACCEPT -A INPUT -p udp -m udp --sport 53 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT -A OUTPUT -s 172.17.0.0/16 -d 172.17.0.0/16 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8080 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 8090 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 8090 -j ACCEPT -A OUTPUT -p udp -m udp --dport 53 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT 2017-04-27 10:57:40,884 DEBG 'start-script' stdout output: -------------------- 2017-04-27 10:57:40,885 DEBG 'start-script' stdout output: [info] Starting OpenVPN... 2017-04-27 10:57:40,891 DEBG 'start-script' stdout output: [info] OpenVPN started 2017-04-27 10:57:42,231 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 10:57:42,231 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 10:57:43,027 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started 2017-04-27 10:58:13,172 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 10:58:13,878 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started 2017-04-27 10:58:44,030 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 10:58:44,030 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 10:58:44,763 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started 2017-04-27 10:59:14,913 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 10:59:15,700 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started 2017-04-27 10:59:45,848 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 10:59:46,663 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started 2017-04-27 11:00:16,791 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 11:00:17,444 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started 2017-04-27 11:00:47,569 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 11:00:47,569 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd not running [info] Attempting to start SABnzbd... 2017-04-27 11:00:48,211 DEBG 'sabnzbd-script' stdout output: [info] SABnzbd started Seems to be in a loop of some kind. I can't get to the web interface for SAB obviously.

Working here too. It's almost like it lost the http_root setting. Never even thought to check that in Plexpy's settings.

Seconded. Same problem.

there was a permissions issue, can you stop affected running containers and delete perms.txt from /config folders then upgrade any containers via unraid webui and start again, let me know how you get on. That worked. Thanks!

Problem after updating the container just now. Container not starting. Relevant portion of the logfile (I think): Mon Feb 22 10:40:30 2016 Initialization Sequence Completed 2016-02-22 10:40:30,088 DEBG 'sabnzbd' stdout output: [info] All checks complete, starting SABnzbd... 2016-02-22 10:40:30,189 DEBG 'privoxy' stdout output: [info] Privoxy set to disabled 2016-02-22 10:40:30,190 DEBG fd 8 closed, stopped monitoring (stderr)> 2016-02-22 10:40:30,190 DEBG fd 6 closed, stopped monitoring (stdout)> 2016-02-22 10:40:30,190 INFO exited: privoxy (exit status 0; expected) 2016-02-22 10:40:30,190 DEBG received SIGCLD indicating a child quit 2016-02-22 10:40:30,701 DEBG 'sabnzbd' stdout output: Error: Can't write to logfile 2016-02-22 10:40:30,733 DEBG fd 19 closed, stopped monitoring (stderr)> 2016-02-22 10:40:30,733 DEBG fd 15 closed, stopped monitoring (stdout)> 2016-02-22 10:40:30,733 INFO exited: sabnzbd (exit status 2; expected) 2016-02-22 10:40:30,734 DEBG received SIGCLD indicating a child quit

Just chiming in to confirm the error message: 2016-02-04 14:27:56,159 DEBG 'start' stderr output: /root/iptable.sh: line 27: lsmod: command not found 2016-02-04 14:27:56,163 DEBG 'start' stdout output: [warn] iptable_mangle module not supported, you will not be able to connect to SABnzbd webui or Privoxy outside of your LAN Latest unRAID, latest version of this container. Everything works - I'm even running it behind a reverse proxy without issue. Just confirming I'm seeing the same error message.

So ownCloud now works, therefore I'm at 100% working again. Thanks for your help!

A fan for 40 years and counting. OK, commands have been run, and so far the log looks like this: ----------------------------------- _ _ _ | |___| (_) ___ | / __| | |/ _ \ | \__ \ | | (_) | |_|___/ |_|\___/ |_| 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 Nov 14 21:45:19 aab3299b69a3 syslog-ng[59]: syslog-ng starting up; version='3.5.3' 151114 21:45:19 mysqld_safe Logging to '/config/databases/aab3299b69a3.err'. 151114 21:45:19 mysqld_safe Starting mysqld daemon with databases from /config/databases No repeating itself over and over. And most importantly I can now connect to the MySQL server from another computer using the root account. I'll now enable the ownCloud docker and see if it connects ok. Will post back when I find out. Thank you for your help! But FYI, I haven't run the newperms script at all since I originally installed MariaDB.

Well... root@Gallifrey:~# docker exec -it mariadb find /config/databases \! -user abc -print /config/databases /config/databases/mysql

I have no idea where that abc user came from. Nothing I've personally created, but I did notice reference in my.cnf to an abc user when I was trying to figure this out earlier. Didn't touch it, haven't changed anything.

My unRAID log is still saying this: 151114 21:21:36 mysqld_safe Starting mysqld daemon with databases from /config/databases 151114 21:21:36 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended 151114 21:21:37 mysqld_safe Logging to '/config/databases/aab3299b69a3.err'. 151114 21:21:37 mysqld_safe Starting mysqld daemon with databases from /config/databases 151114 21:21:37 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended etc

Step 1: Move .err files... root@Gallifrey:~# docker exec -it mariadb /bin/bash root@aab3299b69a3:/# cd /config/databases root@aab3299b69a3:/config/databases# ls -l total 176347 -rw-r----- 1 abc users 20089 Nov 12 21:29 4325730b7f89.err -rw-rw---- 1 abc users 16384 Nov 14 03:23 aria_log.00000001 -rw-rw---- 1 abc users 52 Nov 14 03:23 aria_log_control -rw-rw---- 1 abc users 50331648 Nov 14 03:23 ib_logfile0 -rw-rw---- 1 abc users 50331648 Nov 14 03:23 ib_logfile1 -rw-rw---- 1 abc users 79691776 Nov 14 03:23 ibdata1 -rw-rw---- 1 abc users 0 Oct 12 20:50 multi-master.info drwx------ 2 mysql users 2976 Oct 12 20:50 mysql drwx------ 2 abc users 1512 Nov 8 19:10 owncloud drwx------ 2 abc users 2744 Oct 12 20:50 performance_schema root@aab3299b69a3:/config/databases# mv 4325730b7f89.err 4325730b7f89.old root@aab3299b69a3:/config/databases# exit exit Step 2: Restart docker from unRAID admin Step 3: No new .err file created.

Definitely not.

Thought I had. Oh well. I installed MariaDB originally a couple of months ago. Created my database there and then. Nothing was imported/migrated. Only one database running (for ownCloud). It's been running fine until this problem. Nothing has been migrated, no other MariaDB docker has been used. It's all been the Linuxserver docker right from the get-go.

Learned something new, thanks. Unfortunately, I still have a non-functional MySQL installation. I've tried connecting from another computer with no luck. So I thought maybe the root password is wrong. Made sure the docker was running. Ran a docker exec -it mariadb /bin/bash. Tried to change the password. Got this: root@aab3299b69a3:/# mysqladmin -u root password <password> mysqladmin: connect to server at 'localhost' failed error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2 "No such file or directory")' Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists! That's not right...

I have no idea what that debian-sys-maint@localhost user is. Certainly nothing I've created. I've only created a database for ownCloud, and that has its own user (named "owncloud") associated to it. Also, the log on pastebin isn't reflecting what you asked. It's just the most recent log on there. I'm concerned that the docker says it's logging to a .err file that doesn't actually exist.