Search Engine: Elastic

Article ID: 3401, created on Nov 30, 2007, last review on Apr 28, 2014

  • Applies to:
  • H-Sphere


Most probably this problem is caused by renaming apache configuration file e.g. web_192.168.0.1.conf to web_192.168.0.1.conf.bad by apache. Logical server configuration directory is placed at /hsphere/local/config/httpd/lservers. This happens automatically if apache find any misconfiguration in conf file and can't start. The /hsphere/local/config/httpd/sites/* configuration files can be renamed also.

f213b9fa8759d57bee5d547445806fe7 3ef1f5f998c0dc182718a7fe4376f875

Email subscription for changes to this article
Save as PDF