Followup ^2 -
The reason this happened was that for whatever reason (we're still
investigating), /tmp was writeable only by root.
I only noticed this when using initdb to create a new data directory.
postmaster offered no suggestion that there was a problem here, even when
running at -d5.
chmod 777 /tmp fixed everything.
my best guess (I don't know how postmaster is operating, I didn't run any
of the system-level diagnostic tools to check) is that if postmaster fails
on opening a pipe/tmpfile, rather than check the error properly, it
changes the filename and tries again ad infinitum? Perhaps printing some
error code (especially at debug level 5) would help?
thanks,
--pete
On Wed, 18 Jul 2001, Pete Leonard wrote:
>
> As a followup - the line from top:
>
> 1641 postgres 105 0 2684K 1384K CPU1 0 8:26 99.02% 99.02%
> postgres
>
> As you can see, it's barely taking up any RAM - the process is going nuts
> right off the bat..
>
> On Wed, 18 Jul 2001, Pete Leonard wrote:
>
> >
> > Postgres 7.1.2, FreeBSD 3.4
> >
> > Box got sick, had to bounce it. Postgres wasn't brought down in a
> > graceful fashion..
> >
> > restart didn't bring the DB back properly, so as the postgres user, did
> > the following:
> >
> > /usr/local/pgsql/bin/postmaster -d5 start
> >
> > it dumps the initial environment variables, and then returns nothing. CPU
> > is pegged at 100%. No reporting, no information as to what's happening.
> >
> > Solutions? It the DB corrupted badly? Where do I go from here?
> >
> > thanks,
> >
> > --pete
> >
> >
> >
>
>
