We are installing a dl380g4 and thinking about using this agents. Anyone tried this out and can comment about it?
I have tested them on an ML350G4p and an ML350G3 (both now production servers), went very well. The script is pretty straight forward, make sure you read the readme, and install the dependencies. (alien,wget and fakeroot if I'm not mistaken)
If for any reason you should encounter problems (unlikely, but still ) please post here..
I've installed hpasm using script from this site on Compaq Proliant ML350 G3 on Ubuntu Breezy. Installation process went smooth, but I'm not sure everything goes right.
The drivers and agents are inserted immediately. However, the Health Monitor may take more than two minutes to load, which is expected behavior. On systems with variable speed fans, you may notice that the fans will start spinning more slowly if the temperature is reasonably low.
Hpasm on my machine have started in 1 second (not 2 minutes) and fans have spinned as fast as before.
Further, in the same howto I found:
Quote
To check if the Health Monitor is loaded properly, type [...] ps -efm | grep hpasmd You should see a listing of the processes named hpasmd. There will be 12+ of these entries.
There was only one such an entry. hplog -v shows only one event, from 22th february - I installed hpasm on 21 th march...
Is this normal behaviour?
cheers
tatamisi
« Last Edit: March 22, 2006, 03:11:30 pm by Wojciech Kowalczuk »
Hpasm on my machine have started in 1 second (not 2 minutes) and fans have spinned as fast as before.
i have the agents installed on suse too, and they never took long to load. however stopping of the Health Monitor take some time. check with hplog -f how your fans working, and with hplog -t check the temp. my fans always spin low, perhaps because the temp never rise too much.
Quote
There was only one such an entry.
when i do a ps -efm | grep hpasmd i have 12+ processes like discribed.
Quote
hplog -v shows only one event, from 22th february - I installed hpasm on 21 th march...
what you see there is your Integrated Management Log. try plugging out an redundant powersupply or a raid disc. you should see events there.
« Last Edit: March 23, 2006, 10:32:34 am by mutombo »
dclx01:~# hplog -t ID TYPE LOCATION STATUS CURRENT THRESHOLD 1 ADM1022 Processor Zone Nominal 111F/ 44C 143F/ 62C 2 Maxim 1617 CPU (1) Nominal 131F/ 55C 163F/ 73C 3 ADM1022 I/O Zone Nominal 118F/ 48C 154F/ 68C 4 Maxim 1617 CPU (2) Absent ---F/---C ---F/---C 5 ADM1022 Pwr. Supply Bay Nominal 98F/ 37C 131F/ 55C
dclx01:~# hplog -f ID TYPE LOCATION STATUS REDUNDANT FAN SPEED 1 Var. Speed Processor Zone Nominal Yes Low ( 8) 2 Var. Speed Processor Zone Nominal Yes Low ( 8) 3 Var. Speed I/O Zone Nominal Yes Low ( 15) 4 Var. Speed I/O Zone Nominal Yes Low ( 15) 5 Var. Speed Processor Zone Nominal Yes Low ( 8) 6 Var. Speed Processor Zone Nominal Yes Low ( 8) 7 Var. Speed Pwr. Supply Bay Nominal Yes Low ( 20) 8 Var. Speed Pwr. Supply Bay Nominal Yes Low ( 20)
here i plugged out and in the powersupply
Code:
dclx01:~# hplog -v
ID Severity Initial Time Update Time Count ------------------------------------------------------------- 0000 Information 17:14 02/21/2006 17:14 02/21/2006 0001 LOG: IML cleared through HP ProLiant Health Agent (cmahealthd)
0001 Caution 15:08 03/24/2006 15:08 03/24/2006 0001 LOG: System Power Supply: General Failure (Power Supply 2)
0002 Caution 15:08 03/24/2006 15:08 03/24/2006 0001 LOG: System Power Supplies Not Redundant
dclx01:~# hplog -v
ID Severity Initial Time Update Time Count ------------------------------------------------------------- 0000 Information 17:14 02/21/2006 17:14 02/21/2006 0001 LOG: IML cleared through HP ProLiant Health Agent (cmahealthd)
0001 Repaired 15:08 03/24/2006 15:09 03/24/2006 0001 LOG: System Power Supply: General Failure (Power Supply 2)
0002 Repaired 15:08 03/24/2006 15:09 03/24/2006 0001 LOG: System Power Supplies Not Redundant
you see how the Caution change to Repaired.
im sorry but i dont have a ML350 here right now.
perhaps check the bios for fan speed, some ML have their config there.
I tried to get that package compiling on sarge-amd64, with no luck. Here's the build.log :
Code:
dpkg-buildpackage: source package is hpasm dpkg-buildpackage: source version is 7.4.0-56 dpkg-buildpackage: source maintainer is Christian Michallek <cm@data-consult.de> dpkg-buildpackage: host architecture is amd64 fakeroot debian/rules clean dh_testdir dh_testroot rm -f build-stamp configure-stamp # Add here commands to clean up after the build process. # TL: nothing to be cleaned #-/usr/bin/make clean dh_clean dpkg-source -b debian dpkg-source: warning: source directory `./debian' is not <sourcepackage>-<upstreamversion> `hpasm-7.4.0' dpkg-source: building hpasm in hpasm_7.4.0-56.tar.gz dpkg-source: building hpasm in hpasm_7.4.0-56.dsc debian/rules build dh_testdir # Add here commands to configure the package. touch configure-stamp dh_testdir # Add here commands to compile the package. # TL: nothing to be compiled #/usr/bin/make #docbook-to-man debian/hpasm.sgml > hpasm.1 touch build-stamp fakeroot debian/rules binary dh_testdir dh_testroot dh_clean -k dh_installdirs # Add here commands to install the package into debian/hpasm. # TL: just copy all files #/usr/bin/make install DESTDIR=/root/debian/debian/hpasm cp -a etc opt sbin usr /root/debian/debian/hpasm cp -a install /root/debian/debian/hpasm/opt/compaq/utils/ dh_testdir dh_testroot dh_installchangelogs dh_installdocs dh_installexamples dh_installman dh_link dh_strip dh_compress dh_fixperms dh_makeshlibs dh_installdeb dh_shlibdeps -l debian/hpasm/opt/compaq/hpasm/addon --exclude=cmhp.o --exclude=cmhp_lib.o debian/hpasm/opt/compaq/foundation/bin/cmahostd: error while loading shared libraries: libfakeroot-sysv.so.0: cannot open shared object file: No such file or directory dpkg-shlibdeps: failure: ldd on `debian/hpasm/opt/compaq/foundation/bin/cmahostd' gave error exit status 1 dh_shlibdeps: command returned error code 256 make: *** [binary-arch] Error 1
/usr/lib/fakeroot-sysv.so.0 exists, /usr/lib is in /etc/ld.so.conf, and 'ldconfig' was issued. However, the linking still fails. Any idea ?
Not having any problems per se, but I'm more concerned with how these processes run in a "normal" sarge environment. Functionality is as expected, but hpasm seems to spawn a LOT of processes (more than its older cousins). The original RPMs on RHEL run pretty much 1 task per process (even hpasmd runs only one process contrary to the documentation), but on sarge, I see a lot of hpasmd and cmahealthd processes- although they don't seem to be eating up excess memory or CPU cycles....
Figured it out...if this set of scripts is used on a 2.4 kernel, it spawns mutiple processes per task. On 2.6, it works fine. So if your machine is running 2.4, convert the RHEL2.1 packages instead of the UL packages.
I'm trying to install this management stuff on an ML350 G3. Can anybody help me, where can I download this rpm2deb script, and which version to use for Debian Sarge?
Forum 
Author
Logged
) please post here..
