Bungy

I think I ran into this issue as well and fixed it by manually editing the config.php file. Can you check what the trusted_domains array is in your config.php file and also the permissions of this file?

I used to use openhab but switched to home assistant lately. It's much less buggy and easier to develop on. Im not sure about that specific device being supported but openhab definitely has extensive support for zwave in general.

Hmm. I just updated my gitlab docker after seeing your and I'm not seeing the same thing. It sounds like something is going wrong with your gitlab template or with your docker image. Can you check how much free space your docker image has? You can see this on the dashboard view in unraid.

Are you seeing this during the update or in the docker logs for the gitlab docker?

I believe I've seen that before and simply restarting the docker fixed it. It would help to show the contents of that file as well

Is there anything in your docker logs?

I'm pretty sure they won't unless they start from scratch. The updates pull from the running containers link to the registry and remaking the containers is typically done using the users local cache of the templates

Will do. I refrained since others are already using l3iggs but I'll update the template

I've actually switched away from l3iggs container to the official owncloud container. I found it has less bugs

chmod -R 0770 data

No problem! Happy to help

Give it a few seconds and try the second command again. Sounds like the container is still booting up. I ran in to the same issue.

Dockers are pretty finicky and getting used to them at first can be difficult. I've often start by configuring the minimum amount of settings I need to going and then building from there. Try those two commands I just sent you. They don't include the volume mappings. You may have to wait like 30 seconds after the first one while the docker boots up before you get the 2nd one to work properly. If they work, then you can add the volume mappings in and see if you can get everything up and running. The syntax for volume mappings is -v [host_directory]:[container_directory] Hang in there. Dockers are a HUGE pain at first, but will end up being your best friend once you learn more about how to use them.

So what that command is doing is creating a 2nd mysql docker and trying to connect othe the first one with it. My guess is the permissions table on your docker isn't allowing connections from anywhere but 127.0.0.1, but the ip address of your new temporary docker is 172.17.42.1. Try this instead: # This will get you into the shell of the mysql docker docker exec -it mysql bash mysql -u root -p # Then enter your password Give that a shot and let me know how it works for ya. Here's the result, I have gotten similar results with HeidiSQL, same error that is. root@HORTA-unRaid:~# docker exec -it mysql bash root@4c46fbbf6f82:/# mysql -u root -p Enter password: ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES) root@4c46fbbf6f82:/# I just tried it out on my machine and it works. First command to initiate the mysql container: docker run --name some-mysql -e MYSQL_ROOT_PASSWORD=my-secret-pw -d mysql 2nd command to connect to the mysql instance: docker run -it --link some-mysql:mysql --rm mysql sh -c 'exec mysql -hmysql -uroot -pmy-secret-pw'

So what that command is doing is creating a 2nd mysql docker and trying to connect othe the first one with it. My guess is the permissions table on your docker isn't allowing connections from anywhere but 127.0.0.1, but the ip address of your new temporary docker is 172.17.42.1. Try this instead: # This will get you into the shell of the mysql docker docker exec -it mysql bash mysql -u root -p # Then enter your password Give that a shot and let me know how it works for ya.

The proper way to include your own certificate files are to put them inside of a directory and map that directory to /https in the container. Other then that, are there any files popping up in your configuration directory? Also can you post which volumes you're mapping?

Where would one go for your own certs? How would one install said certs? Check out section 4 of the docker container author's instructions: https://github.com/l3iggs/docker-owncloud

Try to remove the https directory mapping. That mapping is only required if you're providing your own certs (which is highly highly recommended)

:) Assuming you KNOW that only 1 bit has changed in a standard 4.7GB DVD. That's 4,700,000,000 bytes, or 37,600,000,000 bits. To recursively check the impact of a single bit change, you'd have to compute the MD5 for EVERY different bit value. My experience is it takes ~ 30 seconds to calculate the MD5 of a file of that size. Let's assume you found a spectacular algorithm that could cut that time to ONE second. That would still take over 1,000 YEARS to find the missing bit [37,600,000,000 seconds (at 1 sec/check) /60 = 626,666,666.67 minutes /60 = 10,444,444.44 hours /24 = 435,185.19 days /365 = 1,192.29 years !! AND that assumes you KNOW that only one bit has changed. It'd be really depressing to wait 1192 years for the result and find out there weren't any matches 8) ... and that time is for a single-sided DVD of 4.7GB. Double-sided DVDs or BluRay discs are FAR larger ... and would take much longer ! Fair enough, but do i get points for uniqueness?

