Opened 13 years ago

Closed 13 years ago

#14 closed defect (worksforme)

OMSA 5.3 on Ubuntu 6.06.2 not starting

Reported by: Kevin Collins Owned by:
Priority: major Milestone:
Version: 5.3.0 Keywords:
Cc:

Description

Added the repository information and pulled dellomsa via apt. Install seemed to work fine. At the end of the process, when things are supposed to start, I get this:

================================================ Stopping Systems Management Device Drivers: Stopping dcdbas: * Starting Systems Management Device Drivers: Starting dcdbas: * Starting Systems Management Data Engine: Starting dsm_sa_datamgr32d: /opt/dell/srvadmin/dataeng/bin/dsm_sa_datamgr32d: error while loading shared libraries: libdcsmil32.so.5: cannot open shared object file: No such file or directory

*

Starting dsm_sa_eventmgr32d: /opt/dell/srvadmin/dataeng/bin/dsm_sa_eventmgr32d: error while loading shared libraries: libdcsupt32.so.5: cannot open shared object file: No such file or directory

*

================================================

I've done some searching and it appears as though there might be something that I need to do with /etc/ld.so.conf, but I can't find the file or the changes needed to that file.

At this point, I can not access the web gui for the OMSA.

The machine in question is a Dell Poweredge 1950 with the PERC5/i

Anything to help this would be welcomed.

Kevin

Change History (2)

comment:1 Changed 13 years ago by Kevin Collins

OK, found out, during a removal and re-install of dellomsa, that I needed to add several lines to a new file called "/etc/ld.so.conf". Which I did, and now it appears as though most of the omsa package is starting.

However, upon startup of the omsa packages, I receive this notice now:

Starting Systems Management Device Drivers:
Starting ipmi driver:  *

That asterix is red, meaning a failure. I do not show an IMPI driver of any kind loaded. When I access the web interface, I can not get any data. Nor does omreport seem to work:

onyx ~ # omreport system postlog
Error! No POST log found on this system.

onyx ~ # omreport chassis memory
Memory Information

Error : Memory object not found

So I seem to be messing up somewhere still.

comment:2 Changed 13 years ago by anonymous

  • Resolution set to worksforme
  • Status changed from new to closed

I figured it out. I needed to add the statement "pnpacpi=off" to the kernel line in /boot/grub/menu.1st" to prevent ACPI from hogging the IMPI ports.

All is well now.

Note: See TracTickets for help on using tickets.