Hmm I got wake on Lan working at some point but no longer use it. I remember it being a big pain but I'll try to dig up the configuration details.

 

That would be greatly appreciated, and thank you for your work on this docker.

 

This is a snippet from my Office.items file that works for WOL:

Switch	Desktop	"Desktop"	(Office)		{ wol="192.168.1.100#FF:FF:FF:FF:FF:FF"}

 

You'll have to change the ip address and the mac address to match the computer you're trying to wake up.

 

 

Thank you! I mistakenly was starting to think that the first three parts of my openhab instance's IP address had to match that of the computer I was trying to wake, but it turns out that this was incorrect.

 

Thanks again!

No problem! I'm glad it's working for you!

Bungy Bhai-

 

I am desperate need of getting Owncloud on My SQL up and working.. I have a version up and running on a standalone linux box, but not I cannot get your version up and running.. I cannot even get to the web UI ?

 

I can get Gjfhardim's version on SQL lite up and running but that won't scale for my needs.

 

 

I am not working on the local machine, so everytime I try to go to the IP/Port I get nothing ? even though it looks like its up and running ?

 

I have checked your docker page but I can't even see where I am getting lost ?

 

 

-Ashok-

Ashok, can you post your configuration? I'm also using mysql with my owncloud docker, so I should be able to help you out.

Bungy Bhai-

 

I am desperate need of getting Owncloud on My SQL up and working.. I have a version up and running on a standalone linux box, but not I cannot get your version up and running.. I cannot even get to the web UI ?

 

I can get Gjfhardim's version on SQL lite up and running but that won't scale for my needs.

 

 

I am not working on the local machine, so everytime I try to go to the IP/Port I get nothing ? even though it looks like its up and running ?

 

I have checked your docker page but I can't even see where I am getting lost ?

 

 

-Ashok-

Ashok, can you post your configuration? I'm also using mysql with my owncloud docker, so I should be able to help you out.

I'm having this exact same error. I installed this docker from the community applications plugin. I used the default config except for changing the host paths per below because I have a user share appdata for docker containers. When I too go to the WebUI at http://10.0.0.250:8000 it says the page is not available. The docker installed without errors and is running though. What am I doing wrong?

 

/usr/share/webapps/owncloud/data [b]<=>[/b] /mnt/user/appdata/owncloud/data/
/usr/share/webapps/owncloud/config [b]<=>[/b] /mnt/user/appdata/owncloud/config
/https [b]<=>[/b] /mnt/user/appdata/owncloud/certs

Bungy,

 

I am not able to attach pics the forum has been acting weird all day.. first no reply button when they made this a sub forum.. now can't attach pics

 

 

Volume--> Host Path

 

/usr/share/webapps/owncloud/data-->/mnt/user/Owncloud/

 

/usr/share/webapps/owncloud/config-->/mnt/user/Owncloud/config/

 

/https-->/mnt/user/Owncloud/

 

Port mappings set to your default

 

 

I am not able to attach pics the forum has been acting weird all day.. first no reply button when they made this a sub forum.. now can't attach pics

 

Upload them to imgur and link them with the BBcode, much easier to view as well.

Bungy,

 

Once I start MySQL and look in the logs this is what I see:

 

It looks like the IP address isn't binding to the db ? which is why I can't get to the Web UI ?

 

Per your instructions online I try to go to the command line on the unraid box and input the following

 

$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag

 

I can't get it to execute the command ?

 

____________________________________________

 

MySQL init process done. Ready for start up.

 

2015-08-23 12:40:48 0 [Note] mysqld (mysqld 5.6.26) starting as process 1 ...

2015-08-23 12:40:48 1 [Note] Plugin 'FEDERATED' is disabled.

2015-08-23 12:40:48 1 [Note] InnoDB: Using atomics to ref count buffer pool pages

2015-08-23 12:40:48 1 [Note] InnoDB: The InnoDB memory heap is disabled

2015-08-23 12:40:48 1 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2015-08-23 12:40:48 1 [Note] InnoDB: Memory barrier is not used

2015-08-23 12:40:48 1 [Note] InnoDB: Compressed tables use zlib 1.2.7

2015-08-23 12:40:48 1 [Note] InnoDB: Using Linux native AIO

2015-08-23 12:40:48 1 [Note] InnoDB: Using CPU crc32 instructions

