Domains no longer propagate after update

Answered

Leo

• December 06, 2024 17:49

Last night there was an update that has caused all the domain names to no longer propagate.

I got this email right before it stopped working.

The following list of files have FAILED the md5sum comparison test. This means that the file has been changed in some way. This could be a result of an OS update or application upgrade. If the change is unexpected it should be investigated:

/usr/bin/centrino-decode: FAILED
/usr/bin/cpupower: FAILED
/usr/bin/ea-php74: FAILED
/usr/bin/ea-php81: FAILED
/usr/bin/ea-php82: FAILED
/usr/bin/ea-php83: FAILED
/usr/bin/gpio-event-mon: FAILED
/usr/bin/gpio-hammer: FAILED
/usr/bin/iio_event_monitor: FAILED
/usr/bin/iio_generic_buffer: FAILED
/usr/bin/intel-speed-select: FAILED
/usr/bin/lsgpio: FAILED
/usr/bin/lsiio: FAILED
/usr/bin/page_owner_sort: FAILED
/usr/bin/powernow-k8-decode: FAILED
/usr/bin/python3: FAILED
/usr/bin/python3.6: FAILED
/usr/bin/python3.6m: FAILED
/usr/bin/slabinfo: FAILED
/usr/bin/tmon: FAILED
/usr/bin/turbostat: FAILED
/usr/bin/x86_energy_perf_policy: FAILED
/usr/sbin/intel_sdsi: FAILED
/usr/sbin/nginx: FAILED
/usr/sbin/nginx-debug: FAILED
/bin/centrino-decode: FAILED
/bin/cpupower: FAILED
/bin/ea-php74: FAILED
/bin/ea-php81: FAILED
/bin/ea-php82: FAILED
/bin/ea-php83: FAILED
/bin/gpio-event-mon: FAILED
/bin/gpio-hammer: FAILED
/bin/iio_event_monitor: FAILED
/bin/iio_generic_buffer: FAILED
/bin/intel-speed-select: FAILED
/bin/lsgpio: FAILED
/bin/lsiio: FAILED
/bin/page_owner_sort: FAILED
/bin/powernow-k8-decode: FAILED
/bin/python3: FAILED
/bin/python3.6: FAILED
/bin/python3.6m: FAILED
/bin/slabinfo: FAILED
/bin/tmon: FAILED
/bin/turbostat: FAILED
/bin/x86_energy_perf_policy: FAILED
/sbin/intel_sdsi: FAILED
/sbin/nginx: FAILED
/sbin/nginx-debug: FAILED
/usr/local/bin/ea-php74: FAILED
/usr/local/bin/ea-php81: FAILED
/usr/local/bin/ea-php82: FAILED
/usr/local/bin/ea-php83: FAILED

 

I have received these types of emails before but today the domains are all down.

I tried restarting the server, restarting litespeed server, turning off and on the firewall with no changes. What's odd is that access to cpanel and WHM still works. So it looks like something is just causing the requests to be blocked.

 

Can someone provide some guidance and how this can be solved.

I put in a support ticket a few hours ago with no response.

 

 

 

 

 

• 

  ffeingol

  • December 06, 2024 20:00

  Your post is a bit too generic for anyone to really be able to help:

  • Do your domains resolve back to the server (issues with DNS if this server acts a a DNS server)
  • If they resolve, can you access web sites (issues with the web server)
  • If they resolve, can clients access mail (issues with Exim or Dovecot)

  We'd need more details as to what is and is not working.

  0
• 

  Leo

  • December 07, 2024 01:10
  • Edited

  After submitting a ticket, this ended up being an issue with NGINX that was stopping all the domains from loading. Support was awesome and able to figure it out quickly and resolve it like magic. So happy about that.

  However... I was not able to get an answer on how this happened all of a sudden after so many years of running the server so smoothly. I guess it's just going to be a mystery on how this all occurred. My suspicion is still an update last night caused this.. but I guess I will never know...

  0

Please sign in to leave a comment.