Server Management - Systems Insight Manager
1833163 Members
3415 Online
110051 Solutions
New Discussion

Initial Proliant Deployment Problems

 
SOLVED
Go to solution
Annette Jones_2
Regular Advisor

Initial Proliant Deployment Problems

This doesn't happen to authentication problems, things is I have consulted this forum and found loads of solutions. I have yet to get this to work after reading all these links and the Readme file. Is there any command line commands I can run to complete some further testing?

I have completed the add user and the domain, still nothing works?
17 REPLIES 17
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

Also after completing the above I tried ssh domainuser@servername, (administrator@sklukch107), this failed also.Attched is a screenshot of the cmd window, this will also show the contents of the passwd file. This is all completed on a test lab.
Joel Rubenstein
Honored Contributor

Re: Initial Proliant Deployment Problems

check that the OpenSSH server service is started.

using netstat -a you should see an entry of the format

TCP aetdl580:22 aetdl580.aetsim.local:0 LISTENING

To indicate that the server is listening on port 22
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

I don't seem to have this listed, does it not start auto after install?
Joel Rubenstein
Honored Contributor

Re: Initial Proliant Deployment Problems

yes normally the "OpenSSH Server" service is set to "Automatic" startup during installation
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

I think this is the answer, the service is set to automatic, but not started. Once I try to start it it fails

Could not start OpenSSH Server service on Local Computer

Error 193: %1 is not a valid win32 application
Joel Rubenstein
Honored Contributor
Solution

Re: Initial Proliant Deployment Problems

check if you have an empty file named "program" in the root of your c drive. This has been know to cause service startup problems.


For more info


http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q325680
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

Many thanks Joel, this seems to have sorted thi sproblem out, looks like I have a few others,not sure if I can yet complete the initial deply. Will no doubt keep the forum informed.
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

Stil have a problem:

I have followed the readme file, except for the bit where it says Reinstall Systems Manager SSH Keys, not sure how to do that?

example
Anyway from the server sklukch107(2000 server) I used the domain admin acunt to install the software. I added this user and local user to the passwd file, add the domain to the group file. Set the permissions as per the readme except for the above.From the cmd ran sss domainuser@servername (administrator@sklukch107)
could not create directory '/home/administrator/.ssh'
The authenticity of sklukch107 coul dnot be established
RSA key fingerprint is...........
after entering 'yes' to contine
Failed to add the host to the list of known hosts to the above directory
permission denied for password.

That is as far as I'm getting..........I haven't installed Openssh on any managed server,cause reading between the lines the 'Initial PD' doesn't need it and it will install Openssh if you ask?

Definately stuck now............
Joel Rubenstein
Honored Contributor

Re: Initial Proliant Deployment Problems

I have attached the SSH in HP SIM whitepaper. It has a good section on troubleshooting these types of SSH problems. I would start by checking the registry to verify that /home is setup correctly (page 8) and then look closely at the passwd file to verify the path for administrator is set correctly. SSH is trying to create it's configuration directory .ssh when it fails.

The link to the latest version of the whitepaper in the SIM information library is

http://www.hp.com/wwsolutions/misc/hpsim-helpfiles/HPSIM_SSH_WP.pdf

I have attach a copy because I have had reports that sometimes the links I post don't work?

Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

Joel,

White paper was interesting and helped me with the /home problem. The registry had no value set for home until I set it for c:\documents and settings.

I still have problems using ssh. I have ssh configured on the cms just for testing once this works I can these use elsewhere. I can't get openssh to work on this server though. I have gone through allthe permissions, even tried deleting the authorised_keys2 and known_hosts. Still no luck. I have attached the error (permissions) and also attached a list of the directories and files showing their permissions, hopefully you can see something I can't.
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

permission error, to go with previous attachment.
Joel Rubenstein
Honored Contributor

Re: Initial Proliant Deployment Problems

Annette,

I am not sure what is happening to cause the permissions errors.

Can you post a copy of your passwd file and
the output from the ssh -v administraor@sklukch107 command.

Also is this a Windows 2003 server?
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

Joel,

the ssh -v failed on the password again, with permission denied. Just to confirm I am using the domain user password.

The server is a Windows 2000 Advanced.
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

This is the output to ssh -v
Joel Rubenstein
Honored Contributor

Re: Initial Proliant Deployment Problems

What user are you logged in as when doing the ssh testing? A domain administrator or a local administrator?
Annette Jones_2
Regular Advisor

Re: Initial Proliant Deployment Problems

The domain user "administrator", the local admins is also called "administrator", the domain is "deviblgb"
Joel Rubenstein
Honored Contributor

Re: Initial Proliant Deployment Problems

The only time I have seen that permission denied error is when an incorrect password was entered.

All your SSH configurations appear to be correct.


You might want to open a support case with your local support center.