2015-08-23 12:40:48 1 [Note] InnoDB: Initializing buffer pool, size = 128.0M

2015-08-23 12:40:48 1 [Note] InnoDB: Completed initialization of buffer pool

2015-08-23 12:40:48 1 [Note] InnoDB: Highest supported file format is Barracuda.

2015-08-23 12:40:48 1 [Note] InnoDB: 128 rollback segment(s) are active.

2015-08-23 12:40:48 1 [Note] InnoDB: Waiting for purge to start

2015-08-23 12:40:48 1 [Note] InnoDB: 5.6.26 started; log sequence number 1625997

2015-08-23 12:40:48 1 [Note] Server hostname (bind-address): '*'; port: 3306

2015-08-23 12:40:48 1 [Note] IPv6 is not available.

2015-08-23 12:40:48 1 [Note] - '0.0.0.0' resolves to '0.0.0.0';

2015-08-23 12:40:48 1 [Note] Server socket created on IP: '0.0.0.0'.

2015-08-23 12:40:48 1 [Warning] 'proxies_priv' entry '@ root@16d1d0b18b8f' ignored in --skip-name-resolve mode.

2015-08-23 12:40:48 1 [Note] Event Scheduler: Loaded 0 events

2015-08-23 12:40:48 1 [Note] mysqld: ready for connections.

Version: '5.6.26' socket: '/var/run/mysqld/mysqld.sock' port: 3306 MySQL Community Server (GPL)

@d4lions, @X1pheR

 

For owncloud -

Try removing the /https volume mapping. This mapping is required if you want to provide your own ssl certificates. If the directory does not contain server.crt and server.key files, the docker will not run. Alternatively, you can generate your own https ssl certificates - which is highly recommended. Using the built in certificates is a security risk.

 

Here is a good link for how to generate generate the certificates. http://www.akadia.com/services/ssh_test_certificate.html

Bungy,

 

Once I start MySQL and look in the logs this is what I see:

 

It looks like the IP address isn't binding to the db ? which is why I can't get to the Web UI ?

 

Per your instructions online I try to go to the command line on the unraid box and input the following

 

$ docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql:tag

 

I can't get it to execute the command ?

 

 

From the log, it looks like your mysql container is starting correctly. If you want to get it to work with owncloud, start the container with enviornmental variables for:

-e MYSQL_DATABASE=owncloud
-e MYSQL_USER=owncloud
-e MYSQL_PASSWORD=[i]password_for_owncloud_database[/i]

 

Then, when you first initialize your owncloud container, it'll ask you what type of database you want to use. It defaults to sqlite, but you can change it to mysql. Provide it with the datbase user, name, and password that you set in your mysql docker using the environmental variables.

Bungy,

 

I can't get this to execute from the command prompt after I login to the console as root ?

 

where/How do I set these variables?

 

-A-

Bungy,

 

I can't get this to execute from the command prompt after I login to the console as root ?

 

where/How do I set these variables?

 

-A-

Edit docker. Turn on Advanced slider in upper right. Enter Environment Variable Name and Value

@d4lions, @X1pheR

 

For owncloud -

Try removing the /https volume mapping. This mapping is required if you want to provide your own ssl certificates. If the directory does not contain server.crt and server.key files, the docker will not run. Alternatively, you can generate your own https ssl certificates - which is highly recommended. Using the built in certificates is a security risk.

 

Here is a good link for how to generate generate the certificates. http://www.akadia.com/services/ssh_test_certificate.html

 

Thank you for replying. I deleted everything to start fresh. Couldn't remove /https binding at first configuration since the remove button was greyed out. After first config I removed the binding and also set the TARGET_DIR variable to / so that owncloud would show right away. Why would you want it to start as /owncloud? Then it worked! So it was the https binding. I ran into another problem though. After first time setup I choose to use the included mariadb. But now owncloud only displays an error that /usr/share/webapps/owncloud/data is readable for other users and I should set 0770 permissions?

 

This is all new for me since I'm a windows user so once I get it up and running I'll also look at creating my own test certificate.

@d4lions, @X1pheR

 

For owncloud -

Try removing the /https volume mapping. This mapping is required if you want to provide your own ssl certificates. If the directory does not contain server.crt and server.key files, the docker will not run. Alternatively, you can generate your own https ssl certificates - which is highly recommended. Using the built in certificates is a security risk.

 

