Thank you.
On 29/9/22 13:37, John Verhoeven wrote:
On Thursday, 29 September 2022 10:48:43 AM AWST Jiri Kanicky wrote:
I updated debian sid recently and the process is being killed after a
half of a day.
Sep 26 04:33:33 server kernel: Out of memory: Killed process 16702
(transmission-da
On Thursday, 29 September 2022 10:48:43 AM AWST Jiri Kanicky wrote:
> I updated debian sid recently and the process is being killed after a
> half of a day.
>
> Sep 26 04:33:33 server kernel: Out of memory: Killed process 16702
> (transmission-da) total-vm:4933944kB, anon-rss:3566
I updated debian sid recently and the process is being killed after a
half of a day.
Sep 26 04:33:33 server kernel: Out of memory: Killed process 16702
(transmission-da) total-vm:4933944kB, anon-rss:3566896kB, file-rss:0kB,
shmem-rss:0kB, UID:133 pgtables:7928kB oom_score_adj:0d
Any ideas?
m-$Displaynumber-log~"
exec /usr/bin/fvwm > "$HOME/.xsession-fvwm-$Displaynumber-log" 2>&1 &
Wmpid=$!
elif [ -x …
…
…
else
printf '%s\n' "Error - no window manager found"
fi
so that .xsession can avoid terminat
tester64.ex | awk {'print $7'}` --adjust 1000
I spawned more than 8 processes to saturate RAM quickly. Meaning, some
processes were not adjusted to 1000 score. After 20 seconds, OOM event
happened.
And what Linux does? It has at least 8 processes with 1000 score, but
let's
On Wed, Apr 20, 2022 at 04:23:38PM +0100, piorunz wrote:
Sorry but this happened to me a few times, each tome with the same Wine
program. it just loves to eat all available memory when its doing heavy
computations. When I am not careful and I start too many threads, is
eats all memory. My system
On 20/04/2022 11:28, Jonathan Dowland wrote:
On Thu, Mar 31, 2022 at 05:53:20PM +0100, piorunz wrote:
Well, nowadays oom killer is not so picky. It just kills (almost)
EVERYTHING and then offending memory hungry process as a last,
destroying entire work session.
You are extrapolating from your
On Thu, Mar 31, 2022 at 05:53:20PM +0100, piorunz wrote:
Well, nowadays oom killer is not so picky. It just kills (almost)
EVERYTHING and then offending memory hungry process as a last,
destroying entire work session.
You are extrapolating from your single experience to make a
generalisation th
On Tue, Mar 29, 2022 at 10:34:19AM +0100, piorunz wrote:
Instead of killing ONE 7.5 million-worth pagetable process, Linux is
killing everything else! KDE activity manager killed. Then it goes on to
kill EVERYTHING in the system:
Perhaps your wine processes had their oom_adj (etc) values tweake
On Tue, Apr 19, 2022, 11:08 AM wrote:
> On Tue, Apr 19, 2022 at 04:44:36PM +0100, Tim Woodall wrote:
> > On Mon, 18 Apr 2022, piorunz wrote:
> >
> > >
> > > I look from desktop perspective. OS (Linux) runs my desktop and manage
> > > all programs [...]
>
> > Because not every machine that has the
On Tue, Apr 19, 2022 at 04:44:36PM +0100, Tim Woodall wrote:
> On Mon, 18 Apr 2022, piorunz wrote:
>
> >
> > I look from desktop perspective. OS (Linux) runs my desktop and manage
> > all programs [...]
> Because not every machine that has the linux kernel installed runs a
> desktop [...]
As I
On Mon, 18 Apr 2022, piorunz wrote:
I look from desktop perspective. OS (Linux) runs my desktop and manage
all programs. When one programs eats too much memory, program gets
killed. That is default behaviour or any mature operating system, even
in Windows 2000 era we had this. I don't understan
On 15/04/2022 11:14, to...@tuxteam.de wrote:
Thanks for your reply, I appreciate your patience.
- At the "low level": you are talking about "process trees".
Perhaps that's the problem. Perhaps, towards the OOM score,
all those processes count as individual processes.
Each 8GB individual p
On Fri, Apr 15, 2022 at 11:03:07AM +0100, piorunz wrote:
> On 15/04/2022 06:53, to...@tuxteam.de wrote:
> > If you want to learn more about that, the Linux MM ("memory
> > management") people have set up a wiki for that:
> >
> >https://linux-mm.org/OOM_Killer
> >
> > Enjoy:)
> >
> > (and yes
On 15/04/2022 06:53, to...@tuxteam.de wrote:
If you want to learn more about that, the Linux MM ("memory
management") people have set up a wiki for that:
https://linux-mm.org/OOM_Killer
Enjoy:)
(and yes, on my box, more memory-hungry processes have a higher
/proc//oom_score, so they seem to
On Fri, Apr 15, 2022 at 02:09:04AM +0100, piorunz wrote:
> On 01/04/2022 07:08, to...@tuxteam.de wrote:
[...]
> > See man (1) choom and search for oom in man (5) proc.
> Thanks! That's exactly what I needed. Amazing.
You're welcome :)
> Now, after I start the process, I run:
>
> Adjust to max
On 01/04/2022 07:08, to...@tuxteam.de wrote:
On Tue, Mar 29, 2022 at 07:58:38PM +0100, piorunz wrote:
On 29/03/2022 10:56, Sven Hoexter wrote:
E.g. we now have PSI as an information source
https://lwn.net/Articles/759781/
which can be used with the Facebook oomd or systemd-oomd to
have userland
On Tue, Mar 29, 2022 at 07:58:38PM +0100, piorunz wrote:
> On 29/03/2022 10:56, Sven Hoexter wrote:
> > E.g. we now have PSI as an information source
> > https://lwn.net/Articles/759781/
> > which can be used with the Facebook oomd or systemd-oomd to
> > have userland control over which process to
On 30/03/2022 09:18, Tixy wrote:
I may be wrong here, but I seem to remember that something like that
used to happen a long time ago, and it had a habit of picking the X
server as the first thing to kill, not very friendly for GUI users.
Well, nowadays oom killer is not so picky. It just kill
On Tue, 2022-03-29 at 19:39 +0100, piorunz wrote:
> On 29/03/2022 10:56, Sven Hoexter wrote:
>
> > The in kernel oom killing is a constant issue. If you look through the
> > lwn.net articles of the past years there is work done to improve the
> > situation, but I believe that's not in a default se
On Tue, Mar 29, 2022 at 09:03:14PM +0100, piorunz wrote:
> On 29/03/2022 20:16, Greg Wooledge wrote:
> > Resource limits are a thing. man setrlimit (you may have to install
> > manpages-dev first).
>
> How do I use it? I've read manual but that would need to written down as
> a C++ program or som
On 29/03/2022 20:16, Greg Wooledge wrote:
Resource limits are a thing. man setrlimit (you may have to install
manpages-dev first).
Are they crude as hell? Absolutely. But they allow you to set up a
barrier that says "if you use more than x MB of memory, you die". They
work well enough for so
On Tue, Mar 29, 2022 at 07:41:53PM +0100, piorunz wrote:
> And I wanted to highlight that this is not some trivial problem, at the
> moment any rogue non-privileged process running on user account, or
> simple coding error can destroy entire Linux session, be is a important
> server with many servi
On Tue, Mar 29, 2022 at 1:59 PM piorunz wrote:
> On 29/03/2022 10:56, Sven Hoexter wrote:
> > E.g. we now have PSI as an information source
> > https://lwn.net/Articles/759781/
> > which can be used with the Facebook oomd or systemd-oomd to
> > have userland control over which process to kill.
>
On 29/03/2022 10:56, Sven Hoexter wrote:
E.g. we now have PSI as an information source
https://lwn.net/Articles/759781/
which can be used with the Facebook oomd or systemd-oomd to
have userland control over which process to kill.
Thanks, I've read this article. Unfortunately, this is just infor
On 29/03/2022 10:56, Sven Hoexter wrote:
And I wanted to highlight that this is not some trivial problem, at the
moment any rogue non-privileged process running on user account, or
simple coding error can destroy entire Linux session, be is a important
server with many services running or just a
On 29/03/2022 10:56, Sven Hoexter wrote:
The in kernel oom killing is a constant issue. If you look through the
lwn.net articles of the past years there is work done to improve the
situation, but I believe that's not in a default setup yet.
Yes it's terrible, how this can be broken so badly? L
On Tue, Mar 29, 2022 at 10:34:19AM +0100, piorunz wrote:
> Hello,
>
> I use Debian Testing on AMD64, on a workstation with Ryzen 5800X - 16
> CPU cores and 64GB of ECC DDR4 RAM.
>
> Today, Windows application I run on Wine for work has decided to eat all
> available memory, CPU and HDD I/O. I don
/user.slice/user-1000.slice/user@1000.service/background.slice/plasma-kactiv>
kernel: Out of memory: Killed process 4611 (kactivitymanage)
total-vm:551104kB, anon-rss:7068kB, file-rss:0kB, shmem-rss:0kB,
UID:1000 pgtables:248kB oom_score_adj:200
Instead of killing ONE 7.5 million-worth pagetabl
On Vi, 08 ian 21, 23:20:46, ghe2001 wrote:
>
>
> ‐‐‐ Original Message ‐‐‐
> On Friday, January 8, 2021 10:28 PM, Jen Nussbaum wrote:
>
> > I don't know why I tried this, but I then ran simple-scan as root, and...it
> > worked perfectly.
>
> I had a similar problem with vim -- I have n
On Fri, Nov 01, 2019 at 10:10:55AM +, Nagisa Weaton wrote:
>
> Hello everyone, sorry for bothering all of you, but I need some advice.
[...]
> My work (I’m a Java developer) is the same as when I worked on Windows
> installed on my laptop, both of the PC and laptop have 16G memory.
As a st
Nagisa Weaton wrote:
> My work (I’m a Java developer) is the same as when I worked on Windows
> installed on my laptop, both of the PC and laptop have 16G memory.
>
but you don't say what is allocated to the java/jvm process causing the
error. Look there first
> But the laptop never reports the
Hello everyone, sorry for bothering all of you, but I need some advice.
These days I got a new PC to replace my laptop. And I install an Ubuntu MATE
18.04 LTS on the PC.
There is something bothering me. Almost every day, it reports an error that the
memory is not enough.
My work (I’m a Java d
* Maicon Faria (2009-05-20):
[...]
> When I run a program, as user, that uses more then the memory
> avaliable the OOM(OUT-OF-MEMORY) kill this job.
Disarm the OOM killer:
# /etc/sysctl.conf
vm.overcommit_memory=2
-André
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
On Wednesday 20 May 2009 17:17:35 Maicon Faria wrote:
> Package: OpenSSH_5.1p1 Debian-5
>
> When I run a program, as user, that uses more then the memory
> avaliable the OOM(OUT-OF-MEMORY) kill this job.
> After that, ssh crashes and must be restarted by the root.
>
> A
Package: OpenSSH_5.1p1 Debian-5
When I run a program, as user, that uses more then the memory
avaliable the OOM(OUT-OF-MEMORY) kill this job.
After that, ssh crashes and must be restarted by the root.
Anyone has experienced something like that ?
This happens in computers in a cluster where the
On 08/07/2008 10:18 PM, hhding.gnu wrote:
Hi list,
When debian run out of memory, I can only ping the host and can't ssh to
the host.
It seems oom-killer is running but memory is still exhaust.
What should I do then? Only reboot can solve the problem?
Can I protect oom-killer from kil
On Fri, Aug 08, 2008 at 11:18:20AM +0800, hhding.gnu wrote:
> Hi list,
>
> When debian run out of memory, I can only ping the host and can't ssh to
> the host.
> It seems oom-killer is running but memory is still exhaust.
>
> What should I do then? Only reboot can
Hi list,
When debian run out of memory, I can only ping the host and can't ssh to
the host.
It seems oom-killer is running but memory is still exhaust.
What should I do then? Only reboot can solve the problem?
Can I protect oom-killer from kill the sshd then I can ssh to the box to
kil
On Monday 01 May 2006 06:13 am, Linas ?virblis wrote:
> tom arnall wrote:
> >> What about streams then?
> >
> > please tell me how that would work? i'm not familiar with the mechanism.
>
> You could open a file as a stream (or a buffer, it is the same thing),
> read it in chunks of reasonable lengt
tom arnall wrote:
>> What about streams then?
>
> please tell me how that would work? i'm not familiar with the mechanism.
You could open a file as a stream (or a buffer, it is the same thing),
read it in chunks of reasonable length (maximum length you expect the
longest regex match would span),
On Sunday 30 April 2006 04:41 pm, Linas ?virblis wrote:
> tom arnall wrote:
> > Understood, but I am doing a regex on text units which span more than one
> > line. Trying to process this text w' line-by-line io would be possible
> > but, as far as I can see, very awkward.
>
> What about streams the
ry very fast. Too fast for swapout
to complete before you run out of it.
> What I want is for system to be
> swapping mostly for just the perl application.
By doing what you are currently doing, you will probably run out of
memory anyway, but here is a little trick you could try. Not that i
On Saturday 29 April 2006 04:22 pm, Linas ?virblis wrote:
> tom arnall wrote:
> > I am trying to us a perl application that handles large files (.5GB) in
> > scalar variables. When I try to 'slurp' one of these files into a
> > variable (e.g., '$_ = `cat fil
tom arnall wrote:
> i am trying to us a perl application that handles large files (.5GB) in
> scalar
> variables. when i try to 'slurp' one of these files into a variable
> (e.g., '$_ = `cat filename`) i get an out of memory error.
You should consider alternative
i am trying to us a perl application that handles large files (.5GB) in scalar
variables. when i try to 'slurp' one of these files into a variable
(e.g., '$_ = `cat filename`) i get an out of memory error. (same for '@var =
') initially, i ran the script without an
lhost dovecot: child 4600 (imap) returned error 83
(Out of memory)
Dec 3 06:44:03 localhost dovecot: imap(ric): pool_system_malloc(): Out
of memory
For example, it was working fine earlier this morning, but now I am unable to
access the mailboxes and I'm getting the e
On Tuesday 09 September 2003 11:05 am, Diego Calleja García wrote:
> El Tue, 9 Sep 2003 09:33:52 -0700 Kurt Taylor <[EMAIL PROTECTED]>
escribió:
> > USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> > root 368 41.1 67.8 519176 174292 ? D13:47 218:35
> > /usr/X1
El Tue, 9 Sep 2003 09:33:52 -0700 Kurt Taylor <[EMAIL PROTECTED]> escribió:
> USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
> root 368 41.1 67.8 519176 174292 ? D13:47 218:35
> /usr/X11R6/bin/X :0 -dpi 100 -nolisten tcp vt7 -auth /var/lib/kdm/A:0-0B9JDi
> k
I've started to have a problem of my computer running out of memory. It's on
a work computer and it happens during the middle of the night so I'm not here
actively doing anything. The machine has 256MB of RAM and 517MB of swap
space.
In the morning, several of the programs I l
probably one program uses all your memory. Try
ps --sort=rss aux
to check which process uses too much memory.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
My box is a Debian Sid 2.4.21-5-686 full update. I have 1 GB of ram and
another gb of swap. There's a lot of free disk space.
I get lots of out of memory.
Part of the dmesg:
...
GRE over IPv4 tunneling driver
IPv4 over IPv4 tunneling driver
ip_conntrack version 2.1 (8191 buckets, 65528 max)
Nori Heikkinen wrote:
anyone seen this before? i just got a blank message at the top of my
inbox, dated Jan 01 (that's all -- no headers, no nothing), and
checking the procmail logs, i see:
Out of memory!
Callback called exit.
END failed--call queue aborted at /usr/bin/spamassassin li
On Fri, Feb 14, 2003 at 05:29:10PM -0500, Nori Heikkinen wrote:
> anyone seen this before? i just got a blank message at the top of my
> inbox, dated Jan 01 (that's all -- no headers, no nothing), and
> checking the procmail logs, i see:
>
> Out of memory!
> Callback ca
anyone seen this before? i just got a blank message at the top of my
inbox, dated Jan 01 (that's all -- no headers, no nothing), and
checking the procmail logs, i see:
Out of memory!
Callback called exit.
END failed--call queue aborted at /usr/bin/spamassassin line 50.
huh. extraordin
On Mon, Dec 16, 2002 at 04:50:06PM +, Anthony Campbell wrote:
> On 16 Dec 2002, Nicolas SABOURET wrote:
> > Quand j'ai trop de mail d'un coup (genre apr?s un we), il
>
> When I have too much mail it suddenly, usually after a "we" [?], it
on courier ? moi, ? l'aide d'un
> > .forward et d'une r?gle procmail.
> > Quand j'ai trop de mail d'un coup (genre apr?s un we), il p?te les
> > plombs et j'obtiens des :
> > Out of memory: Killed process 12786 (spamassassin)
> > Ma question (
; >
> > When I have too much mail it suddenly, usually after a "we" [?], it
> > crashes and I get "out of memory; killed process..."
> >
> > My desperate question is: when this happens do I use all the mail which
>
On Mon, Dec 16, 2002 at 04:50:06PM +, Anthony Campbell wrote:
> On 16 Dec 2002, Nicolas SABOURET wrote:
[translated]
> I use spamassassin to filter my mail using .forward and a procmail rule.
>
> When I have too much mail it suddenly, usually after a "we" [?], it
>
r?gle procmail.
>> Quand j'ai trop de mail d'un coup (genre apr?s un we), il p?te les
>> plombs et j'obtiens des :
>> Out of memory: Killed process 12786 (spamassassin)
>> Ma question (angoiss?e) est :
>> quand il fait ?a, est-ce que je
On 16 Dec 2002, Nicolas SABOURET wrote:
> Salut,
>
> J'utilise spamassassin pour filtrer mon courier ? moi, ? l'aide d'un
> .forward et d'une r?gle procmail.
> Quand j'ai trop de mail d'un coup (genre apr?s un we), il p?te les
> plombs et j
Salut,
J'utilise spamassassin pour filtrer mon courier à moi, à l'aide d'un
.forward et d'une règle procmail.
Quand j'ai trop de mail d'un coup (genre après un we), il pète les
plombs et j'obtiens des :
Out of memory: Killed process 12786 (spamassassin)
Ma q
ffectively closing off most services. The load
> went from 1 to 50 and back down in the space of approximately 30
> minutes, and while the load was very high, the Apache error logs kept
> posting "Out of Memory Messages"
swapping? dunno. In any case, I would reduce MaxCl
error logs kept
posting "Out of Memory Messages"
My guess is that this was a real memory allocation problem (i.e. kernel
based). I have only seen such loads about a year ago when we had random
VM problems, but since I compiled a 2.2.19 kernel, virtual memory has
been rock solid.
I upgraded several potato packages today and when apt-get was trying to
install xcontrib it gave an out of memory error. The load was quite
high, sometimes over 2.0 and most of my 64 MB of RAM and all my 130 MB
of swap was in use. Needless to say, the system was extremely sluggish
and several
gt; more than 460MB of swap :)))).
I'd got a similar problem with pari on a symbolic computation :
when the program ran out of memory, it tries to double the size
of its allocated memory (in my case it couldn't make better than
48MB RAM + about 30MB swap out of 96). For me, adding a swap
On Mon, 7 Dec 1998 [EMAIL PROTECTED] wrote:
> -BEGIN PGP SIGNED MESSAGE-
>
> Hi Krupa!
>
> On Thu, 3 Dec 1998, Jan Krupa wrote:
>
> >
> > My Debian Linux 2.0 cannot use more than 460MB sawp :(
>
> that's very extrange :-(
You're right. Linux can use my 860MB of swap ( I gave some
ap
-BEGIN PGP SIGNED MESSAGE-
Hi Krupa!
On Thu, 3 Dec 1998, Jan Krupa wrote:
>
> My Debian Linux 2.0 cannot use more than 460MB sawp :(
that's very extrange :-(
> Here are some additional information
> $ free
> total used free sharedbuffers cached
> M
to see what happends.
Sasha.
>
> Unfortunately when the mathematica3.0 is running,
> after using ("consuming") all RAM memory it can only
> use up to 460Mb of swap and then it prints message:
> 'out of memory' and exits the calculations
> (stop running the calcula
> My Debian Linux 2.0 cannot use more than 460MB sawp :(
There is a similar thread going on on linux-kernel that may be apropos to
your situation.
Basically, what it comes down to is that the way a (stock) Linux kernel
lays out memory, it is unable to address more than approximately 960MB
of memo
f swap and then it prints message:
'out of memory' and exits the calculations
(stop running the calculation) but it does not crush,
the front end of it and its kernel can be used further.
It is normal ? How can be the total swap amount (860Mb) used?
Does anybody have some idea, where could
I have tried to install teh debian .96r3 the base system went fine
with no problem but when using dpkg it keeps telling me I am out of
memory.
I have 8 meg of real memory and created a 30meg swap partition when
installing also i have plenty of free disk space, any help would be
greatly
72 matches
Mail list logo
