CentOS 5 :: Service HTTPD Fails When Server Restarted
Apr 22, 2011
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 have the Samba server & users configured, I can access between Linux/Windows shares and both SMB & NMB services are set to be enabled at boot.Everything working.But when I restart the computer, I notice in services configuration that "This service is dead." for NMB. Therefore I have to enable it manually upon boot so that it works.I'm using Fedora 10, fresh installed and updated. I've noticed through search that others have had this issue as well throughout other versions of Fedora, yet I have not found a conclusive solution to this.
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 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?
Well, i can not install httpd service, when i execute yum -y install httpd i get this message
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=5&arch=i386&repo=os error was [Errno 4] IOError: <urlopen error (-3, 'Temporary failure in name resolution')> Error: Cannot retrieve repository metadata (repomd.xml) for repository: base. Please verify its path and try again
I have reviewed the HowTo wiki on Setting up an SSL secured Webserver with CentOS [URL], and have successfully set up my server.
We are using the conditional <IfDefine SSL> tags around the <VirtualHost _default_:443> section. I wanted to do this because we are deploying a standard <VirtualHost> section that is appended to the httpd.conf file for several Apache versions on several OS's, and this makes maintenance much easier. Sometimes the server will be configured with SSL support, and sometimes not, depending on certain functions of our application that the end user will require and determine. Our application then determines which mode the server should be run in depending on these functions, what OS is being run, what version of Apache is being run, etc, and starts the httpd server in the appropriate mode. For CentOS 5 with Apache 2.2, if the application indicates SSL is required (and we expect the server to be configured appropriately), then we do the following:
I have installed fedora 13 in my system. httpd server is also installed. when I tried to start the service of httpd, following error message displayed: Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
I neded to make some changes to the httpd.conf file. Afterwards I tried restarting,but it won't restart.It's saying port 80 is already in use. after checking via lsof -i :80 I get this result:
My mail server is getting problem since 3 days. It automatically get hang and httpd service get dead any time. How I can check what is effecting server, load, network traffic etc...
I am using CentOS 5.6 with Apache 2.2.17. The Apache was compiled from source using RPM build to comply with PCI requirements. Also Plesk 9.3 is used as a control panel, but other than the config files the Apache is pretty standard. When the httpd is started, there are no errors reported in /var/log/messages or in the error_log, and the httpd starts, shows up in ps and the pid file exists in /var/run/httpd.pid.
However when you check the status 'service httpd status' you get 'httpd dead but subsys locked'. You can add websites normally, and the proper config files are generated so I am pretty sure this isn't a control panel issue as I have other servers running the same control panel and Apache 2.2.16 compiled and installed the same way as the 2.2.17 and there are no problems.
Running CentOS 5 x64 And today my httpd is running very slow and I can't find a fix. Looked all over different forums
When starting httpd I get the message: /var/lock/subsys/httpd': No space left on device I checked that directory above and there is no file called httpd tried rebooting server
Can't do updates too: [root@u15438957 ~]# yum update Loaded plugins: fastestmirror, priorities rpmdb: unable to join the environment
1. Watchdog script 2. Daemontools - using "supervise" 3. Monit - open source monitoring tool
From what I can gather, daemontools is probably the best option. Unfortunately, the documentation on the developers site is very vague and I'm having a hard time getting this to work. I think I have it installed correctly, just don't know how to apply it to the service I want monitored.
how to get daemontools to work. All I want to do it monitor a server on my linux box. When it fails, I want it to be restarted automatically.
I turned my home PC running Ubuntu 10.04 into a server, and so i am so lost, after reading like a 10-20 different guides and/or official docs, I am totally lost.
All I wanted was to create a custom 404 error page...i read about how people edited .htaccess files to customize error pages, i tried and failed also, editing apache2.conf, I got lost and i dont wanna mess up everything and also, how you're supposed to not touch either of those as its not how it should be done and instead you need to edit httpd.conf and i did and FAILED! again...
Also how do I make it so that I can make subdomain(s) on my site? and wth is a name server and where do I get one?
I have setup a backup system on a NFS Server, and everything is working fine.Then, I decided to make changes to my backup script, and accidentally, I turned off both the NFS Server and Client without unmounting first.The NFS Server is working fine, but the client is having a problem. I cannot shutdown the nfs service. Here is what I get when I type "service nfs restart":
Shutting down NFS mountd: [ OK ] Shutting down NFS daemon: [ OK ] Shutting down NFS quotas: [ OK ]
[root@itsupport ~]# service httpd restart Stopping httpd: [FAILED] Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80 (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 logs [FAILED] Iam facing the above error when i restart the service httpd
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?
have a fresh install fedora 12 on dell latitude needs xfree for the dell moniter drive. Have installed to the point of autoconfig, get an error dbus service must be restarted. have no idea how to do such. it is a init 1 install. if i reboot here the system gives a black screen and typable screen but goes no futher. what do i do?
i am running cent 5.1 and would like to upgrade httpd v.2.2.3 to the latest 2.2.11 version provided by apache to resolve some ajp errors i am experiencing.
I searched but did not find any rpms for cent nor did i find any instructions on how to do this.
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.
installed a new centOS 5 server, and after the installation, everything seem to work well but for httpd not running. when i try to issue the restart command i get the following error:
[root@appdev ~]# service httpd restart Stopping httpd: [FAILED] Starting httpd: httpd: Syntax error on line 206 of /etc/httpd/conf/httpd.conf: Cannot load
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 have opened up the Service Configuration window that shows all the services and their status. My httpd says that it is enabled, but also that "this service is dead" and there is a orangish triangle. I can run phpMyAdmin on my server, but I can't run it from any other PC on my network.
I have task to do configure a two httpd service in a same linux machine using iptables.
For example: Run primary httpd instance on 80 and 443 port if primary instance is down switch to second instance running on 8080 and 4443 this can be achieved using iptables.