3.0.1 and PAM problem

Dieter <netbsd <at> sopwith.solgatos.com>
writes:

> 
> Continuing with the upgrade to 3.0.1:
> 
> I'm getting a *bunch* of error messages logged that
seem to be PAM related,
> for example:
> 
> in openpam_dynamic(): pam_ksu.so: pam_sm_acct_mgmt():
Undefined 
symbol "pam_sm_acct_mgmt"
> in openpam_dynamic(): pam_ksu.so:
pam_sm_open_session(): Undefined 
symbol "pam_sm_open_session"
> in openpam_dynamic(): pam_ksu.so:
pam_sm_close_session(): Undefined 
symbol "pam_sm_close_session"
> in openpam_dynamic(): pam_ksu.so: pam_sm_chauthtok():
Undefined 
symbol "pam_sm_chauthtok"
> 
> Somehow this doesn't give me a warm, cozy feeling.
> 
> I can't search the archives until I get this machine
running properly.
> Please cc me on any response.  Thanks.

We are seeing the same problem here, mostly when doing a
'su'; this is a box 
that has been upgraded from NetBSD 2.0.1. Did you find a
solution yet?


regards,

Derkjan

On 16 Aug 2006, at 12:13, Derkjan wrote:

> Dieter <netbsd <at> sopwith.solgatos.com>
writes:
> 
> > 
> > Continuing with the upgrade to 3.0.1:
> > 
> > I'm getting a *bunch* of error messages logged
that seem to be PAM
> > related, for example:
> > 
> > in openpam_dynamic(): pam_ksu.so:
pam_sm_acct_mgmt(): Undefined 
> symbol "pam_sm_acct_mgmt"
> > in openpam_dynamic(): pam_ksu.so:
pam_sm_open_session(): Undefined 
> symbol "pam_sm_open_session"
> > in openpam_dynamic(): pam_ksu.so:
pam_sm_close_session(): Undefined 
> symbol "pam_sm_close_session"
> > in openpam_dynamic(): pam_ksu.so:
pam_sm_chauthtok(): Undefined 
> symbol "pam_sm_chauthtok"
> > 
> > Somehow this doesn't give me a warm, cozy
feeling.
> > 
> > I can't search the archives until I get this
machine running
> > properly. Please cc me on any response.  Thanks.
> 
> We are seeing the same problem here, mostly when doing
a 'su'; this is
> a box that has been upgraded from NetBSD 2.0.1. Did you
find a
> solution yet?

Isn't this covered in the installation/update instructions 
INSTALL.txt section on upgrading?

I had the same problem and needed to run through the
suggested 
postinstall steps (sorry it was a while back and I don't
have exact 
details at hand). 

David