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.
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?
We 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:
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 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?
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.
[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 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:/#
ive 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?
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?
My 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?
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)
Sometimes when I try to restart Apache 2.4 using the supplied ApacheMonitor.exe I get this error. Then, I have to "taskkill /f /im httpd.exe" or wait like 30 sec before trying to start Apache again.
I'm using PHP cURL with the Plesk API to dynamically create Subscriptions. The problem I'm having is that the Apache server tends to reset before the response is returned, ultimately interrupting the connection.
I found a Plesk setting to define the Apache restart interval. I set it to 120 seconds, which I thought solved the issue, but I'm still having unreliable connection issues.
The request to create/remove a subscription always completes, but it's the response that I'm struggling to have returned.
