Re: Unable to connect to a dabase

Please do group replies so the list gets cc'd.

> From: Sally Sally [mailto:dedeb17(at)hotmail(dot)com]
> The main reason I decided to kill the vacuum was because
> there were several
> postmaster processes spewed from scripts trying to access the
> database and
> they were all hanging. After killing the vacuum I decided to
> restart the
> server. However because of the hanging processes it was not
> letting me shut
> down so I had to kill the postmaster processes. The log gave
> a warning about
> shared memory corruption at this point. After this I started
> the postmaster
> did a proper shut down and restarted again. Now when I try to
> connect to the
> db it just hangs and there are no logs.
>
> The last log was
> LOG: database system was shut down at 2006-01-13 18:04:05 EST
> LOG: checkpoint record is at 505/C80F1010
> LOG: redo record is at 505/C80F1010; undo record is at 0/0;
> shutdown TRUE
> LOG: next transaction ID: 1341794294; next OID: 1358710904
> LOG: database system is ready

Well, that looks like a clean startup. I'm not sure if anyone else on the list has any ideas. Maybe getting a stack trace of psql trying to connect would shed some light...

Does a backend get spawned when you try running psql? (Look at ps aux|grep postgres before and after running psql).

> >From: "Jim C. Nasby" <jnasby(at)pervasive(dot)com>
> >To: Sally Sally <dedeb17(at)hotmail(dot)com>
> >CC: pgsql-general(at)postgresql(dot)org
> >Subject: Re: [GENERAL] Unable to connect to a dabase
> >Date: Fri, 13 Jan 2006 16:55:16 -0600
> >
> >Please don't hijack threads fo new questions.
> >
> >On Fri, Jan 13, 2006 at 10:45:51PM +0000, Sally Sally wrote:
> > > I had to kill a vacuum in the middle with -9. I shut down
> and restarted
> >the
> > > postgres server several times after that but I am unable
> to connect to
> >the
> > > db that I was initially running vacuum on
> > > I'm doing "psql dbname" and it hangs for a while. I'm
> still waiting. Any
> > > ideas?
> >
> >What's the logfile say about it?
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461