search for: overcommit_ratio

...antiago # free total used free shared buffers cached Mem: 2052176 234828 1817348 0 15352 112852 -/+ buffers/cache: 106624 1945552 Swap: 2052088 0 2052088 # sysctl -a |grep commit vm.overcommit_memory = 0 vm.overcommit_ratio = 50 vm.nr_overcommit_hugepages = 0 # sysctl -w vm.overcommit_memory=2 vm.overcommit_memory = 2 # ls -bash: fork: Cannot allocate memory # #--- CENTOS6 -------------------------- # uname -a Linux joker 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 x86_64 x86_64 GNU/Linux # lsb_r...

This patch includes feedback from apevec to remain backward compatible with the previous karg, ovirt_local_boot.

...s/ovirt-early b/scripts/ovirt-early index cdd4afd..cda1b3f 100755 --- a/scripts/ovirt-early +++ b/scripts/ovirt-early @@ -135,7 +135,7 @@ start() { # ovirt_init=[usb|scsi[:serial#]|/dev/...] # ovirt_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MB:DATA_MB # ovirt_overcommit=<overcommit_ratio> - # ovirt_local_boot + # ovirt_upgrade # ovirt_standalone # ovirt_firstboot # rescue @@ -182,9 +182,9 @@ start() { # or a specific positive number in MB vol_data_size= - # ovirt_local_boot + # ovirt_upgrade # install/update oVirt Node im...

...e: alignment check: stack segment: fpu exception: simd exception: iret exception: /var/log/messages -- /usr/bin/abrt-dump-oops -xtD I had made a few changes to sysctl.conf which I have now reverted and the error still exists. my sysctl.conf contained; vm.swappiness=0 vm.overcommit_memory=2 vm.overcommit_ratio=90 - this was only added this morning because of an 'out of memory' error in postgresql. kernel.shmmax=35433480192 kernel.shmall=2214592512 which I have now removed. Can anyone shine any light on this? A little search on Google mentions faulty memory, I will install memtest today and se...

Hey guys and gals, Yesterday I had one of my scientists kill one of my servers when his program ran amok and gobbled up all the memory, or forked too many processes, or I'm just not exactly sure what to be honest. Is there something I can run manually in cron to look for rampant programs and kill them? I know that may be hard to discern but I could also include a list if "known

Resending the refactored patch: I realized after I emailed it that it referenced the wrong bugzilla.

On 02/17/2016 07:08 AM, Michael H wrote: > On 17/02/16 13:01, Johnny Hughes wrote: >> I normally just let the daily announce post to this list show what >> is available for updates, but there is a CVE (CVE-2015-7547) that >> needs a bit more attention which will be on today's announce list >> of updates. >> >> We released a new glibc yesterday for

...greSQL database server. > Feb 17 13:46:16 db1 systemd: Unit postgresql.service entered failed state. > Feb 17 13:46:16 db1 systemd: postgresql.service failed. > > > I have kernel parameters specified in /etc/sysctl.conf > > vm.swappiness=0 > vm.overcommit_memory=2 > vm.overcommit_ratio=90 > kernel.shmmax=35433480192 > kernel.shmall=8650752 > > After the update my postgresql service could not start because these > parameters had been reset, I promptly rebooted to server to re-apply them. > > Has something changed?!? after a reboot the service still complaine...

...17 13:46:16 db1 systemd: Failed to start PostgreSQL database server. Feb 17 13:46:16 db1 systemd: Unit postgresql.service entered failed state. Feb 17 13:46:16 db1 systemd: postgresql.service failed. I have kernel parameters specified in /etc/sysctl.conf vm.swappiness=0 vm.overcommit_memory=2 vm.overcommit_ratio=90 kernel.shmmax=35433480192 kernel.shmall=8650752 After the update my postgresql service could not start because these parameters had been reset, I promptly rebooted to server to re-apply them. Has something changed?!? after a reboot the service still complained that my max_stack_depth was too h...

...able = 0 vm.hugetlb_shm_group = 0 vm.laptop_mode = 0 vm.legacy_va_layout = 0 vm.lowmem_reserve_ratio = 256 32 32 vm.max_map_count = 65530 vm.min_free_kbytes = 3084 vm.mmap_min_addr = 4096 vm.nr_hugepages = 0 vm.nr_overcommit_hugepages = 0 vm.nr_pdflush_threads = 0 vm.overcommit_memory = 0 vm.overcommit_ratio = 50 vm.page-cluster = 3 vm.percpu_pagelist_fraction = 0 vm.scan_unevictable_pages = 0 vm.stat_interval = 1 vm.swappiness = 30 vm.user_reserve_kbytes = 131072 vm.vdso_enabled = 1 vm.vfs_cache_pressure = 100 # ulimit -a core file size (blocks, -c) 0 data seg size (kbytes, -d) unl...

...17 13:46:16 db1 systemd: Failed to start PostgreSQL database server. Feb 17 13:46:16 db1 systemd: Unit postgresql.service entered failed state. Feb 17 13:46:16 db1 systemd: postgresql.service failed. I have kernel parameters specified in /etc/sysctl.conf vm.swappiness=0 vm.overcommit_memory=2 vm.overcommit_ratio=90 kernel.shmmax=35433480192 kernel.shmall=8650752 After the update my postgresql service could not start because these parameters had been reset, I promptly rebooted to server to re-apply them. Has something changed?!? after a reboot the service still complained that my max_stack_depth was too h...

...Feb 17 13:46:16 db1 systemd: Unit postgresql.service entered failed state. >> Feb 17 13:46:16 db1 systemd: postgresql.service failed. >> >> >> I have kernel parameters specified in /etc/sysctl.conf >> >> vm.swappiness=0 >> vm.overcommit_memory=2 >> vm.overcommit_ratio=90 >> kernel.shmmax=35433480192 >> kernel.shmall=8650752 >> >> After the update my postgresql service could not start because these >> parameters had been reset, I promptly rebooted to server to re-apply them. >> >> Has something changed?!? after a reboot t...

...greSQL database server. > Feb 17 13:46:16 db1 systemd: Unit postgresql.service entered failed state. > Feb 17 13:46:16 db1 systemd: postgresql.service failed. > > > I have kernel parameters specified in /etc/sysctl.conf > > vm.swappiness=0 > vm.overcommit_memory=2 > vm.overcommit_ratio=90 > kernel.shmmax=35433480192 > kernel.shmall=8650752 > > After the update my postgresql service could not start because these > parameters had been reset, I promptly rebooted to server to re-apply them. > > Has something changed?!? after a reboot the service still complaine...

...t postgresql.service entered failed state. >>> Feb 17 13:46:16 db1 systemd: postgresql.service failed. >>> >>> >>> I have kernel parameters specified in /etc/sysctl.conf >>> >>> vm.swappiness=0 >>> vm.overcommit_memory=2 >>> vm.overcommit_ratio=90 >>> kernel.shmmax=35433480192 >>> kernel.shmall=8650752 >>> >>> After the update my postgresql service could not start because these >>> parameters had been reset, I promptly rebooted to server to re-apply them. >>> >>> Has something...

...rs # BOOTIF=link|eth*|<MAC> (appended by pxelinux) # ovirt_init=[usb|scsi[:serial#]|/dev/...] - # ovirt_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MB:DATA_MB + # ovirt_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MB:COREDUMP_MB:DATA_MB # ovirt_overcommit=<overcommit_ratio> # ovirt_local_boot # ovirt_standalone @@ -166,13 +166,14 @@ start() { # w/o value - grab the first disk (/dev/?da) init= - # ovirt_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MB:DATA_MB + # ovirt_vol=BOOT_MB:SWAP_MB:ROOT_MB:CONFIG_MB:LOGGING_MB:COREDUMP_MB:...

On Tue, Jan 26, 2016 at 1:51 PM, Michal Privoznik <mprivozn@redhat.com> wrote: > On 26.01.2016 14:35, Andrei Perietanu wrote: > > On Tue, Jan 26, 2016 at 12:39 PM, Michal Privoznik <mprivozn@redhat.com> > > wrote: > > > >> On 26.01.2016 12:30, Andrei Perietanu wrote: > >>> Hi all, > >>> > >>> I am running KVM on a 3.18

The following patches introduce support for multipath and cciss devices to the ovirt-node and node-image. Comments are appreciated. These patches assume that the 3 patches (2 node, 1 node-image) from Joey are all incorporated. Mike