| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Martín Marqués <martin(at)2ndquadrant(dot)com> |
| Cc: | Graeme Gemmill <graeme(at)gemmill(dot)name>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: pgsql in a virtual environment |
| Date: | 2014-05-16 15:51:46 |
| Message-ID: | 14127.1400255506@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?UTF-8?B?TWFydMOtbiBNYXJxdcOpcw==?= <martin(at)2ndquadrant(dot)com> writes:
> 2014-05-16 11:56 GMT-03:00 Graeme Gemmill <graeme(at)gemmill(dot)name>:
>> $ ./pg_ctl start -D /mnt/post/pgsql/data &
>> [1] 3692
>> [postgres(at)localhost bin]$ pg_ctl: could not open PID file
>> "/mnt/post/pgsql/data/postmaster.pid": Protocol error
> Looks like a libpq - backend server mismatch.
No --- pg_ctl is trying to read the postmaster's PID file, and it's
getting some bizarre error from fopen(). I have no idea exactly what
"Protocol error" might mean in this context. It would make some sense
if the data directory were on NFS or other network-based file system,
but otherwise it's kind of weird.
Anyway this is a filesystem problem. libpq is not involved. I would
venture that it's either a kernel bug or some misconfiguration of the
virtual environment. The fix is below Postgres' level, for sure.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | J Adams | 2014-05-16 16:07:40 | Monitoring Streaming Replication in 9.2 |
| Previous Message | image | 2014-05-16 15:41:55 | Re: Psycopg2 : error message. |