• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Apache failure: unable to find IPv4 address

E

ElricM

Guest
I've been getting the following error periodically I presume when Apache tries to restart:

Code:
[alert] (EAI 2)Name or service not known: mod_unique_id: unable to find IPv4 address of "server836.alphared.com"

The result is Apache fails to startup and all my domains are down until I notice the problem (or someone emails me). Happened again after midnight, I didn't notice until 7am. I tried to compensate with a Webmin service monitor but that doesn't work.

Can anyone tell me why this problem occurs and what I can do about it?

System is RHEL3 (all errata/packages up to date) and Plesk 7.5.3
 
Back
Top