1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
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:
><i> Op woensdag 27 maart 2013 15:44:48 schreef Guillaume Rousse:
</I>>><i> Le 27/03/2013 15:09, AL13N a écrit :
</I>>>><i> the other day i tried to get cores, but somehow unlimited meant 0 meant no
</I>>>><i> core at all
</I>>><i>
</I>>><i> You need to set LimitCORE=infinity in unit file, according to
</I>>><i> systemd.exec man page. And you probably need the adequate sysctl setting
</I>>><i> (kernel.core_pattern) to ensure the core file get dumped into a
</I>>><i> predictible directory.
</I>><i>
</I>><i> actually, no, setting LimitCORE=infinity (also our default as shown with
</I>><i> systemctl show *.service) ends up with the actual limit being 0 as shown by
</I>><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?
><i> moreover, the systemd is compiled without coredump functionality, and that
</I>><i> seems to have an effect on this and disallows one to configure systemd-coredump
</I>><i> (which isn't build nor packaged) for usage with integrated coredumps with the
</I>><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.).
><i> @colin, so please, fix these 2 issues (first one looks like a systemd issue;
</I>><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>
|
