I had installed mod_tile and apache2 and tile server worked without problem. after that i installed php5.5.3. it changed all file structures of apache2 conf. i think something has changed. "LoadModule tile_module"had been removed from the config file. I added it in new apache2.conf file. but now when i restart apache it shows this message:
apache2: Syntax error on line 141 of /etc/apache2/apache2.conf: Syntax error on line 1 of /etc/apache2/mods-enabled/mod_tile.conf: Cannot load /usr/lib/apache2/modules/mod_tile.so into server: /usr/lib/apache2/modules/mod_tile.so: undefined symbol: unixd_set_global_mutex_perms
Action 'configtest' failed.
and this is /etc/apache2/mods-enabled/mod_tile.conf
LoadModule tile_module /usr/lib/apache2/modules/mod_tile.so
Related
Trying to enable the mod_ssl module on Apache 2.4.25, I get the following error:
httpd: Syntax error on line 129 of /ld01/otsweb/build/apache/httpd24.conf: Cannot load modules/mod_ssl.so into server: \t0509-022 Cannot load module /usr/local/apache24/modules/mod_ssl.so.\n\t0509-150 Dependent module libssl.so could not be loaded.\n\t0509-022 Cannot load module libssl.so.\n\t0509-026 System error: A file or directory in the path name does not exist.\n\t0509-022 Cannot load module /usr/local/apache24/modules/mod_ssl.so.\n\t0509-150 Dependent module /usr/local/apache24/modules/mod_ssl.so could not be loaded.
Line 129 is the LoadModule ssl_module modules/mod_ssl.so line in the httpd.conf file.
I have the same configuration running correctly on another server. That server does not have a libssl.so file on it, yet Apache with SSL is running.
Apache was configured with: (OpenSSL version is 1.0.2k from openssl.org)
./configure --enable-mods-shared="proxy proxy_http" --enable-auth-digest --enable-ssl --with-ssl=/usr/local/ssl/bin
Has anyone seen this same error?
With the release of OpenSSL 1.0.2l we decided to reinstall Apache from scratch, and everything is working correctly. A clean install of both seems to have cleared out the problem.
In ubuntu server when I try to start apache it gives following error message.
apache2: Syntax error on line 210 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/mods-enabled/proxy_scgi.load: No such file or directory
Action 'configtest' failed.
The Apache error log may have more information.
...fail!
What is the reason for the error? And how can I get through this issue?
This issue can be fixed by enabling the proxy_scgi module. Following is the command to enable the module in linux.
sudo a2enmod proxy_scgi
Team,
I am trying to start httpd
$# service httpd start
Starting httpd: httpd: Syntax error on line 162 of /etc/httpd/conf/httpd.conf: Syntax error on line 2 of /etc/httpd/conf.d/proxy_ajp.conf: Cannot load /etc/httpd/modules/mod_proxy_ajp.so into server: /etc/httpd/modules/mod_proxy_ajp.so: undefined symbol: proxy_module
[FAILED]
Process got exiting as per above.
I am running this in RHEL 5.2 server.
I am new to httpd / apache .Please let me know how to debug this ?
Many Thanks,
-Rishal
First place to look, make sure the following exists in the httpd.conf file:
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
Remember the file mod_proxy.so must exist and contain the necessary permissions.
If it doesn't work, are you able to copy in the contents of your proxy_ajp.conf? It maybe useful to see line 162 (and surroundings) of your httpd.conf file too .
I am using Ubuntu 12.04 LTS, and Apache 2.4.
I've installed TLS by following the steps on this link: https://help.ubuntu.com/community/GnuTLS
When restarting Apache I get the following error:
apache2: Syntax error on line 212 of /etc/apache2/apache2.conf:
Syntax error on line 1 of /etc/apache2/mods-enabled/gnutls.load:
Cannot load /usr/lib/apache2/modules/mod_gnutls.so into server:
/usr/lib/apache2/modules/mod_gnutls.so: undefined symbol: unixd_config
If I remove the #gnutls.conf file from the /etc/apache2/mods-enabled directory Apache restarts.
What is causing the module not to load?
Your level of mod_gnutls isn't aware of Apache 2.4, one breaking change in 2.4 is the symbol unixd_config is replaced by ap_unixd_config. There will probably be a slew of similar issues.
The actual directory of the apache2.conf is /etc/apache/apache.conf. And there is sites-enabled directory. I changed the directory path of the sites-enabled directory to /var/www/sites-enabled. Further went on to change the directory pat of the sites-enabled in the apacche2.conf as ../../var/www/sites-enabled/
It throws the error
apache2: Syntax error on line 230 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/var/www/sites-enabled/: No such file or directory
Action 'configtest' failed.
Any ideas on how I could resolve this?
Put in the correct path now it throws this error
apache2: Syntax error on line 230 of /etc/apache2/apache2.conf: Could not open configuration file /var/www/sites-enabled/000-default: No such file or directory
Action 'configtest' failed.
Thanks
Jean
You might have built the dangling a while ago. You should remove the association by
d2dissite 000-default
Then add your website alias with
a2ensite yoursite.com
I met similar errors before. It occurred when I was installing new modules but configured it wrongly. My solution was to locate the error configuration and remove the configure file.
If the error was caused by modules related configuration, you can try:
/etc/init.d/apache2 -M
This generated error message for me
apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/mods-enabled/ example.load: No such file or directory
I checked that directory, and found there is an example.load file, I deleted it and restart the server, and the problem solved.
Generally, I think you should try:
locate which was the origin of the error.
systemctl status apach2.status
If it is originated by wrong module configurations, locate which configuration file was the origin of the error.
/etc/init.d/apache2 restart
In your case, it may be caused by your wrong configuration on the site, you can check the configuration and modify it correctly.
It was due to permission error
sudo apache2 restart