• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.

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