Here is a good link for how to generate generate the certificates. http://www.akadia.com/services/ssh_test_certificate.html

 

Thank you for replying. I deleted everything to start fresh. Couldn't remove /https binding at first configuration since the remove button was greyed out. After first config I removed the binding and also set the TARGET_DIR variable to / so that owncloud would show right away. Why would you want it to start as /owncloud? Then it worked! So it was the https binding. I ran into another problem though. After first time setup I choose to use the included mariadb. But now owncloud only displays an error that /usr/share/webapps/owncloud/data is readable for other users and I should set 0770 permissions?

 

This is all new for me since I'm a windows user so once I get it up and running I'll also look at creating my own test certificate.

 

There is one thing to keep in mind when running the docker without the /https volume mount. This will use the built in ssl certificates, which is a potential security risk. If somebody gets the certificates, they would be able to sniff the data transfer over the network. This is probably a small risk, but still a risk. The easy way around it is to create the server.crt and server key files yourself using the guide I posed earlier.

 

To fix your current problem, run these commands on your unraid server assuming your owncloud volume mounts are stored in /mnt/cache/appdata/owncloud:

 

chmod -Rv 0770 /mnt/cache/appdata/owncloud/data
chown -Rv sshd:sshd /mnt/cache/appdata/owncloud/data

 

In my opinion, the docker should set these permissions on bootup, but I'm not the creator of the docker. If I get time, I may submit a merge request that sets these permissions.

Bungy, thanks a lot for the great openHAB docker. I'm running openHAB on a RPI right now but want to switch to your docker moving forward.

 

Here is the log that I'm getting from the webgui:

Addons are up-to-date
configuration found.
Linking openhab configuration
Installing HABmin
Copying HABmin addon files to persistant storage and to the addons directory
'/etc/openhab/habmin/addons/org.openhab.binding.zwave-1.5.0-SNAPSHOT.jar' -> '/opt/openhab/addons/org.openhab.binding.zwave-1.5.0-SNAPSHOT.jar'
'/etc/openhab/habmin/addons/org.openhab.io.habmin-1.5.0-SNAPSHOT.jar' -> '/opt/openhab/addons/org.openhab.io.habmin-1.5.0-SNAPSHOT.jar'
Linking the HABmin to the webapps directory
No webapps require linking
2015-09-01 11:24:36,015 CRIT Supervisor running as root (no user in config file)
2015-09-01 11:24:36,015 WARN Included extra file "/etc/supervisor/conf.d/openhab.conf" during parsing
2015-09-01 11:24:36,015 WARN Included extra file "/etc/supervisor/conf.d/openhab_debug.conf" during parsing
2015-09-01 11:24:36,120 INFO RPC interface 'supervisor' initialized
2015-09-01 11:24:36,120 CRIT Server 'inet_http_server' running without any HTTP authentication checking
2015-09-01 11:24:36,120 INFO RPC interface 'supervisor' initialized
2015-09-01 11:24:36,120 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2015-09-01 11:24:36,120 INFO supervisord started with pid 1
2015-09-01 11:24:37,123 INFO spawned: 'openhab' with pid 20
2015-09-01 11:24:38,125 INFO success: openhab entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

I followed your guidance here:

If you would like to begin starting your own configuration, set up the volume mounts as you have and extract the demo configuration into your configuration directory. The demo configuration provides a good basis for getting started.

 

For me, the configuration directory is located at /mnt/user/appdata/openhab/config. Inside this directory there should be an items, persistence, rules, scripts, and sitemaps directories. There should also be the openhab.cfg and addons.cfg file.

 

So this is what I'm having in my addons folder (all other add ons have been moved into an "unused" folder):

