search

mikenye / docker-adsb-to-influxdb

Pull ADS-B data (Beast, SBS, Raw or JSON), send to InfluxDB
32 stars 10 forks source link

Can't authenticate with InfluxDB #5

Closed Wombot closed 4 years ago

Wombot commented 4 years ago

Hope all is well down on the other side of the planet!

There doesn't seem to be a way to pass credentials for InfluxDB into this container.

My InfluxDB requires at least simple user/pass authentication for Telegraf, per https://docs.influxdata.com/influxdb/v1.8/administration/authentication_and_authorization/#authenticate-telegraf-requests-to-influxdb

I am not seeing a way to provide those given the available arguments, and inspecting rootfs/etc/cont-init.d/02-telegraf seems to indicate that it's just not possible currently.

mikenye commented 4 years ago

Hi @Wombot, all is well down here! Hope all is well up there too.

I don't have authorization enabled for my InfluxDB (it's not exposed externally).

I can add a INFLUXDB_USERNAME and INFLUXDB_PASSWORD to the environment variables and modify rootfs/etc/cont-init.d/02-telegraf to include this in the config if you like?

Wombot commented 4 years ago

I think that would do the trick! I'm happy to try it out and report back.

mikenye commented 4 years ago

Hi @Wombot, if you could try out mikenye/adsb-to-influxdb:development, this contains INFLUXDBUSERNAME and INFLUXDBPASSWORD. Let me know how you go.

If it works, I'll merge the changes into master.

Thanks!

Wombot commented 4 years ago

Hey Mike, sorry for the delay in getting back to you! So, I think the user/pass fields are working. However, I can't really tell because no data is ever attempted to be written to the database, I think because adsb2influxdb isn't actually intaking any data from my readsb container.

I've tried the ADSBHOST=readsb as well as via IP. I've gone into the container, installed ping and NetCat, and made sure that the adsb2influxdb container is able to reach readsb (both by name and IP) and that the proper ports are open (they are). This is a bone-stock mikenye/readsb container that's happily sending data to every other feeder container.

I thought to use the JSONPORT, so I mapped 30012:30012 and tried to nc to it, but get a "connection refused" when I do. I opened up 30013 as well, just because I'm grasping at straws, same result. I'm not able to connect to those ports from either inside or outside the container.

If it's easier, I did also just join the ADSBX Discord and saw you're active over there. I'm happy to close this out and discuss there!

mikenye commented 4 years ago

Sure thing. Shoot me a message on Discord or let me know your username. I can’t see any “wombot”... :-)

mikenye commented 4 years ago

FYI for anyone that comes across this - the problem was with the readsb build process using -march=native by default. Overriding this by adding OPTIMIZE="-O3" to the readsb make command seems to have solved this.