Launched cloudformation template with all default parameters (see screenshot below)
Waited 30 minutes (just to ensure all setup scripts run)
Attempted to go to http://<myElasticIP> and got a 504 Gateway Timeout
Note: I ran through the exact same procedure for version 0.8.4-3 and was successfully able to get it running.
Cloudwatch Logs
I checked the Cloudwatch logs to compare between deployments. Both the successful 0.8.5-2 and 0.8.4-3 had these error logs but since both had them, it seems likely to simply be initial timeouts that were eventually retried (i.e. red herring)
From jambonz-api-server cloudwatch logs:
at PoolConnection._handleTimeoutError (/home/admin/apps/jambonz-api-server/node_modules/mysql2/lib/connection.js:189:17)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
fatal: true
From jambonz-feature_server cloudwatch logs:
Error: connect ETIMEDOUT
at PoolConnection._handleTimeoutError (/home/admin/apps/jambonz-feature-server/node_modules/mysql2/lib/connection.js:189:17)
at listOnTimeout (node:internal/timers:569:17)
at process.processTimers (node:internal/timers:512:7) {
errorno: 'ETIMEDOUT',
code: 'ETIMEDOUT',
syscall: 'connect',
fatal: true
The jambonz-mini version
0.8.5-2
through AWS marketplace is failing to start up successfully.Reproduction Steps Follow steps in guide: https://blog.jambonz.org/installing-jambonz-using-aws-marketplace
0.8.5-2
as the software version.http://<myElasticIP>
and got a 504 Gateway TimeoutNote: I ran through the exact same procedure for version
0.8.4-3
and was successfully able to get it running.Cloudwatch Logs
I checked the Cloudwatch logs to compare between deployments. Both the successful
0.8.5-2
and0.8.4-3
had these error logs but since both had them, it seems likely to simply be initial timeouts that were eventually retried (i.e. red herring)From
jambonz-api-server
cloudwatch logs:From
jambonz-feature_server
cloudwatch logs: