Apache Errors on new system

[MACscr]

Im seeing these errors on a newly provisioned CL7 cPanel 11.58 system with EA4. Why would these values be added to the system if they are going to cause warnings?

[email protected] [~]# httpd -V
[Tue Aug 02 05:38:48.529447 2016] [alias:warn] [pid 369025] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 690 will probably never match because it overlaps an earlier Alias.
[Tue Aug 02 05:38:48.529691 2016] [alias:warn] [pid 369025] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 691 will probably never match because it overlaps an earlier Alias.
[Tue Aug 02 05:38:48.529709 2016] [alias:warn] [pid 369025] AH00671: The ScriptAlias directive in /etc/apache2/conf/httpd.conf at line 695 will probably never match because it overlaps an earlier ScriptAlias.
[Tue Aug 02 05:38:48.529806 2016] [alias:warn] [pid 369025] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 702 will probably never match because it overlaps an earlier Alias.
Server version: Apache/2.4.23 (cPanel)
Server built:   Jul 21 2016 11:16:28
Server's Module Magic Number: 20120211:61
Server loaded:  APR 1.5.2, APR-UTIL 1.5.2
Compiled using: APR 1.5.2, APR-UTIL 1.5.2
Architecture:   64-bit
Server MPM:     prefork
  threaded:     no
    forked:     yes (variable process count)
Server compiled with....
-D APR_HAS_SENDFILE
-D APR_HAS_MMAP
-D APR_HAVE_IPV6 (IPv4-mapped addresses disabled)
-D APR_USE_SYSVSEM_SERIALIZE
-D APR_USE_PTHREAD_SERIALIZE
-D SINGLE_LISTEN_UNSERIALIZED_ACCEPT
-D APR_HAS_OTHER_CHILD
-D AP_HAVE_RELIABLE_PIPED_LOGS
-D DYNAMIC_MODULE_LIMIT=256
-D HTTPD_ROOT="/etc/apache2"
-D SUEXEC_BIN="/usr/sbin/suexec"
-D DEFAULT_PIDLOG="/var/run/apache2/httpd.pid"
-D DEFAULT_SCOREBOARD="logs/apache_runtime_status"
-D DEFAULT_ERRORLOG="logs/error_log"
-D AP_TYPES_CONFIG_FILE="conf/mime.types"
-D SERVER_CONFIG_FILE="conf/httpd.conf"

[email protected] [~]# tail -f -n 100 /etc/apache2/conf/httpd.conf
Alias /img-sys /usr/local/cpanel/img-sys/
Alias /sys_cpanel /usr/local/cpanel/sys_cpanel/
ScriptAliasMatch ^/?kpanel/?$ /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAliasMatch ^/?securecpanel/?$ /usr/local/cpanel/cgi-sys/sredirect.cgi
ScriptAliasMatch ^/?webmail(/.*|/?)$ /usr/local/cpanel/cgi-sys/wredirect.cgi
ScriptAlias /cgi-sys /usr/local/cpanel/cgi-sys/
ScriptAliasMatch ^/?securecontrolpanel/?$ /usr/local/cpanel/cgi-sys/sredirect.cgi
ScriptAliasMatch ^/?cpanel/?$ /usr/local/cpanel/cgi-sys/redirect.cgi
Include "/usr/local/apache/conf/includes/errordocument.conf"
ScriptAliasMatch ^/?securewhm/?$ /usr/local/cpanel/cgi-sys/swhmredirect.cgi
ScriptAliasMatch ^/Autodiscover/Autodiscover.xml /usr/local/cpanel/cgi-sys/autodiscover.cgi
ScriptAliasMatch ^/?whm/?$ /usr/local/cpanel/cgi-sys/whmredirect.cgi
Alias /java-sys /usr/local/cpanel/java-sys/
ScriptAliasMatch ^/?controlpanel/?$ /usr/local/cpanel/cgi-sys/redirect.cgi
ScriptAliasMatch ^/autodiscover/autodiscover.xml /usr/local/cpanel/cgi-sys/autodiscover.cgi

 

[cPanelMichael]

Hello,

Could you verify if you have made any custom changes to the Apache 2.4 template through the main.local file? It's located at:

/var/cpanel/templates/apache2_4/main.local

Also, note that EasyApache 4 with CloudLinux is still considered beta:

Beta: EasyApache 4 released for CloudLinux

Thank you.

 

[MACscr]

[email protected] [~]# cat /var/cpanel/templates/apache2_4/main.local
cat: /var/cpanel/templates/apache2_4/main.local: No such file or directory

I already had CL check things out and they told me it was an issue i needed to ask you about.

 

[cPanelMichael]

Could you open a support ticket using the link in my signature so we can take a closer look? You can post the ticket number here so we can update this thread with the outcome.

Thank you.

 

[jasperthedummy]

Hi there,

I have also encountered a similiar problem on my server, but unlike MACscr, I actually had EA4 successfully running on PHP-FPM for a week before an apparent automatic server update in the wee hours of the morning caused my entire website (except the homepage) to go down.

Suspecting that this is caused by Apache not properly following rewrite rules in my .htaccess, I reverted back to EA3.

I determined that an automatic server update had occurred because I received an email from my system with the following content:

---snip---

There is a new stable version available
Upgrading plugin...
CentOS 6 installation script
EasyApache 4 detected
cPanel version 11.60.0.17 installed
Internal ionCube loader version installed: 5.1.2
Permissions Fix Done
Upgrading script...
pyxsoft_antimalware registered
install.sh: line 198: httpd: command not found
Apache version:  (>= 2.4.0)
Portfix installed in httpd.ini
Pyxsoft Virtual Host installed
Restarting apache...
Stopping httpd: [  OK  ]
Starting httpd: [Mon Nov 14 02:04:15.585651 2016] [alias:warn] [pid 22436:tid 140412889790432] AH00671: The ScriptAlias directive in /etc/apache2/conf/httpd.conf at line 579 will probably never match because it overlaps an earlier ScriptAlias.
[Mon Nov 14 02:04:15.585742 2016] [alias:warn] [pid 22436:tid 140412889790432] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 585 will probably never match because it overlaps an earlier Alias.
[Mon Nov 14 02:04:15.585747 2016] [alias:warn] [pid 22436:tid 140412889790432] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 586 will probably never match because it overlaps an earlier Alias.
[Mon Nov 14 02:04:15.585757 2016] [alias:warn] [pid 22436:tid 140412889790432] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 589 will probably never match because it overlaps an earlier Alias.
[  OK  ]
Determining the Mod Security installed version...
Mod security version could not be detected.
It is normal, I will detect the version when you visit the plugin in WHM.
Downloading signatures (1/3)...
Downloading signatures (2/3)...
Downloading signatures (3/3)...
FTP Inspector already installed
HTTP Inspector enabled OK
<code>
Stopping httpd: [  OK  ]
Starting httpd: [Mon Nov 14 02:04:20.351910 2016] [alias:warn] [pid 22620:tid 139642090256352] AH00671: The ScriptAlias directive in /etc/apache2/conf/httpd.conf at line 579 will probably never match because it overlaps an earlier ScriptAlias.
[Mon Nov 14 02:04:20.351999 2016] [alias:warn] [pid 22620:tid 139642090256352] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 585 will probably never match because it overlaps an earlier Alias.
[Mon Nov 14 02:04:20.352005 2016] [alias:warn] [pid 22620:tid 139642090256352] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 586 will probably never match because it overlaps an earlier Alias.
[Mon Nov 14 02:04:20.352010 2016] [alias:warn] [pid 22620:tid 139642090256352] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 589 will probably never match because it overlaps an earlier Alias.
[  OK  ]
</code>

---snip---

I did not customise any of my Apache configuration except for what was available in the WHM interface.

Couldn't find out why an update would have caused this. Please help.

 

[cPanelMichael]

I have also encountered a similiar problem on my server, but unlike MACscr, I actually had EA4 successfully running on PHP-FPM for a week before an apparent automatic server update in the wee hours of the morning caused my entire website (except the homepage) to go down.

Hello,

PHP-FPM is officially supported in cPanel version 60:

60 Release Notes - Documentation - cPanel Documentation

Could you verify the method you used to enable PHP-FPM prior to cPanel version 60? The previously documented method of enabling PHP-FPM on EDGE build tiers prior to cPanel version 60 is unsupported, and it's recommended to revert any customization you made to ensure the official feature is working as intended.

Thank you.

 

[jasperthedummy]

Hello,

PHP-FPM is officially supported in cPanel version 60:

60 Release Notes - Documentation - cPanel Documentation

Could you verify the method you used to enable PHP-FPM prior to cPanel version 60? The previously documented method of enabling PHP-FPM on EDGE build tiers prior to cPanel version 60 is unsupported, and it's recommended to revert any customization you made to ensure the official feature is working as intended.

Thank you.

Hello,

I am using WHM 60.0 (Build 17). I only upgraded to EasyApache 4 after upgrading to WHM 60 via RELEASE.

Prior to the upgrade to EasyApache 4, I was running the default Apache configuration using SuPHP. No other manual customisations were done. The upgrade from EA3 SuPHP to EA4 PHP-FPM was rather smooth via the following command:

$ /scripts/migrate_ea3_to_ea4 --run

PHP-FPM was running fine for about a week via EA4 when suddenly an automatic PYXSoft definitions update (according to the email sent to me that I copied in the thread earlier) broke my configuration.

I did notice that the automatic upgrade script seems to have written to my httpd.conf file, but when I discovered that my website was inaccessible except for the home page, I did not check if the httpd.conf file was written to since I was rushing on getting the site up, which was by reverting back to EA3.

$ /scripts/migrate_ea3_to_ea4 --revert --run

