not able to start docker file... about fritzinfluxdb HOT 11 CLOSED

Hi,

you need to change the config (fritzinfluxdb.ini) BEFORE running docker build.

can you try that?

from fritzinfluxdb.

Hi

Yes... now it's running... ;o)

Connected to Fritzbox, but I have to check my influx database, get "ERROR: Problem connecting to database: HTTPConnectionPool(host='127.0.0.1', port=8086): Max retries exceeded with url: /query?q=SHOW+DATABASE&db=fritzbox (Caused by NewConnectionError('<urllib3.connection.TTPConnection object at 0x7f8c02550d30>: Failed to establish a new connection: [Errno 111] Connection refused',))

Another question... If I now want to change the running configuration, I can do this over the ini in the docker run?

update 1:
In grafana I can add the database, so it's running, Could it be a problem, that influx is also running in a docker container? iDo you know if it is possible to connect the both container? I can get access to influx (crono) and grafane over localhost:3004 and 3003... Influx over localhost:8086... hmmm

update 2: tried also a local influx installation. same error message.

Thanks for your quick response!!
Ronald

from fritzinfluxdb.

You need to know which port influxdb exposes to the host.
you could test on your machine if curl http://127.0.0.1:8086 works and inxluxdb responds. If not then you need to find the correct influx port.

from fritzinfluxdb.

i don't know... with curl i get "404 page not found"

if I run influx I get the the message: Connected to http://localhost:8086 version 1.8.3

and it looks like that influx is listening on :8088 and 8086

ss -lntu
Netid State Recv-Q Send-Q Local Address:Port Peer Address:Port
tcp LISTEN 0 128 127.0.0.1:8088 0.0.0.0:*
tcp LISTEN 0 128 0.0.0.0:22 0.0.0.0:*
tcp LISTEN 0 128 *:3000 :
tcp LISTEN 0 50 *:1716 :
tcp LISTEN 0 128 :8086 :
tcp LISTEN 0 128 [::]:22 [::]:

In grafana I also use http://localhost:8086 without getting trouble.

Update:
nmap -p 8086 127.0.0.1
Starting Nmap 7.70 ( https://nmap.org ) at 2021-01-13 17:04 CET
Nmap scan report for localhost (127.0.0.1)
Host is up (0.000065s latency).

PORT STATE SERVICE
8086/tcp open d-s-n

so it looks like that 127.0.0.1:8086 is the right one...

from fritzinfluxdb.

Sorry for not getting back.

can you try to add --network host to the docker run command?

from fritzinfluxdb.

thanks for still helping me... ;o)

I tried again with... --network 127.0.0.1, --network localhost and --network 192.168.178.20...

everytime i get: docker: Error response from daemon: network xxxxxxxx not found.

I don't know whats wrong with my installation...

cheers
ronald

from fritzinfluxdb.

it's running... but I don't know, why...

All changes I made was not successful. so I modified the username in section [fritzbox] to check if I will get a error message because of wrong username and also changed host ip adress from 127.0.0.1 to 192.168.178.20 in section [influx] and started the container with docker run -d -v /usr/share/fritzbox/fritzinfluxdb.ini:/app/idefault.ini --name fritzinfluxdb fritzinfluxdb as written in your description... but nothing happend... still connected to my fritzbox...

Then I change the running command to docker run -d -v /usr/share/fritzbox/fritzinfluxdb.ini:/app/fritzinfluxdb.ini --name fritzinfluxdb fritzinfluxdb still with the wrong username and host = 192.168.178.20.

and that's what I get...

pi@raspberrypi:/usr/share/fritzbox $ docker logs fritzinfluxdb --details
2021-01-18 20:02:39,850 - INFO: Done parsing config file
2021-01-18 20:02:39,864 - INFO: Connection to InfluxDB established and database present
2021-01-18 20:02:42,001 - INFO: Successfully connected to FritzBox
2021-01-18 20:02:42,003 - INFO: Starting main loop

I took a look inside the container... and checked the inside fritzinfluxdb.ini. It contains the wrong username, but it's running and I also get the informations in grafana... Anyway... HAPPY, that's now running even with the wrong username. ;)

Could you explain, why it's now running, even with a wrong fritzbox username?
Answer: I checked, only for some special parameters you need username and password. And it's now running because of host adresse

thanks a lot for your support...

Cheers
Ronald

from fritzinfluxdb.

Because it's now running, and I know why, I will close this issue... thanks for your patience and support...

from fritzinfluxdb.

Hey,

I got some time to test around and figured out why it wasn't working for you.

Yes, the instructions about the docker run command was wrong. Fixed it.

can you check this part of the docs if this works for you?: https://github.com/yunity/fritzinfluxdb#example

from fritzinfluxdb.

Hi Ricardo

Thanks for taking a look... I made it as written in "example" and it is running well...

But I think you have some typos... you wrote my-frTIzinfluxdb.ini and /PATH/TO/my-frTIzinfluxdb.ini:/app/frTIzinfluxdb.ini

The otherway to get the connection to the influxdb ist to write the IP address from the InfluxDB Host inside the fritzinfluxdb.ini. In my case the IP address from my RasPI.

Anyway, now it's running and I appreciate your work and support...!!!

Cheers
Ronald

from fritzinfluxdb.

Hi Ricardo

Thanks for taking a look... I made it as written in "example" and it is running well...

But I think you have some typos... you wrote my-frTIzinfluxdb.ini and /PATH/TO/my-frTIzinfluxdb.ini:/app/frTIzinfluxdb.ini

THANK YOU. This is embarrassing but fixed now.

The otherway to get the connection to the influxdb ist to write the IP address from the InfluxDB Host inside the fritzinfluxdb.ini. In my case the IP address from my RasPI.

This works as well, true. But needs to be the interface IP. With the --link option the traffic stays inside the docker bridge network and you don't need to expose the influxdb port if influx is just consumed by other docker containers.

Anyway, now it's running and I appreciate your work and support...!!!

You're welcome

from fritzinfluxdb.