similar to: (no subject)

I added a subject so we can track this message on the list easier. ;) On Fri, Mar 21, 2014 at 12:19 PM, John Doe <jdmls at yahoo.com> wrote: > Hey, > > kernel: rsync invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0, > oom_score_adj=0 > ... > kernel: Out of memory: Kill process 27974 (mysqld) score 361 or > sacrifice child > kernel: Killed process

Hi all, Please find below a complete transcript of the emails between debian/kernel-mm mailing lists. I've had a response back from someone on the deb mailing list stating: ==================================== The bug seems to be that sshd does not reset the OOM adjustment before running the login shell (or other program). Therefore, please report a bug against openssh-server.

Hi all, Recently I build XEN 4.1 (from the xen.org) on centIOS 5.5 (kernel 2.6.38.4). After changing the grub file and rebooting the machine, I am continuously getting out of memory error. The content of my grub file: default=0 timeout=5 serial --unit=0 --speed=115200 terminal --timeout=10 console serial splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.38.4) root

Our domain controllers have run samba 4.4.3 since it was released. We didn't upgrade because it was so stable :) I recently decided that release was too old and upgraded to 4.8.2 (then current). Our domain controllers were crashing on 4.8.2 so I upgraded to 4.8.3 as soon as it was released but this has not resolved the issue. When the issue occurs the DC becomes unresponsive and needs to be

https://bugzilla.mindrot.org/show_bug.cgi?id=1838 Summary: /proc/self/oom_adj needs to use /proc/self/oom_score_adj Product: Portable OpenSSH Version: 5.6p1 Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: sshd AssignedTo: unassigned-bugs at

Hello, ?? First, I have to compliment the crew on the documentation.? It's solid. ?? Running on Ubuntu 12.04.3, I was using rsync to synchronize a 5T filesystem across two servers.? The default Ubuntu configuration is to run rsync over ssh, conveniently the way I prefer it. ?? Initially, it would run for hours and copy 4T or so data.? Then as it began to progress further, perhaps using

My web & name server runs out of memory from time to time, to the point where it's completely unresponsive to anything. At that point reset is the only alternative. (Or, as this is a virtual guest, I just say "virsh destroy"). But why this happens - I would like to know. The host in question is a KVM guest, and runs CentOS 6.4. From "top" (situation now): Mem:

I did a batch update on a number of Xen vservers, with kernel 2.6.32-573.26.1 being installed. In addition to load averages being high and these #s not being reflected by the individual CPU numbers within top, I now have a spattering of occasional daemon crashes that the vservers have historically never had. Such as, here is the start of a nameserver blowing up in my logs: May 12 04:03:41 XXX

Hi all, Recently I build XEN 4.1 (from the xen.org) on centIOS 5.5 (kernel 2.6.38.4). After changing the grub file and rebooting the machine, I am continuously getting out of memory error. The content of my grub file: default=0 timeout=5 serial --unit=0 --speed=115200 terminal --timeout=10 console serial splashimage=(hd0,0)/grub/splash.xpm.gz hiddenmenu title CentOS (2.6.38.4) root

Package: xen-hypervisor-4.0-amd64 Version: 4.0.1-2 Severity: normal Tags: upstream When creating Xen DomU's, at some point xend invokes the oom-killer and the entire machine restarts: Sep 5 12:04:59 arbiter kernel: [259697.101212] __ratelimit: 136 callbacks suppressed Sep 5 12:04:59 arbiter kernel: [259697.101218] xend invoked oom-killer: gfp_mask=0x200da, order=0, oom_adj=0 Sep 5

Hai, How is the swappiness set? cat /proc/sys/vm/swappiness Its probely set to 60, i suggest, lower it to 10 or 20. That wil help keeping the samba processes out of swap. I've see more programs gettting OOM Killed due too out of swap. echo 10 > /proc/sys/vm/swappiness Stop and start samba Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba

Hi Laurent, > > We upgraded a legacy (NT4) domain from 3.6 series to 4.8 and then 4.9.4 > samba version (using sernet subscription packages / debian stable) > > The setup is composed of 4 DCs with each 2 CPU/16GB RAM. > > We currently have ~700 user accounts / ~600 computers / ~150 groups > > Our mail setup, SSO, ... query the 4 DCs constantly. > > > Every 5 to

https://bugzilla.mindrot.org/show_bug.cgi?id=2156 Bug ID: 2156 Summary: Fix oom_adj on Linux after sshd reload Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 Component: sshd Assignee: unassigned-bugs at mindrot.org

Hi, i''ve a big problem in a xenU (256M RAM, 2.6.11.12-xenU, in 3 LVM partition (/, swap and /home) This xenU freeze and crash with this messages in syslog. This xenU work very fine since 2005 september. Is it serious ? What could be the solution ? Regards Franck ############ SYSLOG ...................... Jun 18 08:45:21 lemodev kernel: oom-killer: gfp_mask=0x1d2 Jun 18 08:45:21

Currently, on linux sshd attempts to remove itself from the influence of oom-killer by modifying the oom_adj parameter for itself in proc to -17. This is controlled via two functions; oom_adjust_setup() and oom_adjust_restore(). Setup saves the old score (typically zero on initialization) and sets sshd to -17 whilst oom_adjust_restore places the saved value from initialization back into the

Just did some testing.. root at vicky:~# cat /var/log/auth.log | grep "Set" May 30 21:41:05 vicky sshd[1568]: Set /proc/self/oom_adj from -17 to -17 May 30 21:41:07 vicky sshd[1574]: Set /proc/self/oom_adj to -17 root at vicky:~# ps faux | grep 1574 root 1574 0.0 0.0 70488 3404 ? Ss 21:41 0:00 \_ sshd: root at pts/1 root at vicky:~# ps faux | grep

https://bugs.freedesktop.org/show_bug.cgi?id=72978 Priority: medium Bug ID: 72978 Assignee: nouveau at lists.freedesktop.org Summary: nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All Reporter: mikhail.v.gavrilov at

Hello! I use NSD 4.7.0 self compiled: Configure line: --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking

Hello all, had an issue on with a virtualmachine on XenServer 7.0 yesterday. It is a Centos 7.4.1708 and in a OOM situation it just shut down. No kernel panic where I could see a message, but it just turned itself off. All I could see in the /var/log/messages was the following: ------------------------------------------------------------------------ Sep 24 03:11:08 hostname xe-daemon: Running

Hello All, Anyone have seen this before? Did samba_spnupdate really caused the crash??? [ 49.753564] block drbd1: drbd_sync_handshake: [ 49.753571] block drbd1: self BB16E125AF60AEDC:0000000000000000:30D97136FB1DA7A3:30D87136FB1DA7A3 bits:0 flags:0 [ 49.753576] block drbd1: peer 6365B5AFF049F16D:BB16E125AF60AEDD:30D97136FB1DA7A2:30D87136FB1DA7A3 bits:1 flags:0 [ 49.753580] block drbd1: