another mission accomplished
just another blog …
the first time i build a icinga monitoring for a vsphere environment. before i configured only checks for esxi machines directly. love the check_esx3.pl module from op5.com. some pics from pnp4nagios:
got the system running on a debian squeeze, all packages from the main,nonfree,controb repositories. pnp4nagios is backported. so all packages are covered with security updates and the normal apt super cow power !
installed another centos 5.7 for a web application on a vmware structure – i hate the hole packet management. had to do things like “configure the boot stages for the nrpe daemon”, adding strange yum repositorys *sigh
works ! nice !
it`s getting complicated these days …
got an customers w2k8 r2 mgmt machine with symantec endpoint and vmware vsphere. the problem: after installing the endpoint product under vmware vsphere the performance graphs for the vm’s don`t apear and the client crashes immediately(detail: the vmware webservice services crash and cannot restart successfully). cause: both software product got webservers on board, that means port conflicts. the solution: the machine got two nics; one nic for mgmt net, one nic for a production net. i changed in the vmware tomcat config the localhost definitions to the mgmt ip because i saw that the endpoint used the other interface automatically. now the tomcat services for the vsphere installation run on a different interface and there are no more conflicts with the two webserver instances… the better solution is not to install two products with different webservers on one machine – especially under a windows server.
You must be logged in to post a comment.