![]() ![]() I have been setting up different Ghost instances since version 3, and this is quite the first time, no matter how many times I re-do the whole setup, Ghost is unable to connect to mysql, though I do know in the past. 61 I recommend against closing this question as too localized. The hostname saved in this file ( /etc/hostname) will be preserved on system reboot (and will be set using the same service). From all the results, I think Ghost have no issues but this mysql issue kept coming up oddly. To follow this tutorial, you will need the following: One Ubuntu 20.04 server set up by following the Ubuntu 20.04 initial server setup guide, including a sudo non-root user and a firewall. Note : Above command to make the change active. If you wanted a 1-click way to deploy a Docker application to a live server, take a look at DigitalOcean App Platform. You should see the following screen: As you can see, the message sudo: unable to resolve host newpc indicates that the hostname command cannot determine the IP address of host newpc In simple terms, the hostname command cannot resolve the hostname of your system. You must keep both your host names in /etc/hosts (127.0.0.1 newhost oldhost) until you execute the command below: sudo service hostname start To change without a reboot, you can just use hostname.sh after you edit /etc/hostname. Attempt to use the sudo command after updating the hosts file and it should work. To address this issue update the hostname or FQDN of the Archiving server in the /etc/hosts file and save the file. So Ive found a few suggestions on solutions, but they seem to be dated or not applicable to my ca. Now after a reboot, your hostname will be the new one you chose Without Reboot Solution: This issue can occur if the host name is not updated or incorrect in the /etc/hosts file. Im trying to use dnsmasq on Ubuntu 20.04 and I get a port clash on port 53 with systemd-resolved. ![]() If you have already done it, press ESC on the grub menu, choose recovery, and edit your host file to the correct settings) To resolve this issue, make sure that Elasticsearch is running by following the Elasticsearch troubleshooting sections. 127.0.1.1 your-hostname The commands used in the example are: cat /etc/hostname the command 'cat' will print the content of '/etc/hostname' file hostname without arguments, this command will do the same as above command cat /etc/hosts will print the content of '/etc/hosts' file sudo nano /etc. Note : i have read it on a forum > Edit /etc/hosts and change the old 127.0.1.1 line to your new hostname (if you don't do this, you wont be able to use sudo anymore. To resolve this issue you must find (or set) your hostname and insert next line into /etc/host. If by any chance git is missing, install it by running the following command. In most Ubuntu 18.04 systems, git comes already installed. Once you have successfully created the user ‘stack’ and assigned sudo privileges, switch to the user using the command. Listen_address = ":9252" concurrent = 25 check_interval = 90 log_level = "info" session_timeout = 1800 ] name = "gitlab-runner-all-develop-gitlab-runner-ff99c489d-7br7w" output_limit = 4096 request_concurrency = 30 url = "" token = "*********************" executor = "kubernetes" clone_url = "" host = "" bearer_token_overwrite_allowed = false image = "ubuntu:18.Changing the hostname or computer name in ubuntu without restartĮdit /etc/hostname and change to the new value, nano /etc/hostnameĮdit /etc/hosts and change the old 127.0.1.1 line to your new hostname 127.0.0.1 localhostġ27.0.1.1 ubuntu.local ubuntu # change to your new hostname/fqdn Step 3: Install git and download DevStack. Digital Ocean & Published with Ghost & Rinne. # = # INCLUDE TEMPLATES # = include : - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-audit.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-base.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-build.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-dast.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-deploy.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-global.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-scanning.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-sonarqube.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-web-performance.yml" - project : " shared/devops/pipeline" file : " /ci/.gitlab-ci-rules.yml" # = # DEFAULT IMAGE # = image : docker:19.03.0 # = # SERVICES # = services : - docker:19.03.0-dind # = # STAGES # = stages : # = # WORKFLOW RULES # = workflow : rules : - if : $PIPELINE_DISABLE = "true" when : never - if : $CI_MERGE_REQUEST_ID when : never - when : always # = # GLOBAL VARIABLES # = variables : DOCKER_HOST : tcp://localhost:2375 DOCKER_TLS_CERTDIR : " " DOCKER_DRIVER : overlay2 DOCKER_BUILDKIT : 1 GIT_DEPTH : 1 GIT_SUBMODULE_STRATEGY : none GIT_STRATEGY : none Actual behavior This is important otherwise youll start seeing sudo: unable to resolve host error.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |