Twenty•3mo ago

Server Container Hanging During Startup

Hey how's it going y'all? I'm looking to test out deploying twenty to an AWS ECS cluster but I'm running into an interesting error right now where the latest twentyhq/twenty docker container seems to hang when it's deployed as a task. From the looks of it, the container hangs on the yarn command:prod upgrade command in the entrypoint.sh file. It's running in a container with 8GB ram and decent CPU, so I don't think it's a resource constraint. The yarn command is not outputting any logs to stdout, so I'm at a bit of a loss. Any ideas what to check next to troubleshoot?

Mem: 5642940K used, 10426568K free, 532K shrd, 163672K buff, 4272176K cached
CPU:   0% usr   0% sys   0% nic  99% idle   0% io   0% irq   0% sirq
Load average: 0.02 0.02 0.02 5/313 224
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
   78    58 node     S    10.9g  71%   0   0% /usr/local/bin/node dist/src/command/command upgrade
   70    28 root     S    1890m  12%   1   0% /managed-agents/execute-command/ssm-agent-worker
  112    70 root     S    1885m  12%   0   0% /managed-agents/execute-command/ssm-session-worker ecs-execute-command-lzuvyi7po2ki9c8xbquv5io93e
   28     0 root     S    1805m  11%   1   0% /managed-agents/execute-command/amazon-ssm-agent
   58    40 node     S     756m   5%   0   0% /usr/local/bin/node /app/.yarn/releases/yarn-4.4.0.cjs command:prod upgrade
   40     1 node     S     694m   4%   0   0% node /opt/yarn-v1.22.22/bin/yarn.js command:prod upgrade
  123   112 root     S     1708   0%   1   0% /bin/sh
    1     0 node     S     1648   0%   1   0% {entrypoint.sh} /bin/sh /app/entrypoint.sh node dist/src/main
  224   123 root     R     1636   0%   1   0% top

Mem: 5642940K used, 10426568K free, 532K shrd, 163672K buff, 4272176K cached
CPU:   0% usr   0% sys   0% nic  99% idle   0% io   0% irq   0% sirq
Load average: 0.02 0.02 0.02 5/313 224
  PID  PPID USER     STAT   VSZ %VSZ CPU %CPU COMMAND
   78    58 node     S    10.9g  71%   0   0% /usr/local/bin/node dist/src/command/command upgrade
   70    28 root     S    1890m  12%   1   0% /managed-agents/execute-command/ssm-agent-worker
  112    70 root     S    1885m  12%   0   0% /managed-agents/execute-command/ssm-session-worker ecs-execute-command-lzuvyi7po2ki9c8xbquv5io93e
   28     0 root     S    1805m  11%   1   0% /managed-agents/execute-command/amazon-ssm-agent
   58    40 node     S     756m   5%   0   0% /usr/local/bin/node /app/.yarn/releases/yarn-4.4.0.cjs command:prod upgrade
   40     1 node     S     694m   4%   0   0% node /opt/yarn-v1.22.22/bin/yarn.js command:prod upgrade
  123   112 root     S     1708   0%   1   0% /bin/sh
    1     0 node     S     1648   0%   1   0% {entrypoint.sh} /bin/sh /app/entrypoint.sh node dist/src/main
  224   123 root     R     1636   0%   1   0% top

1 Reply

CrashOP•3mo ago

I kept tweaking my config files around and I solved my issue - I think the change that fixed my issue was my redis server was only accessible over TLS and I was using the regular "redis://" URL. Once I used the correct "rediss://" protocol, things started running smoother. Hopefully that helps someone else out later lol

Gaming

Programming

Server Container Hanging During Startup

Did you find this page helpful?