###@###.### 2002-02-08

HW: x86
SW: s9_55
Cluster: SUNWCall
Locales: en_US,ja,ja_JP.PCK,ja_JP.UTF-8

While trying to execute a diskless client smosservice add command, SMC cannot be started and produces a Java core dump. Here are the console messages:
-----------------------------------------------------------------------
firetail# Starting Solaris Management Console server version 2.1.0.
endpoint created: :898

Unexpected Signal : 11 occurred at PC=0xD980CE91
Function=[Unknown.]
Library=(N/A)

NOTE: We are unable to locate the function name symbol for the error
      just occurred. Please refer to release documentation for possible
      reason and solutions.


Current Java thread:

Dynamic libraries:
0x8050000 /usr/java/bin/java
0xddb50000 /usr/lib/libthread.so.1
0xddb80000 /usr/lib/libdl.so.1
0xdda70000 /usr/lib/libc.so.1
0xdd730000 /usr/j2se/jre/lib/i386/client/libjvm.so
0xdd710000 /usr/lib/libCrun.so.1
0xdd6e0000 /usr/lib/libsocket.so.1
0xdd630000 /usr/lib/libnsl.so.1
0xdd610000 /usr/lib/libm.so.1
0xdda40000 /usr/lib/libw.so.1
0xdd5d0000 /usr/lib/libmp.so.2
0xdd5b0000 /usr/lib/librt.so.1
0xdd590000 /usr/lib/libaio.so.1
0xdd570000 /usr/lib/libmd5.so.1
0xdd540000 /usr/j2se/jre/lib/i386/native_threads/libhpi.so
0xdd4f0000 /usr/j2se/jre/lib/i386/libverify.so
0xdd4c0000 /usr/j2se/jre/lib/i386/libjava.so
0xdd490000 /usr/j2se/jre/lib/i386/libzip.so
0xdb900000 /usr/lib/locale/en_US.ISO8859-1/en_US.ISO8859-1.so.2
0xcced0000 /usr/j2se/jre/lib/i386/libnet.so

Local Time = Fri Feb 8 13:35:57 2002
Elapsed Time = 10
#
# HotSpot Virtual Machine Error : 11
# Error ID : 4F530E43505002D3
# Please report this error at
# http://java.sun.com/cgi-bin/bugreport.cgi
#
# Java VM: Java HotSpot(TM) Client VM (1.4.0-rc-b89 mixed mode)
#
# An error report file has been saved as hs_err_pid2726.log.
# Please refer to the file for further information.
#
Feb 8 13:36:00 firetail genunix: NOTICE: core_log: java[2726] core dumped: /
var/crash/firetail/core.java.2726.1013204158
---------------------------------------------------------------
I am attaching the core file to this report.

firetail# file core.java.2726.1013204158
core.java.2726.1013204158: ELF 32-bit LSB core file 80386 Version 1, from 'java'
firetail# adb core.java.2726.1013204158
core file = core.java.2726.1013204158 -- program ``/usr/j2se/bin/java
'' on platform i86pc
SIGABRT: Abort

Please recategorize this report as appropriate. I will see if it happens for s9_56 as well.

--------------------------------------------------------------

For Java folks looking at this, any SMC client that establishes a connection to
the server can be used to try to reproduce the problem:
   smosservice list --
   smuser list --

And there are 2 ways to start the server:
   1) You can start the java daemon manually by running "/etc/init.d/init.wbem start"

   2) Or, you can start the server's native boot proxy, which sits on the port
      and waits for incoming connections. When the proxy receives one, it starts up
      the java daemon, hands over the port to it, and then dies. This is the state
      after every system boot, but you can force this state without a reboot by
      doing the following:

       /bin/sh
       VIPER_HOME=/usr/sadm/lib/smc
       export VIPER_HOME
       ${VIPER_HOME}/bin/smcboot

If the server dies and you have problems restarting it, simply implement the cure for a
"sick server", as described at http://smpt.east/projects/SMC/FAQ/#ResetSickServer

###@###.###