Skip site navigation (1) Skip section navigation (2)

Re: BUG #5121: Segmentation Fault when using pam w/ krb5

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Ryan Douglas <rdouglas(at)arbinet(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5121: Segmentation Fault when using pam w/ krb5
Date: 2009-10-15 21:22:32
Message-ID: 4AD79298.5030107@enterprisedb.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Ryan Douglas wrote:
> The following bug has been logged online:
> 
> Bug reference:      5121
> Logged by:          Ryan Douglas
> Email address:      rdouglas(at)arbinet(dot)com
> PostgreSQL version: 8.4.1
> Operating system:   Fedora 11
> Description:        Segmentation Fault when using pam w/ krb5
> Details: 
> 
> Whenever I use psql to remotely connect to the database the server crashes
> (see log below). If I use psql with the '-W' option then it's fine. 
> 
> I also tested with pam_tacplus.so and in both cases the db didn't crash. It
> just complained about not having credentials to authenticate when the -W
> option is not used.
> 
> I can reproduce at will so let me know if you need more information.

Can you get a stack trace with gdb? Something along the lines of:

ulimit -c unlimited
(start postmaster)
(reproduce the crash)
gdb /usr/bin/postgres $PGDATA/core
bt

-- 
  Heikki Linnakangas
  EnterpriseDB   http://www.enterprisedb.com

In response to

Responses

pgsql-bugs by date

Next:From: Tom LaneDate: 2009-10-15 21:33:17
Subject: Re: BUG #5120: Performance difference between running a query with named cursor and straight SELECT
Previous:From: Tom LaneDate: 2009-10-15 21:19:38
Subject: Re: BUG #5121: Segmentation Fault when using pam w/ krb5

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group