Article ID: 129742, created on Oct 29, 2016, last review on Oct 29, 2016

  • Applies to:
  • Operations Automation 5.5
  • Operations Automation 5.4

Symptoms

Apache cannot be started on Legacy Shared Hosting server:

# /etc/init.d/pemhttpd restart
httpd: Syntax error on line 156 of /usr/local/pem/etc/apache/httpd.conf_pem: Syntax error on line 60 of /usr/local/pem/etc/apache/httpd.conf_pem.common: Syntax error on line 12 of /usr/local/pem/etc/apache/httpd.conf_pem.vhosts: Could not open configuration file /usr/local/pem/vhosts/xxxxxx/webspace/conf/vhost.conf: No such file or director

Cause

vhost.conf file of some webspace was either removed or corrupted (or the whole webspace was lost/removed/corrupted).

Resolution

As a quick fix to bring apache up, check if there are any tasks affecting the mentioned webspace in OA. For example, there can be a task that generates Apache config files, it should have name like Generate configuration files for service with id 997. If there is such failed / cancelled task, do the following steps:

  1. create empty folder for this webspace:

    mkdir -p /usr/local/pem/vhosts/xxxxxx/webspace/conf
    
  2. Process the task in OA
  3. try to start apache, comment any strings related to the problem webspace in apache config file if it still fails

To fix the webspace itself, restore the content of webspace if there are any backups, uncomment lines commented at the step 3 above and try to restart apache again.

Search Words

Web site unavailable

pemhttpd

apache fails to start

legacy shared hosting

some vhost.conf files disappeared from pemlinweb81

ac82ce33439a9c1feec4ff4f2f638899 caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 5356b422f65bdad1c3e9edca5d74a1ae 2554725ed606193dd9bbce21365bed4e 5b048d9bddf8048a00aba7e0bdadef37

Email subscription for changes to this article
Save as PDF