1.  Check the /var/opt/vmsa/logs/server.log file for "SIGSYS  12*  bad argument to system call"

Starting RMI Registry
Mon Jan 20 13:18:05 MST 2003
Starting VERITAS VM Storage Administrator Command Server
Mon Jan 20 13:18:05 MST 2003
Starting VERITAS VM Storage Administrator Server
Mon Jan 20 13:18:06 MST 2003
security enabled
rebinding ....
rebound  //e03k19:2410/vrts.remote.vrtsServer
SIGSYS    12*  bad argument to system call

Full thread dump:
   "ConnectionExpiration-199.5.164.124:32776" (TID:0xed6a5b00, sys_thread_t:0x3a6c10, state:CW, thread_t: t@17, sp:0x0 threadID:0xee561dd0, stack_base:0xee561d64, stack_size:0x20000) prio=5
sun.rmi.transport.tcp.TCPChannel$Reaper.run(Compiled Code)
java.lang.Thread.run(Compiled Code)
   "Cleaner" (TID:0xed6a5120, sys_thread_t:0x265068, state:CW, thread_t: t@16,


2.  Check to see if the system has the  /etc/pam.conf file.

The /etc/pam.conf file is the configuration file for Pluggable Authentication Modules (PAM). PAM is a framework of interfaces and libraries used by Solaris and other operating systems for authentication. The pam.conf file can be edited by the system administrator to include other services and service modules.

In this particular case, SEOS entries in pam.conf are preventing VERITAS Volume Manager Storage Administrator (VMSA) from starting up. Check for the following entries in /etc/pam.conf:

# SeOS integrate auth and account
#
other auth optional /usr/lib/security/$ISA/pam_seos.so
rlogin auth optional /usr/lib/security/$ISA/pam_seos.so
other account optional /usr/lib/security/$ISA/pam_seos.so

3.  These entries belong to the Computer Associates eTrust product. If they are not needed,  comment them out by putting the "#' character at the beginning of each line.

For example,

# SeOS integrate auth and account
#
# other auth optional /usr/lib/security/$ISA/pam_seos.so
# rlogin auth optional /usr/lib/security/$ISA/pam_seos.so
# other account optional /usr/lib/security/$ISA/pam_seos.so

4.  Kill and restart the vmsa_server process using the following commands:

# /opt/VRTSvmsa/bin/vmsa_server -k
# /opt/VRTSvmsa/bin/vmsa_server &

5.  Launch the VMSA GUI again and log in.