Re: [EMAIL PROTECTED] Apache 1.3 vs Apache 2
On 07/12/05, Michael Jeung <[EMAIL PROTECTED]> wrote: Good morning all,Recently, we've migrated one of our production servers from a Linuxbox to a FreeBSD box. We're running Apache 1.3.34, with a PHP/MySQLweb application. Listed below, you can find how apache has beencompiled.Yesterday afternoon, we put this new server into production and itseemed to be behaving relatively OK, with system-load of 4-5. We thought everything was going well and that this issue was wrappedup. Serves us right - today we got into the office and found thatloads on our server had spiked to 150.Before we pulled the server from production, we grabbed a few snapshots of what the system was doing. After taking a look atthese, I haven't been able to make much head-way. If someone withmore experience in this matter could take a look, I would greatlyappreciate it. Ultimately, my goal here is to get Apache to behave. Any solutionthat will allow Apache to run without killing the server isacceptable -- including upgrading to Apache 2. (Does Apache2outperform Apache 1.3?) Hi I recently recovered from a similiar problem and mysql was the culprit, it looked innocent sitting there using 0% cpu but when I ran mytop I seen dozens of threads just sitting there so it had somehow locked up causing a chain reaction to apache. Of course restarting apache and leaving mysql alone would recover the situation for a temporary period because it killed all these open connections to mysql unclogging it. What I did to resolve the problem was (a) disable keepalive on apache, which helped a great deal, (b) changed the threading on mysql I also stopped using WITH_PROC_SCOPE_PTH and disabled kern.threads.thr_scope_sys, I still have mysqld statically compiled tho. (c) I did change a few things in my.cnf like reduce thread caching and timeout values but I think (a) and (b) were what solved it, I am not 100% confident yet but I am close to 48 hours without a hitch and was having to restart apache numerous times a day. Chris
Re: [EMAIL PROTECTED] Apache 1.3 vs Apache 2
If your using the 4.4.1 version of php you might be having problems with the bug described here http://bugs.php.net/bug.php?id=35067 I had to step up to the 4.4.1 dev version where that bug is patched. The problem was creating a situation where httpd process consumption would spike out to 100% on one of my servers. I updated to the developer snapshot of php and everything went back to normal on that server. I hope this helps. Sincerely, Adam Ossenford - Original Message - From: "Joshua Slive" <[EMAIL PROTECTED]> To: Sent: Wednesday, December 07, 2005 1:00 PM Subject: Re: [EMAIL PROTECTED] Apache 1.3 vs Apache 2 On 12/7/05, Michael Jeung <[EMAIL PROTECTED]> wrote: Yesterday afternoon, we put this new server into production and it seemed to be behaving relatively OK, with system-load of 4-5. We thought everything was going well and that this issue was wrapped up. Serves us right - today we got into the office and found that loads on our server had spiked to 150. Before we pulled the server from production, we grabbed a few snapshots of what the system was doing. After taking a look at these, I haven't been able to make much head-way. If someone with more experience in this matter could take a look, I would greatly appreciate it. You need to use tools like mod_status, your access_log, strace, and a debugger to see what those processes are actually doing. Given the amount of memory they are using, they clearly aren't serving static files, so this is likely something php or database related. Ultimately, my goal here is to get Apache to behave. Any solution that will allow Apache to run without killing the server is acceptable -- including upgrading to Apache 2. (Does Apache2 outperform Apache 1.3?) Apache 2 will outperform 1.3 in some cases because of sendfile support, among other things. But since your site looks very php/database dependent, it's unlikely changing the underlying web server will have any measurable effect. Joshua. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [EMAIL PROTECTED] Apache 1.3 vs Apache 2
On 12/7/05, Michael Jeung <[EMAIL PROTECTED]> wrote: > Yesterday afternoon, we put this new server into production and it > seemed to be behaving relatively OK, with system-load of 4-5. We > thought everything was going well and that this issue was wrapped > up. Serves us right - today we got into the office and found that > loads on our server had spiked to 150. > > Before we pulled the server from production, we grabbed a few > snapshots of what the system was doing. After taking a look at > these, I haven't been able to make much head-way. If someone with > more experience in this matter could take a look, I would greatly > appreciate it. You need to use tools like mod_status, your access_log, strace, and a debugger to see what those processes are actually doing. Given the amount of memory they are using, they clearly aren't serving static files, so this is likely something php or database related. > > Ultimately, my goal here is to get Apache to behave. Any solution > that will allow Apache to run without killing the server is > acceptable -- including upgrading to Apache 2. (Does Apache2 > outperform Apache 1.3?) Apache 2 will outperform 1.3 in some cases because of sendfile support, among other things. But since your site looks very php/database dependent, it's unlikely changing the underlying web server will have any measurable effect. Joshua. - The official User-To-User support forum of the Apache HTTP Server Project. See http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: [EMAIL PROTECTED] " from the digest: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[EMAIL PROTECTED] Apache 1.3 vs Apache 2
Good morning all, Recently, we've migrated one of our production servers from a Linux box to a FreeBSD box. We're running Apache 1.3.34, with a PHP/MySQL web application. Listed below, you can find how apache has been compiled. Yesterday afternoon, we put this new server into production and it seemed to be behaving relatively OK, with system-load of 4-5. We thought everything was going well and that this issue was wrapped up. Serves us right - today we got into the office and found that loads on our server had spiked to 150. Before we pulled the server from production, we grabbed a few snapshots of what the system was doing. After taking a look at these, I haven't been able to make much head-way. If someone with more experience in this matter could take a look, I would greatly appreciate it. Ultimately, my goal here is to get Apache to behave. Any solution that will allow Apache to run without killing the server is acceptable -- including upgrading to Apache 2. (Does Apache2 outperform Apache 1.3?) server# httpd -V Server version: Apache/1.3.34 (Unix) Server built: Nov 28 2005 12:49:01 Server's Module Magic Number: 19990320:18 Server compiled with -D EAPI -D EAPI_MM -D EAPI_MM_CORE_PATH="/var/run/httpd.mm" -D HAVE_MMAP -D USE_MMAP_SCOREBOARD -D USE_MMAP_FILES -D HAVE_FLOCK_SERIALIZED_ACCEPT -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D DYNAMIC_MODULE_LIMIT=64 -D HARD_SERVER_LIMIT=512 -D SO_ACCEPTFILTER -D ACCEPT_FILTER_NAME="httpready" -D HTTPD_ROOT="/usr/local" -D SUEXEC_BIN="/usr/local/sbin/suexec" -D DEFAULT_PIDLOG="/var/run/httpd.pid" -D DEFAULT_SCOREBOARD="/var/run/httpd.scoreboard" -D DEFAULT_LOCKFILE="/var/run/httpd.lock" -D DEFAULT_ERRORLOG="/var/log/httpd-error.log" -D TYPES_CONFIG_FILE="etc/apache/mime.types" -D SERVER_CONFIG_FILE="etc/apache/httpd.conf" -D ACCESS_CONFIG_FILE="etc/apache/access.conf" -D RESOURCE_CONFIG_FILE="etc/apache/srm.conf" This is vmstat during the problem -- note that CPU is 0% idle. server# vmstat 1 procs memory pagedisks faults cpu r b w avmfre flt re pi po fr sr da0 md0 in sy cs us sy id 56 115 0 4105968 293024 10839 6 0 0 10462 13 0 0 660 5051 423 9 9 82 43 120 0 2559320 288348 75582 14 0 0 70335 0 0 0 1874 23305 1700 74 25 0 39 126 0 3174044 281440 65374 66 0 0 60878 0 64 0 1712 23361 1646 69 31 0 24 127 0 3171440 280976 24325 229 0 0 19744 0 1 0 2202 47064 2373 74 26 0 25 128 0 3164152 288296 41649 74 0 0 39391 0 1 0 1573 34180 1600 64 36 0 21 132 0 2649152 294112 66247 272 0 0 63361 0 1 0 1595 22986 1938 64 36 0 21 129 0 1634504 282236 31834 668 0 0 28466 0 91 0 1588 58544 2087 70 30 0 23 131 0 2243500 281344 56292 21 0 0 53558 0 1 0 1356 34243 1669 58 42 0 19 133 0 2235948 285932 37381 12 0 0 36987 0 2 0 1547 30101 1784 72 28 0 32 134 0 798396 295432 34687 4 0 0 36695 0 0 0 1079 2982 246 6 94 0 31 135 0 1312772 294476 202898 0 0 0 196045 0 12 0 1357 16086 1242 21 79 0 16 138 0 1325712 285204 90288 16 0 0 85205 0 8 0 1257 19917 1297 50 50 0 16 138 0 3459864 290800 48865 10 0 0 48583 0 2 0 1365 26674 1655 62 38 0 22 135 0 1415696 282132 62415 5 0 0 57784 0 1 0 1123 36272 1230 57 43 0 22 137 0 1390288 295284 90665 8 0 0 88675 0 2 0 1800 32413 2110 50 50 0 23 135 0 3550672 289536 29287 11 0 0 21393 0 0 0 1694 21543 1810 76 24 0 Our first top output: last pid: 62787; load averages: 56.24, 105.03, 121.49 up 0+21:28:37 08:42:36 388 processes: 58 running, 314 sleeping, 16 zombie CPU states: 19.3% user, 0.0% nice, 80.4% system, 0.4% interrupt, 0.0% idle Mem: 1803M Active, 1349M Inact, 343M Wired, 124M Cache, 199M Buf, 278M Free Swap: 8000M Total, 8000M Free PID USERNAME PRI NICE SIZERES STATE C TIME WCPUCPU COMMAND 36765 httpd 63 0 507M68K RUN0 0:39 10.69% 10.69% httpd 43430 httpd 60 0 505M56K RUN0 0:40 3.27% 3.27% httpd 60922 httpd 51 0 506M 122M RUN0 0:02 2.69% 2.69% httpd 38828 httpd 51 0 507M 7152K RUN1 0:32 2.34% 2.34% httpd 51672 httpd 2 0 507M56K sbwait 0 0:19 2.10% 2.10% httpd 51040 httpd 2 0 506M88K sbwait 0 0:26 1.95% 1.95% httpd 43457 httpd 50 0 507M 15508K RUN1 0:33 1.56% 1.56% httpd 39021 httpd 2 0 505M 118M sbwait 0 0:44 1.27% 1.27% httpd 39007 httpd 46 0 507M 123M RUN0 0:49 0.93% 0.93% httpd 36636 httpd 2 0 516M 122M sbwait 0 0:42 0.93% 0.93% httpd 50650 httpd 2 0 504M56K sbwait 1 0:28 0.93% 0.93% httpd 43472 httpd 2 0 506M 122M sbwait 0 0:39 0.88% 0.88% httpd 50870 httpd 2 0 505M