root@Tower:/mnt/cache/.Docker/appdata/openhab/config/addons# ls -ali
total 37112
6617042 drwxrwxr-x 1 nobody users     1454 Sep  1 12:01 ./
6617035 drwxrwxr-x 1 nobody users      248 Aug 31 09:32 ../
6617043 -rwxrwxr-x 1 nobody users      874 Aug 31 09:32 README.TXT*
6636532 drwxrwxrwx 1 root   root     11422 Sep  1 12:01 not\ used/
6617062 -rwxrwxr-x 1 nobody users    80977 Aug 31 09:32 org.openhab.binding.astro-1.7.1.jar*
6617091 -rwxrwxr-x 1 nobody users    63873 Aug 31 09:32 org.openhab.binding.exec-1.7.1.jar*
6617105 -rwxrwxr-x 1 nobody users    19558 Aug 31 09:32 org.openhab.binding.http-1.7.1.jar*
6617115 -rwxrwxr-x 1 nobody users   430031 Aug 31 09:32 org.openhab.binding.knx-1.7.1.jar*
6617137 -rwxrwxr-x 1 nobody users    10156 Aug 31 09:32 org.openhab.binding.ntp-1.7.1.jar*
6617175 -rwxrwxr-x 1 nobody users   325425 Aug 31 09:32 org.openhab.binding.weather-1.7.1.jar*
6617184 -rwxrwxr-x 1 nobody users    38729 Aug 31 09:32 org.openhab.core.jsr223-1.7.1.jar*
6617185 -rwxrwxr-x 1 nobody users   645724 Aug 31 09:32 org.openhab.io.cv-1.7.1.jar*
6617188 -rwxrwxr-x 1 nobody users   143118 Aug 31 09:32 org.openhab.io.gpio-1.7.1.jar*
6618028 -rwxrwxr-x 1 nobody users  1123714 Sep  1 11:24 org.openhab.io.habmin-1.5.0-SNAPSHOT.jar*
6617190 -rwxrwxr-x 1 nobody users  9175347 Aug 31 09:32 org.openhab.io.multimedia.tts.freetts-1.7.1.jar*
6617193 -rwxrwxr-x 1 nobody users 22250374 Aug 31 09:32 org.openhab.io.multimedia.tts.marytts-1.7.1.jar*
6617194 -rwxrwxr-x 1 nobody users    36586 Aug 31 09:32 org.openhab.io.multimedia.tts.speechdispatcher-1.7.1.jar*
6617195 -rwxrwxr-x 1 nobody users   322270 Aug 31 09:32 org.openhab.io.myopenhab-1.7.0.jar*
6617196 -rwxrwxr-x 1 nobody users   322391 Aug 31 09:32 org.openhab.io.myopenhab-1.7.1.jar*
6617201 -rwxrwxr-x 1 nobody users  2340480 Aug 31 09:32 org.openhab.persistence.db4o-1.7.1.jar*
6617202 -rwxrwxr-x 1 nobody users     6163 Aug 31 09:32 org.openhab.persistence.exec-1.7.1.jar*
6617206 -rwxrwxr-x 1 nobody users     7386 Aug 31 09:32 org.openhab.persistence.logging-1.7.1.jar*
6617211 -rwxrwxr-x 1 nobody users   624538 Aug 31 09:32 org.openhab.persistence.rrd4j-1.7.1.jar*

 

1.) I can see all the elements that I have defined but I can't switch on/off anything. I'm afraid that the issues is here:

2015-09-01 12:25:45.730 [ERROR] [b.k.i.connection.KNXConnection] - Error connecting to KNX bus: on connect to /192.168.178.100:3671: Cannot assign requested address

 

2.) How do I invoke Habmin?

 

Thanks a lot.

So, I'm not familiar with the KNX gateway or the KNX binding, but my guess is that the docker is unable to connect to that ip address. Try running this command to see if your docker can ping the knx gateway.

 

docker exec -it openhab ping 192.168.178.100

 

I'm guessing it got the ip address 192.168.178.100 from your openhab.cfg file. If openhab cannot ping that ip address, I would start looking into connectivity issues. Make sure your unraid can access that ip, check your firewall, check that the ip is correct, etc.

 

As for #2, habmin is now installed by default. Simply point your browser to: http://tower:8080/habmin. Of course adjust the hostname and port to match your configuration.

 

Let me know how it goes. I hope this helps you out.

Thanks Bungy, here you are:

root@Tower:~# docker exec -it openhab ping 192.168.178.100
PING 192.168.178.100 (192.168.178.100) 56(84) bytes of data.
64 bytes from 192.168.178.100: icmp_seq=1 ttl=15 time=2.39 ms
64 bytes from 192.168.178.100: icmp_seq=2 ttl=15 time=1.52 ms
64 bytes from 192.168.178.100: icmp_seq=3 ttl=15 time=1.47 ms

 

Thanks for the Habmin link...you might add that to the initial post? Just a thought and I might just have overlooked it