It seems to me that the problem should be fully constrained under the assumption of bitrot. For example, if just one bit in the file changed and you know it is just one bit, you should be able to recursively modify one bit and recalculate the checksum until it matches the original file. This may not be doable in practice if very similar (but different) files have the same checksum. I forget the term for this situatuon, but just some food for thought.

AAron, He's definitely correct. You need to provide your own ssl certificates if you use the https mapping. Otherwise, you can exclude the mapping and it'll generate the certificates itself. I provide my own ssl certificates because it is linked to my domain, but you can certainly use the genSSLKey script provided within the docker. You can try running with the environment variables REGENRATESSL_CERT=true and SUBJECT=/C=US/ST=CA/L=CITY/O=ORGANIZATION/OU=UNIT/CN=localhost (change the values for your needs) The first time you run with these, it'll create the ssl certs in /https and then you can remove those variables for the next run.

Quick update - after a docker restart my owncloud came back up and running. I'm not sure what the issue was, but it looks to be working now. No telling how long it'll stay up for.

If you file an issue with him, itmay be worth it to include th lgs in /var//lib/mysql/*.err This is what mine looks like: 2015-12-21 10:29:14 47924972562880 [Note] /usr/bin/mysqld (mysqld 10.1.9-MariaDB-log) starting as process 128 ... 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Using mutexes to ref count buffer pool pages 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: The InnoDB memory heap is disabled 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Memory barrier is not used 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Compressed tables use zlib 1.2.8 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Using Linux native AIO 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Using CPU crc32 instructions 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Initializing buffer pool, size = 128.0M 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Completed initialization of buffer pool 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Highest supported file format is Barracuda. 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: The log sequence numbers 1616819 and 1616819 in ibdata files do not match the log sequence number 1616849 in the ib_logfiles! 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Database was not shutdown normally! 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Starting crash recovery. 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Reading tablespace information from the .ibd files... 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Restoring possible half-written data pages 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: from the doublewrite buffer... 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: 128 rollback segment(s) are active. 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Waiting for purge to start 2015-12-21 10:29:15 47924972562880 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.26-74.0 started; log sequence number 1616849 2015-12-21 10:29:16 47925289838336 [Note] InnoDB: Dumping buffer pool(s) not yet started 2015-12-21 10:29:16 47924972562880 [Note] Plugin 'FEEDBACK' is disabled. 2015-12-21 10:29:16 47924972562880 [Note] Recovering after a crash using mysql-bin 2015-12-21 10:29:16 47924972562880 [Note] Starting crash recovery... 2015-12-21 10:29:16 47924972562880 [Note] Crash recovery finished. 2015-12-21 10:29:16 47924972562880 [Warning] Failed to create a socket for IPv6 '::': errno: 97. 2015-12-21 10:29:16 47924972562880 [Note] Server socket created on IP: '0.0.0.0'. 2015-12-21 10:29:16 47924972562880 [Note] /usr/bin/mysqld: ready for connections. Version: '10.1.9-MariaDB-log' socket: '/run/mysqld/mysqld.sock' port: 3306 MariaDB Server

Hmm... I'm having the same issue. I'm not actually the author of the docker - I just provided the template. Can you post an issue with him? https://github.com/l3iggs/docker-owncloud

Edgar, Make sure that you are accessing using a url such as: http://tower:8080/habmin/ Other then that, I would guess something is screwed up with either the addon(s) for habmin being deleted or the webapp altogether being deleted. This is often a problem using java based applications - configurations get screwed up often and easily. I find openhab is extremely susceptible to errors in configuration. I'm a bit slammed with work ATM, so the best thing I could do for you is to suggest starting the docker fresh, make sure you can access habmin, and slowly integrating your configuration back in.