diff options
Diffstat (limited to 'zarb-ml/mageia-sysadm/2011-March/003021.html')
| -rw-r--r-- | zarb-ml/mageia-sysadm/2011-March/003021.html | 138 |
1 files changed, 138 insertions, 0 deletions
diff --git a/zarb-ml/mageia-sysadm/2011-March/003021.html b/zarb-ml/mageia-sysadm/2011-March/003021.html new file mode 100644 index 000000000..976030be0 --- /dev/null +++ b/zarb-ml/mageia-sysadm/2011-March/003021.html @@ -0,0 +1,138 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<HTML> + <HEAD> + <TITLE> [Mageia-sysadm] Alamut memory problem + </TITLE> + <LINK REL="Index" HREF="index.html" > + <LINK REL="made" HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Alamut%20memory%20problem&In-Reply-To=%3C45706ea2c5ef7e1943e7f9f4f8f0f58e%40www.ephaone.org%3E"> + <META NAME="robots" CONTENT="index,nofollow"> + <META http-equiv="Content-Type" content="text/html; charset=us-ascii"> + <LINK REL="Previous" HREF="003020.html"> + <LINK REL="Next" HREF="003027.html"> + </HEAD> + <BODY BGCOLOR="#ffffff"> + <H1>[Mageia-sysadm] Alamut memory problem</H1> + <B>Michael Scherer</B> + <A HREF="mailto:mageia-sysadm%40mageia.org?Subject=Re%3A%20%5BMageia-sysadm%5D%20Alamut%20memory%20problem&In-Reply-To=%3C45706ea2c5ef7e1943e7f9f4f8f0f58e%40www.ephaone.org%3E" + TITLE="[Mageia-sysadm] Alamut memory problem">misc at zarb.org + </A><BR> + <I>Sun Mar 6 12:57:28 CET 2011</I> + <P><UL> + <LI>Previous message: <A HREF="003020.html">[Mageia-sysadm] Forums : nfrance machine +</A></li> + <LI>Next message: <A HREF="003027.html">[Mageia-sysadm] Alamut memory problem +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3021">[ date ]</a> + <a href="thread.html#3021">[ thread ]</a> + <a href="subject.html#3021">[ subject ]</a> + <a href="author.html#3021">[ author ]</a> + </LI> + </UL> + <HR> +<!--beginarticle--> +<PRE> Hi, + + it seems that alamut memory usage is growing since a few days ( in + fact, we have seen it now that we monitor it thanks to xymon + installation, but it should be since a much longer time ). + + After some hours of debugging with dmorgan, I narrowed the problem down + to viewvc, after careful looking to logs and with the help of watch -d + & + ps .Each time we see a line IOError in error.log, that the sign + there is a memory leaked ( as we can see on graphs if we look carefully + ). I + suspect that the problem is on viewvc side, as explained on : + + <A HREF="http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4254&dsMessageId=2364399">http://viewvc.tigris.org/ds/viewMessage.do?dsForumId=4254&dsMessageId=2364399</A> + + Before, we did allowed wsgi web software to register custom signals + handler ( + <A HREF="http://svnweb.mageia.org/adm/puppet/modules/apache/templates/mod_wsgi.conf?r1=908&r2=1051">http://svnweb.mageia.org/adm/puppet/modules/apache/templates/mod_wsgi.conf?r1=908&r2=1051</A> + ), but this caused apache to not restart, and so it was disabled again( + <A HREF="http://svnweb.mageia.org/adm/puppet/modules/apache/templates/mod_wsgi.conf?r1=1051&r2=1195">http://svnweb.mageia.org/adm/puppet/modules/apache/templates/mod_wsgi.conf?r1=1051&r2=1195</A> + ). + + So basically, when we see this : + + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] Traceback + (most recent call last): + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] File + "/usr/share/viewvc/bin/wsgi/viewvc.wsgi", line 40, in application + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] + viewvc.main(server, cfg) + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] File + "/usr/share/viewvc/lib/viewvc.py", line 4415, in main + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] + view_error(server, cfg) + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] File + "/usr/share/viewvc/lib/viewvc.py", line 4403, in view_error + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] + debug.PrintException(server, exc_dict) + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] File + "/usr/share/viewvc/lib/debug.py", line 81, in PrintException + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] + server.write("<h3>An Exception Has Occurred</h3>\\n") + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] File + "/usr/share/viewvc/lib/sapi.py", line 252, in write + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] + self._wsgi_write(s) + [Tue Mar 01 07:31:43 2011] [error] [client 74.125.16.66] IOError: + client connection closed + + there is a problem. + + At first, I thought it was some users with crappy internet connexion, + but this example is googlebot. + + So far, we have a few options : + - going back on cgi would mask the errors, to the cost of speed + - asking to apache to recycle more often his childs would also mask the + error + - reallowing mod_wsgi to add a signal handler would likely do it too + - fixing the leak on viewvc side should IMHO better but maybe too + complex + + So I propose the following : + + - use python-flup to make viewvc run a external fastcgi process, so it + can register signal handler as he see fit, and do not interfer with + apache. This also bring consistancy ( since we use fastcgi for almost + everything, except bugzilla and django applications ), and would allow + a finer grained control ( as we can see each process taking memory and + plan ressources based on this ). + + WDYT ? + +-- + Michael Scherer + +</PRE> + + + + + + + +<!--endarticle--> + <HR> + <P><UL> + <!--threads--> + <LI>Previous message: <A HREF="003020.html">[Mageia-sysadm] Forums : nfrance machine +</A></li> + <LI>Next message: <A HREF="003027.html">[Mageia-sysadm] Alamut memory problem +</A></li> + <LI> <B>Messages sorted by:</B> + <a href="date.html#3021">[ date ]</a> + <a href="thread.html#3021">[ thread ]</a> + <a href="subject.html#3021">[ subject ]</a> + <a href="author.html#3021">[ author ]</a> + </LI> + </UL> + +<hr> +<a href="https://www.mageia.org/mailman/listinfo/mageia-sysadm">More information about the Mageia-sysadm +mailing list</a><br> +</body></html> |