CentOS 6 (old, i'm working on it), ISPConfig 3.2.5 (3.2.6 causes issues) - running well for months/years. I needed to add a couple aliasdomains to an existing website. I did so using the following settings: domain = alias domain (myaliassite.com) parent = main domain (mymainsite.com) redirect type = R redirect path = https://mymainsite.com auto-subdomain = none seo redirect = no redirect no ssl = unchecked active = checkedI immediately started getting the following message via email whenever I made changes trying to get it to work (the above settings are the final settings that worked - rather touchy): dns.myserver.com - 19.11.2021-09:23 - WARNING - Apache did not restart after the configuration change for website mymainsite.com. Reverting the configuration. Saved non-working config as /etc/httpd/conf/sites-available/mymainsite.com.vhost.erra diff between the vhost config file and the vhost.err config file yield only the following added to the vhost.err file RewriteEngine on RewriteCond %{HTTP_HOST} ^myaliassite\.com$ [NC] RewriteCond %{REQUEST_URI} !^/\.well-known/acme-challenge/ RewriteRule ^/(.*)$ https://mymainsite.com [R] i tried restarting httpd manually, and get the following (different) complaint: Starting httpd: [Fri Nov 19 14:58:38 2021] [warn] NameVirtualHost *:443 has no VirtualHosts [Fri Nov 19 14:58:38 2021] [warn] NameVirtualHost *:80 has no VirtualHosts (98)Address already in use: make_sock: could not bind to address 0.0.0.0:80 no listening sockets available, shutting down Unable to open logsand yet, it's still serving web pages from mymainsite.com AND myaliassite.com, as well as other sites. and a status check on httpd says "httpd is stopped" i checked httpd.conf and ServerRoot is set to "/etc/httpd", and ErrorLog path is set to "logs/error_log", CustomLog is set to "logs/access_log combined", and when put together, both files exist. both are owned by root.root and have perms of 644 i don't know where .well-known is located, but I assume it's the SSL location, and the sites that are active are also working via HTTPS, so i'm assuming that's good too. any thoughts on what could have caused this to all muck up? thanks.
just realized i put this under the wrong forum - if someone could move it to ISPConfig, that would be appreciated.
Sounds like you have a httpd running that the init system has lost track of. Try a "stop" of httpd, then check via "ps aux" if there's still an httpd running, and kill it. Then try starting httpd again.
I honestly wouldn't have thought that was a probability, but it appears you're correct. repeated "stops" kept returning "OK", and "ps aux" still showed multiple httpd processes running. Not sure how we got there, but there's a server restart manually restarting httpd is clean now. now I guess the question is how did updating an aliasdomain create that situation? I've got some more to create, so I'll let you know if it occurs again. thank you!
