Thread: 7.4.5 stopped working?

7.4.5 stopped working?

From
Klint Gore
Date:
I had the latest cygwin postgres (as of yesterday) working when I went
home last night and this morning I cant start the postmaster.  I cant
think of anything that changed.

$ uname -a
CYGWIN_NT-5.0 kgb 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin

$ postmaster --version
postmaster (PostgreSQL) 7.4.5

cygserver starts and stays running.  last night it was a process and
thats how I started it this morning.  in trying to work out what's
happening, i've installed the service now.

$ /usr/sbin/cygserver --version
cygserver: (cygwin) 1.10
API version 1.5.11(0.116/4/1)-(3.0.0.2) 2004-09-04 23:17
Copyright 2001, 2002, 2003 Red Hat, Inc.
Compiled on Sep  4 2004

when I try to start the postmaster using
   pg_ctl -D /usr/local/pgsql/data -l /var/log/pgsql/logfile start
it just exits straight away.

with normal logging the log file is empty.  with debug5 i get the envion
dump followed by
DEBUG:  -----------------------------------------
DEBUG:  found "/usr/bin/postgres" using argv[0]
DEBUG:  invoking IpcMemoryCreate(size=17776640)

config file is default except for (log settings added today after trying
to start failed; this install is just a tempory test so fsync=false is
acceptable)
  tcpip_socket=true
  shared_buffers=2000
  fsync=false
  log_min_messages=debug5
  log_min_error_statement=debug5

initdb was run yesterday with --locale=C

if I run "postmaster -D /usr/local/pgsql/data" i get the same invoking
ipcmemorycreate followed by "Bad system call"

Any ideas?

klint.

+---------------------------------------+-----------------+
: Klint Gore                            : "Non rhyming    :
: EMail   : kg@kgb.une.edu.au           :  slang - the    :
: Snail   : A.B.R.I.                    :  possibilities  :
: Mail      University of New England   :  are useless"   :
:           Armidale NSW 2351 Australia :     L.J.J.      :
: Fax     : +61 2 6772 5376             :                 :
+---------------------------------------+-----------------+

Re: 7.4.5 stopped working?

From
"Mike G."
Date:
Have you tried rebooting?  That error message usually happens when cygwin requests resouces from windows and fails.

 If you upgraded from a version prior to 7.4.2 then it is looking for the cygserver service to be running and in your
path.

 Mike
>
> On Tue, Sep 21, 2004 at 10:38:43AM +1000, Klint Gore wrote:
> > I had the latest cygwin postgres (as of yesterday) working when I went
> > home last night and this morning I cant start the postmaster.  I cant
> > think of anything that changed.
> >
> > $ uname -a
> > CYGWIN_NT-5.0 kgb 1.5.11(0.116/4/2) 2004-09-04 23:17 i686 unknown unknown Cygwin
> >
> > $ postmaster --version
> > postmaster (PostgreSQL) 7.4.5
> >
> > cygserver starts and stays running.  last night it was a process and
> > thats how I started it this morning.  in trying to work out what's
> > happening, i've installed the service now.
> >
> > $ /usr/sbin/cygserver --version
> > cygserver: (cygwin) 1.10
> > API version 1.5.11(0.116/4/1)-(3.0.0.2) 2004-09-04 23:17
> > Copyright 2001, 2002, 2003 Red Hat, Inc.
> > Compiled on Sep  4 2004
> >
> > when I try to start the postmaster using
> >    pg_ctl -D /usr/local/pgsql/data -l /var/log/pgsql/logfile start
> > it just exits straight away.
> >
> > with normal logging the log file is empty.  with debug5 i get the envion
> > dump followed by
> > DEBUG:  -----------------------------------------
> > DEBUG:  found "/usr/bin/postgres" using argv[0]
> > DEBUG:  invoking IpcMemoryCreate(size=17776640)
> >
> > config file is default except for (log settings added today after trying
> > to start failed; this install is just a tempory test so fsync=false is
> > acceptable)
> >   tcpip_socket=true
> >   shared_buffers=2000
> >   fsync=false
> >   log_min_messages=debug5
> >   log_min_error_statement=debug5
> >
> > initdb was run yesterday with --locale=C
> >
> > if I run "postmaster -D /usr/local/pgsql/data" i get the same invoking
> > ipcmemorycreate followed by "Bad system call"
> >
> > Any ideas?
> >
> > klint.
> >
> > +---------------------------------------+-----------------+
> > : Klint Gore                            : "Non rhyming    :
> > : EMail   : kg@kgb.une.edu.au           :  slang - the    :
> > : Snail   : A.B.R.I.                    :  possibilities  :
> > : Mail      University of New England   :  are useless"   :
> > :           Armidale NSW 2351 Australia :     L.J.J.      :
> > : Fax     : +61 2 6772 5376             :                 :
> > +---------------------------------------+-----------------+
> >
> > ---------------------------(end of broadcast)---------------------------
> > TIP 9: the planner will ignore your desire to choose an index scan if your
> >       joining column's datatypes do not match

