Thread: lost synchronization with server: got message type "Z"
Hello,
From time to time we receive following event from application (Adobe Campaign - former Neolane):
PostgreSQL error: lost synchronization with server: got message type "Z", length 0\n (iRc=-2006)
Last time underlying sql statement was an update.
At the backend side there is:
LOG: unexpected EOF on client connection with an open transaction
From http://doxygen.postgresql.org/fe-protocol3_8c_source.html#l00450 I can read:
444 /*
445 * handleSyncLoss: clean up after loss of message-boundary sync
446 *
447 * There isn't really a lot we can do here except abandon the connection.
448 */
Could something else than network cause this event?
PostgreSQL version:
postgres=# select version();
version
----------------------------------------------------------------------------------------------------------------
PostgreSQL 9.2.13 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7 20120313 (Red Hat 4.4.7-11), 64-bit
(1 row)
Thank you
Marek
"Marek Petr" <maper@seznam.cz> writes:
> From time to time we receive following event from application (Adobe
> Campaign - former Neolane):
> PostgreSQL error: lost synchronization with server: got message type "Z",
> length 0\n (iRc=-2006)
Hm.
> Could something else than network cause this event?
We've fixed bugs with related symptoms in the past.
> postgres=# select version();
> PostgreSQL 9.2.13 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7
> 20120313 (Red Hat 4.4.7-11), 64-bit
What libpq version is being used on the client side? The most recent
related bugfix I can find in the 9.2 commit history was in libpq, and
it came out in 9.2.8.
regards, tom lane
Thank you for the response.
Remote psql client (application server) version is 9.2.16 and pg_lib_version function of DBD::Pg module returned version 80412.
Remove connection via psql client:
$ psql
psql (9.2.16, server 9.2.13)
Type "help" for help.
postgres=#
PQlibVersion function of libpq returned version 90213 at database server where 9.2.13 is running version of PostgreSQL.
Could it be caused by older still installed release at database server (see below)?
# yum list installed postgres\*
Loaded plugins: product-id, rhnplugin, security, subscription-manager
This system is receiving updates from RHN Classic or RHN Satellite.
Installed Packages
postgresql.x86_64 8.4.20-6.el6 @rhel-x86_64-server-6
postgresql-libs.x86_64 8.4.20-6.el6 @rhel-x86_64-server-6
postgresql-server.x86_64 8.4.20-6.el6 @rhel-x86_64-server-6
postgresql92.x86_64 9.2.13-1PGDG.rhel6 @/postgresql92-9.2.13-1PGDG.rhel6.x86_64
postgresql92-libs.x86_64 9.2.13-1PGDG.rhel6 @/postgresql92-libs-9.2.13-1PGDG.rhel6.x86_64
postgresql92-server.x86_64 9.2.13-1PGDG.rhel6 @/postgresql92-server-9.2.13-1PGDG.rhel6.x86_64
Regards
Marek
---------- Původní zpráva ----------
Od: Tom Lane <tgl@sss.pgh.pa.us>
Komu: Marek Petr <maper@seznam.cz>
Datum: 27. 9. 2016 14:55:44
Předmět: Re: [GENERAL] lost synchronization with server: got message type "Z"
"Marek Petr" <maper@seznam.cz> writes:
> From time to time we receive following event from application (Adobe
> Campaign - former Neolane):
> PostgreSQL error: lost synchronization with server: got message type "Z",
> length 0\n (iRc=-2006)
Hm.
> Could something else than network cause this event?
We've fixed bugs with related symptoms in the past.
> postgres=# select version();
> PostgreSQL 9.2.13 on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.4.7
> 20120313 (Red Hat 4.4.7-11), 64-bit
What libpq version is being used on the client side? The most recent
related bugfix I can find in the 9.2 commit history was in libpq, and
it came out in 9.2.8.
regards, tom lane
"Marek Petr" <maper@seznam.cz> writes:
> Remote psql client (application server) version is 9.2.16 and pg_lib_version
> function of DBD::Pg module returned version 80412.
Ouch. 8.4.x has been out of support for almost two years now, and 8.4.12
is a good four years old. You should try to get an up-to-date version of
libpq and see if that doesn't make things better.
Note that I never heard of "Adobe Campaign" before, and have no idea what
it would take to link it against a newer libpq. You might have to get
Adobe involved, unless it goes through DBD::Pg.
regards, tom lane