Topic: Playing with httpd.conf has rendered my web server unaccessible

[kevincallan]

I get Page Load Error--Failed to Connect when attempting to access my web server.

I was editing the httpd.conf file directly to test some configurations while trying to get MODx (www.modxcms.com) friendly URLs to work.  I worked on the actual file in spite of the banner at the top that states to not directly modify the file since it will be overwritten next time the templates are expanded.  That is actually what I want since I am experimenting.

After setting AllowOverride All on /home/e-smith/files/ibays/Primary/html directory and adding

Code: [Select]

LoadModule rewrite_module modules/mod_rewrite.so
I restarted httpd with

Code: [Select]

/etc/init.d/httpd-e-smith restart
That broke my server.  I rebooted thinking that the templates would expand over my errors and fix the problem, but no.

Any ideas?

[mercyh]

Code: [Select]

expand-template /etc/httpd/conf/httpd.conf

Code: [Select]

/etc/init.d/httpd-e-smith restart

Code: [Select]

signal-event post-upgrade

Code: [Select]

signal-event reboot
This might be overkill but i bet it would do it.

[kevincallan]

mercyh--

Thank you!  I suppose that the templates are not expanded on reboot?

I tried the web server after the first two commands and I am back in business.

Thanks,
K

[janet]

kevincallan

I suppose that the templates are not expanded on reboot?

Correct.
You need to manually expand the particular template and restart the appropriate service

Alternatively the command
signal-event post-upgrade
will expand ALL templates
and then follow with
reboot