summaryrefslogtreecommitdiffstats
path: root/zarb-ml/mageia-dev/2013-March/023907.html
diff options
context:
space:
mode:
Diffstat (limited to 'zarb-ml/mageia-dev/2013-March/023907.html')
-rw-r--r--zarb-ml/mageia-dev/2013-March/023907.html175
1 files changed, 175 insertions, 0 deletions
diff --git a/zarb-ml/mageia-dev/2013-March/023907.html b/zarb-ml/mageia-dev/2013-March/023907.html
new file mode 100644
index 000000000..f744578d1
--- /dev/null
+++ b/zarb-ml/mageia-dev/2013-March/023907.html
@@ -0,0 +1,175 @@
+<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
+<HTML>
+ <HEAD>
+ <TITLE> [Mageia-dev] Apache doesn't always like restarting....
+ </TITLE>
+ <LINK REL="Index" HREF="index.html" >
+ <LINK REL="made" HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Apache%20doesn%27t%20always%20like%20restarting....&In-Reply-To=%3C51537CCD.2040801%40colin.guthr.ie%3E">
+ <META NAME="robots" CONTENT="index,nofollow">
+ <META http-equiv="Content-Type" content="text/html; charset=us-ascii">
+ <LINK REL="Previous" HREF="023898.html">
+ <LINK REL="Next" HREF="023912.html">
+ </HEAD>
+ <BODY BGCOLOR="#ffffff">
+ <H1>[Mageia-dev] Apache doesn't always like restarting....</H1>
+ <B>Colin Guthrie</B>
+ <A HREF="mailto:mageia-dev%40mageia.org?Subject=Re%3A%20%5BMageia-dev%5D%20Apache%20doesn%27t%20always%20like%20restarting....&In-Reply-To=%3C51537CCD.2040801%40colin.guthr.ie%3E"
+ TITLE="[Mageia-dev] Apache doesn't always like restarting....">mageia at colin.guthr.ie
+ </A><BR>
+ <I>Thu Mar 28 00:12:13 CET 2013</I>
+ <P><UL>
+ <LI>Previous message: <A HREF="023898.html">[Mageia-dev] Apache doesn't always like restarting....
+</A></li>
+ <LI>Next message: <A HREF="023912.html">[Mageia-dev] Apache doesn't always like restarting....
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#23907">[ date ]</a>
+ <a href="thread.html#23907">[ thread ]</a>
+ <a href="subject.html#23907">[ subject ]</a>
+ <a href="author.html#23907">[ author ]</a>
+ </LI>
+ </UL>
+ <HR>
+<!--beginarticle-->
+<PRE>'Twas brillig, and AL13N at 27/03/13 18:46 did gyre and gimble:
+&gt;<i> Op woensdag 27 maart 2013 15:44:48 schreef Guillaume Rousse:
+</I>&gt;&gt;<i> Le 27/03/2013 15:09, AL13N a &#233;crit :
+</I>&gt;&gt;&gt;<i> the other day i tried to get cores, but somehow unlimited meant 0 meant no
+</I>&gt;&gt;&gt;<i> core at all
+</I>&gt;&gt;<i>
+</I>&gt;&gt;<i> You need to set LimitCORE=infinity in unit file, according to
+</I>&gt;&gt;<i> systemd.exec man page. And you probably need the adequate sysctl setting
+</I>&gt;&gt;<i> (kernel.core_pattern) to ensure the core file get dumped into a
+</I>&gt;&gt;<i> predictible directory.
+</I>&gt;<i>
+</I>&gt;<i> actually, no, setting LimitCORE=infinity (also our default as shown with
+</I>&gt;<i> systemctl show *.service) ends up with the actual limit being 0 as shown by
+</I>&gt;<i> prlimit. (this was with help from #systemd people)
+</I>
+Can you point at a commit that fixes this then. I'm a little confused as
+I've used this setup to happily get segv's from apache (namely php) so
+I'm a little confused as to why it doesn't work for you :s
+
+Even running prlimit here, I don't see a problem:
+
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">colin at jimmy</A> scripts (master)]$ ps aux | grep httpd
+root 4576 0.0 0.2 413372 21936 ? Ss 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4577 0.0 0.3 426024 30288 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4579 0.0 0.1 413804 14408 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4581 0.0 0.1 414012 15680 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4582 0.0 0.1 413804 14312 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4583 0.0 0.1 413812 14380 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4584 0.0 0.4 434512 38160 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4585 0.0 0.4 434488 38140 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+apache 4586 0.0 0.1 413804 14344 ? S 19:41 0:00
+/usr/sbin/httpd -DFOREGROUND
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">colin at jimmy</A> scripts (master)]$ prlimit -c -p 4576
+prlimit: failed to get the CORE resource limit: Operation not permitted
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">colin at jimmy</A> scripts (master)]$ sudo prlimit -c -p 4576
+RESOURCE DESCRIPTION SOFT HARD UNITS
+CORE max core file size unlimited unlimited blocks
+[<A HREF="https://www.mageia.org/mailman/listinfo/mageia-dev">colin at jimmy</A> scripts (master)]$ sudo prlimit -c -p 4577
+RESOURCE DESCRIPTION SOFT HARD UNITS
+CORE max core file size unlimited unlimited blocks
+
+
+
+Are you absolutely sure it's not just apache resetting the value when
+you don't set CoreDumpDirectory in your httpd.conf?
+
+
+&gt;<i> moreover, the systemd is compiled without coredump functionality, and that
+</I>&gt;<i> seems to have an effect on this and disallows one to configure systemd-coredump
+</I>&gt;<i> (which isn't build nor packaged) for usage with integrated coredumps with the
+</I>&gt;<i> systemd-coredump-ctl executable, (which is packaged).
+</I>
+This was a deliberate decision at the time. There were not sufficient
+tools to extract coredumps from the journal logs and really the coredump
+support should be separate from the coredump capturing and logging to
+the journal anyway, so it shouldn't affect anything you're doing right
+now (e.g. it shouldn't affect how you setup apache)
+
+The fact that systemd-coredump-ctl is build is IMO a bug, and one that
+could very well be fixed upstream already (probably is) but I didn't
+want to keep the rm in the %install section of the spec lest it was
+accidentally left in there when we turn the feature on (when it's
+generally more useful - i.e. you can store cores in a directory outside
+of the journal etc etc.).
+
+&gt;<i> @colin, so please, fix these 2 issues (first one looks like a systemd issue;
+</I>&gt;<i> while the second one is a packaging issue)
+</I>
+Like I say I've not actually observed the first problem personally, and
+have actively gotten core files from apache and my prlimit settings seem
+to be different from yours so I'm not really sure what to solve.
+
+
+As for the core dump support, I would be happy enough re-enabling it
+again. I'm just not convinced that storing the dumps in the journal is a
+great idea. I mean if you get a constantly crashing service, your logs
+will fill up quickly and be rotated away quickly. I think the cores
+should be stored outside of the journal. I can't remember off hand if
+the patch that implemented this was finally committed or not - I'll have
+a look and check.
+
+Col
+
+
+
+--
+
+Colin Guthrie
+colin(at)mageia.org
+<A HREF="http://colin.guthr.ie/">http://colin.guthr.ie/</A>
+
+Day Job:
+ Tribalogic Limited <A HREF="http://www.tribalogic.net/">http://www.tribalogic.net/</A>
+Open Source:
+ Mageia Contributor <A HREF="http://www.mageia.org/">http://www.mageia.org/</A>
+ PulseAudio Hacker <A HREF="http://www.pulseaudio.org/">http://www.pulseaudio.org/</A>
+ Trac Hacker <A HREF="http://trac.edgewall.org/">http://trac.edgewall.org/</A>
+</PRE>
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+<!--endarticle-->
+ <HR>
+ <P><UL>
+ <!--threads-->
+ <LI>Previous message: <A HREF="023898.html">[Mageia-dev] Apache doesn't always like restarting....
+</A></li>
+ <LI>Next message: <A HREF="023912.html">[Mageia-dev] Apache doesn't always like restarting....
+</A></li>
+ <LI> <B>Messages sorted by:</B>
+ <a href="date.html#23907">[ date ]</a>
+ <a href="thread.html#23907">[ thread ]</a>
+ <a href="subject.html#23907">[ subject ]</a>
+ <a href="author.html#23907">[ author ]</a>
+ </LI>
+ </UL>
+
+<hr>
+<a href="https://www.mageia.org/mailman/listinfo/mageia-dev">More information about the Mageia-dev
+mailing list</a><br>
+</body></html>