cmanic & hprsm - BUG??

[Ryan Hobbs_2]

First off, I tried submitting this via a contact us on hp.com and after selecting my product and selecting Linux from the dropdown, the closest distro to my system was RHEL 2.1 (I'm running RHEL 4 U3), I then entered kernel & remaining information. Got an HP tech to tell me they don't support RHEL 2.1 with that kernel version --- DUH. There was no option for RHEL 4 in the dropdown list there.. so, then I try and login to their ITRC and apparently I don't have a software contract (??? It is their software that has the issues!) what great support. So, I alas I am here posting this in hopes another user has experienced or can validate my findings. And/Or perhaps people from HP actually brose their own customer forums..

FROM: cmanic-7.4.0-7.rhel4.linux.txt
-------------------------------------
"2) The HP NIC Agents are configured to start at the same runlevels as the snmpd daemon. Ensure the snmpd daemon is configured to start at the desired runlevels before installing the HP NIC Agents,..."
-------------------------------------

OH REALLY?

#rpm -Uvh cmanic-7.4.0-7.rhel4.linux.rpm
Preparing... ########################################### [100%]
1:cmanic ########################################### [100%]
cmanic installation: snmpd Start script is detected at runlevels 3
cmanic installation: cmanic Start script is installed at runlevels 2 3 4 5
Shutting down kernel logger: [ OK ]
Shutting down system logger: [ OK ]
Starting system logger: [ OK ]
Starting kernel logger: [ OK ]
cmanic installation: snmpd restarted
cmanic installation: Foundation agent (cmafdtn) restarted

So, it found the runlevel of snmpd as 3, but decided to install at runlevel 2345 anyways?

That's fine:
"...otherwise the HP NIC Agents will need to be manually configured after installation using chkconfig or a similar utility."

So let's do that.

[root@sparvmwp001 installed]# chkconfig --list cmanic
cmanic 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@sparvmwp001 installed]# chkconfig --list hprsm
hprsm 0:off 1:off 2:off 3:on 4:off 5:off 6:off
[root@sparvmwp001 installed]# chkconfig --levels 1245 cmanic off
[root@sparvmwp001 installed]# chkconfig --list hprsm
hprsm 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@sparvmwp001 installed]# chkconfig --list cmanic
cmanic 0:off 1:off 2:off 3:on 4:off 5:off 6:off
[root@sparvmwp001 installed]# chkconfig --levels 1245 hprsm off
[root@sparvmwp001 installed]# chkconfig --list cmanic
cmanic 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@sparvmwp001 installed]# chkconfig --list hprsm
hprsm 0:off 1:off 2:off 3:on 4:off 5:off 6:off


That looks great! Turning of cmanic for 245 seems to have tripped hprsm to now 'on' at runlevels 245. And, turning hprsm back off for 245?? You guessed it!!! It turns cmanic back on for 245!

Can anyone make sense of this? Thanks in advance for your help.

[Ivan Ferreira]

This is extrange, please run the following command:

strace -o cmanic.out chkconfig --levels 1245 cmanic off

strace -o hprsm.out chkconfig --levels 1245 hprsm off

Let's check what is doing. Attach the resulting files.

You can of course disable the service directly deleting the file from the corresponding rcX.d directory.

[Ryan Hobbs_2]

cmanic.out attached.

[Ryan Hobbs_2]

hprsm attached.

[Ivan Ferreira]

From the output, it seems that chkconfig is not doing what it has to do. The command line options is --level, without the "s", but this is not the real problem.

When you execute chkconfig, it reads all files in /etc/init.d and looks like resets all services to the defaults found in the init files. The chkconfig should only configure the specified service. Maybe this is a bug. Try updating the chkconfig package.

[Ryan Hobbs_2]

The following packages you requested are already updated:
chkconfig

It doesn't do this for any other service HP/or other that I can see. hpasm and hpsmhd runlevels stay the same. Therefore i can't see how it is a chkconfig issue.

[Ivan Ferreira]

You are right, only a few, not all services, are reconfigured, those services are:

vmware, cmanic, ipmi, hprsm.

Seems that all are installed after the default installation. What is the content of /etc/init.d? Can you post these files on a tar/zip/gzip file?

I don't know what is happening here.

[Ryan Hobbs_2]

On another note,
I also just noticed that when you start|stop hpasm, that package starts|stops hprsm & cmanic anyway!!! So, there is absolutely no reason to have cmanic & hprsm be active! From my understanding, when you boot, things are only executed and therefore if you had cmanic & hprsm off for that run level, it wouldn't matter because they would get started in hpasm (if that is set to start) and they wouldn't get executed because they are a K.

Also of note is that
# hpaducli -v
7.40.1.0
/usr/sbin/hpaducli: line 9: 27750 Segmentation fault $HPADU_LIB_INSTALLATION_DIR.hpaducli $*

These HP utilities seem to be a "piece of work"... with no tangible support from HP or any place to submit bug reports.

Here is the latest reply from HP's team of support professionals:

"Thank you for contacting Hewlett-Packard's ISS Solutions Center.

Current support version of Red hat is the following

Minimum Supported Red Hat Updates
â ¢ Red Hat Enterprise Linux 4 initial release (single core processors)
â ¢ Red Hat Enterprise Linux 4 Update 1 (dual core processors)
â ¢ Red Hat Enterprise Linux 3 Update 2 (SCSI model and single core processors only)
â ¢ Red Hat Enterprise Linux 3 Update 5 (SAS model or dual core processors only)


This was found at the following link

Once again, thank you for contacting Hewlett-Packard's ISS Solutions Center."


They were posed with the same question I posted on this forum. Very helpful information. They might as well have told me how many calories are in a peanut-butter & jelly sandwich!

A partial sysreport has been uploaded.

[Ryan Hobbs_2]

Well apparenetly, the issue here is in the /etc/rc.d/init.d/ scripts themselves. Modifying the top portion to:

Particularly:

# chkconfig: - 99 1
..
# Default-Start:
# Default-Stop:

Fixed the issue.