Re: [users@httpd] Apache HTTP Server and Weblogic Plug-in for Apache
Hi all, thanks for your attention and pacience. My Apache nversion can be seen below (sorry for forgeting to say): [apache@vm-apache conf]$ apachectl -v Server version: Apache/2.2.15 (Unix) Server built: Feb 13 2012 18:23:03 I had some progress... i disabled the firewall (SELinux) on the Apache server. Before, i had just disabled the firewall from the Weblogic Server. Now, when i access the apache server, it redirects (sometimes, actually) the request to my Weblogic Cluster. Let's say that 50% of the time it works and the other 50% i get the error informed previously. I am using the *apache* user and the ulimit of this user is: [apache@vm-apache conf]$ ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unlimited scheduling priority (-e) 0 file size (blocks, -f) unlimited pending signals (-i) 15915 max locked memory (kbytes, -l) 64 max memory size (kbytes, -m) unlimited open files (-n) 1024 pipe size(512 bytes, -p) 8 POSIX message queues (bytes, -q) 819200 real-time priority (-r) 0 stack size (kbytes, -s) 8192 cpu time (seconds, -t) unlimited max user processes (-u) 1024 virtual memory (kbytes, -v) unlimited file locks (-x) unlimited From the Apache server (192.168.0.149), when i execute the "culr" command, i get the following message: [apache@vm-apache conf]$ curl http://192.168.0.123:7006/benefits 302 Moved Temporarily This document you requested has moved temporarily. It's now at http://192.168.0.123:7006/benefits/";> http://192.168.0.123:7006/benefits/. The message above represents a OK situation or a problematic one? Below you can see the last few lines of my Error Log and Access Log: * ### error log ###* [Thu Dec 18 20:54:16 2014] [error] [client 192.168.0.123] <340514189468553> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID [Thu Dec 18 20:54:16 2014] [error] [client 192.168.0.123] <340314189468563> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID [Thu Dec 18 20:54:17 2014] [error] [client 192.168.0.123] File does not exist: /var/www/html/favicon.ico [Thu Dec 18 20:54:17 2014] [error] [client 192.168.0.123] File does not exist: /var/www/html/favicon.ico [Thu Dec 18 20:54:21 2014] [error] [client 192.168.0.123] <340114189468603> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID, referer: http://192.168.0.149:8080/benefits/ [Thu Dec 18 20:54:44 2014] [error] [client 192.168.0.149] <339814189468792> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID [Thu Dec 18 20:54:44 2014] [error] [client 192.168.0.149] <339814189468792> weblogic: initJVMID: parseClusterServerList failure [Thu Dec 18 20:54:45 2014] [error] [client 192.168.0.123] <339914189468844> weblogic: parseJVMID: could not resolve hostname '-1062731653'. Returning NULL from parseJVMID, referer: http://192.168.0.149:8080/benefits/servlet [Thu Dec 18 20:54:45 2014] [error] [client 192.168.0.123] <339914189468844> weblogic: initJVMID: parseClusterServerList failure, referer: http://192.168.0.149:8080/benefits/servlet [Thu Dec 18 20:54:56 2014] [error] [client 192.168.0.149] <339814189468792> weblogic: request [/benefits/welcome.html] did NOT process successfully.. [Thu Dec 18 20:54:57 2014] [error] [client 192.168.0.123] <339914189468844> weblogic: request [/benefits/welcome.html] did NOT process successfully.., referer: http://192.168.0.149:8080/benefits/servlet * ### access log ###* 192.168.0.123 - - [18/Dec/2014:20:54:15 -0300] "GET /benefits HTTP/1.1" 302 267 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5" 192.168.0.123 - - [18/Dec/2014:20:54:16 -0300] "GET /benefits/ HTTP/1.1" 200 5832 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5" 192.168.0.123 - - [18/Dec/2014:20:54:17 -0300] "GET /favicon.ico HTTP/1.1" 404 290 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5" 192.168.0.123 - - [18/Dec/2014:20:54:17 -0300] "GET /favicon.ico HTTP/1.1" 404 290 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5" 192.168.0.123 - - [18/Dec/2014:20:54:20 -0300] "POST /benefits/servlet HTTP/1.1" 200 492 "http://192.168.0.149:8080/benefits/"; "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5" 192.168.0.149 - - [18/Dec/2014:20:54:39 -0300] "GET /benefits/welcome.html HTTP/1.1" 503 250 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120605 Firefox/10.0.5" 192.168.0.123 - - [18/Dec/2014:20:54:44 -0300] "GET /benefits/welcome.html HTTP/1.1" 503 250 "http://192.168.0.149:8080/benefits/servlet"; "Mozilla/5.0 (X11; Linux
Re: [users@httpd] Apache 2.4 create a huge amount of shared memory segments
On Fri, Dec 19, 2014 at 12:06 AM, Yann Ylavic wrote: > If you can manage to recompile the APR library used by your Apache 2.4 > (you probably did that already since 2.4 does not seem to be the > version packaged with RHEL 6.4), you can use "./configure > --enable-posix-shm ..." to use another shared memory mechanism than > the default one (IPC SysV) which is limited to 32K segments (system > wide). > The number of segments would then be limited by the usual number of > file descriptors per process (ulimit -n). > > Unfortunately, there no equivalent to the Mutex directive for shared > memories, this can't be changed by httpd's configuration (as far as I > know). Oups, this leading part was not meant to be sent, and is rephrased anyway below according to message, more accurately. Please ignore it... > > On Thu, Dec 18, 2014 at 2:30 PM, Sylvain Goulmy wrote: >> >> I also noticed that a single proxy_balancer creates almost 350 shm on the >> system. >> >> Is it normal that a single proxy_balancer creates so many shm ? > > How many VirtualHost(s) do you use in your configuration? > Also, how do you declare the balancer(s), in each VirtualHost or in > the main section using BalancerInherit on? > >> >> Do i really have to increase the memory segment on my system in huge >> proportion to handle all my proxy_balancers ? > > The number of IPC SysV shared-memory segments is limited to 32768 on > linux (system wide), and you are already above with 100 * 350, so you > would need to use another SHM mechanism. > Unfortunately, there no equivalent to the Mutex directive for shared > memories, AFAIK this can't be changed by httpd's configuration. > So you would have to recompile the APR library used by your Apache 2.4 > (you probably did that already since RHEL 6.4 does not seem to package > 2.4 by default), and do for example "./configure --enable-posix-shm > ..." to use another shared-memory mechanism. > The number of segments would then be limited by the usual number of > file descriptors per process (ulimit -n). > > However 350 shm per balancer looks weird to me, your configuration may > do something not optimal... > > Regards, > Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
Re: [users@httpd] Apache 2.4 create a huge amount of shared memory segments
If you can manage to recompile the APR library used by your Apache 2.4 (you probably did that already since 2.4 does not seem to be the version packaged with RHEL 6.4), you can use "./configure --enable-posix-shm ..." to use another shared memory mechanism than the default one (IPC SysV) which is limited to 32K segments (system wide). The number of segments would then be limited by the usual number of file descriptors per process (ulimit -n). Unfortunately, there no equivalent to the Mutex directive for shared memories, this can't be changed by httpd's configuration (as far as I know). On Thu, Dec 18, 2014 at 2:30 PM, Sylvain Goulmy wrote: > > I also noticed that a single proxy_balancer creates almost 350 shm on the > system. > > Is it normal that a single proxy_balancer creates so many shm ? How many VirtualHost(s) do you use in your configuration? Also, how do you declare the balancer(s), in each VirtualHost or in the main section using BalancerInherit on? > > Do i really have to increase the memory segment on my system in huge > proportion to handle all my proxy_balancers ? The number of IPC SysV shared-memory segments is limited to 32768 on linux (system wide), and you are already above with 100 * 350, so you would need to use another SHM mechanism. Unfortunately, there no equivalent to the Mutex directive for shared memories, AFAIK this can't be changed by httpd's configuration. So you would have to recompile the APR library used by your Apache 2.4 (you probably did that already since RHEL 6.4 does not seem to package 2.4 by default), and do for example "./configure --enable-posix-shm ..." to use another shared-memory mechanism. The number of segments would then be limited by the usual number of file descriptors per process (ulimit -n). However 350 shm per balancer looks weird to me, your configuration may do something not optimal... Regards, Yann. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Learn more about how Apache writes log files to disk (and impact on i/o)
Hi, I'm trying to learn more about the technical details regarding how Apache writes to log files. Specifically, does Apache call an fsync() on log writes or perhaps just a close()? Just trying to figure out how much log writing contributes to disk i/o with Apache 2.2. I would appreciate any insight a developer might offer me on this issue. Thanks, Bryan - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
[users@httpd] Apache 2.4 create a huge amount of shared memory segments
I'm currently working on a migration from Apache 2.2 to 2.4 (2.4.10). I'm facing an issue with the usage of proxy_balancer with Apache 2.4. They now require the mod_slotmem_shm.so module to work correctly. I have added this module but i noticed that a single proxy_balancer now creates many memory shared segments on the OS. The problem is that my configuration declares many proxy_balancer (nearly 100), actually i soon as i declare more that 10 proxy balancers, i encountered this error : [proxy_balancer:emerg] [pid 1430:tid 140583699289856] (28)No space left on device: AH01185: worker slotmem_create failed After many investigation i finally identified that the shared memory segment is the ressource exceeded which raises that error. On my OS (RHEL 6.4), i have the following configuration : -- Shared Memory Limits max number of segments = 4096 max seg size (kbytes) = 67108864 max total shared memory (kbytes) = 17179869184 min seg size (bytes) = 1 I also noticed that a single proxy_balancer creates almost 350 shm on the system. Is it normal that a single proxy_balancer creates so many shm ? Do i really have to increase the memory segment on my system in huge proportion to handle all my proxy_balancers ? Am i missing something ? :) Thanks in advance.
