Domoticz

Posted: **Sunday 26 January 2020 20:41**

This evening I thought I'd give my Pi a fresh start and install everything from scratch.

I installed the latest Buster release available and proceeded to install Domoticz. All well and good so far.

Then I decided to try the new Auto Installation. It seems to get an error and abort mid way. I can set this up manually but thought I'd post this here and see if we can find a solution.

Here is a copy of my SSH session trying to install Dashticz.

Code: Select all

pi@raspberrypi:~ $ . <(wget -qO - https://raw.githubusercontent.com/Dashticz/dashticz/beta/scripts/dashticz_install.sh )
This is the installation script for Dashticz

Using default settings

Dashticz repository: https://github.com/Dashticz/dashticz
Branch: master
Port: 8082

The script will create a folder for Dashticz in the following location:
/home/pi

Enter the folder name [dashticz]: dashticz

Dashticz will be installed in
dashticz


Dashticz has a master branch (=stable) and a beta branch (=most up-to-date)
Which branch to install? [master]: beta
Checking for git: [OK!]

Now cloning the Dashticz repository https://github.com/Dashticz/dashticz

Cloning into 'dashticz'...
remote: Enumerating objects: 202, done.
remote: Counting objects: 100% (202/202), done.
remote: Compressing objects: 100% (120/120), done.
remote: Total 8621 (delta 88), reused 164 (delta 75), pack-reused 8419
Receiving objects: 100% (8621/8621), 38.30 MiB | 1.12 MiB/s, done.
Resolving deltas: 100% (5634/5634), done.
Checking out files: 100% (596/596), done.

Checking for make: [OK!]
Configuring Dashticz.

What is the IP:port address of your Domoticz server? (example: 192.168.178.18:8080): 192.168.0.22:8080

Finding a free port for Dashticz
Port 8082 is available

Setting up Dashticz on port 8082


Starting make process ...

Checking container dtv3-8082
Checking port 8082
sudo docker build --build-arg tz="Europe/London" -t dtv3-8082 .
Sending build context to Docker daemon  72.79MB
Step 1/4 : FROM php:apache
 ---> 3041b4d61e21
Step 2/4 : ARG tz="Europe/Amsterdam"
 ---> Using cache
 ---> 098b8075fa68
Step 3/4 : RUN printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini
 ---> Running in 2054f064100d
The command '/bin/sh -c printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini' returned a non-zero code: 139
make: *** [Makefile:51: start] Error 139
Error during Make. Exiting
Connection to 192.168.0.22 closed.

Posted: **Monday 27 January 2020 8:55**

Thanks for the feedback!
Apparently something goes wrong with setting the correct timezone while building the Docker image. I'll have a look.

Posted: **Wednesday 15 April 2020 8:40**

Hi, is there a solution for this problem?
I also have this problem.

Posted: **Wednesday 15 April 2020 12:05**

danman87 wrote: ↑Wednesday 15 April 2020 8:40 Hi, is there a solution for this problem?
I also have this problem.

I was not able to reproduce yet. So, let's try...
You have the same error as Scotty?

What is the result of the following command:

Code: Select all

 cat /etc/timezone

Open Makefile.ini (in the Dashticz root folder):

Code: Select all

nano Makefile.ini

Add the following to Makefile.ini:
(You don't have to change the lines starting with APP and PORT)

Code: Select all

TZ=Europe/Amsterdam

and then try to rebuild the Docker image:

Code: Select all

make start

Posted: **Wednesday 15 April 2020 13:16**

hi Lokonli,

Yes, i have exactly the same issue.

cat /etc/timezone
Europe/Amsterdam

pi@raspberrypi:~$ nano Makefile.ini
GNU nano 2.7.4 File: Makefile.ini

files was empty. i added ''TZ=Europe/Amsterdam''

i did the ''make start'' command, but i got the same error:

pi@raspberrypi:~/dashticz$ make start
Checking container dtv3-8082
Checking port 8082
sudo docker build --build-arg tz="Europe/Amsterdam" -t dtv3-8082 .
Sending build context to Docker daemon 90.36MB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini
---> Running in 93f2b3260664
The command '/bin/sh -c printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini' returned a non-zero code: 139
Makefile:49: recipe for target 'start' failed
make: *** [start] Error 139

Posted: **Wednesday 15 April 2020 15:19**

ok. Try the following.
Create a basic Dockerfile in a new folder somewhere:

Code: Select all

mkdir ~/test
cd ~/test
nano Dockerfile

Add the following content to Dockerfile:

Code: Select all

FROM php:apache
ARG tz="Europe/Amsterdam"
RUN ls
RUN printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini

Build the Docker container:

Code: Select all

sudo docker build .

and post the output of the build process here.

Posted: **Wednesday 15 April 2020 19:47**

Hi Lokonli,

Thank you for the fast reply.
i did the steps, here the output:

pi@raspberrypi:~/test$ sudo docker build
"docker build" requires exactly 1 argument.
See 'docker build --help'.

Usage: docker build [OPTIONS] PATH | URL | -

Build an image from a Dockerfile

Posted: **Wednesday 15 April 2020 19:51**

a new ''make start'' turns with the same error.

pi@raspberrypi:~/dashticz$ make start
Checking container dtv3-8082
Checking port 8082
sudo docker build --build-arg tz="Europe/Amsterdam" -t dtv3-8082 .
Sending build context to Docker daemon 90.36MB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini
---> Running in 1c8a7bda7d90
The command '/bin/sh -c printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini' returned a non-zero code: 139
Makefile:49: recipe for target 'start' failed
make: *** [start] Error 139

myself i thought it had something to do with r/w rights, but i think i set it right allready.

Posted: **Wednesday 15 April 2020 19:52**

Don't forget the dot behind sudo docker build .

Sent from my SM-A320FL using Tapatalk

Posted: **Wednesday 15 April 2020 20:01**

ahh yes, did that now.
i get this output now:

pi@raspberrypi:~/dashticz$ sudo docker build .
Sending build context to Docker daemon 90.36MB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini
---> Running in 8196aad9652a
The command '/bin/sh -c printf "[PHP]\ndate.timezone = $tz\n" > /usr/local/etc/php/conf.d/tzone.ini' returned a non-zero code: 139

it's not saying recipe for target 'start' failed anymore

Posted: **Wednesday 15 April 2020 20:03**

Please run it in the test folder, so that the new Dockerfile that you created is being used.

Sent from my SM-A320FL using Tapatalk

Posted: **Wednesday 15 April 2020 20:07**

yes you are right idd. here it is:

pi@raspberrypi:~/test$ sudo docker build .
Sending build context to Docker daemon 2.048kB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN ls
---> Running in daa77d7bec6d
The command '/bin/sh -c ls' returned a non-zero code: 139

Posted: **Wednesday 15 April 2020 20:21**

The first real Docker command already throws an error. I've seen some reports on Docker issues.
Can you first upgrade your system with sudo update followed by sudo upgrade?

Sent from my SM-A320FL using Tapatalk

Posted: **Wednesday 15 April 2020 21:04**

did the upgrade with sudp apt update and sudo apt ugrade
but i get the same:

pi@raspberrypi:~/test$ sudo docker build .
Sending build context to Docker daemon 2.048kB
Step 1/4 : FROM php:apache
---> fabd924a2602
Step 2/4 : ARG tz="Europe/Amsterdam"
---> Using cache
---> 86575eebd038
Step 3/4 : RUN ls
---> Running in 6a2c9d739b54
The command '/bin/sh -c ls' returned a non-zero code: 139

Posted: **Wednesday 15 April 2020 21:24**

Ok, good.
Next step is to fix Docker.
How did you install Docker: via the Dashticz auto install script, or did you install Docker yourself?
You use a raspberry pi?

Sent from my SM-A320FL using Tapatalk

Posted: **Wednesday 15 April 2020 21:28**

yes i think docker is not working. i installed it via the auto install script.
And yes i use an raspberry pi

Posted: **Wednesday 15 April 2020 21:32**

i am running on buster btw.
i started at jessie, then upgraded to stretch and then to buster.
updated domoticz to the newest version, and that is working fine.

Posted: **Wednesday 15 April 2020 21:50**

danman87 wrote: ↑Wednesday 15 April 2020 21:32 i am running on buster btw.
i started at jessie, then upgraded to stretch and then to buster.
updated domoticz to the newest version, and that is working fine.

Let's check the docker apache image. What's the output of:

Code: Select all

sudo docker images | grep apache

Posted: **Wednesday 15 April 2020 21:58**

ill get this now:

pi@raspberrypi:~$ sudo docker images | grep apache
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
pi@raspberrypi:~$ sudo service docker start
Job for docker.service failed because the control process exited with error code.
See "systemctl status docker.service" and "journalctl -xe" for details.
pi@raspberrypi:~$ sudo docker images | grep apache
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
pi@raspberrypi:~$ systemctl status docker
â— docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Wed 2020-04-15 21:57:27 CEST; 24s ago
Docs: https://docs.docker.com
Process: 1845 ExecStart=/usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock (code=exited, status=1/FAILURE)
Main PID: 1845 (code=exited, status=1/FAILURE)

Apr 15 21:57:25 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 15 21:57:25 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.
Apr 15 21:57:27 raspberrypi systemd[1]: docker.service: Service RestartSec=2s expired, scheduling restart.
Apr 15 21:57:27 raspberrypi systemd[1]: docker.service: Scheduled restart job, restart counter is at 3.
Apr 15 21:57:27 raspberrypi systemd[1]: Stopped Docker Application Container Engine.
Apr 15 21:57:27 raspberrypi systemd[1]: docker.service: Start request repeated too quickly.
Apr 15 21:57:27 raspberrypi systemd[1]: docker.service: Failed with result 'exit-code'.
Apr 15 21:57:27 raspberrypi systemd[1]: Failed to start Docker Application Container Engine.

Posted: **Wednesday 15 April 2020 22:17**

Sounds like a docker problem.

What's the output of:

Code: Select all

sudo journalctl -xe

Domoticz

Problem with auto installer

Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer

Re: Problem with auto installer