cpanel dnsonly
We have a problem with cpanel dns only server. to be sure its not a cloud provider related issue, we tried to set it up on gcloud and on aws.
the instance gets unavailable after a certain time. at this point, the vm is not available anymore over port 2087 or ssh. the connection times out.
for setup we used the almalinux images available on each cloud provider (8.9 on gcloud and 8.10 on aws).
the installation results with no error. the following description is based on gcloud:
we followed these procedures:
- https://docs.cpanel.net/installation-guide/cpanel-dnsonly-installation/
- https://docs.cpanel.net/knowledge-base/web-services/how-to-install-cpanel-on-google-compute-engine-through-the-google-marketplace/#create-the-hostname-fix-hook
the vm has 2vcpus and 16gb ram. that should be more than required.
after the issue begins, on serial console are also network errors for the gcloud agent. if you try to ping anything, it won't get resolved. but before the issue exists, you can ping anything and it works as expected.
we set dns resolver to 8.8.8.8 and 8.8.4.4. but also on the default value the same problem occurs.
we are talking to google support since more than two weeks now and could not find a solution yet.
gcloud logs:
Jun 5 13:01:59 debug OSConfigAgent[109178]: 2024-06-05T13:01:59.8731Z OSConfigAgent Critical main.go:112: Error parsing metadata, agent cannot start: network error when requesting metadata, make sure your instance has an active network and can reach the metadata server: Get "http://169.254.169.254/computeMetadata/v1/?recursive=true&alt=json&wait_for_change=true&last_etag=0&timeout_sec=60": dial tcp 169.254.169.254:80: connect: network is unreachable
Jun 5 13:01:59 debug systemd[1]: google-osconfig-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 5 13:01:59 debug systemd[1]: google-osconfig-agent.service: Failed with result 'exit-code'.
Jun 5 13:02:01 debug systemd[1]: google-osconfig-agent.service: Service RestartSec=1s expired, scheduling restart.
Jun 5 13:02:01 debug systemd[1]: google-osconfig-agent.service: Scheduled restart job, restart counter is at 1123.
Jun 5 13:02:01 debug systemd[1]: Stopped Google OSConfig Agent.
Jun 5 13:02:01 debug systemd[1]: Started Google OSConfig Agent.
Jun 5 13:02:10 debug systemd[1]: google-guest-agent.service: start operation timed out. Terminating.
Jun 5 13:02:10 debug google_guest_agent[109084]: ERROR instance_setup.go:158 Failed to reach MDS(all retries exhausted): context canceled
Jun 5 13:02:10 debug systemd[1]: google-guest-agent.service: Main process exited, code=exited, status=1/FAILURE
Jun 5 13:02:10 debug systemd[1]: google-guest-agent.service: Failed with result 'timeout'.
Jun 5 13:02:10 debug systemd[1]: Failed to start Google Compute Engine Guest Agent.
Jun 5 13:02:10 debug systemd[1]: google-guest-agent.service: Service RestartSec=100ms expired, scheduling restart.
Jun 5 13:02:10 debug systemd[1]: google-guest-agent.service: Scheduled restart job, restart counter is at 758.
Jun 5 13:02:10 debug systemd[1]: Stopped Google Compute Engine Guest Agent.
Jun 5 13:02:10 debug systemd[1]: Starting Google Compute Engine Guest Agent...
Jun 5 13:02:10 debug google_guest_agent[109267]: GCE Agent Started (version 20240109.00)
resolv.conf
GNU nano 2.9.8 /etc/resolv.conf
search europe-west6-c.c.projectname.internal c.projectname.internal google.intern$
# Generated by NetworkManager
nameserver 8.8.8.8
nameserver 8.8.4.4
-
Hey there! if the instance isn't available even over SSH or a basic ping, that would indicate an issue with the machine that is deeper than the cPanel software, so I don't have much help I can provide for this one. If you'd like to submit a ticket we could examine the system to see if there is anything obvious we can see, but the ultimate fix is likely not going to be related to any cPanel tools.
0 -
I'd like to open a ticket but it says "Invalid Support Access ID". i get the id using
/usr/local/cpanel/cpanel -S
0 -
You can email cs@cpanel.net and that will get a ticket started with our team.
1 -
Looks like you've tried to configure the IP:
169.254.169.254
This IP is from a bogon prefix:
169.254.0.0/16 Link local Hence, it wouldn't resolve on your server.
0 -
The IP address
169.254.169.254
is a link-local address used by cloud environments, including Google Cloud Platform (GCP), Amazon Web Services (AWS), and others. This IP address is used to provide metadata to instances running in the cloud environment.That problem doesn't occur directly after installing the server. after installing, everything works fine. for testing purpose i created a new instance and didn't change anything except the hostname.
after 30-60 minutes port 22/2087 will timeout and not be available again. even after restarts, even after restoring from a previous snapshot.
i will have a call with gcloud support tomorrow, lets see :)
0
Please sign in to leave a comment.
Comments
5 comments