can anyone help me I am getting that message on ubuntu I installed Ubuntu on my
nexus 6 phone
# service postgresql start
[] Starting PostgreSQL 9.4 database server: main[] The PostgreSQL
server failed to start. Please check the log output: 2016-04-01 15:06:57 UTC
[31454-1] FATAL: could
On 3 March 2014 13:27, Sorin Sbârnea wrote:
> I have the same problem with latest LTS Ubuntu, and the proper solution
> is to set BOTH SHMMAX and SHMALL to the same value, the best is ¼ of
> total memory.
>
> kernel.shmmax = xxx
> kernel.shmall = xxx
>
> Still, I would consider this an real bug,
I have the same problem with latest LTS Ubuntu, and the proper solution
is to set BOTH SHMMAX and SHMALL to the same value, the best is ¼ of
total memory.
kernel.shmmax = xxx
kernel.shmall = xxx
Still, I would consider this an real bug, especially because the
postgres error is misleading and inco
This just started happening to me in 12.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/264336
Title:
pgsql fails to start due to shared buffer setting greater than kernel
allows
To manage noti
This is still not fixed. I just installed postgresql-9.1 on a brand new
installation of Ubuntu 13.04 (64-bit) and received the following error
when attempting to start the server:
* Starting PostgreSQL 9.1 database server
* The PostgreSQL server failed to start. Please check the log outp
** Package changed: postgresql-8.4 (Ubuntu) => postgresql-9.1 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/264336
Title:
pgsql fails to start due to shared buffer setting greater than kern
** Changed in: postgresql-8.3 (Ubuntu)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/264336
Title:
pgsql fails to start due to shared buffer setting greater tha
** Changed in: postgresql-8.4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/264336
Title:
pgsql fails to start due to shared buffer setting greater than kern
** Changed in: postgresql-8.3 (Ubuntu)
Assignee: Martin Pitt (pitti) => (unassigned)
** Changed in: postgresql-8.4 (Ubuntu Jaunty)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchp
Confirmed on Ubuntu 9.10 and postgresql-8.4.
workaround:
cd /etc/init.d
sudo update-rc.d -f postgresql-8.4 remove
sudo update-rc.d postgresql-8.4 defaults
This changed the scripts in /etc/rc*.d from S19 to S20.
Solution thus similar to
https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug
As previously indicated the default configuration is unchanged since
hardy at least. The value can be simply changed in a persistant way,
and application which rely on it being higher likely should document
this and/or supply a sysctl configration to up it. Closing the kernel
task.
** Changed in
I have the same problem in Ubuntu 10.4.
I execute /etc/init.d/postgresql-8.4 start
and the error is:
* The PostgreSQL server failed to start. Please check the log output:
2010-09-06 09:44:00 CEST FATAL: could not create shared memory segment:
Argomento non valido
2010-09-06 09:44:00 CEST DETAI
It does appear that these errors are triggered due to the per-segment
limit being 32MB. People can work round this by either reducing the
size of the segment in their application or by increasing the kernel
limit using sysctl, this can be made permenant using files in
/etc/sysctl.d. These should
reopening the kernel task per discussion with Colin.
** Changed in: linux (Ubuntu)
Status: Invalid => Triaged
** Changed in: linux (Ubuntu)
Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned)
** Tags added: kernel-core kernel-needs-review
--
pgsql fails to start
** Changed in: linux (Ubuntu)
Assignee: Colin King (colin-king) => Canonical Kernel Team
(canonical-kernel-team)
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member
Just had the same issue with 10.04 Lucid and Postgres-8.4. Never saw it
before.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
I had the same issue with Debian squeeze and PostgreSQL today. The
solution was to add a line: kernel.shmmax = 41943040 to file
/etc/sysctl.conf . Maybe it will help you.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You re
Now the problem is back again on 9.10 and postgres-8.4.
I am willing to give complete ssh-access (with sudo previleges) to a
server to however believe they have the capabilities to investigate and
solve this issues.
Jarl
** Also affects: postgresql-8.4 (Ubuntu)
Importance: Undecided
St
getting the same with 9.10 and postgres-8.4, too
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs maili
I have this problem on jaunty. Postgres would not start when the server
starts, but it will start when I do it manually. We have vmware server
installed. I tried preventing vmware server from auto starting and also
tried the S19 -> S20 workaround, but neither worked. We then followed
this advic
I have now created /etc/sysctl.d/90-postgres.conf with the following content:
kernel.shmmax = 41943040
to increase it to 40MB, this seems to have solved the problem in my
situation. Increasing kernel.shmall to 1GB did not make any difference.
--
pgsql fails to start due to shared buffer setting
@Morten Minke, Could you post the exact content of your
/etc/sysctl.d/90-postgres.conf workaround? Please? As it seems that I am
now also hit by this bug in a way that I cannot start postgresql at
all...
@Martin, how do you want to take this bug forward? Dit the discussion
with upstream PostgreSQL
Now (probably after upgrading to kernel 2.6.28-14) postgres will no
longer start, not even when I try to start it manually with sudo
/etc/init.d/postgresql-8.3 start, it complains with
2009-08-06 10:55:59 CEST FATAL: could not create shared memory segment:
Invalid argument
2009-08-06 10:55:59 CE
As pre request
(https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/387682/comments/4)
> You can confirm that "sudo mv /etc/rc2.d/S19postgresql-8.3
> /etc/rc2.d/S20postgresql-8.3" reliably fixes the problem?
Yes, "sudo mv /etc/rc2.d/S19postgresql-8.3 /etc/rc2.d/S20postgresql-8.3"
relia
I forgot the ouput of "ls -l /etc/rc2.d/S19*" (after I have "sudo mv
/etc/rc2.d/S19postgresql-8.3 /etc/rc2.d/S20postgresql-8.3"):
lrwxrwxrwx 1 root root 15 2009-06-11 19:39 /etc/rc2.d/S19mysql ->
../init.d/mysql
lrwxrwxrwx 1 root root 16 2009-05-06 13:24 /etc/rc2.d/S19vmware ->
../init.d/vmware
By the way here is the output of ls -l /etc/rc2.d/S19*
I have vmware workstation installed!
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is
As pre request
(https://bugs.launchpad.net/ubuntu/+source/postgresql-8.3/+bug/387682/comments/4)
$ ls -l /etc/rc2.d/S20*
gives
lrwxrwxrwx 1 root root 16 2009-05-06 11:26 /etc/rc2.d/S20apport ->
../init.d/apport
lrwxrwxrwx 1 root root 28 2009-05-06 12:24 /etc/rc2.d/S20dkms_autoinstaller ->
../i
** Changed in: postgresql-8.3 (Ubuntu)
Importance: Undecided => High
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: postgresql-8.3 (Ubuntu)
Status: New => Confirmed
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Thanks Colin for confirming. I'll discuss it with the upstream
PostgreSQL guys.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: postgresql-8.3 (Ubuntu)
Status: Won't Fix => New
** Changed in: postgresql-8.3 (Ubuntu)
Assignee: (unassigned) => Martin P
@Martin, how do you want to take this bug forward?
** Changed in: linux (Ubuntu)
Status: New => Incomplete
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of
@Martin,
>do we change the default SHM* parameters in any way, or are we using current
>upstream's? If the latter,
> I'll go back to discuss it with upstream. If the former, what was the reason
> for this? Thanks!
> (Assigning mainly to get your input; feel free to unassign/WONTFIX as you see
sorry, we do not need a fancy error handler in postgresql-common, since
a failed startup already logs the reason for the failure.
** Changed in: postgresql-common (Ubuntu Jaunty)
Status: In Progress => Invalid
** Changed in: postgresql-common (Ubuntu Jaunty)
Assignee: Martin Pitt (pit
What we should do here, though, is to not make package installation fail
if cluster startup fails. This involves creating an error handler in
postgresql-common and telling postgresql-8.3's init script to use it.
** Changed in: postgresql-common (Ubuntu Jaunty)
Importance: Undecided => High
**
Morten Minke [2009-04-01 11:03 -]:
> I have added a file:
>
> /etc/sysctl.d/90-postgres.conf
>
> in which I have changed the kernel settings for shmmax to make postgres
> run correctly.
That's fine.
> Isn't this why this folder was created, to make individual packages
> change the configura
I have added a file:
/etc/sysctl.d/90-postgres.conf
in which I have changed the kernel settings for shmmax to make postgres
run correctly.
Isn't this why this folder was created, to make individual packages
change the configurations according to their needs?
I do not get exactly why this would
I have set SHMALL to 1GB & it's ok now.
thx
2009/4/1 Martin Pitt
> I thought about this problem a little, and also discussed it with
> upstream. Basically, we have four options:
>
> (1) Ignore
>+ no hidden magic
>- very inconvenient, package installation does not create default
> cl
Kernel team,
do we change the default SHM* parameters in any way, or are we using
current upstream's? If the latter, I'll go back to discuss it with
upstream. If the former, what was the reason for this? Thanks!
(Assigning mainly to get your input; feel free to unassign/WONTFIX as
you see fit).
I thought about this problem a little, and also discussed it with
upstream. Basically, we have four options:
(1) Ignore
+ no hidden magic
- very inconvenient, package installation does not create default
cluster sometimes, or the default cluster fails to start on
system boot
Reduced shared_buffers and postgresql starts now without problems Ubuntu
Intrepid updated today.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which
I started a discussion upstream.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
Hit by the same problem. Reduced shared_buffers and postgresql started.
Jaunty x86_64.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I increase kernel.shmmax to 40 mb and now postgresql starts.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
I rebooted my machine with some logging in the postgres startup script.
[at boot time]
$ ipcs -m
-- Shared Memory Segments
keyshmid owner perms bytes nattch status
$ sysctl -a | grep -i shm
kernel.shmmax = 33554432
kernel.shmall = 2097152
kernel.
Like what aardvark told, I too have the same situation.
At boot time I get the error, but if I later start the service manually
(/etc/init.d/postgresql-8.3 start) the postgres db starts without
errors.
For me it seems that when the postgres service is started at boot time,
the shm parameters are
** Changed in: postgresql-common (Ubuntu)
Importance: Medium => High
Assignee: (unassigned) => Martin Pitt (pitti)
Status: Confirmed => Triaged
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this b
Ah, seems that X.org is taking away tons of shared memory.
So, the failure message should make this clear enough, but I'll keep
this open as a reminder to investigate the possibility of automatically
configuring smaller SHM limits in postgresql.conf.
** Changed in: postgresql-common (Ubuntu)
I
And the lsof
** Attachment added: "lsof.txt"
http://launchpadlibrarian.net/22650602/lsof.txt
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which
Ok here are the outputs of my ipcs and lsof.
** Attachment added: "ipcs"
http://launchpadlibrarian.net/22650544/ipcs_output.txt
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you
Yes. I just changed the shared_buffers to 24 megs and Postgresql now
starts. So I guess that fixed it.
Thanks.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubu
This is a default setting in postgresql-8.x, and since the error message
is very clear, this will not be fixed in the upstream code itself. We
could give some more clever defaults in pg_createcluster (in postgresql-
common), so I keep the -common task open and close the -8.3 task.
** Changed in: p
I guess not, since I get the very same settings under 9.04/i386 as
Richard describes in the original description.
So I guess there are some other programs running on your boxes which use
shared memory a lot. Can you please give me the output of
sudo ipcs -m
and do
sudo lsof > /tmp/lsof.txt
Did anyone of you tweak the default shm limits? I newer saw this problem
on my boxes.
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
I get exactly the same error with nearly the same parameters:
2009-02-07 08:34:38 CET FATAL: could not create shared memory segment: Invalid
argument
2009-02-07 08:34:38 CET DETAIL: Failed system call was shmget(key=5432001,
size=39288832, 03600).
2009-02-07 08:34:38 CET HINT: This error usual
I can replicate in my install. Please upgrade to critical; it's hit a
few production servers. Yikes!
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, w
I don't know if it is really the same issue, I haven't the "SHMAX" comment, but
the rest seems similar on a installing postgres, I've got :
Paramétrage de postgresql-8.3 (8.3.5-0ubuntu8.10) ...
* Starting PostgreSQL 8.3 database server * The PostgreSQL server failed to
start. Please check the l
Automatic upgrades on Ubuntu 8.10 i386 desktop failed with:
Setting up postgresql-8.3 (8.3.5-0ubuntu8.10) ...
* Starting PostgreSQL 8.3 database server
* The PostgreSQL server failed to
This happens for me too in Intrepid on AMD64, except pgsql attempts to
allocate 40MB while the shmax setting is still 32MB.
2008-11-02 00:31:09 GMT FATAL: could not create shared memory segment: Invalid
argument
2008-11-02 00:31:09 GMT DETAIL: Failed system call was shmget(key=5432001,
size=39
** Changed in: postgresql-common (Ubuntu)
Sourcepackagename: postgresql-8.3 => postgresql-common
--
pgsql fails to start due to shared buffer setting greater than kernel allows
https://bugs.launchpad.net/bugs/264336
You received this bug notification because you are a member of Ubuntu
Bugs, which
59 matches
Mail list logo