Hmm. Well it looks like you can connect to that machine. Have you double checked your knx binding configuration? Also, is there any way to get connection logs from the KNX side to see if it's a failed authorization or something like that?

 

I have the link in the Readme markdown for the docker, but I definitely should put it along with the openhab template for unraid. I've been meaning to update my documentation, but time is short these days.

Have you double checked your knx binding configuration? Also, is there any way to get connection logs from the KNX side to see if it's a failed authorization or something like that?

 

Well, is is only about the little changes that I made (openhab.cfg file) and then to add the KNX binding file into the addon folder:

knx:ip=192.168.178.100
knx:type=TUNNEL
knx:localIp=192.168.178.28
knx:autoReconnectPeriod=30

 

I can't think of anything else...I also tried the Network Type Bridge and Host which made no difference.

Hmm and it works in your pi with the same version of openhab and the same binding version?

Exactly right - only difference is this line:

knx:localIp=192.168.178.100

(this is the RPI IP, the unRIAD IP is 192.168.178.28)

Ahhh i see. Try setting that IP to 127.0.0.1. I believe that it should be connecting to the openhab docker and not to the host (unraid).

....try to specify the actual IP address of the local host....

2015-09-01 17:54:01.331 [iNFO ] [b.k.i.connection.KNXConnection] - Trying to (re-)connect to KNX...
2015-09-01 17:54:01.332 [ERROR] [b.k.i.connection.KNXConnection] - Error connecting to KNX bus: on connect to /192.168.178.100:3671: Invalid argument
2015-09-01 17:54:01.333 [iNFO ] [b.k.i.connection.KNXConnection] - KNX link will be retried in 30 seconds
2015-09-01 17:54:01.334 [ERROR] [tuwien.auto.calimero          ] - [Timer-3] KNXnet/IP Tunneling 192.168.178.100:3671: communication failure on connect
java.io.IOException: Invalid argument
at java.net.PlainDatagramSocketImpl.send(Native Method) ~[na:1.8.0_45]
at java.net.DatagramSocket.send(DatagramSocket.java:693) ~[na:1.8.0_45]
at tuwien.auto.calimero.knxnetip.ClientConnection.connect(ClientConnection.java:143) ~[na:na]
at tuwien.auto.calimero.knxnetip.KNXnetIPTunnel.<init>(KNXnetIPTunnel.java:117) ~[na:na]
at tuwien.auto.calimero.link.KNXNetworkLinkIP.<init>(KNXNetworkLinkIP.java:180) ~[na:na]
at org.openhab.binding.knx.internal.connection.KNXConnection.connectByIp(KNXConnection.java:263) ~[na:na]
at org.openhab.binding.knx.internal.connection.KNXConnection.connect(KNXConnection.java:159) ~[na:na]
at org.openhab.binding.knx.internal.connection.KNXConnection$ConnectTimerTask.run(KNXConnection.java:483) ~[na:na]
at java.util.TimerThread.mainLoop(Timer.java:555) ~[na:1.8.0_45]
at java.util.TimerThread.run(Timer.java:505) ~[na:1.8.0_45]
2015-09-01 17:54:01.334 [WARN ] [tuwien.auto.calimero          ] - [Timer-3] KNXnet/IP Tunneling 192.168.178.100:3671: try to specify the actual IP address of the local host

It looks like it's still trying to connect using the RPi's ip

 

2015-09-01 17:54:01.332 [ERROR] [b.k.i.connection.KNXConnection] - Error connecting to KNX bus: on connect to /192.168.178.100:3671: Invalid argument

..this is what I have in my cfg file:

knx:ip=192.168.178.100
knx:localIp=127.0.0.1

 

Let me give you all IP addresses:

KNX gateway: 192.168.178.100

RPI: 192.168.178.101

unRAID: 192.168.178.28

Interesting new message on my console:

Message from syslogd@Tower at Sep  1 18:03:26 ...
kernel:unregister_netdevice: waiting for lo to become free. Usage count = 1

Try running docker exec -it openhab ifconfig

 

Grab the eth0 ip address and set the ip address to that number. This is a dirty hack since this ip will change when the container restarts, but it should at least tell you if that part of the config is the problem.

 

That message you're getting occurs pretty frequently for me too (and many others). I, or others, have yet to see any adverse effects so I've been ignoring it for the time being.