New pern here. I’ve installed InfluxDB3 and Explorer on an EC2 instance. ( debian )
from looking at systemctl it appears that Influx is up. it’s installed bare metal.
the Explorer is installed in docker. Explorer allows me to connect back to the bare metal DB3 as I can apparently create databases. I have created 3 in flapping around here, including one of the sample databases.
when I try to fire up Data Explorer I am told ‘loading chunk 4747 failed. ( error: http://n.n.n.n:8888/_query tool_app/4747…….js )
In the container I see Nest howling about the same thing - the HttpExceptionFilter catches it. It also reports that a Database is Required, and that AI settings are not found for this session (surprise )
oh if I try to make a dashboard same deal.
Q:Should I have opened more ports or something?
EDIT: it’s also complaining about a license:
data: “query error: error while planning query: Error during planning: table ‘public.system.license’ not found”
Does the Explorer docker container have persistent storage? I have seen that behavior related to storage and or permissions.
Also have you deployed the Explorer container multiple times? Deleting a container instance and deploying a new one with the same settings? In that case the Explorer DB could be the issue. Remove all ‘old’ data before deploying a new one.
And if you want to setup a new complete deployment feel free to look at my Docker Automated extended TIG deployment @ GitHub - EdwardVoermans/ETIG-Stack-InfluxDB3: Extended TIG Stack InfluxDB3 auto deployed on Docker Containers
It sounds like a network setting issue, make sure the docker URL is correct for the InfluxDB 3. Also are you using Enterprise version if so is the license correctly setup ? Is this using AWS Timestream for InfluxDB or you are doing it all by yourself?
Thanks, E. Persistent storage outside the container, no, or at least none that I explicitly configured. I have built and destroyed the container multiple times.
Thanks Suyash.
As the docker-contained Explorer is giving me the ‘green checkmark’ when I define the connection I have to conclude that the connection to the database server is working. Trust me I had a few first tries at that which didn’t route! right? secondly if I can use Explorer to create databases in the server there is some kind of communication happening.
Not the enterprise version; and the error message reads to be about a public license.
Also, not the AWS packaged version. Straight from the Influx repos.
It’s as if the docker image is messed up, or Nest or confused about the name of that component.
quite baffling.
