[dummy title body text appended to avoid empty title body]
wkw replied
can u remove this line -e NC_DB="mysql2://host.docker.internal:3306?u=root&p=password&d=d1" \
n try again
wkw replied
for elb failing, it s hard to tell, you may need to check
- the connection from elb to ecs
- the connection between ecs n db
i.e. like security groups - make sure the ports are opened n the traffic are allowed etc
amarnath replied
i am using terraform to control all the changes. my present nocodb is 0.84.14(task definition 15), and trying to upgrade to 0.91.1 (task definition 16)
while 15 is working, 16 is not.
and i have removed NC_DB, now its working locally
amarnath replied
```➜ ~ diff task1 task2
1d0
<
67c66
< “image”: “nocodb/nocodb:0.84.14”,
—
> “image”: “nocodb/nocodb:0.91.1”,
94c93
< “taskDefinitionArn”: “arn:aws:ecs:ap-southeast-1:33333914:task-definition/nocodb:15”,
—
> “taskDefinitionArn”: “arn:aws:ecs:ap-southeast-1:30333914:task-definition/nocodb:16”,
135c134
< “revision”: 15,
—
> “revision”: 16,```
wkw replied
if you cant get into dashboard, then it means something is wrong with your NC_DB (as you proved that by not using NC_DB)
wkw replied
so now i think you only got 2 choices
1. use a new DB as NC_DB (this should be faster if all of your projects are connecting to external DB but you have to create those projects again and meta will be lost such as sorting / filtering etc)
2. otherwise, u need to check Cloudwatch logs to figure out what goes wrong with the upgrade
amarnath replied
1st one is not an option. there are lot of projects. why 84.14 is working, 0.90.0 is not (i have tested this version as well)
wkw replied