openssh unix dev - Jun 2001 - WARNING: putuserattr SEC_COMMIT failed: A file or directory

hi,
I am taking an error like this while loging into a AIX 4.3.3 on ssh 2.4.0

WARNING: putuserattr SEC_COMMIT failed: A file or directory in the path
name does not exist.

is there any one knowing why this happens or do you know anybody who can
tell me why it happens ?

thanks in advance .

On Fri, Jun 08, Genco Yilmaz wrote:
> hi,
> I am taking an error like this while loging into a AIX 4.3.3 on ssh 2.4.0
> 
> WARNING: putuserattr SEC_COMMIT failed: A file or directory in the path
> name does not exist.
> 
> is there any one knowing why this happens or do you know anybody who can
> tell me why it happens ?
What exactly are you trying to do ? connect to AIX server(running the
commercial ssh 2.4.0) ? How is this related to OpenSSH ? Are you using
openssh client and the server error happens only when connecting with
openssh-client ?

-Jarno

-- 
Jarno Huuskonen - System Administrator   |  Jarno.Huuskonen at uku.fi

Hello,

     I'm going on memory here. I remember seeing this problem
when you /etc/security/lastlog file is corrupted. As a test, backup and
truncate you lastlog file. Commands similar to:

cp /etc/security/lastlog /etc/security/lastlog.saveme
cp /dev/null /etc/security/lastlog

If this works.. I have no idea what process corrupts the lastlog
file..

Good Luck,

EdGy


Jarno Huuskonen <Jarno.Huuskonen at uku.fi>@mindrot.org on 06/08/2001
05:54:28

Sent by:  owner-openssh-unix-dev at mindrot.org


To:   openssh-unix-dev at mindrot.org
cc:
Subject:  Re: WARNING: putuserattr SEC_COMMIT failed: A file or directory



On Fri, Jun 08, Genco Yilmaz wrote:
> hi,
> I am taking an error like this while loging into a AIX 4.3.3 on ssh 2.4.0
>
> WARNING: putuserattr SEC_COMMIT failed: A file or directory in the path
> name does not exist.
>
> is there any one knowing why this happens or do you know anybody who can
> tell me why it happens ?
What exactly are you trying to do ? connect to AIX server(running the
commercial ssh 2.4.0) ? How is this related to OpenSSH ? Are you using
openssh client and the server error happens only when connecting with
openssh-client ?

-Jarno

--
Jarno Huuskonen - System Administrator   |  Jarno.Huuskonen at uku.fi