Help after updating from ssh site goes down

[kynic]

I followed this and updated discourse via ssh

How do I manually update Discourse and Docker image to latest?

If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occasionally need to do this additional step. Discourse itself should be updated about twice a month, by clicking the “Update to Latest Version” button in your admin dashboard ( admin/upgrade). We do beta releases roughly once every week. Every two months we recommend SSH’ing…

After doing this site goes down pls help me I in stress pls help

it shows this when I try to start launcher

./launcher start app
x86_64 arch detected.

starting up existing container
+ /usr/bin/docker start app
Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: sethostname: invalid argument: unknown
Error: failed to start containers: app

[tobiaseigen]

Try this instead:

cd /var/discourse
git pull
./launcher rebuild app

[kynic]

Already did still same;

git pull
Already up to date.

./launcher rebuild app
in end this shows up:

 ess 02:fc:33:3e:fd:f6 local_discourse/app /sbin/boot
589988dcb7e5e026f29b8af3b507e51a260e9de2f1ddfaea0620e1fbd2ea80e7
docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: sethostname: invalid argument: unknown.

[tobiaseigen]

Did you try discourse doctor?

Announcing Discourse Doctor

Following the example from Discourse-doctor , I’ve created discourse-doctor, now included in discourse_docker. If you run ./discourse-doctor, you’ll see something like: DISCOURSE DOCTOR Tue Jul 24 08:50:32 UTC 2018 OS: Linux twonames 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux Found containers/app.yml ==================== YML SETTINGS ==================== DISCOURSE_HOSTNAME=twonames.ltcmp.net SMTP_ADDRESS=mail.domain.com DEVELOPER_EMAILS=…

[kynic]

Just did after you said this what I get in end lines:

sudo: unable to resolve host discourse-ubuntu-s-1vcpu-1gb-nyc1-01-1606640043912-s-2vcpu-4gb-n: Name or service not known
Error response from daemon: Container 387d78b520911e93647a157c578f479a9b4ceaf4fef60b19c638a03de162444c is not running

Replacing: SMTP_PASSWORD
Replacing: LETSENCRYPT_ACCOUNT_EMAIL
Replacing: DEVELOPER_EMAILS
Replacing: DISCOURSE_DB_PASSWORD
Replacing: Sending mail to

==================== DONE! ====================

[tobiaseigen]

And then you rebuild again and what happens?

[kynic]

I changed the hostname to ‘discourse-ubuntu’ earlier it was a long name, by editing these files…

nano /etc/hostname

discourse-ubuntu

nano etc/hosts

127.0.1.1 discourse-ubuntu
127.0.0.1 localhost

after that, I reboot and rebuild, and then it’s fixed finally.

Thank you for all your help.