I am running CPanel and WHM, and every morning, I need to restart apache manually in order to work. Then it works for the whole day. It crashes I guess, but I don't know why. What logs do I need to check?
View 9 RepliesI am running a dedicated server.
My apache crashes daily and I am investigating the cause of it.
I have found this strange message in my apache error_log....
I tried to upgrade from apache 2.0.51 to 2.0.63 but it crashes as soon as new version is started and httpd is reloaded.
here is a part of the log
[Fri Apr 25 10:57:46 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations
Segmentation Fault in 3642, waiting for debugger
Segmentation Fault in 3697, waiting for debugger
Segmentation Fault in 3696, waiting for debugger
[Fri Apr 25 10:58:11 2008] [notice] caught SIGTERM, shutting down
[Fri Apr 25 10:58:22 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Apr 25 10:58:22 2008] [notice] mod_security/1.9.4 configured
[Fri Apr 25 10:58:22 2008] [notice] Digest: generating secret for digest authentication ...
[Fri Apr 25 10:58:22 2008] [notice] Digest: done
[Fri Apr 25 10:58:22 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Fri Apr 25 10:58:22 2008] [notice] LDAP: SSL support unavailable
[Fri Apr 25 10:58:23 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations
Segmentation Fault in 5422, waiting for debugger
Segmentation Fault in 5421, waiting for debugger
Segmentation Fault in 5452, waiting for debugger
Segmentation Fault in 5461, waiting for debugger
Segmentation Fault in 5451, waiting for debugger
Segmentation Fault in 5466, waiting for debugger
Segmentation Fault in 5465, waiting for debugger
Segmentation Fault in 7363, waiting for debugger
Segmentation Fault in 5435, waiting for debugger
Segmentation Fault in 5906, waiting for debugger
Segmentation Fault in 7251, waiting for debugger
Segmentation Fault in 6041, waiting for debugger
Segmentation Fault in 7723, waiting for debugger
Segmentation Fault in 7986, waiting for debugger
Segmentation Fault in 9659, waiting for debugger
Segmentation Fault in 9643, waiting for debugger
Segmentation Fault in 9361, waiting for debugger
Segmentation Fault in 9744, waiting for debugger
Segmentation Fault in 9543, waiting for debugger
Segmentation Fault in 9879, waiting for debugger
Segmentation Fault in 9794, waiting for debugger
Segmentation Fault in 9758, waiting for debugger
[Fri Apr 25 11:01:10 2008] [notice] caught SIGTERM, shutting down
[Fri Apr 25 11:01:12 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Apr 25 11:01:12 2008] [notice] mod_security/1.9.4 configured
[Fri Apr 25 11:01:12 2008] [notice] Digest: generating secret for digest authentication ...
[Fri Apr 25 11:01:12 2008] [notice] Digest: done
[Fri Apr 25 11:01:12 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Fri Apr 25 11:01:12 2008] [notice] LDAP: SSL support unavailable
[Fri Apr 25 11:01:13 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations
Segmentation Fault in 11634, waiting for debugger
Segmentation Fault in 11635, waiting for debugger
Segmentation Fault in 11661, waiting for debugger
Segmentation Fault in 11695, waiting for debugger
Segmentation Fault in 11760, waiting for debugger
Segmentation Fault in 11723, waiting for debugger
Segmentation Fault in 11694, waiting for debugger
Segmentation Fault in 11837, waiting for debugger
Segmentation Fault in 11812, waiting for debugger
Segmentation Fault in 12022, waiting for debugger
Segmentation Fault in 11848, waiting for debugger
Segmentation Fault in 11879, waiting for debugger
Segmentation Fault in 13342, waiting for debugger
Segmentation Fault in 12062, waiting for debugger
Segmentation Fault in 13428, waiting for debugger
Segmentation Fault in 13569, waiting for debugger
Segmentation Fault in 11849, waiting for debugger
Segmentation Fault in 13881, waiting for debugger
Segmentation Fault in 13380, waiting for debugger
[Fri Apr 25 11:02:27 2008] [notice] caught SIGTERM, shutting down
[Fri Apr 25 11:02:29 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Fri Apr 25 11:02:29 2008] [notice] mod_security/1.9.4 configured
[Fri Apr 25 11:02:29 2008] [notice] Digest: generating secret for digest authentication ...
[Fri Apr 25 11:02:29 2008] [notice] Digest: done
[Fri Apr 25 11:02:29 2008] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Fri Apr 25 11:02:29 2008] [notice] LDAP: SSL support unavailable
[Fri Apr 25 11:02:30 2008] [notice] Apache/2.0.63 (Unix) configured -- resuming normal operations
Segmentation Fault in 14123, waiting for debugger
Segmentation Fault in 14154, waiting for debugger
Segmentation Fault in 14156, waiting for debugger
Segmentation Fault in 14273, waiting for debugger
Segmentation Fault in 14114, waiting for debugger
Segmentation Fault in 14308, waiting for debugger
Segmentation Fault in 14316, waiting for debugger
Segmentation Fault in 14274, waiting for debugger
Segmentation Fault in 14315, waiting for debugger
Segmentation Fault in 15562, waiting for debugger
Segmentation Fault in 14113, waiting for debugger
Segmentation Fault in 15583, waiting for debugger
Segmentation Fault in 15615, waiting for debugger
Segmentation Fault in 15616, waiting for debugger
Segmentation Fault in 15584, waiting for debugger
Segmentation Fault in 15637, waiting for debugger
Segmentation Fault in 15631, waiting for debugger
Segmentation Fault in 15614, waiting for debugger
Segmentation Fault in 16332, waiting for debugger
Segmentation Fault in 14262, waiting for debugger
Segmentation Fault in 17504, waiting for debugger
Segmentation Fault in 15638, waiting for debugger
Segmentation Fault in 17515, waiting for debugger
Segmentation Fault in 18105, waiting for debugger
Segmentation Fault in 17516, waiting for debugger
Segmentation Fault in 18163, waiting for debugger
Segmentation Fault in 18175, waiting for debugger
Segmentation Fault in 18177, waiting for debugger
Segmentation Fault in 18178, waiting for debugger
Segmentation Fault in 18149, waiting for debugger
Segmentation Fault in 19931, waiting for debugger
Segmentation Fault in 20098, waiting for debugger
Segmentation Fault in 18176, waiting for debugger
I am on VPS and myself am quite a noob in this. Upgrade is performed by the support people.
If you guys can help please explain in lame terms
Let me know if you need some specific info about the system.
I was suggested that some modules might not be upgraded yet and they cause the crash, so to fix I should remove modules one by one from httpd config until get to the problematic one.
I've been trying to see whats going on with this server for a few days now but am unable to resolve the issue.
This is a 3 server setup. One is a mail server, another a mysql server and the host server. The apache on the host has plenty of ram (8 gigs) and it is currently under 5 gigs. The site is mainly a social networking site.
Now the apache would crash at times like 1:16, 2:17, 3:16, 4:18; basically in 1 hour intervals. Now it doesn't always crash every hour. Sometimes it might go up to 5 hours and may crash at say 8:50
Well it turns out that the mail server new mass mailing method has some sort of effect on the host server.
This is what happens.
1.) Host has a ton of apache processes up and running (site is fine and dandy).
2.) Mail server is about to launch its barrage email (load about .5)
3.) Then all of the apache processes stopped appearing on my top (nobody is able to browse the site at this point).
4.) after a few minutes the apache processes reappear and the site loads again.
5.) Mail server is now mass mailing and its loads reaches up to 4.
6.) WHM emails me that apache was down and it restarted the service.
Here is the interesting thing about this. First of all I found out that the apache processes were actually not gone. They were somehow suppressed. For example during this freeze moment, if I run a "ps aux" I see that all the apache process are running yet they are not using any cpu or ram (which is why I don't see them on top). Now if I were to do a "service httpd restart" during this moment, it will restart but will still be frozen until its set time.
When the site is accessible again, that is when the mail starts leaving from the mail server.
The owner thinks this is related, and I tend to agree.
The only problem is that I have no clue as to what is going on. Apache does not leave any error logs period. Nothing in messages or in exim logs. For a while I thought it might be lfd killing the apache but I was wrong. Nothing informative on the lfd logs either.
Could it be perhaps a bind issue? Somehow the mail server takes over the host system before its launch?
I'm posting this in the hope that some of the techies here and give me some hints and directions where I can find an answer. Perhaps someone who read this thread has seen this kind of issue before.
I'm using mod_perl 2.0.7 on Windows with Apache 2.2.23. I got Apache from Apachelounge, and compiled mod_perl and perl 5.16.2 myself using Visual Studio 2008. I'm using a 32-bit Windows Vista.
Pretty frequently my app (which works just fine on Linux) makes Apache crash. If I perform 500 requests with Apache Bench, I see this:
Benchmarking localhost (be patient)
Completed 100 requests
Completed 200 requests
Completed 300 requests
apr_socket_recv: An existing connection was forcibly closed by the
remote host. (730054)
Total of 338 requests completed
In the apache error log I see apache is restarting, but this results in some HTTP 500 errors that make the apache-bench results fail. When using a web browser, I also get these http 500 errors.
If I run the application using native CGI (i.e. I turn off mod_perl) I do not see crashes but of course it is *very* slow.
How can I find out what makes apache/mod_perl crash?
I asked the same on the modperl mailing lists, there they said I needed the symbol files for apache (*.pdb files). Where are these?
I encountered a strange problem when installing apache 2.2 or 2.4 as a service and set the service to be automaticly started.On restart of windows, apache service crashes with an access violation.
View 3 Replies View RelatedI've got a problem at a local customer with rotatelogs.exe and the current release of Apache HTTPD 2.4.12.
I've downloaded the 64-bit zip-file (VC11) and installed the VC11 vcredist in both 32- and 64-bit version.
The project is to upgrade apache 2.2 to apache 2.4. I've adjusted the configuration and added rotatelogs for log rotation for error_log and access_log.
The configuration is 100% correct, I can copy the line to cmd.exe and it runs correctly.
Variables are set in global environment, APACHE_HOME is set with "/" instead of "" to get sure rotatelogs.exe is found.
I have 8 apache servers that is sharing one httpd.conf file... When changes made in the httpd.conf, you have you restart httpd... How can I restart all 8 servers at the same time instead of logging into each server and do it manually?
View 2 Replies View RelatedWe are unable to restart apache on our server, as a result no sites are accessible in the browser. Our host states we need to clear out the following files:
[root@server1 logs]# ls -lAh|grep -v ' 0 '
total 1.9G
-rw-r--r-- 1 root root 92M Jul 17 07:55 access_log
-rw-r----- 1 root root 463K Dec 9 2007 audit_log
-rw-r--r-- 1 root root 1.2G Jul 17 07:57 error_log
-rw-r--r-- 1 root root 6 Jul 17 07:42 httpd.pid
-rw-r--r-- 1 root root 92K Feb 18 2008 ssl_engine_log
-rw-r--r-- 1 root root 535M Jul 17 07:46 suexec_log
-rw-r--r-- 1 root root 10 Jul 17 03:21 suexec_log.offset
-rw------- 1 root nobody 5.6M Dec 10 2007 suphp_log
Is it ok to simply delete these files? If so, will they recreate
themselves?
I'm running Apache 2.0.52 on a CentOS 4.4 server.
Running two static sites and one CMS.
I have no trouble logging in through SSH
Also no problem accessing webmin on port 10000
I've tried to restart Apache httpd
And tried to reboot the server...
Nothing.
I recently did a Yum Update,
also removed ISPconfig - it's probably the latter thats the problem, although I haven't used it - at all - just playing around setting up PHPmyadmin, Squirrelmail and a couple of email accounts.
But the only error log output I get is that there are no virtual servers for 88.198.81.186:80 and 88.198.81.187:80 and Unable to open logs | unable to start piped log program
Since the update and removal of ISPconfig 4-5 days ago there hasn't been any issues. I haven't done anything. Yet I do think might be some of the old ISPconfig settings acting up.
I am trying to restart my apache since i made changes to my php.ini file.
I tried using this command /etc/init.d/httpd restart which didnt work for me..any ideas guys? Its a basic dedicated server from a hosting company..
Today I got the devastating and heart-stopping news that all administraters fear most: "I'm looking at your website, and something's terribly wrong!!!"
The person went on to say that each page was just "filled with code ro something." When I finally saw it myself I discovered that my raw PHP pages were being served to the end user with no compilation --all of my top secret code; a real nightmare.
I went to look at the error logs and found that for several restarts Apache had not been compiling PHP.
It usually looks like this:
Quote:
[Wed Apr 18 18:35:11 2007] [notice] bandwidth monitoring enabled (mapping file: /etc/virtualhosting/mappings/apache.domainmap)
[Wed Apr 18 18:35:11 2007] [notice] Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_gzip/1.3.19.1a mod_fastcgi/2.2.10 mod_jk/1.2.0 mod_perl/1.24_01 PHP/4.2.2 FrontPage/5.0.2 mod_ssl/2.8.12 OpenSSL/0.9.6b configured -- resuming normal operations
[Wed Apr 18 18:35:11 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Wed Apr 18 18:35:11 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Wed Apr 18 18:35:11 2007] [notice] FastCGI: process manager initialized (pid 16385)
But now it looked like this:
Quote:
[Sun Apr 22 04:02:18 2007] [notice] Apache/1.3.27 (Unix) (Red-Hat/Linux) mod_gzip/1.3.19.1a configured -- resuming normal operations
[Sun Apr 22 04:02:18 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sun Apr 22 04:02:18 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/a1b2c3d4e5f6g7h8i9/nonexistentfile.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/adxmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/adserver/adxmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/phpAdsNew/adxmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/phpadsnew/adxmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/phpads/adxmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/Ads/adxmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/ads/adxmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/xmlrpc/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/xmlsrv/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/blog/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/drupal/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/community/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/blogs/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/blogs/xmlsrv/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/blog/xmlsrv/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/blogtest/xmlsrv/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/b2/xmlsrv/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/b2evo/xmlsrv/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/wordpress/xmlrpc.php
[Sun Apr 22 21:21:57 2007] [error] [client 209.85.60.98] File does not exist: /var/www/html/phpgroupware/xmlrpc.php
[Mon Apr 23 04:02:21 2007] [notice] SIGUSR1 received. Doing graceful restart
WTH?
I could be WAAAY off base, but my first reaction was that I'd been hacked -- someone had found a way to disable PHP so they could find sensitive information in raw PHP pages. That could be totally wrong.
At any rate, even if I never learn why Apache sometimes will compile without PHP (and some other modules) without me telling it to do so, I'd like to be prepared for an embarassment like like this.
Is there any way, say, in the .htaccess file (or anywhere, anyway), I can tell Apache not to serve **ANY** pages unless the PHP module is present?
Code:
[Sat Jul 28 21:40:09 2007] [notice] Apache/2.0.52 (Red Hat) configured -- resuming normal operations
[Sat Jul 28 21:45:08 2007] [notice] caught SIGTERM, shutting down
[Sat Jul 28 21:45:18 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:18 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [notice] Digest: generating secret for digest authentication ...
[Sat Jul 28 21:45:19 2007] [notice] Digest: done
[Sat Jul 28 21:45:19 2007] [notice] LDAP: Built with OpenLDAP LDAP SDK
[Sat Jul 28 21:45:19 2007] [notice] LDAP: SSL support unavailable
[Sat Jul 28 21:45:19 2007] [notice] mod_python: Creating 4 session mutexes based on 256 max processes and 0 max threads.
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:45:19 2007] [notice] Apache/2.0.52 (Red Hat) configured -- resuming normal operations
[Sat Jul 28 21:50:08 2007] [notice] caught SIGTERM, shutting down
[Sat Jul 28 21:50:08 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec)
[Sat Jul 28 21:50:08 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Sat Jul 28 21:50:08 2007] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
........
Server runs FreeBSD 6.1 and WHM/CPanel. Everything was working as usual, no changes were being made to the server, and all of a sudden all the web sites went down. WHM and CPanel and SSH remained accessible.
Restarting Apache (HTTPD) through WHM gives an error: "httpd has failed, please contact the sysadmin."
Rebooting the server didn't help, httpd still won't restart.
Attempting to do it via SSH gives this error:
server# /etc/rc.d/init.d/httpd restart
/etc/rc.d/init.d/httpd restart: httpd not running, trying to start
Syntax error on line 210 of /usr/local/apache/conf/httpd.conf:
Cannot load /usr/local/apache/libexec/libphp4.so into server: /usr/local/lib/mysql/libmysqlclient.so.14: Undefined symbol "gethostbyname_r"
/etc/rc.d/init.d/httpd restart: httpd could not be started
# tail -f /usr/local/apache/logs/error_log
only shows some standard http errors for files not being found.
I am having an issue with apache. Want to know how people are running huge forums having 700 800 users online at a time.
I am currently running a single forum having peak users upto 250, making posts and downloading files from within forum. Its running on dual opteron with 2 gig ram and its database is hosted on another cross connected dual opteron + 2 gig ram server.
Although there are enough resources, no load is there but still apache just crahsed and restarts after 4 min interval. As it seems apache gets out of resources and crashes.
how to allow apache to use more ram and cpu so that it simply don't crash.
How to restart apache automatic every 12 hours ?
View 6 Replies View Relatedis there a way to automate apache restart when my server's load reached 5+ sever load?
View 8 Replies View RelatedI keep trying to restart Apache but it wont restart... I run a command line to restart it, but nothing happens. Here is what I have tried:
Quote:
-bash-3.1# chroot /home/fatehost.net/runtime_layeredpanel/
fatehost:/# /etc/
bash: /etc/: is a directory
fatehost:/# /etc/init.d
bash: /etc/init.d: is a directory
fatehost:/# /etc/init.d/httpd-users
Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload
fatehost:/# /etc/init.d/httpd-users start
Starting web server: Apache2(98)Address already in use: make_sock: could not bind to address 205.209.135.132:80
no listening sockets available, shutting down
Unable to open logs
fatehost:/# /etc/init.d/httpd-users restart
Forcing reload of web server: Apache2httpd (pid 5955) already running
.
fatehost:/# /etc/init.d/httpd-users force-reload
Forcing reload of web server: Apache2.
fatehost:/# /etc/init.d/httpd force-reload
Forcing reload of web server: Apache2.
fatehost:/# /etc/init.d/httpd-users restart
Forcing reload of web server: Apache2httpd (pid 13475) already running
.
fatehost:/#
fatehost:/# /etc/init.d/httpd-users start
Starting web server: Apache2(98)Address already in use: make_sock: could not bind to address 205.209.135.132:80
no listening sockets available, shutting down
Unable to open logs
fatehost:/# /etc/init.d/httpd-users stop
Stopping web server: Apache2.
fatehost:/#
fatehost:/# /etc/init.d/httpd-users start
Starting web server: Apache2(98)Address already in use: make_sock: could not bind to address 205.209.135.132:80
no listening sockets available, shutting down
Unable to open logs
fatehost:/#
fatehost:/# sudo /etc/init.d/httpd-users stop
bash: sudo: command not found
fatehost:/# su root /etc/init.d/httpd-users restart
Forcing reload of web server: Apache2httpd (pid 20391) already running
.
fatehost:/# /etc/init.d/httpd-users reboot
Usage: /etc/init.d/apache2 start|stop|restart|reload|force-reload
fatehost:/# reboot
WARNING: could not determine runlevel - doing soft reboot
(it's better to use shutdown instead of reboot from the command line)
shutdown: timeout opening/writing control channel /dev/initctl
init: timeout opening/writing control channel /dev/initctl
fatehost:/# WARNING: could not determine runlevel - doing soft reboot
bash: WARNING:: command not found
fatehost:/# (it's better to use shutdown instead of reboot from the command line)
> shutdown: timeout opening/writing control channel /dev/initctl
> init: timeout opening/writing control channel /dev/initctl
>
fatehost:/# /home/fatehost.net/runtime_layeredpanel
bash: /home/fatehost.net/runtime_layeredpanel: No such file or directory
fatehost:/#
Apache service auto restart many times ( every minute ).
View 10 Replies View Relatedi ask of cpanel.net that why : my apache any 1h going to down and i force run restart httpd
cpanel :
Howdy,
This is occurring because your server is consistently hitting the maximum
allowed concurrent connection limit, defined by MaxClients in httpd.conf:
[root@part7 ~]# grep MaxClient /usr/local/apache/logs/error_log | tail -5
[Mon Oct 22 13:07:46 2007] [error] server reached MaxClients setting, consider
raising the MaxClients setting
[Mon Oct 22 13:32:03 2007] [error] server reached MaxClients setting, consider
raising the MaxClients setting
[Mon Oct 22 14:03:29 2007] [error] server reached MaxClients setting, consider
raising the MaxClients setting
[Mon Oct 22 14:16:07 2007] [error] server reached MaxClients setting, consider
raising the MaxClients setting
[Mon Oct 22 16:48:36 2007] [error] server reached MaxClients setting, consider
raising the MaxClients setting
[root@part7 ~]#
You will need to adjust this setting to a value which better accommodates your
server to prevent any further downtime.
write a cronjob so that apache will restart when the server reaches a load of 20.
View 13 Replies View Relatedive got a fairly beefy server but at the moment its hosting alot of resource intensive sites (unfortunatly i dont currently have a choice on where to run them all) and apache is crashing to the point its taking upto 2 mins to load pages within about 24hours but once restarted is fine again. so im wondering if anyone can suggest a way to automaticly restart apache via a cron job every 24hours or so?
View 6 Replies View RelatedThe latest versions of Apache for Windows sometimes refuse to do a "soft" restart with httpd -k restart.
View 4 Replies View RelatedI am experiencing this problem right now. None of my website is running. But httpd status says running. What's wrong?
[root@cent cron]# apachectl restart
[Mon Apr 13 20:10:11 2008] [warn] module php5_module is already loaded, skipping
[root@cent cron]# service httpd restart
Stopping httpd: [ OK ]
Starting httpd: [Mon Apr 13 20:10:55 2008] [warn] module php5_module is already loaded, skipping
[root@cent cron]# service httpd status
httpd (pid 24100 24099 24098 24097 24096 24094) is running...
I am having a problem on my VPS. I am running the latest version of Apache on Windows Server 2K3, and after editing httpd.conf to allow virtual hosts (#Include /conf/extra/httpd-vhosts.conf) and trying to restart the service, an error appears saying the operation failed.
I have even tried restarting/starting the service via services.msc
If I am not using the default httpd.conf Apache will not restart at all... it is very strange. I have also tried doing a repair of the installation of Apache.
Sometimes my apache gets hanged due to memory leak or persistence connection, then needs to be restarted manually, how can I make this process automatic, that is it get restarted whenever it got hanged or shutdown?
View 9 Replies View RelatedMy host is experiencing "issues" with my WordPress. It keeps going above their upper limit of open MySQL connections. So, while I am diagnosing it, I need to restart the server every few hours to avoid it going down.
How do I write a cron to restart Apache every 3 hours?
I have root ssh access to a server and we notice when doing a bash ./mysq-backup script to dump the data from the web site's databases into .sql and .tgz them that httpd goes down sometimes. That, and sometimes it seems that httpd goes down in other situations. All fine, we will figure out why. But ..
It would be nice to run a crontab to check every 15 minutes if httpd is running, if not, to restart it.
Right now I when I notice the site is down I log into the ssh as root and type: service httpd restart. If it is up it will then first stop it, and restart it. I can look at the screen and see it happen, so I feel pretty safe doing this. One of my concerns is that when I am not at the screen and it stays down .. I do not notice this and downtime increases. And we don't want to just crontab service httpd restart, so a bash script to check for the pid and restart if it down .. would be nice.
I thought this would work:
(chmod 755 httpdcheck)
Code:
delta:~ root# cat httpdcheck
#!/bin/bash
if [ ! "$(pidof httpd)" ]
then
echo "Could not find pid of httpd - restarting"
service httpd restart
else
echo "Found pid of httpd - NO need to restart"
fi
delta:~ root#
And I have this crontab entry:
Code:
delta:~ root# crontab -l
*/5 * * * * /root/httpdcheck | mail my@email
delta:~ root#
When testing, I did service httpd stop and waited 5 minutes and I received the email : could not find it, restarting. But when I go to the web site in browser it remains down. I have to login to ssh and do service httpd start manually to really load it.
Manually loading btw .. shows it works as bash script just fine, so I dont't know why it won't work when run from cron?
Code:
delta:~ root# ./httpdcheck
Could not find pid of httpd - restarting
Stopping httpd: [FAILED]
Starting httpd: [ OK ]
delta:~ root#
So .. when is it going wrong? Am I forgetting something?
I upgraded to php 5.2.3 and it broke my apache somehow.
Here is the error i get in WHM when tring to restart.
Code:
Waiting for httpd to restart.... . . . . . . . . . . finished.
httpd statusroot 14613 1.0 2.1 23736 22060 ? S 02:55 0:00 /usr/local/cpanel/whostmgr/bin/whostmgr ./reshttpd
root 14626 1.2 1.0 20896 10408 ? Ss 02:55 0:00 /usr/local/apache/bin/httpd -DSSL
httpd: [ != HTTP/1..] httpd has failed, please contact the sysadmin
Im running CentOS with apache 1.3 and trying to run Php5 with whm 11.2.0 and cpanel 11.6.0.
Ive tried everything from loading the least amount of modules to trying to go back to php 4.3 but nothing seems to work and i get the same error no matter which way i go.
My zend is the latest required for php5 too.
Here is a tail from my apache error log.
Code:
[Sat Aug 4 02:55:13 2007] [notice] FastCGI: process manager initialized (pid 14627)
[Sat Aug 4 02:55:13 2007] [notice] Apache/1.3.37 (Unix) PHP/5.2.3 mod_gzip/1.3.26.1a mod_fastcgi/2.4.2 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 F$
[Sat Aug 4 02:55:13 2007] [notice] suEXEC mechanism enabled (wrapper: /usr/local/apache/bin/suexec)
[Sat Aug 4 02:55:13 2007] [notice] Accept mutex: sysvsem (Default: sysvsem)
[Sat Aug 4 02:55:28 2007] [notice] child pid 14633 exit signal Segmentation fault (11)
[Sat Aug 4 02:56:14 2007] [notice] child pid 14634 exit signal Segmentation fault (11)