Dell OMSA 5 on Debian

Since the advent of the debianized version of Dell OMSA installation has been a breeze. Just add the following lines to /etc/apt/sources.list

# OMSA
deb http://ftp.sara.nl/pub/sara-omsa dell sara

and then install using

aptitude update
aptitude install dellomsa

In case you have the mpt-based SAS controller you need to load the mptctl module. I haven't tested this myself but I had some feedback from user using the SAS 5/i storage controllers. Thanks for that info! Well, just load the module and restart OMSA and the storage information should be available.

modprobe mptctl
/etc/init.d/instsvcdrv restart

On a 64-bit machine you will not be able to login to the web interface unless you add some files from a 32-bit installation and edit a configuration file. So if you have a 64-bit installation of Etch then copy these files from a 32-bit version of an Etch installation:

/lib/libselinux.so.1
/lib/libsepol.so.1
/lib/security/pam_nologin.so
/lib/security/pam_unix.so

I've put up the files from a Debian Etch 32-bit in case you don't have a 32-bit system. See link below.

Start with copying the libraries to /lib32/. You might need to install the package ia32-libs to get 32-bit applications playing on a 64-bit system.

Edit /etc/pam.d/omauth and replace /lib with /lib32 so the end result looks like this:

#%PAM-1.0
#auth       required     pam_stack.so service=system-auth
#auth       required    /lib/security/pam_nologin.so
#account    required    pam_stack.so service=system-auth
auth       required     /lib32/security/pam_unix.so nullok
auth       required     /lib32/security/pam_nologin.so
account    required     /lib32/security/pam_unix.so nullok

Restart the services after this change:

/etc/init.d/instsvcdrv restart

The web service hasn't started yet.

/etc/init.d/dsm_om_connsvc start

If you want it to start after a reboot then run:

update-rc.d dsm_om_connsvc defaults 95

After this you should be able to login to your server.

https://192.168.0.10:1311/

Check the syslog for errors if you can't login. You can login using a ordinary user account on the machine and if logging in as root you will be able to do some more stuff. I believe I don't have to tell you that you should be very restrictive about who is having access to this service.

AttachmentSize
lib.zip153.25 KB

Comments

32-bit files link

You wrote:
I've put up the files from a Debian Etch 32-bit in case you don't have a 32-bit system. See link below.

I can't see where is this link. Is it missing?

--
Olivier Korn

Link to 32-bit libs

Sorry about that. Forgot to allow anonymous users to access the attachment.

Give it another try.

// John 

 

Thank you so much!

Hi John,

Thank you for the link. I can see it now (and I can download the file too).

By the way, I managed to extract the 4 files by myself, using 7-zip and .deb files from packages.debian.org repository.

This should be written somewhere too : for the storage to be monitored, you have to "modprobe mptctl" before "/etc/init.d/instsvcdrv restart".

Thank you for your article. It was very helpful.

Regarding mptctl

If you need mptctl depends on what kind of controller you have. SAS 5/i is mpt based but Perc 5/i is not.

See this post at Dell

By the way, good I could be of help!

Cheers!

OMSA 5.1 Login

Hi there, I'm able to view https://ip-address:1311 in my server. However, I'm not able to login...Can please tell me where to check the error? I do not change lib directory name there but I can still view the web login page of OMSA in my debian server.

OMSA 5.1 Login

If it's a 64-bit Debian system then you need the 32-bit libs that I mention in the description above. Assuming that they are in place and you have edited the file /etc/pam.d/omauth check the logs for any errors.

Do you see any errors showing up in /var/log/auth.log? Try tail the log:

tail -f -n20 /var/log/auth.log

Now try to login and see if anything is logged. If you see these lines you have probably supplied the wrong username/password.

Jan 25 19:32:22 server dsm_om_connsvc32d: (pam_unix) check pass; user unknown
Jan 25 19:32:22 server dsm_om_connsvc32d: (pam_unix) authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=
 

It might be worthwhile to check the syslog as well to see if any files are missing. When logging in you might see these lines (even when you are able to login) so they can probably be ignored:

Jan 25 19:32:51 server dsm_om_connsvc32d: PAM unable to dlopen(/lib/security/pam_unix.so)
Jan 25 19:32:51 server dsm_om_connsvc32d: PAM [dlerror: /lib/security/pam_unix.so: cannot open shared object file: No such file or directory]
Jan 25 19:32:51 server dsm_om_connsvc32d: PAM adding faulty module: /lib/security/pam_unix.so

Do you see any message that any other file is missing?

Do you login using the same username and password as an existing system user?

// John

cannot login

I see the missing files:
...
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM adding faulty module: /lib32/security/pam_unix.so
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM unable to dlopen(/lib32/security/pam_nologin.so)
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM [error: /lib32/security/pam_nologin.so: cannot open shared object file: No such file or directory]
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM adding faulty module: /lib32/security/pam_nologin.so
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM unable to dlopen(/lib/security/pam_unix.so)
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM [error: /lib/security/pam_unix.so: wrong ELF class: ELFCLASS64]
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM adding faulty module: /lib/security/pam_unix.so
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM unable to dlopen(/lib/security/pam_smbpass.so)
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM [error: /lib/security/pam_smbpass.so: cannot open shared object file: No such file or directory]
May 9 15:58:41 euclosbi dsm_om_connsvc32d: PAM adding faulty module: /lib/security/pam_smbpass.so
....

What To do?

It seems that some files are

It seems that some files are still missing. For example pam_nologin.so.

Did you copy the files from the zip file lib.zip that is attached to this post and did you put them under the /lib32 dir? That is where they belong on a 64-bit server in case you are using that?

After the copying did you change the paths accordingly in the /etc/pam.d/omauth so that they point to the new libraries and then restarted OMSA?

Sorry, that I reply here but I removed you supplied email address so that you should get spam, but I forgot what it was to quickly :-(

 // John

  

ELFCLASS64 errors

If you're getting the ELFCLASS64 errors it means it's trying to use 64bit modules where you need 32bit ones. Copy the ones in the lib.zip file provided above into the lib32 directory. Double check that they're all 32bit files by running the file command eg"file pam_nologin.so" on all the files. run ldconfig and try logging in again.

-Alan

Thanks

Thanks for the howto. Got my Dell 2970 working without any probs.

Hilbert

Great Work

You are wonderful, I can't believe the simplicity of the installation. This project of yours makes installing OMSA a breeze. apt-get ... and it all works (32-bit machine), on a Dell PE2650 PERC3

Thank you for your effort.

Thanks for your efforts...

Works great on all our dell servers. Your efforts are much appreciated!

One comment on the installation:
We monitor our servers with Nagios. For this reason OMSA needs to be snmp enabled.
After the proposed installation method above I found that snmp isn't enabled by default. This can be done with the following command:

/etc/init.d/dataeng enablesnmp
/etc/init.d/snmpd restart

Thanks again :-)

Tim van Dijk

Perc 4e/di controller support ?

Great, got it working except my controller isn't showing up (Perc4e/Di on a Dell 2850)
Anyone know what I need to support this controller ?

-Trevor.

Perc 4e/di controller support

I've just used Perc 4e/Di with OMSA 4.4 and that worked great. OMSA 5 is supposed to support Perc 4. Are you running Ubuntu or Debian or any other flavor?

There have been some reports of trouble when running certain kernel versions and that might be a issue with the IPMI module. Check this out:

http://lists.us.dell.com/pipermail/linux-poweredge/2008-September/037387.html

// John

Post new comment

  • Allowed HTML tags: <a> <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd><pre>
  • Lines and paragraphs break automatically.

More information about formatting options

To combat spam, please enter the code in the image.