- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- Problems installing Agentless Management Service o...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-02-2017 03:28 PM - edited 09-02-2017 05:18 PM
09-02-2017 03:28 PM - edited 09-02-2017 05:18 PM
Problems installing Agentless Management Service on Proliant DL380 G7 - Debian 9.1
Hello Forum,
I am currently trying to install the Agentless Management Service on a DL380 G7 under Debian stretch 9.1.
BIOS is P67 08/16/2015 & ILO is 1.88 Jul 13 2016.
The install is via apt using the instructions here: https://downloads.linux.hpe.com/SDR/project/mcp/
Unfortunately, one of the warnings given is "This program requires the host to hav… BMC" but unfortunately part of the warning has been snipped off in the apt logs.
The machine is a vanilla build. I am also not sure if I need any BIOS configuration changes to enable this. It is currently default.
Does anyone have any advice on this problem please?
Further details below:
kepler@jupiter:~$ sudo apt-get install hp-ams [sudo] password for kepler: Reading package lists... Done Building dependency tree Reading state information... Done hp-ams is already the newest version (2.6.0-2378.51). 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up hp-ams (2.6.0-2378.51) ... Job for hp-ams.service failed because the control process exited with error code. See "systemctl status hp-ams.service" and "journalctl -xe" for details. invoke-rc.d: initscript hp-ams, action "start" failed. ● hp-ams.service - LSB: HP AMS helper Loaded: loaded (/etc/init.d/hp-ams; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2017-09-03 08:14:30 AEST; 6ms ago Docs: man:systemd-sysv-generator(8) Process: 3622 ExecStart=/etc/init.d/hp-ams start (code=exited, status=1/FAILURE) Sep 03 08:14:30 jupiter systemd[1]: Starting LSB: HP AMS helper... Sep 03 08:14:30 jupiter hp-ams[3622]: This program requires the host to hav… BMC Sep 03 08:14:30 jupiter systemd[1]: hp-ams.service: Control process exited,…us=1 Sep 03 08:14:30 jupiter systemd[1]: Failed to start LSB: HP AMS helper. Sep 03 08:14:30 jupiter systemd[1]: hp-ams.service: Unit entered failed state. Sep 03 08:14:30 jupiter systemd[1]: hp-ams.service: Failed with result 'exi…de'. Hint: Some lines were ellipsized, use -l to show in full. dpkg: error processing package hp-ams (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: hp-ams E: Sub-process /usr/bin/dpkg returned an error code (1) kepler@jupiter:~$
running the systemctrl status hp-ams.service command below gave me:
kepler@jupiter:~$ systemctl status hp-ams.service ● hp-ams.service - LSB: HP AMS helper Loaded: loaded (/etc/init.d/hp-ams; generated; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2017-09-03 08:19:32 AEST; 1min 1 Docs: man:systemd-sysv-generator(8) Process: 4092 ExecStart=/etc/init.d/hp-ams start (code=exited, status=1/FAILUR
Thanks
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2017 01:39 AM
09-03-2017 01:39 AM
Re: Problems installing Agentless Management Service on Proliant DL380 G7 - Debian 9.1
Hi again,
As a follow up to the query above;
Ive found the current apt version does not support ILO3. Running hp-ams from /etc/init.d gave a meanignful error indicating it was for ILO4 only.
I went back to some older version to try get a version compatible with a G7 (ilo3).
I tried
hp-ams_1.4.2-1114.2_amd64.deb package and
hp-ams_1.2.0-775.36_amd64.deb package.
Neither worked, giving the error that the version only supported G8 or higher.
My new question is which version of hp-ams will support a DL380 G7 AND Debian 9.1 Stretch?
Thanks
Stephen
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-03-2017 06:52 AM
09-03-2017 06:52 AM
Re: Problems installing Agentless Management Service on Proliant DL380 G7 - Debian 9.1
AMS only works on systems that have iLO4 or higher. For a G7 system you will need to use the SNMP health agent and SMH (System Management Homepage). I do not know the current release schedule or if the older health agent will be offered for Zesty or Stretch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-16-2017 02:15 PM
09-16-2017 02:15 PM
Re: Problems installing Agentless Management Service on Proliant DL380 G7 - Debian 9.1
Thanks for the reply.
As the other utilities are dependant on AMS I will look for an older thealth agent suite.
Regards
Stephen