Hi, for long, in the script that starts certain program, I used this (as plain user): # Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program Suddenly, after an update applied yesterday, I get: /home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument Line 81 being: ulimit -H -c 0 What has changed re ulimit? -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E. R. wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
Line 81 being: ulimit -H -c 0
Fwiw, I see the same on 15.1, but updated 7 August. -- Per Jessen, Zürich (20.7°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2019 13.06, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
Line 81 being: ulimit -H -c 0
Fwiw, I see the same on 15.1, but updated 7 August.
Yes, I try to update the home server once a month, so I saw it yesterday. If I don't limit the size of coredumps, it can dump 8gigs or even more if the process swapped before crashing. Takes an awful lot of time in that puny machine. The "echo" line seems to be accepted. And anyway, the developer of that program doesn't want them... -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E.R. <robin.listas@gmx.es> [08-16-19 07:29]:
On 16/08/2019 13.06, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
Line 81 being: ulimit -H -c 0
Fwiw, I see the same on 15.1, but updated 7 August.
Yes, I try to update the home server once a month, so I saw it yesterday.
If I don't limit the size of coredumps, it can dump 8gigs or even more if the process swapped before crashing. Takes an awful lot of time in that puny machine. The "echo" line seems to be accepted.
And anyway, the developer of that program doesn't want them...
turn off the core dumps on *that* machine. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2019 13.36, Patrick Shanahan wrote:
* Carlos E.R. <robin.listas@gmx.es> [08-16-19 07:29]:
On 16/08/2019 13.06, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
Line 81 being: ulimit -H -c 0
Fwiw, I see the same on 15.1, but updated 7 August.
Yes, I try to update the home server once a month, so I saw it yesterday.
If I don't limit the size of coredumps, it can dump 8gigs or even more if the process swapped before crashing. Takes an awful lot of time in that puny machine. The "echo" line seems to be accepted.
And anyway, the developer of that program doesn't want them...
turn off the core dumps on *that* machine.
Suffices to stop them for that process only. There may be others of interest. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
* Carlos E.R. <robin.listas@gmx.es> [08-16-19 07:49]:
On 16/08/2019 13.36, Patrick Shanahan wrote:
* Carlos E.R. <robin.listas@gmx.es> [08-16-19 07:29]:
On 16/08/2019 13.06, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
Line 81 being: ulimit -H -c 0
Fwiw, I see the same on 15.1, but updated 7 August.
Yes, I try to update the home server once a month, so I saw it yesterday.
If I don't limit the size of coredumps, it can dump 8gigs or even more if the process swapped before crashing. Takes an awful lot of time in that puny machine. The "echo" line seems to be accepted.
And anyway, the developer of that program doesn't want them...
turn off the core dumps on *that* machine.
Suffices to stop them for that process only. There may be others of interest.
then take a little initiative. ulimit is not working for you, try another way. limit the amount of storage allowed a core dump via: edit /etc/systemd/coredump.conf change the size allowed -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2019 14.07, Patrick Shanahan wrote:
* Carlos E.R. <> [08-16-19 07:49]:
On 16/08/2019 13.36, Patrick Shanahan wrote:
* Carlos E.R. <> [08-16-19 07:29]:
On 16/08/2019 13.06, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
Line 81 being: ulimit -H -c 0
Fwiw, I see the same on 15.1, but updated 7 August.
Yes, I try to update the home server once a month, so I saw it yesterday.
If I don't limit the size of coredumps, it can dump 8gigs or even more if the process swapped before crashing. Takes an awful lot of time in that puny machine. The "echo" line seems to be accepted.
And anyway, the developer of that program doesn't want them...
turn off the core dumps on *that* machine.
Suffices to stop them for that process only. There may be others of interest.
then take a little initiative. ulimit is not working for you, try another way.
That's not the issue. The issue is finding out why ulimit is complaining now, when a month ago it didn't. What has changed and why? Is it that it has to be done by root? Is it that the syntax changed? Is it a bug? I don't care about other solutions. I'm not asking for them, I know about them. (maybe you have not noticed that the echo line is apparently working) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Carlos E.R. wrote:
On 16/08/2019 13.06, Per Jessen wrote:
Carlos E. R. wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
Line 81 being: ulimit -H -c 0
Fwiw, I see the same on 15.1, but updated 7 August.
Yes, I try to update the home server once a month, so I saw it yesterday.
If I don't limit the size of coredumps, it can dump 8gigs or even more
ISTR actually having to enable core dumps, are you sure they are not disabled by default? There is also something about systemd looking after core dumps now: https://www.freedesktop.org/software/systemd/man/systemd-coredump.html -- Per Jessen, Zürich (21.1°C) http://www.hostsuisse.com/ - dedicated server rental in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2019 13.50, Per Jessen wrote:
Carlos E.R. wrote:
If I don't limit the size of coredumps, it can dump 8gigs or even more
ISTR actually having to enable core dumps, are you sure they are not disabled by default? There is also something about systemd looking after core dumps now:
https://www.freedesktop.org/software/systemd/man/systemd-coredump.html
I have some notes somewhere about how it is done. The thing is, some releases enable them, then another disables them. My script have seen both sides. To avoid surprises, I disable it for this process. This particular process has a failure mode which is consume all the ram and more. A coredump of that takes atrocious CPU time, because of the default compression mode chosen, when I saw the issue. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On 8/16/19 12:54 PM, Carlos E. R. wrote:
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
I think the bug is that hard limit cannot be smaller than soft limit. # ulimit -H -c unlimited # ulimit -c unlimited # ulimit -H -c 0 -bash: ulimit: core file size: cannot modify limit: Invalid argument # ulimit -c 0 # ulimit -H -c 0 # ulimit -H -c 0 Hope this helps. - Adam -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2019 15.26, Adam Majer wrote:
On 8/16/19 12:54 PM, Carlos E. R. wrote:
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
I think the bug is that hard limit cannot be smaller than soft limit.
# ulimit -H -c unlimited
# ulimit -c unlimited
# ulimit -H -c 0 -bash: ulimit: core file size: cannot modify limit: Invalid argument
# ulimit -c 0 # ulimit -H -c 0 # ulimit -H -c 0
Hope this helps.
Wow! I see. Thank you and Dave H. :-) -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
Отправлено с iPhone
16 авг. 2019 г., в 18:58, Carlos E.R. <robin.listas@gmx.es> написал(а):
On 16/08/2019 15.26, Adam Majer wrote:
On 8/16/19 12:54 PM, Carlos E. R. wrote: # Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
I think the bug is that hard limit cannot be smaller than soft limit.
# ulimit -H -c unlimited
# ulimit -c unlimited
# ulimit -H -c 0 -bash: ulimit: core file size: cannot modify limit: Invalid argument
# ulimit -c 0 # ulimit -H -c 0 # ulimit -H -c 0
Hope this helps.
Wow! I see. Thank you and Dave H. :-)
And how exactly does it answer your question? Which was “The issue is finding out why ulimit is complaining now, when a month ago it didn't. What has changed and why?” You seem to apply double standard, where you scorn at one reply that does not answer your question but praise another. Also this setting is mostly irrelevant in openSUSE which is using systemd core manager by default so kernel ignores these limits. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Andrei Borzenkov wrote:
Also this setting is mostly irrelevant in openSUSE which is using systemd core manager by default so kernel ignores these limits.
Yes, I was pretty certain systemd was in charge. ISTR wanting to let my own code do a core dump and not being able to change the settings, without root access? -- Per Jessen, Zürich (20.8°C) http://www.hostsuisse.com/ - virtual servers, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 16/08/2019 19.18, Andrei Borzenkov wrote:
Отправлено с iPhone
16 авг. 2019 г., в 18:58, Carlos E.R. <robin.listas@gmx.es> написал(а):
On 16/08/2019 15.26, Adam Majer wrote:
On 8/16/19 12:54 PM, Carlos E. R. wrote: # Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
I think the bug is that hard limit cannot be smaller than soft limit.
# ulimit -H -c unlimited
# ulimit -c unlimited
# ulimit -H -c 0 -bash: ulimit: core file size: cannot modify limit: Invalid argument
# ulimit -c 0 # ulimit -H -c 0 # ulimit -H -c 0
Hope this helps.
Wow! I see. Thank you and Dave H. :-)
And how exactly does it answer your question? Which was “The issue is finding out why ulimit is complaining now, when a month ago it didn't. What has changed and why?”
What has changed, I understand, is that now hard limit can not be smaller than soft limit, and both have to be applied separately instead of simultaneouzsly. This is what has changed, that they have to be applied separately in certain order.
You seem to apply double standard, where you scorn at one reply that does not answer your question but praise another.
Wow.
Also this setting is mostly irrelevant in openSUSE which is using systemd core manager by default so kernel ignores these limits.
No, it doesn't. The coredumps of this process stopped when I first applied this command a year or two ago. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Sat, 17 Aug 2019 08:26:01 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 16/08/2019 19.18, Andrei Borzenkov wrote:
Отправлено с iPhone
16 авг. 2019 г., в 18:58, Carlos E.R. <robin.listas@gmx.es> написал(а):
On 16/08/2019 15.26, Adam Majer wrote:
On 8/16/19 12:54 PM, Carlos E. R. wrote: # Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
I think the bug is that hard limit cannot be smaller than soft limit.
# ulimit -H -c unlimited
# ulimit -c unlimited
# ulimit -H -c 0 -bash: ulimit: core file size: cannot modify limit: Invalid argument
# ulimit -c 0 # ulimit -H -c 0 # ulimit -H -c 0
Hope this helps.
Wow! I see. Thank you and Dave H. :-)
And how exactly does it answer your question? Which was “The issue is finding out why ulimit is complaining now, when a month ago it didn't. What has changed and why?”
What has changed, I understand, is that now hard limit can not be smaller than soft limit, and **both have to be applied separately instead of simultaneouzsly. This is what has changed, that they have to be applied separately in certain order.**
No, you can change them together. You just can't reduce the hard limit below the soft limit.
You seem to apply double standard, where you scorn at one reply that does not answer your question but praise another.
Wow.
Also this setting is mostly irrelevant in openSUSE which is using systemd core manager by default so kernel ignores these limits.
No, it doesn't.
The coredumps of this process stopped when I first applied this command a year or two ago.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 8/17/19 8:26 AM, Carlos E. R. wrote:
The coredumps of this process stopped when I first applied this command a year or two ago.
ahem, you're getting core dumps for an open source program for such a long time, and you're in contact with the developer and he/she doesn't fix it? Weird ... BTW: if it's a closed source program, then still avoiding to write huge core files is only half of the solution. The program in question could already have gone wild before actually triggering a coredump in the kernel. Have a nice day, Berny -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 19/08/2019 18.54, Bernhard Voelker wrote:
On 8/17/19 8:26 AM, Carlos E. R. wrote:
The coredumps of this process stopped when I first applied this command a year or two ago.
ahem, you're getting core dumps for an open source program for such a long time, and you're in contact with the developer and he/she doesn't fix it? Weird ...
Yep. He develops in Windows, probably has no toolset to debug in Linux. That's not the worst problem, though.
BTW: if it's a closed source program, then still avoiding to write huge core files is only half of the solution. The program in question could already have gone wild before actually triggering a coredump in the kernel.
Certainly. Some of the crashes were because all memory was used. I could limit its memory usage, too, forcing it to crash earlier. But that particular problem has not happened since some months. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)
On Fri, 16 Aug 2019 12:54:17 +0200 "Carlos E. R." <robin.listas@telefonica.net> wrote:
Hi,
for long, in the script that starts certain program, I used this (as plain user):
# Avoid huge dump core ops - doesn't work on Leap 42.2 ulimit -H -c 0 echo 0 > /proc/self/coredump_filter program
Suddenly, after an update applied yesterday, I get:
/home/cer/bin/fusion: line 81: ulimit: core file size: cannot modify limit: Invalid argument
You cannot modify the hard limit to be less than the soft limit. So either first set the soft (i.e. effective) limit to 0 and then set the hard limit (i.e. ceiling) to 0 or just do both at once: ulimit -c 0
Line 81 being:
ulimit -H -c 0
What has changed re ulimit?
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (8)
-
Adam Majer -
Andrei Borzenkov -
Bernhard Voelker -
Carlos E. R. -
Carlos E.R. -
Dave Howorth -
Patrick Shanahan -
Per Jessen