🐞 [Bug]: Discourse zinit Error(Exited(Pid(348), 1))

Mik-TF commented 5 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

which package/s did you face the problem with?

Dashboard

What happened?

Deploying Discourse on mainnet, it gets stuck at:

"Be Patient We are getting everything ready for you, it takes some time."

SSH into the VM and running zinit I get the error:

Error(Exited(Pid(348), 1))

Steps To Reproduce

deploy on mainnet discourse app
see json log for info

which network/s did you face the problem on?

Main

version

latest

Twin ID/s

No response

Node ID/s

No response

Farm ID/s

No response

Contract ID/s

No response

Relevant screenshots/screen records

Relevant log output

{
  "version": 0,
  "contractId": 461097,
  "nodeId": 534,
  "name": "dcsldy9",
  "created": 1716821483,
  "status": "ok",
  "message": "",
  "flist": "https://hub.grid.tf/tf-official-apps/forum-docker-v3.1.2.flist",
  "publicIP": null,
  "planetary": "303:9e0a:87f1:1542:a13d:e0c5:6dc5:e09c",
  "myceliumIP": "4f5:d512:2559:533a:ff0f:0:400:2",
  "interfaces": [
    {
      "network": "nwiys53",
      "ip": "10.20.4.2"
    }
  ],
  "capacity": {
    "cpu": 1,
    "memory": 2048
  },
  "mounts": [
    {
      "name": "diskwy0",
      "mountPoint": "/var/lib/docker",
      "size": 16106127360,
      "state": "ok",
      "message": ""
    }
  ],
  "env": {
    "SSH_KEY": "ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABgQDVRwvsIUUudUJt+DvzX/Jre2hAHS2Y1HDutbe6vxK5Hnr9QoA7iKuTjqcRu9yDR2mN/JFHFIef7nFiXNjERbISqrFK4HIaFLHXuJaGMbUj7Bl3d1g5xGYeDtgh6+rmgeKvxauopY/VwGKVcZ83UYmT6ffkJRCgCqbrVzvfKJUNvucehZPpELcwbVSk3yNmqX+n3twuVsvoyH/m6D6DxiBrbQ0HfW1nDPp4AVfD7cn1fyNOleuHp9vvHy970a+2K5/fpU62sFLDAlvjpKBHaheAPdY+Sck7MfNlSrzAlt1+VSGnj8MsSvcdV1CAdc7muus77o59aIquUxwCfBLfeI85WBLQ63EsafDmkHeF7sJ90Jq5gnzX++fhgAySMFUJKX30HlWJhPCQTaEMSbXkrbqJGchoeY6fH/CWhiBmuZDTe5JOLbpKvSrVz91asD7+mIl+/CFLGwSgilzty+zwgmdlR5PAfK9oiA+cxorZmSu/S7iZv5+rB+mSXbvVONa+LDk= pcone@pcone-computer",
    "DISCOURSE_HOSTNAME": "dc708dcsldy9.gw331.salzburg1.greenedgecloud.com",
    "DISCOURSE_DEVELOPER_EMAILS": "email@example.com",
    "DISCOURSE_SMTP_ADDRESS": "smtp.gmail.com",
    "DISCOURSE_SMTP_PORT": "587",
    "DISCOURSE_SMTP_ENABLE_START_TLS": "false",
    "DISCOURSE_SMTP_USER_NAME": "email@example.com",
    "DISCOURSE_SMTP_PASSWORD": "uv6wDN8tTTji",
    "THREEBOT_PRIVATE_KEY": "WTCkU5lTODHXiriv8gkRgZt2mQYG6jst6EsP7pYv6A4=",
    "FLASK_SECRET_KEY": "hrVZUr4Q"
  },
  "entrypoint": "/sbin/zinit init",
  "metadata": "",
  "description": "",
  "rootfs_size": 524288000,
  "corex": false,
  "gpu": [],
  "deploymentName": "dcsldy9",
  "projectName": "discourse/dcsldy9",
  "billing": "No Data Available",
  "wireguard": "[Interface]\nAddress = 100.64.20.3/32\nPrivateKey = Qi5dXVluPu29L3twu6rkS1rX4OOt5cgBy8jT3dJrpQg=\n\n[Peer]\nPublicKey = G11sm3JC/vOpZ4X1a3skEmNACId5njW8TUFm27niAhE=\nAllowedIPs = 10.20.0.0/16, 100.64.20.0/32\nPersistentKeepalive = 25\nEndpoint = 195.192.213.244:21541"
}

ramezsaeed commented 5 months ago

If you still has this instance please provide zinit logs

Mik-TF commented 5 months ago

I redeployed on the same node 534, and Discourse worked. It only took some minutes to load, and zinit output was all success/running. Closing this thanks.

threefoldtech / tfgrid-sdk-ts