I have 3-node cluster, On first node i have installed my service in kerberos enabled mode.
For load-balancer, on second node i have installed httpd 2.2.15 version, apr 1.5.2 and apr-util 1.5.4 and "./configure" , make, make install command was executed successfuly.
To enabled kerberos, i have install mod_auth_kerb.so module and also added in httpd.conf, and im restarting the apache service using "./apachectl restart" it give me an error
httpd: Syntax error on line 80 of /usr/local/apache2/conf/httpd.conf:
Cannot load /usr/lib64/httpd/modules/mod_auth_kerb.so into server:
/usr/lib64/httpd/modules/mod_auth_kerb.so: undefined symbol:
ap_log_error
Related
I have a Apache2 installed with Homebrew on a Mac running OSX Monterey. I haven't done LAMP development for a while, so I'm not sure when the error started, but I've recently updated OSX to 12.5. When I returned to working on a LAMP project, my Apache installation stopped working. Running brew services produced the following output: Name Status User File httpd error 256 root ~/Library/LaunchAgents/homebrew.mxcl.httpd.plist mysql started Nizz0k ~/Library/LaunchAgents/homebrew.mxcl.mysql.plist.
Running the stop, start, and restart commands produces "success" output in the terminal, but Apache doesn't work. I can't navigate to my local vhosts, and of course, running brew services still shows an error.
In running apachectl -e error Apache complains about permissions to the error logs
I have tried:
uninstalling and reinstalling HTTPD
The apr-utilities fix.
confirming Mac installed Apache is stopped.
At this point, I think my problem is that there was conflicting information about how to run Apache on Homebrew. Earlier versions apparently required sudo, but running it this was now produces warnings like this:
Warning: Taking root:admin ownership of some httpd paths:
/usr/local/Cellar/httpd/2.4.54/bin
/usr/local/Cellar/httpd/2.4.54/bin/httpd
/usr/local/opt/httpd
/usr/local/opt/httpd/bin
/usr/local/var/homebrew/linked/httpd
This will require manual removal of these paths using `sudo rm` on
brew upgrade/reinstall/uninstall.
Warning: httpd must be run as non-root to start at user login!
/Library/LaunchDaemons/homebrew.mxcl.httpd.plist: service already bootstrapped
Bootstrap failed: 37: Operation already in progress
Error: Failure while executing; `/bin/launchctl bootstrap system /Library/LaunchDaemons/homebrew.mxcl.httpd.plist` exited with 37.
The issue is even after removing the paths as suggested in the error, a reinstallation brings Root back as the owner.
I do have the same problem with nginx.
Manually unloaded it and then restarting it worked fine.
Try:
sudo launchctl bootout system /Library/LaunchDaemons/homebrew.mxcl.httpd.plist
sudo brew services start httpd
I have installed php7.2, apache and mysql.
When I copied codeigniter folder in my var/www/html it runs but give one error as
A PHP Error was encountered
Severity: Core Warning
Message: PHP Startup: Unable to load dynamic library 'php_mysqli'
(tried: /usr/lib/php/20170718/php_mysqli
(/usr/lib/php/20170718/php_mysqli: cannot open shared object file: No
such file or directory), /usr/lib/php/20170718/php_mysqli.so
(/usr/lib/php/20170718/php_mysqli.so: cannot open shared object file:
No such file or directory))
Filename: Unknown
Line Number: 0
Backtrace:
I search for the same and tried with different solution as updating php.ini file but still getting the same error.
I am using Ubuntu 18.04.1 LTS OS
Your help would be appreciated.
Thanks.
Install php extension for mysql.
use this command
sudo apt-get install php-mysql
After installation restart apache with this command
sudo service apache2 restart
update
If sudo apt-get install php-mysql
not work for you then you should use
sudo apt-get install php7.2-mysql
You should open php.ini file and check if the line:
extension=mysqli.so
presented and not commented with # sign
I am trying to install Cobbler on a brand new Ubuntu 15.10 virtual box but it is not working. When I run the apt-get install cobbler cobbler-web it seems to break apache completely to the point I can't get it working again.
I see this in the apache error log:
[wsgi:crit] [pid 8112:tid 140273573488512] mod_wsgi (pid=8112): The mod_python module can not be used on conjunction with mod_wsgi 4.0+. Remove the mod_python module from the Apache configuration.
and this in the auth.log:
polkitd(authority=local): Unregistered Authentication Agent for unix-process:8081:54865 (system bus name :1.24, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
I have tried removing the mod_python and wsgi modules but apache still doesn't start up. And I think Cobbler uses them anyways, so I kind of need them.
I have also tried disabling polkitd. I don't find any clues when searching for that weird error message.
I was able to install Cobbler on Ubuntu 14.04 pretty easily and apache works fine.
Here is the basic chain of install commands I used:
apt-get update
apt-get install apache2
apt-get install isc-dhcp-server
apt-get install bind9 bind9utils bind9-doc
apt-get install cobbler cobbler-web debmirror mkisofs
Disable the module by typing sudo a2dismod python
You should then see this:
Module python disabled. To activate the new configuration, you need to
run: service apache2 restart
So type sudo service apache2 restart.
If that doesn't fix it, check the error log for more information by typing
cat /var/log/apache2/error.log.
I attempting to deploy a number of cookbooks to configure Apache2 and Passenger on Ubuntu 14.04. Below is the list of cookbooks I am installing in the order in which they appear in the run_list:
build-essential 2.1.3,
apt 2.6.1,
iptables 0.14.1,
logrotate 1.7.0,
apache2 2.0.0,
vim 1.1.2,
passenger_apache2 2.2.3
I am bootstrapping my vagrant vm from my development workstation and the cookbooks all appear to get installed with no errors, except when it gets to the passenger_apache2 cookbook. I can provide the entire extensive output, but I believe the following is the informative part of the output:
STDERR: [Wed Jan 21 14:05:17.027610 2015] [core:warn] [pid 26648] AH00111: Config variable ${APACHE_LOG_DIR} is not defined
node.vagrantup.com (2)No such file or directory: AH02297: Cannot access directory '/etc/apache2/${APACHE_LOG_DIR}/' for log file '${APACHE_LOG_DIR}/other_vhosts_access.log' defined at /etc/apache2/conf-enabled/other-vhosts-access-log.conf:2
node.vagrantup.com AH00014: Configuration check failed
I have seen only a couple of discussions indicating an issue with the $HOME environment variable not being set for the daemonized chef-client. However, I am unclear on how to remedy this situation. I would appreciate any insight the community can provide as I learn how to use Chef.
Thx
UPDATE: Viewing the passenger_apache2 cookbook README, apparently this cookbook is not yet supported on Ubuntu 14.04 due to the use of Apache 2.4 in that version of the OS. Further, I see I missed an error in the output which says:
WARNING: Apache doesn't seem to be compiled with the 'prefork', 'worker' or 'event' MPM
node.vagrantup.com Phusion Passenger has only been tested on Apache with the 'prefork', the
node.vagrantup.com 'worker' and the 'event' MPM. Your Apache installation is compiled with
node.vagrantup.com the '' MPM. We recommend you to abort this installer and to recompile
node.vagrantup.com Apache with either the 'prefork', the 'worker' or the 'event' MPM.
Curious to know if anyone is deploying passenger on Ubuntu 14.04 with Apache 2.4 using Chef Server. If so, how?
UPDATE 2: I can not get this working with the supposedly supported Ubuntu 12.04 either. Would really like to know if anybody has this cookbook working and if so, how.
I fixed this issue by taking the following actions:
Downloaded the latest Apache2 cookbook and uploaded it to my Chef server
Downloaded the latest Passenger_Apache2 cookbook.
Uploading the new Passenger_Apache2 cookbook failed with an error indicating that there was a dependency on Apache 1.0 that was unmet. I then modified the metadata.rb file of the Passenger_Apache2 cookbook and changed the following line:
depends 'apache2', '~> 1.0'
to:
depends 'apache2', '~> 3.0'
Now when I bootstrap my chef node, it installs passenger with no errors. Hope this helps others.
I have a VPS running Ubuntu 13.10 and Apache which I use to host Rails sites.
Yesterday I decided to do a release upgrade before applying a shellshock patch $do-release-upgrade. The upgrade failed with a broken pipe error (I should have made a note of the exact error but didn't — sorry). I logged back in and the Ubuntu version remains the same. I noticed that Apache didn't restart so tried to start it up myself $ sudo /etc/init.d/apache2 start but I'm getting an error:
* Starting web server apache2
apache2: Syntax error on line 16 of /etc/apache2/apache2.conf: Cannot load
/home/simon/.rvm/gems/ruby-1.9.3-p448/gems/passenger-4.0.19/buildout/apache2/mod_passenger.so
into server: /home/simon/.rvm/gems/ruby-1.9.3-p448/gems/passenger-4.0.19/buildout/apache2/mod_passenger.so:
undefined symbol: unixd_config
Action 'start' failed.
I've read that this type of error can happen when upgrading from Apache 2.2 - 2.4. I'm not 100% what version I was on before (or if it even upgraded yesterday — I'm assuming it did but feel free to tell me if I'm making stupid assumptions) but currently Server version: Apache/2.4.6 (Ubuntu) is installed.
Is there a way for me to re-install Apache 2.2? (Is this even likely to rectify my issue or is there a better solution that I should try out?)
The cause of your problem isn't Apache. It's Phusion Passenger. You installed Phusion Passenger against an older Apache version. Then you upgraded your OS, which upgraded Apache too, so that broke Phusion Passenger and now Apache refuses to start.
The solution: reinstall Phusion Passenger, so that it is recompiled against your current Apache version. Don't reinstall Apache; that doesn't help.