Guys
Just installed Virtual Centre 2.0.
Tried to add my ESX 3.0 host, which it has - although it's disconnected.
RTFM or is there something else I should know about?
Did you get a message about the virtual center agent failing to install? Yes or no I would check out this KB article:http://kb.vmware.com/kb/4478241
Do you also have sufficient licensing (i.e. for virtualcenter agents) when you installed your VC license server?
Message was edited by:
ken.cline@hp.com to shorten the URL
Ok couple of things..
1. When I logon to my Virtual Centre server via terminal services..
a) the web apache server isn't started, everytime I start it.. it stops!
b) I've logged onto the ESX Server ,changed the licencing from host-based to 'licence server' pointing it to the IP of my Virtual Centre.
c) the licence then shows up as 'X.X.X.X...(being the IP) and "Host Licence File - None". is that right?
d) I have an evaluation copy of a licence, which was emailed to me via VMWare, which I want to use as an eval. I logged onto the Virtual Centre Server, grabbed the licence file and hit 're read licence file'.
All with no joy!
Any ideas on why the apache service keeps stopping and why the licence file won't work?
hhmm..?
Look at the VC log file for more info on why it stopped (C:\Windows\Temp\VPX directory), also check the Windows event viewer.
\[2007-09-18 11:34:39.240 'App' 4176 warning] ============BEGIN FAILED METHOD CALL DUMP============
\[2007-09-18 11:34:39.240 'App' 4176 warning] Invoking \[upgrade] on \[vim.AgentManager:ha-agentmgr]
\[2007-09-18 11:34:39.240 'App' 4176 warning] Fault Msg: "Failed to install the VirtualCenter Agent service"
\[2007-09-18 11:34:39.240 'App' 4176 warning] ============END FAILED METHOD CALL DUMP============
\[2007-09-18 11:34:39.287 'App' 4176 error] \[VpxdHostAccess] Upgrade on hostd failed: vim.fault.AgentInstallFailed
\[2007-09-18 11:34:39.287 'App' 4176 error] \[VpxdHostUpgrader] Failed to run script on host 192.168.23.150
\[2007-09-18 11:34:39.474 'App' 4176 info] \[VpxLRO] -- FINISH task-21 -- group-h25 -- vim.Folder.addStandaloneHost
\[2007-09-18 11:44:53.418 'App' 1580 info] Initiating VMware VirtualCenter shutting down
\[2007-09-18 11:44:53.418 'App' 5368 info] Shutting down VMware VirtualCenter...
\[2007-09-18 11:44:53.418 'App' 1580 error] SetServiceStatus failed: The handle is invalid
\[2007-09-18 11:44:53.652 'App' 4660 info] \[VpxdHostCnx] Host connection reaper thread exiting
Well it looks like it is trying to install the vpxa agent on your ESX host (192.168.23.150) and failing. Does the VC server start and can you log into it with the VI Client? Does your ESX host have a /tmp/vmware-root directory as stated in the kb article Dave posted above?
for some unknown reason i can't login to the console via putty with my 'root' password which is the same as the one I use with the VI client directly into the ESX server, which works! Weird.
Yes, the VC server starts, and yes i can log into it.
however, when I add a host in the VC it says 'disconnected'.
I'll see if I can login to the console some other way to check Dave's suggestion...
By default root access via SSH is disabled for security reasons. You have to enable it at the physical console first.
How do I enable root access for SSH? This is generally not recommended because of security risks which is why it is disabled by default, but if you have to do it here are the steps:
Login to service console
Edit /etc/ssh/sshd_config with Nano or Vi
Change PermitRootLogin to yes (or comment out the line with a #)
Save & exit
Type service sshd restart
strange behaviour..
i can't login to the ESX via Putty using my root login/password.
I can login via 'administrator' which is an account that I have created in ESX using the VI Client, gave it the same priv/group rights as root, but it's only giving me the "$" not "#" at the logon prompt.
Admin seems to authenticate fine.
I've changed the password to 'root' using the VI Client, went to login via Putty, and still no go!
Strange.
LOL.. and as I'm reading your post, this was an Exam question.
HAHAHAHA.. Oops \*grin*
Run SSH then log in with the Administrator account that you created in VI then type:
su-
password:<enter root password here>
If administrators are assigned accounts on each ESX server then when they log into the ESX via SSH a log is kept of who accessed it and when, and using the su- (superuser) they then can still administer the server and a log is kept of who did the work.