search for: shmall

Hi List, I'm tuning up a new database server and I'm finding very mixed information online. Here are the default shmmax and shmall from my new system cat /proc/sys/kernel/shmmax 4294967295 cat /proc/sys/kernel/shmall 268435456 SHMALL is close enough to being SHMMAX / 16. Now, everything I'm finding online tells me that SHMALL = SHMMAX / PAGE_SIZE. default page size is 4096. Has something changed in this calculation?...

...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 high because k...

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

On 2/17/2016 6:39 AM, Michael H wrote: > Some additional information; > > sysctl -a | grep kernel.shm > kernel.shmall = 8650752 > kernel.shmmax = 35433480192 > kernel.shmmni = 4096 > > which corresponds to my /etc/sysctl.conf > kernel.shmmax=35433480192 > kernel.shmall=8650752 > > but contradicts; > ulimit -a > [...] > stack size (kbytes, -s) 8192 SysV Shared Memory...

Hello again, on CentOS 6 / 64 bit what is please the best way to permanently increase the shared memory? I'd like to give shared_buffers = 4096MB to PostgreSQL 8.4 on my machine with 16 GB RAM, but I currently only have: # sysctl -A|grep shm kernel.shmmax = 33554432 kernel.shmall = 2097152 kernel.shmmni = 4096 and this produces the error in /var/lib/pgsql/pgstartup.log: FATAL: could not create shared memory segment: Invalid argument DETAIL: Failed system call was shmget(key=5432001, size=4399202304, 03600). HINT: This error usually means that PostgreSQL's reque...

...following entries in /boot/loader.conf: kern.ipc.shm_use_phys="1" kern.ipc.semmns="500" kern.ipc.semmni="40" kern.ipc.semmap="500" which are set correctly. Unfortunately, the following two entries kern.ipc.shmmax="512000000" kern.ipc.shmall="65526" do not change the corresponding values according to sysctl, no matter whether I put them in /boot/loader.conf or /etc/sysctl.conf. Changing them by hand (as root with 'sysctl') afterwards however _does_ work, so I have (for now) put those two settings in a little script...

...ut what do you have in > /proc/sys/kernel/shmmni ? > > According to man shmget: > ENOSPC All possible shared memory IDs have been taken (SHMMNI), or > allocating a segment of the requested size would cause the > system to exceed the system-wide limit on shared memory (SHMALL). "cat /proc/sys/kernel/shmmni" shows 4096. And, I find that "wc -l /proc/sysvipc/shm" shows that they are indeed all in use. A badly coded java game appears to be the culprit. It's grabbing SHM IDs by the thousands. Thanks for the pointer. Your shot in the dark was righ...

...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 high because k...

...atabase 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 high because kernel shmmax and shmall were t...

...rror Jan 22 23:41:19 Keepalived_healthcheckers[1998]: Netlink: filter function error Jan 22 23:41:19 systemd-sysctl[23246]: Overwriting earlier assignment of kernel/shmmax in file '/etc/sysctl.d/99-sysctl.conf'. Jan 22 23:41:19 systemd-sysctl[23246]: Overwriting earlier assignment of kernel/shmall in file '/etc/sysctl.d/99-sysctl.conf'. Jan 22 23:41:19 systemd-sysctl[23246]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/99-sysctl.conf'. Roberto -----Original Message----- From: tinc [mailto:tinc-bounces at tinc-vpn.org] On Behalf Of Guus Sliepen Se...

...atabase 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 high because kernel shmmax and shmall were t...

Hi, Anybody have success with postgresql 8.1.3 on a new Intel OS X box? All hints welcome, please! I installed postgres 8.1.3 via darwinports, and everything is great until the initdb step. Initdb fails on shmget saying it couldn''t allocate enough memory (see below). So, I edited /etc/rc and increased kern.sysv.shmmax from 4194304 to 41943040 (4MB to 40MB) After reboot and

In CentOS 6.7, if I start emacs from a terminal session, I always see a message, "(emacs:{PID}): Gdk-WARNING **: shmget failed: error 28 (No space left on device)" The message is also logged to .xsession-errors, and that occurs regardless of how emacs is started. The same thing occurs with SELinux in permissive mode. Emacs version is emacs-23.1-28.el6.x86_64 . Output from strace

...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 see what the output is like. Thanks Michael

Greetings, all: OS: CentOS 6.4 x86_64 Kernel: 2.6.32-358.14.1 I could use some assistance with setting up pulse to load balance my dns servers. I've configured tcp and udp port 53 with the piranha gui, set up arptable rules on the real servers and added the virtual ip to the bond0 interface on the real servers, but I'm still having no luck in getting things going. A dig against the

...te. >> 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...

...function error Jan 22 23:14:49 Keepalived_vrrp[1999]: Netlink: filter function error Jan 22 23:14:49 systemd-sysctl[19049]: Overwriting earlier assignment of kernel/shmmax in file '/etc/sysctl.d/99-sysctl.conf'. Jan 22 23:14:49 systemd-sysctl[19049]: Overwriting earlier assignment of kernel/shmall in file '/etc/sysctl.d/99-sysctl.conf'. Jan 22 23:14:49 systemd-sysctl[19049]: Overwriting earlier assignment of kernel/sysrq in file '/etc/sysctl.d/99-sysctl.conf'. Jan 22 23:14:49 tincd[19046]: System call `getaddrinfo' failed: Name or service not known Jan 22 23:14:49 tincd[1...

Hi, I worked with puppet (< 0.25) back in 2008/2009. We were able to deploy 200 servers from scratch and manage them. It worked fine. I''m now with a new customer and I''m pushing Puppet (and I''m also back to puppet on a side project). We''re considering Puppet 2.6 to manage RHEL/CentOS 5 or 6 hosts. I''m "upgrading myself" to Puppet

...temd: 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 >>>...

...1 error: "net.bridge.bridge-nf-call-ip6tables" is an unknown key error: "net.bridge.bridge-nf-call-iptables" is an unknown key error: "net.bridge.bridge-nf-call-arptables" is an unknown key kernel.msgmnb = 65536 kernel.msgmax = 65536 kernel.shmmax = 68719476736 kernel.shmall = 4294967296 I switched the cables and switches, and changed the connection with the public internet. Can anybody offer some advise on this? Greetings, J. -- Johan Vermeulen IT-medewerker Caw De Kempen Opensource Software is the future.