PE2850: Ubuntu + OSMA

Collins, Kevin L. kcollins at nei-ky.com
Fri Apr 6 12:08:55 CDT 2007


Andrew Reid wrote
> 
> Collins, Kevin L. wrote:
> > Looks like I was mistaken.  OMSA only survived until I rebooted the
> > machine.
> >
> > Now when the init script "instsvcdrv" tries to start, I get this:
> > =====================================================
> > root at biege:~# /etc/init.d/instsvcdrv restart
> > Stopping Systems Management Data Engine:
> > Stopping dsm_sa_eventmgr32d:  *
> > Stopping dsm_sa_datamgr32d:  *
> > Stopping Systems Management Device Drivers:
> > Starting Systems Management Device Drivers:
> > Starting ipmi driver:  *
> > Starting Systems Management Data Engine:
> > Starting dsm_sa_datamgr32d:  *
> > touch: cannot touch `/var/lock/subsys/dataeng': No such file or
> > directory
> > Starting dsm_sa_eventmgr32d:  *
> > touch: cannot touch `/var/lock/subsys/dataeng': No such file or
> > directory
> > =====================================================
> 
> This error is caused by the fact that /var/lock is a tmpfs filesystem,
> it isn't a real filesystem on disk. It gets recreated every boot. This
> means that the subdirectory subsys gets blown away every boot. The
Dell
> startup scripts DO NOT check for the existence of this subdirectory
and
> fail (with the noted error message) and fail to start. You can easily
> fix the startup script not to do this, but in the short term,
> 
>   mkdir -p /var/lock/subsys
> 
> then retry the startup script.

You're exactly right!  I've added a small check in the "instsvcdrv" init
script for the existence of this directory.  If the directory isn't
there, I have the script create it.  I just restarted the machine and it
appears as though I at least have the OMSA web interface up and running
again.

Thanks for your help!

FWIW, on my system I added this at the top of /etc/init.d/instsvcdrv:

#
========================================================================
==
# -- This script, in its default form, didn't check for the existence of
--
# -- the directory /var/lock/subsys, which it needs to properly
function. --
# -- This small little addition will fix that.
--
#
========================================================================
==
if [ ! -d /var/lock/subsys ]; then
   mkdir /var/lock/subsys
   chmod 0755 /var/lock/subsys
fi



More information about the Linux-PowerEdge mailing list