Hi @flamber, thanks for responding.
I increased the memory to 2GB and it was running fine for couple of days. Now it’s back to 502 Bad gateway error.
To experiment, I’ve increased the aws ec2 instance to t2.xlarge(16GB memory and 4CPU).
Regarding the metabase log, even after following all the steps in https://www.metabase.com/docs/latest/operations-guide/running-metabase-on-debian.html, log file is not updating. (if there’s any other link to help setup log, please do share).
sudo java -jar /var/metabase/metabase.jar, everything went smoothly without any errors. But accessing the URL gives a fresh installation of metabase - showing setup page.
The metabase is setup is done as a service.
sudo java -jar /var/metabase/metabase.jar migrate release-locks, below is the output.
10-09 09:22:27 DEBUG plugins.classloader :: Using NEWLY CREATED classloader as shared context classloader: clojure.lang.DynamicClassLoader@377c68c6
10-09 09:22:27 DEBUG plugins.classloader :: Setting current thread context classloader to shared classloader clojure.lang.DynamicClassLoader@377c68c6…
10-09 09:22:28 INFO metabase.util :: Loading Metabase…
10-09 09:22:28 INFO metabase.util :: Maximum memory available to JVM: 3.5 GB
10-09 09:22:31 INFO util.encryption :: Saved credentials encryption is DISABLED for this Metabase instance.
For more information, see https://metabase.com/docs/latest/operations-guide/encrypting-database-details-at-rest.html
10-09 09:22:35 INFO metabase.driver :: Registered abstract driver :sql
10-09 09:22:42 WARN metabase.db :: WARNING: Using Metabase with an H2 application database is not recommended for production deployments. For production deployments, we highly recommend using Postgres, MySQL, or MariaDB instead. If you decide to continue to use H2, please be sure to back up the database file regularly. For more information, seehttps://metabase.com/docs/latest/operations-guide/migrating-from-h2.html
10-09 09:22:43 INFO metabase.db :: Setting up Liquibase…
10-09 09:22:43 INFO metabase.db :: Liquibase is ready.