no data

[Giuseppe]

Dear vmktree veterans

I have just recently installed vmktree on esxi 3.5 and it works swell
for two out of the three machines. However, I am having a very hard
time getting this third machine to work. At first the third machine
did not have the correct ssh key to allow the vmktree machine to ssh
in ( even though ssh was enabled and i had run the addesx command).
Now the vmktree switches between thinking that the machine is offline
(red dot next to its name) and online (green dot) however even when it
thinks it is online there is no data being displayed.

Is there something i'm doing wrong? something i'm missing?

sincerly
Joe

[Lars Troen]

Joe,
Is this third host using the same build number of ESXi as the others?

No connectivity issues to the vmkernel nic port?

When vmktree fails to collect data from a host it will also store error messages in a text file with the name of the server. This text file is removed once it successfully collects data again. You can find it under the sys directory found under /var/lib/vmktree or /var/www/vmktree-data (depending on the type of distro you've installed vmktree in).

Lars

[Giuseppe]

Lars

the builds are identical, the only thing that is different is the
hardware.

I looked for the file but i couldn't find it. In var/lib/vmktree/sys/
there was a folder with the name of my server, and a host-list with
the name of my server but no txt with the name of my server.

with my limited knowledge i have a feeling that this problem has
something to do with a bad ssh connection but i don't know what.
Because with my other two servers logging on through ssh is quick,
while with this third one it is unexplainablly slow.

thanks again
joe

[Lars Troen]

Joe,
Slow ssh logins are often related to the dns setup. For every ssh connection the server will try to resolve the dns name of the ip address connecting (for logging). If you have configured aa wrong dns ip address it will have to wait until the name resolution times out before it allows the connection to go through.

Other things that could slow down this connection could be if there's a autosensing issue on the physical nic/switch port.

Lars

[Giuseppe]

Lars,

i don't think dns is the issue because i use it exact ip adress.

the other machines are configured the same when it comes to the port.

is there a way i can look at the configuration of the ssh, and its
daemon on the servers. i googled in hopes to find the answer but the
search was not very fruitful.

thanks
joe

[Lars Troen]

Joe,
Using the ip address when connecting is really unrelated as the issue here is that the server is querying the dns server for the client's ip address when it connects:
http://www.netadmintools.com/art605.html
http://www.warningnsfw.com/slow-centos-ssh-login-speed-it-up/

Lars

[Giuseppe]

Lars,

okay my bad... but my previous question still stands where is the sshd
config file on a esxi 3.5 u2 server, or its appropriate counterpart.


Joe

On Jul 10, 3:20 pm, Lars Troen <lar...@colargol.tihlde.org> wrote:
> Joe,

> Using the ip address when connecting is really unrelated as the issue here is that the server is querying the dns server for the client's ip address when it connects:http://www.netadmintools.com/art605.htmlhttp://www.warningnsfw.com/slow-centos-ssh-login-speed-it-up/

[Lars Troen]

Joe,
I don't think ESXi has such a config file and only has command line options. You could try to edit the /etc/hosts file and setup the ip address of your vmktree machine there to see if it improves ssh login time.

Lars

[Giuseppe]

Lars

It Worked! I added the vmktree ip address to the /etc/hosts file. And
now everything seems to be working swell.

Thanks a bunch
Joe

[Giuseppe]

Update: everything is not working swell.

Half of the problem seems to be fixed: the server now has its
appropriate graphs. However, the graphs of the vms have alot of
'holes' in the graph, as in places where vmktree did not receive data.
What i feel to be associated to this problem, the vmktree gets
confused when individual vms are online or not. Interestingly enough
the issue of thinking machines are online or not does not have to do
specifically with one machine, but the problem about holes in the
graphs is more pronounced in one of the three machines.

could have speeding up the ssh login only be a cover for a deeper
problem?

joe.

[Lars Troen]

Joe,
Have any of your VMs been copied and have the same VMware UUID?

Lars