Re: 7.4.5 stopped working?

From
Reini Urban
Date:
Klint Gore schrieb:
> with normal logging the log file is empty.  with debug5 i get the envion
> dump followed by
> DEBUG:  -----------------------------------------
> DEBUG:  found "/usr/bin/postgres" using argv[0]
> DEBUG:  invoking IpcMemoryCreate(size=17776640)

not enough shared memory.
you might need to increase the buffer size or number of buffers.

> if I run "postmaster -D /usr/local/pgsql/data" i get the same invoking
> ipcmemorycreate followed by "Bad system call"

either ipcclean will help or you have to restart cygserver.
ipcs shows your ipc status.

--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: 7.4.5 stopped working?

From
Klint Gore
Date:
On Tue, 21 Sep 2004 12:24:01 +0200, Reini Urban <rurban@x-ray.at> wrote:
> Klint Gore schrieb:
> > with normal logging the log file is empty.  with debug5 i get the envion
> > dump followed by
> > DEBUG:  -----------------------------------------
> > DEBUG:  found "/usr/bin/postgres" using argv[0]
> > DEBUG:  invoking IpcMemoryCreate(size=17776640)
>
> not enough shared memory.
> you might need to increase the buffer size or number of buffers.

It was working with this setting.


> > if I run "postmaster -D /usr/local/pgsql/data" i get the same invoking
> > ipcmemorycreate followed by "Bad system call"
>
> either ipcclean will help or you have to restart cygserver.
> ipcs shows your ipc status.

$ ipcclean
Signal 12

$ ipcs
Bad system call

What could this mean?

klint
(my linux test server is back so I dont need to fix this, but it'd be
interesting to find out what happened).

+---------------------------------------+-----------------+
: Klint Gore                            : "Non rhyming    :
: EMail   : kg@kgb.une.edu.au           :  slang - the    :
: Snail   : A.B.R.I.                    :  possibilities  :
: Mail      University of New England   :  are useless"   :
:           Armidale NSW 2351 Australia :     L.J.J.      :
: Fax     : +61 2 6772 5376             :                 :
+---------------------------------------+-----------------+

Re: 7.4.5 stopped working?

From
Reini Urban
Date:
Klint Gore schrieb:
>>>if I run "postmaster -D /usr/local/pgsql/data" i get the same invoking
>>>ipcmemorycreate followed by "Bad system call"
>>
>>either ipcclean will help or you have to restart cygserver.
>>ipcs shows your ipc status.
>
> $ ipcclean
> Signal 12
>
> $ ipcs
> Bad system call
>
> What could this mean?

That cygserver is not running.
I also experience dying postmaster's during the night. Wonder if a
ipcclean cronjob will help, or increasing memory.
--
Reini Urban
http://xarch.tu-graz.ac.at/home/rurban/

Re: 7.4.5 stopped working? [solved]

From
Klint Gore
Date:
On Wed, 22 Sep 2004 11:33:24 +0200, Reini Urban <rurban@x-ray.at> wrote:
> Klint Gore schrieb:
> >>>if I run "postmaster -D /usr/local/pgsql/data" i get the same invoking
> >>>ipcmemorycreate followed by "Bad system call"
> >>
> >>either ipcclean will help or you have to restart cygserver.
> >>ipcs shows your ipc status.
> >
> > $ ipcclean
> > Signal 12
> >
> > $ ipcs
> > Bad system call
> >
> > What could this mean?
>
> That cygserver is not running.

it is running according to ps

$ ps
      PID    PPID    PGID     WINPID  TTY  UID    STIME COMMAND
     1660       1    1660       1660  con 1006 09:35:28 /usr/bin/bash
      564       1     564        564  con 1006 10:12:14 /usr/bin/bash
      988     564     988        932  con 1006 10:12:20 /usr/X11R6/bin/XWin
      964     564     964       1896  con 1006 10:12:40 /usr/bin/ssh
     1704    1660    1704       1288  con 1006 10:14:51 /usr/sbin/cygserver
     1868    1660    1868       1944  con 1006 10:14:55 /usr/bin/ps

found it. "cygwin" environment variable not set to "server".

klint.

+---------------------------------------+-----------------+
: Klint Gore                            : "Non rhyming    :
: EMail   : kg@kgb.une.edu.au           :  slang - the    :
: Snail   : A.B.R.I.                    :  possibilities  :
: Mail      University of New England   :  are useless"   :
:           Armidale NSW 2351 Australia :     L.J.J.      :
: Fax     : +61 2 6772 5376             :                 :
+---------------------------------------+-----------------+