vmsa security exception: error in pam_auth_acct_mgmt: 13 - Veritas Volume Manager

This is a discussion on vmsa security exception: error in pam_auth_acct_mgmt: 13 - Veritas Volume Manager ; since some days, when starting vmsa (version 3.0.6) and logging in with root gets the error: "user is not authorized to connect to server.(root)" in the /opt/var/vmsa/logs/server.log we got: "SERVER SERVICE Socket: Socket[addr=dei.ic3s.de/192.168.132.32,port=44248,localport=43009] SERVER VxSecureListenerSocket: accepting connection VxServerSvcSocket: closing socket ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: vmsa security exception: error in pam_auth_acct_mgmt: 13

  1. vmsa security exception: error in pam_auth_acct_mgmt: 13


    since some days, when starting vmsa (version 3.0.6) and logging in with root

    gets the error:
    "user is not authorized to connect to server.(root)"

    in the /opt/var/vmsa/logs/server.log we got:
    "SERVER SERVICE Socket: Socket[addr=dei.ic3s.de/192.168.132.32,port=44248,localport=43009]
    SERVER VxSecureListenerSocket: accepting connection
    VxServerSvcSocket: closing socket Socket[addr=dei.ic3s.de/192.168.132.32,port=44248,localport=43009]
    VxServerSvcSocket: creating a server socket for remote port 44277 and local
    port 43009
    receiving client id ...
    user received = root
    sending server challenge ...
    error in pam_auth_acct_mgmt: 13
    VxServerSvcSocket: closing socket Socket[addr=dei.ic3s.de/192.168.132.32,port=44277,localport=43009]
    security local exception
    SERVER SERVICE Socket: Socket[addr=dei.ic3s.de/192.168.132.32,port=44277,localport=43009]
    SERVER VxSecureListenerSocket: accepting connection
    VxServerSvcSocket: closing socket Socket[addr=dei.ic3s.de/192.168.132.32,port=44277,localport=43009]"

    thank you for any hint.
    christoph

  2. Re: vmsa security exception: error in pam_auth_acct_mgmt: 13

    Christoph


    SUN changed the PAM (Password Authentication Module) in one of their
    patches (can not remember which one now). This messes up the
    authentication. SUN and Veritas suggested an upgrade to Volume Manager
    3.5 which now contains anew jave GUI, called VEA (Veritas Enterprise
    Administrator). This solved the PAM error.

    We downloaded Volume Manager from
    ftp://ftp.veritas.com/pub/products/v...1.sol.CD.tar.Z


    You can upgrade without getting a new license



    Christoph wrote:

    > since some days, when starting vmsa (version 3.0.6) and logging in with root
    >
    > gets the error:
    > "user is not authorized to connect to server.(root)"
    >
    > in the /opt/var/vmsa/logs/server.log we got:
    > "SERVER SERVICE Socket: Socket[addr=dei.ic3s.de/192.168.132.32,port=44248,localport=43009]
    > SERVER VxSecureListenerSocket: accepting connection
    > VxServerSvcSocket: closing socket Socket[addr=dei.ic3s.de/192.168.132.32,port=44248,localport=43009]
    > VxServerSvcSocket: creating a server socket for remote port 44277 and local
    > port 43009
    > receiving client id ...
    > user received = root
    > sending server challenge ...
    > error in pam_auth_acct_mgmt: 13
    > VxServerSvcSocket: closing socket Socket[addr=dei.ic3s.de/192.168.132.32,port=44277,localport=43009]
    > security local exception
    > SERVER SERVICE Socket: Socket[addr=dei.ic3s.de/192.168.132.32,port=44277,localport=43009]
    > SERVER VxSecureListenerSocket: accepting connection
    > VxServerSvcSocket: closing socket Socket[addr=dei.ic3s.de/192.168.132.32,port=44277,localport=43009]"
    >
    > thank you for any hint.
    > christoph



+ Reply to Thread