|
Home > Archive > Slony1 PostgreSQL Replication > September 2005 > Postgresql crashes when running slony on FreeBSD.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Postgresql crashes when running slony on FreeBSD.
|
|
| Dennis Jenkins 2005-09-07, 8:25 pm |
| Hello.
Two of our postgresql database servers crash
(both are provider nodes) when starting up the slony
daemon. We use FreeBSD 5.4, Postgresql 8.0.1 (two are
8.0.3) and Slony 1-1.1.0_1. All binaries are compiled
with gcc 3.2.4.
I have posted a highly detailed description of
the system setup, including version info, config
files, stack traces from core dumps, output of "ldd
postmaster", slonik scripts, pg_hba.conf and
postgresql.conf files online [1]
The crash seems to be related to using an SSL
connection. The postmaster process doesn't die if I
disable SSL (which I can't do for security reasons).
Does anyone have any suggestions on what to try
to make the system work properly?
Has anyone observed a problem like this before?
Is there any more data that I can provide to
assist with diagnosis?
Any help would be greatly appreciated.
[1] http://unwg.no-ip.com/postgresql_crash.html
Dennis Jenkins
| |
| Darcy Buskermolen 2005-09-07, 8:25 pm |
| On Wednesday 07 September 2005 14:41, Dennis Jenkins wrote:
> Hello.
>
> Two of our postgresql database servers crash
> (both are provider nodes) when starting up the slony
> daemon. We use FreeBSD 5.4, Postgresql 8.0.1 (two are
> 8.0.3) and Slony 1-1.1.0_1. All binaries are compiled
> with gcc 3.2.4.
>
> I have posted a highly detailed description of
> the system setup, including version info, config
> files, stack traces from core dumps, output of "ldd
> postmaster", slonik scripts, pg_hba.conf and
> postgresql.conf files online [1]
>
> The crash seems to be related to using an SSL
> connection. The postmaster process doesn't die if I
> disable SSL (which I can't do for security reasons).
>
> Does anyone have any suggestions on what to try
> to make the system work properly?
>
> Has anyone observed a problem like this before?
>
> Is there any more data that I can provide to
> assist with diagnosis?
Does psql using ssl from/to the db's in question work properly? Because slon
and slonik are just libpq apps and this error looks to be coming from within
libpq (pqcomm.c)
>
> Any help would be greatly appreciated.
>
> [1] http://unwg.no-ip.com/postgresql_crash.html
>
> Dennis Jenkins
> ____________________
____________________
_______
> Slony1-general mailing list
> Slony1-general- AuKwsB3Fm+ugFIWk8tvy
RWD2FQJk+8+b@public.gmane.org
> http://gborg.postgresql.org/mailman.../slony1-general
--
Darcy Buskermolen
Wavefire Technologies Corp.
http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759
| |
| Dennis Jenkins 2005-09-08, 11:25 am |
|
--- Darcy Buskermolen <darcy- QSklyHmfoqpWk0Htik3J
/w@public.gmane.org> wrote:
>=20
> Does psql using ssl from/to the db's in question
> work properly? Because slon=20
> and slonik are just libpq apps and this error looks
> to be coming from within=20
> libpq (pqcomm.c)=20
>=20
I ran the following on system A, connecting to system
B. It seemed to work just fine (the query ran over
and over and over). It ran for several minutes with
no crashes. =20
djenkins@A$ while [ "1" =3D=3D "1" ] ; do psql -Uslony
-hB B-DATABASE -c "select count(*), table_name from
audit group by table_name order by 1 desc limit 10;" ;
done
I know that is it using an SSL connection. Host B
won't allow non-SSL at the moment & when I connect
interactively is says "SSL connection (cipher:
DHE-RSA-AES256-SHA, bits: 256)". I could not think of
any other easy way to use libpq to test the
connection.
I could try to craft something in perl. Sometimes I
use DBD::Pg (uses libpq) and other times DBD::PgPP
(implements pgsql protocol in perl, so no libpq).=20
Would this help with the diagnosis?
Dennis Jenkins
|
|
|
|
|