Similar issues happen with the container which runs Nginx. The container takes about 3Mb of RAM when it runs on my laptop, way less than the 512Mb available on the Nano instance. I couldn't find any other output or logs from Lightsail.
It also starts in about 5 seconds, including opening the connection to the database and running a few quick transactions on it, so I don't think it's a matter of slow start.
Aws bitnami djangostack default ssh user code#
The container's ENTRYPOINT script prints some output (for instance, it executes `env` to show the environment), but I don't see it in the logs and the Go code is verbose when it starts up but I don't see the expected output in the logs either. The Docker image I created on my laptop runs fine on my laptop, it can even open the connection to the database (I made the database public while debugging).īut when I push the image to Lightsail and try to deploy it, all I get is: I setup a nano single instance and try to run two containers - one with a Go program which talks to a database and one with Nginx front-end serving a React application.įor the sake of troubleshooting, I narrowed it down to just the Go program. This is the first time I try to use AWS Lightsail.
Aws bitnami djangostack default ssh user how to#
I don't want to keep using localhost dbs, I want to centralize my data in a dedicated database.ĭoes anyone know how to handle this problem? Localhost is Mariadb 10, dedicated database server is MySQL 8 My current traffic is 2000 visitors per day.Īws lightsail update-relational-database-parameters -relational-database-name Database-1 -parameters "parameterName=max_connections,parameterValue=150,applyMethod=immediate" I have increased the number of max_connections from 65 to 500 using the aws CLI (localhost is 150). **The web app seems to work with the dedicated Lightsail db server when I am the only one using it** and until I open it to more traffic, then I get the connection error. **I can connect to the database using the command line tool**: mysql -u uuuu -p -h hhhhh (ie: it is not a problem with entering the wrong credentials) Even though it is not necessary I have tried enabling VPC peering and opening the db to the public.
My instances and database are in the same region. The front end reads "cannot connect to MySQL database" and in the database server log I read : ` IP address '' could not be resolved: Name or service not known" where the IP is the private IP address of my instance.` When I want to connect the instances to a Lightsail database instead of localhost, it works sporadically. I have a web app running on Lightsail instances stacked with LAMP (PHP 7/MariaDB 10 service).
0 kommentar(er)