However, my immediate suspicions was that the PYXSoft definitions update wrote to the Apache configuration, causing Apache rewrites to not work since other pages on my website other than the home page depended on rewrite rules in my .htaccess file. At that time when my website was inaccessible, I also verified that the .htaccess file was unmodified and is the same as the backup version I had.

 

[cPanelMichael]

Hello,

This suggests an issue with the PYXSoft plugin. You may want to disable that plugin and then try using EasyApache 4 again, as I was unable to find any information on the PYXSoft website that suggests support for EasyApache 4.

Thank you.

 

[rahnev]

I have similar warnings after upgrade to EA4 in CL6. I made a change on logformat directive in ea4_main.local file as described in this thread - Apache log format issue with EasyApache 4 (apache 2.4), Varnish and mod_remoteip. And now getting errors like these:

[alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line xxx will probably never match because it overlaps an earlier Alias.
[alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line xxx will probably never match because it overlaps an earlier Alias.
[alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line xxx will probably never match because it overlaps an earlier Alias.

If I run /scripts/rebuildhttpdconf warnings disappear but on the next day they appear again.

 

[cPanelMichael]

If I run /scripts/rebuildhttpdconf warnings disappear but on the next day they appear again.

Could you verify the specific custom entries added to the include files within the "/usr/local/apache/conf/includes" directory? Are you using any third-party plugins that interact with Apache?

Thank you.

 

[rahnev]

No, I'm not using 3rd partly plugins for Apache. I only changed the LogFormat as you described in Apache log format issue with EasyApache 4

If I remove the ea4_main.local file everything is OK and no warnings. Warning are for Alias and ScriptAlias directives, declared in both ea4_main.local and
ea4_main.default files.

 

[cPanelMichael]

Hello,

In the error output you provided, the line numbers are excluded. Could you let us know the full error message, including the specific line numbers?

Thank you.

 

[rahnev]

Here they are:

[Tue Nov 22 01:15:01.850010 2016] [alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 499 will probably never match because it overlaps an earlier Alias.
[Tue Nov 22 01:15:01.850175 2016] [alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 501 will probably never match because it overlaps an earlier Alias.
[Tue Nov 22 01:15:01.850193 2016] [alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 502 will probably never match because it overlaps an earlier Alias.
[Tue Nov 22 01:15:01.850207 2016] [alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 503 will probably never match because it overlaps an earlier Alias.
[Tue Nov 22 01:15:01.850224 2016] [alias:warn] [pid 692758] AH00671: The Alias directive in /etc/apache2/conf/httpd.conf at line 505 will probably never match because it overlaps an earlier Alias.
[Tue Nov 22 01:15:01.850243 2016] [alias:warn] [pid 692758] AH00671: The ScriptAlias directive in /etc/apache2/conf/httpd.conf at line 508 will probably never match because it overlaps an earlier ScriptAlias.
[Tue Nov 22 01:15:01.850270 2016] [alias:warn] [pid 692758] AH00671: The ScriptAlias directive in /etc/apache2/conf/httpd.conf at line 514 will probably never match because it overlaps an earlier ScriptAlias.

 

[rahnev]

Here is more info. Directives that matches these lines are:

Alias /java-sys /usr/local/cpanel/java-sys/
Alias /mailman/archives /usr/local/cpanel/3rdparty/mailman/archives/public/
Alias /sys_cpanel /usr/local/cpanel/sys_cpanel/
ScriptAlias /mailman /usr/local/cpanel/3rdparty/mailman/cgi-bin/
Alias /pipermail /usr/local/cpanel/3rdparty/mailman/archives/public/
ScriptAlias /cgi-sys /usr/local/cpanel/cgi-sys/
Alias /img-sys /usr/local/cpanel/img-sys/

 

[Recifier]

I'm seeing the same thing. If I delete httpd.conf and rebuild a new one, it goes away, but every time there is a cpanel update, those overlap errors reappear.

 

[webcast33]

I am also getting these Alias and ScriptAlias messages (written to the console only; not to error_log) when I restart Apache. These messages started after upgrading to EA4 and Apache 2.4. It appears that there is duplication in the specification of some Script and ScriptAlias directives between a "<IfModule alias_module>" conditional block right after httpd.conf sets the error_log and ".ht" permissions and a set of directives at the very end of httpd.conf (after virtual host definition). Can a cPanel engineer clarify whether these warning messages should be a concern?

I also noticed that the Directory directive for error_log is still using the Order and Deny statements instead of the 2.4 Require statement. Is this a bug?

Thank you.

 

[cPanelMichael]

Hello,

The output itself is just a warning and should not result in any issues. That said, could you open a support ticket using the link in my signature so we can take a closer look and see which particular duplicate entries are resulting in that output on the affected system?

@webcast33, I've separated your additional question into a new thread at:

New Thread - Apache 2.4 Order and Deny Statements

Thank you.