HPMGMT agents not installing on ESX 3.5

[James D. Young]

Installation of the Management Agents is done using either of these two methods. The second one is what I want to use, but both fail.

./installvm800.sh

./installvm800.sh --silent --inputfile hpmgmt.conf

Every time i Get
: command not foundline 11:
: command not foundline 16:
: command not foundline 19:
: command not foundline 22:
: command not foundline 24:
: command not foundline 26:
'/installvm800.sh: line 97: syntax error near unexpected token '{
'/installvm800.sh: line 97: `Set Failure() {

I looked at the installvm800.sh file and at the lines above they are blank lines.

This was the clean download of the tar file and it is a clean install of the server. I am logged in as ROOT so it is not a permission issue either.

Looking for Ideas on why the default install will not work.

[David Claypool]

How did you create your inputfile? Was it on a Linux or a Windows system? Bad CR/LF from Windows text editors could cause the problem you're experiencing.

[James D. Young]

I used the one that came with it.

The inoput file is not where the problem is because I get the above without it. It is in the installvm800.sh that comes with it, but why should I be modifying the installvm800.sh file, that would mean HP screwed up in creating their own file. If I remember correctly I had the same problem with 7.8 and modified it to work by cleaning up the errors.

I am trying to find out why I am having a problem with a default file that comes with the install package that should work.

[Rob Buxton · Accepted solution]

That seems to be the shell script itself is getting corrupted.
Are you copying extracted files to the ESX Host or are you copying the tar file and then extracting it on the host?
I always copy the tar file to the host and extract it there and don't get those issues. Not yet tried installing version 8.0 though.

[James D. Young]

I usually uncompress the tar from a windows box onto my software share then copy the contents to a USB drive which I then copy from the USB drive to the ESX host, or even try running from the USB drive.

I will try copying the tar file then decompress on the esx host.

[James D. Young]

I copied the gz file over and tried to extract it with tar and it did not like the file.

I had this problem with 7.8 and thought I got around it but I can not seem to duplicate what ever I did.

I have attached the installvm800.sh file.

[Olivier Masse]

What do you mean by it did not like the file?

Did you do "tar xvf file" or "tar xzvf file". Without the z, it will fail as z instructs tar to uncompress the file.

Be sure that you do not modify the original file when you're copying it.

Here is a suggestion to copy your file without using an USB key:

1. On 3.x, root can no longer login directly without modifying the config of the ssh daemon, so create an "admin" user which is part of the "wheel" group, and enable it for shell access.

2. Download WinSCP on your computer (free), then use it to copy using SFTP an UNTOUCHED .tar.gz file in the "admin" account, in its default directory which will be /home/admin.

3. Go on the console through the iLO or a direct attached computer. Login as root. Then go in admin's home directory, "cd /home/admin". Then extract the file, "tar xzvf file"

[James D. Young]

I am more a windows user but do know some unix/linux. I do not do alot of tar files, and it has been a while since I have. I got the file unzipped and ran the install with my conf file and it worked just fine.

So something is not likeing the decompression of the files on windows. I will not do that again.

Thanks all for the help.

[Rob Buxton]

You can also mount a Windows share directly and copy the files.
You need the SMB Client enabled under security for the host and you use the mount -t smbfs to mount the share. You need an account and password.

[Richard Litchfield_1]

It looks like there really is a problem with the cr/lf end-of-line thing difference between windows/linux.

I had the same problem, even though the editor I was using is supposed to sort that out. ALWAYS use DOS2UNIX.EXE to make sure the script files are correctly formatted.