From: | kay <efesar(at)nmia(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: PG 7.1.2 Crash: cannot read xlog dir |
Date: | 2003-06-05 22:07:17 |
Message-ID: | NGBBKFMOILMAGDABPFEGCEPDENAA.efesar@nmia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Tom,
Thanks for the advice. I realize your concern, but it turns out there was a
simple solution. I'd like to share that solution with the list, since the
solution I received was not posted on the list. Since "VDS" servers are
becoming more popular by the day, this might be useful to some other admins
in the future.
> Please contact your ISP. There is a bug in the "VDS" jail that
> causes this behavior.
> The solution is to create the soft link in the /dev of the VDS
> linking console to null:
> cd /dev; ln -s null console
> You can not do this , your ISP has to do it for you.
It worked perfectly. Thanks to Jefim Matskin for this solve.
-Keith
> -----Original Message-----
> From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
> Sent: Sunday, June 01, 2003 9:30 AM
> To: kay
> Cc: pgsql-admin(at)postgresql(dot)org
> Subject: Re: [ADMIN] PG 7.1.2 Crash: cannot read xlog dir
>
>
> kay <efesar(at)nmia(dot)com> writes:
> > Please keep in mind my hands are tied, and I can't recompile and I can't
> > upgrade.
> > If anybody can think of a workaround I'd really appreciate it.
>
> Find another ISP. You should not be having to work around broken system
> software, and you certainly aren't going to be able to do so without
> recompiling.
>
> regards, tom lane
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Alex.H.Pollock | 2003-06-05 23:38:02 | Diagnose Database Corruption |
Previous Message | Robert Treat | 2003-06-05 21:41:54 | Re: Error while loading external data into Postgres table |