CentOS 5 Server :: Httpd Daemon Not Active On Startup - No Errors?
Oct 31, 2010
I've added httpd to runlevels 2-5 using chkconfig, and also double checked it using ntsysv, but it still won't run on startup, even though it works just fine when started manually (using "sudo service httpd start").The results of "chkconfig --list httpd" show it is on for levels 2-5, and I've confirmed the current runlevel to be 3. I've found no errors in the logs (neither Apache's nor the system's), but maybe I'm looking at them wrong...My machine is a VPS (on VMWare) running CentOS 5.5 32bit. For additional information, see the output of getinfo.sh: http://pastebin.centos.org/35570I would greatly appreciate help on this, as it is delaying our NGO from moving servers.
I used my boot disk in rescue mode to solve this, but I would really like to know how to do this the easy way.
Question: when I am booting up and getting all those "OK" green remarks, how do I cancel a daemon that freezes instead of giving me an ok or failed? I have tried <Ctrl><C> with no joy. I have tried dropping to interactive mode ("I") and bypassing the bad daemon, but interactive mode freezes when I go to start GDM, so no joy there either.
I have just configured CentOS server my new office. This is the first time I am using CentOS.
Whenever I am trying to change the webroot of the httpd server, it usually say "directory doesn't exist". whereas which can't be the case as it is home directory of the user.
To achieve this, what Do I need to do?
The second issue, I am facing that whenever I am adding new directories to public_html folder, it is not accessible. as the error page 404 is shown. I have changed the permissions to 0705 and ownership is also transferred to other user. What else is required to make new directories accessible by the web?
I'd like to share /usr/share/docs out to my local subnet via httpd so I can read server documentation from my workstation. I've simply done a generic install of httpd and httpd-manual and added this to the bottom of my httpd.conf file:
alias /docs /usr/share/doc <Directory /usr/share/doc> Order deny,allow
I just upgraded to CentOS 5.6 (been on 5.2 for ages....) and am getting the following error in the apache error_log file:[Sat Jul 02 13:50:25 2011] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)[Sat Jul 02 13:50:25 2011] [error] SSL Library Error: -8187 Security library: invalid argumentsThe notice entry, I can understand, however the SSL error is halting apache from starting. It has been suggested that this might be a package mismatch issue. I'll be more than happy sharing the package list for this box on request.
We had servers that worked fine for years. After updated them to the latest version of CentOS (5.2 with latest updates), they keeps on hanging when being scanned by PCI Verdors (a Credit Card security standard). Basically, the scan causes httpd process to eat up all memory, and the server becomes unresponsive. Normal operations resume after the scan stops for 5, 10 minutes. Output from top looks like the following:
I have a VPS server installed with centos 5.3. The server has directadmin. Probably that when directadmin was installed, the httpd server of choice was apache 2.2.13.
My problem is that i whant to install mod_dav_svn trough yum but without updating the latest version of apache form yum repository. If i exclude the httpd package when doing yum install mod_dav mod_dav_svn i get a dependency error witch say that i nedd httpd-mmn installed. So, my question is, how can i use yum to install mod_dav_svn without updating the httpd.
For the first time in installed and configured centos-ds from this HowTos and from the manuals.It is running nicely but disabled my httpd.Is it not possible to run directory service and httpd in the same machine
I installed centos 5.5 and httpd service was working well for the last 2 weeks till yesterday. I restarted server and noted my hosting service were not working. I have tried service httpd restart on the terminal and it dispalys [FAILED]. I updated my machine and and have tried restarting it but it doesn't work. I am new to centos and I dont know how to solve this.
I've got a box with a fresh installation of CentOS 5.6, but had several configs copied from an old 4.8 box that I've now got to finish. Most everything seems fine, but I can't get apache running. It reports that it starts up fine, but immediately stops and reports "httpd dead but subsys locked"Most of the advice I've found while searching suggests to just delete the http.pid file and restart, which doesn't help in my case. I did find a few problems where SELinux was restricting httpd from creating or touching certain files (I found reports in /var/log/messages) but I've worked through that.
So the big question here is: /var/log/messages and /var/log/httpd/error_log are now empty, and don't show any more errors when I restart httpd. Does anyone know where else I can look for reporting/logging on what's happening to httpd to cause it to die?
I set up rsyslog for the first time on my sole Linux server (Debian Lenny), and I am using one PC to test it over the next few days. I currently have the Windows syslog daemon disabled so only the client is active.Before I recommend using it to collect logs from our production servers, has anyone heard of or had any problems with Syslog for Windows (URL...) running on XP/2003/etc? From what I've read is that since it sends the data over the network using UDP instead of TCP or an NFS mount, there should be no potential for problems.
On my virtual server I had the same issue within the last three month. The postfix daemon stopped working suddenly and I don't know why. I can restart postfix normally and it's working normally for a couple of weeks until the next crash. Does anyone have the same problems with CentOS 5.6 and postfix?
I am running centos 5.4, kernel 2.6.18. Also running httpd (apache2) as a reverse proxy with the following modules mod_ssl mod_cache mod_proxy_*
Recently after updating these modules: mod_ssl x86_64 1:2.2.3-31.el5.centos.2 httpd x86_64 2.2.3-31.el5.centos.2 distcache x86_64 1.4.5-14.1
I am getting wierd errors in the error logs: [Wed Feb 10 15:44:18 2010] [error] (103)Software caused connection abort: cache: error returned while trying to return disk cached data [Wed Feb 10 15:44:45 2010] [error] (103)Software caused connection abort: cache: error returned while trying to return disk cached data [Wed Feb 10 15:44:48 2010] [error] (103)Software caused connection abort: cache: error returned while trying to return disk cached data .....
accidentally I do something wrong with my server and the httpd folder missing and I need it to setup my mail server and anyone can help me what can I do without reinstalling my Cent OS? Here is the error msg :
[root@mydomain etc]# service httpd stop Stopping httpd: [FAILED] [root@mydomain etc]# service httpd restart
I would prefer to use a linux server for authentication but I will need the same configuration features.I have been looking for a good guide to setting up CentOS as an alternative to Active Directory, but have not found one yet.The features I want to see.
1. works with Windows clients. 2. Network Home folders (does not neessisarly need to hold profile information) 3. Logon scripts for clients. 4. shared printers 5. shared folders. 6. can log linux boxes in with the same credentials and logon scripts.
okay so we have multiple servers running CentOS and multiple people who need access to these machines for various tasks. i would like to be able to use the credentials from Active Directory (running on server 2008) to give them access to these servers without having to go through each server and add these people into permission groups. basically a single sign-on for all of these servers depending upon what permissions were granted in Active Directory. how do i go about doing this?
Basicly just installed a fresh version of Cent OS 5.4 with apache httpd installed automaticly during the installation. The http daemon is running and when navigating to localhost i get the welcome cent os apache page thingy. The problem is when i put an index.html file in /var/http/www then try and navigation to localhost I get a 403 forbidden error.
I have just been told that httpd was not running on my Centos virtual server. It seems that my hosting company rebooted my server 2 days ago and that httpd restart failed due to:
Starting httpd: httpd: Syntax error on line 213 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
I had worked around and forgotten about this some time ago. The problem arose because the most recent httpd update installed proxy_ajp.conf into /etc/httpd/conf.d which was then loaded on restart The trouble is I do not use mod_proxy (I think just to try and get a lean and mean web server) and proxy_ajp.conf does not check if mod_proxy is loaded before it tries to LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
Hence httpd fails to restart. RedHats's bug tracker lists this as an old issue (which was never resolved) [URL] My workaround was to rename proxy_ajp.conf to proxy_ajp.conf.orig so that httpd would start up correctly. However any updates simply reinstall proxy_ajp.conf and so IMO the problem needs to be resolved at source. how to ensure that httpd updates do not bite me in the future? Do I really have to run mod_proxy whether or not I need it?
I was working to integrate Centos 5 and AD 2003 R2, this is my set up Windows side:
1. Install Identity Management for Unix, (Windows R2 already includes the Unix attribute not entirely necessary to install IMU, but it makes easier to configure the attributes from ADUC, when IMU is installed the Unix attributes TAB is shown in the user properties)
2. Configure the Unix attributes for every user account that will be authenticating from centos.
3. Create an user account to be used as a proxy for ldap, a regular user would be enough. Password never expires.
4. Create a computer account for every centos host; assign this computer account as pre-windows 2000 account.
5. Assign a value of 4128 to the user account control property for the computer account.