OMSA 5.4.0-1 on lenny: web interface not working

Alessandro FAGLIA a.faglia at farmol.it
Thu Oct 9 07:23:37 CDT 2008


-------- Original Message  --------
Subject: OMSA 5.4.0-1 on lenny: web interface not working
From: Alessandro FAGLIA <a.faglia at farmol.it>
To: Dell Poweredge list server <linux-poweredge at dell.com>
Date: Fri Oct 03 2008 16:47:31 GMT+0200 (ora legale Europa occidentale)
> I've always managed to have OMSA 5.2 working on all my PE servers.
>
> Now I have my first T300 with debian lenny and I'm trying to put OMSA 
> 5.4 on it.
>
> Everything works fine, but the web interface does not work. In the sense 
> that, after I issued
>
> # /etc/init.d/dsm_om_connsvc start
> # /etc/init.d/dsm_om_connsvc status
> dsm_om_connsvc32d (pid 4689) is running
>
> as usual, I cannot see my server listening on port 1311, and I obviously 
> cannot connect to it.
>
> # netstat -nat
> Active Internet connections (servers and established)
> Proto Recv-Q Send-Q Local Address           Foreign Address         State
> tcp        0      0 0.0.0.0:39694           0.0.0.0:*               LISTEN
> tcp        0      0 0.0.0.0:111             0.0.0.0:*               LISTEN
> tcp        0      0 0.0.0.0:113             0.0.0.0:*               LISTEN
> tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN
> tcp        0      0 127.0.0.1:25            0.0.0.0:*               LISTEN
>
> Any idea? BTW, the CLI is working as expected:
>
> # ./omreport about
>
> Product name : Information Not Available.
> Version      : 3.4.0
> Copyright    : Copyright (C) Dell Inc. 1995-2008. All rights reserved.
> Company      : Dell Inc.
>
>
>   

Hi.

Can anybody help me on this problem? Still trying to have the web 
interface working but with no success.

BTW, I tried also with OMSA 5.2 but the outcome is the same. Looking at 
the traditional log files (syslog, messages) I don't see any message 
that could help.
The only hint I've found is into /var/log/dsm_om_connsvc32dIO.log, but I 
don't know how to manage it:

> status(-34) #
> # An unexpected error has been detected by Java Runtime Environment:
> #
> #  SIGSEGV (0xb) at pc=0xb7e93064, pid=3626, tid=2897214352
> #
> # Java VM: Java HotSpot(TM) Client VM (1.6.0-b105 mixed mode)
> # Problematic frame:
> # C  [libc.so.6+0x71064]  strcmp+0x14
> #
> pure virtual method called
> tarting the startserver thread
> [Oct  9 13:52:38 2008] (3626) ModuleAttach: exit
> [Oct  9 13:52:38 2008] (3626) RunServer: ModuleAttach success
> [Oct  9 13:52:38 2008] (3626) RunServer:worker waiting for shutdown 
> message...
> [Oct  9 13:52:38 2008] (3625) RunServer:daemon waiting for shutdown 
> signal...
> [Oct  9 13:52:38 2008] (3624) RunServer:parent process EXIT status(0)
> [Oct  9 13:52:38 2008] (3626) RunServer(ERROR):worker shutdown wait 
> failed, should not occur!
> [Oct  9 13:52:38 2008] (3626) RunServer:worker process EXIT status(-34)
> [Oct  9 13:52:38 2008] (3626) RunServer exit with status(-34)

Thanks.
-- Alessandro



More information about the Linux-PowerEdge mailing list