VmBix: vsphere monitoring

[c.mammoli]

I tried with the very latest version of ESXi and vSphere 5.1

[Kryol]

If i run with

$ vmbix -P 12050 -u username -p password -s https://vcenter.mycompany.com/sdk

all works fine
But if I try to use

$ vmbix -c /etc/vmbix/vmbix.conf -f /var/run/vmbix.pid

I get

creating pid file /var/run/vmbix.pid 32525
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused
RemoteException: java.rmi.RemoteException: VI SDK invoke exception:java.net.ConnectException: Connection refused

If I start as daemon I get same result.
I think vmbix does not read config.

Any suggestions

---
It was my typo in config. Problem have been resolved

[Kryol]

Vmbix write a lot of messages to log such as:

Feb 21 15:41:35 s-vm-vma vmbixd: thread created, collecting data in 1 threads
Feb 21 15:41:37 s-vm-vma vmbixd: thread  closed, collecting data in 0 threads
Feb 21 15:41:38 s-vm-vma vmbixd: thread created, collecting data in 1 threads
Feb 21 15:41:39 s-vm-vma vmbixd: thread created, collecting data in 2 threads
Feb 21 15:41:40 s-vm-vma vmbixd: thread  closed, collecting data in 1 threads
Feb 21 15:41:41 s-vm-vma vmbixd: thread  closed, collecting data in 0 threads
Feb 21 15:42:35 s-vm-vma vmbixd: thread created, collecting data in 1 threads
Feb 21 15:42:37 s-vm-vma vmbixd: thread  closed, collecting data in 0 threads
Feb 21 15:42:38 s-vm-vma vmbixd: thread created, collecting data in 1 threads
Feb 21 15:42:39 s-vm-vma vmbixd: thread created, collecting data in 2 threads
Feb 21 15:42:40 s-vm-vma vmbixd: thread  closed, collecting data in 1 threads
Feb 21 15:42:41 s-vm-vma vmbixd: thread  closed, collecting data in 0 threads
Feb 21 15:43:35 s-vm-vma vmbixd: thread created, collecting data in 1 threads
Feb 21 15:43:37 s-vm-vma vmbixd: thread  closed, collecting data in 0 threads
Feb 21 15:43:38 s-vm-vma vmbixd: thread created, collecting data in 1 threads
Feb 21 15:43:39 s-vm-vma vmbixd: thread created, collecting data in 2 threads
Feb 21 15:43:40 s-vm-vma vmbixd: thread  closed, collecting data in 1 threads

I would like to see error messages only. Is it possible?

[gavind]

I think you need to do some filtering. Have you found out how to do this yet?

[Kryol]

I turned off such logging

[aleksardain]

I am currently undertaking the supervison of VMWare with VMBix only I meet some difficulties, so I want to know:

is there a configuratin bring VMWare side, or all the manipulation is done only on zabbix server?? In the configuration file vmbix.conf line "serviceurl" what does it get??

wxhen vmbixd the startup of service, I get an error on the demon message
Starting vmbixd $ / etc / init.d / vmbixd: 37: / etc / init.d / vmbixd: daemon: not found
and I can not locate the problem to solve.

i'm Stuck and I can not find a solution. Thank you for your help!

[hryamzik]

What OS do you use to run VmBix?
SDK URL should look like 'https://vcenter.mycompany.com/sdk'. It's mentioned on google code wiki page, please check it out here.

[aleksardain]

I use Ubuntu 12.04 as OS. For 'https://vcenter.mycompany.com/sdk ', vcenter.mycompany.com = IP address or ESXi vSphere??. Also there is no configuration to do VMWare side??

Thanks .

[hryamzik]

There's no configuration on vsphere side required. vcenter.mycompany.com = ip address or dns name of vcenter or esx(i), depending on your configuration.

[gavind]

Does using a port other than the default one make a difference here?

[hryamzik]

No, any port, just don't forget to redirect traffic.

[JS86]

i get the same error like aleksardain.

i use the Zabbix Appliance 2.0.6


/etc/init.d/vmbixd: line 37: daemon: command not found

[hryamzik]

Does it work from command line? Show me the arguments you use.

[JS86]

The last days, yes but at this time i get this:

Connected to https://192.168.5.25/sdk, time taken:360ms
starting server on port
Usage:
vmbix {-P|--port} listenPort {-s|--serviceurl} http[s]://serveraddr/sdk {-u|--username} username {-p|--password} password [-f|--pid pidfile]
or
vmbix [-c|--config] config_file [-f|--pid pidfile]
java.net.BindException: Address already in use
Shutting down
disconnected
Shutted down

But the init script does not work at any time.

[JS86]

chkconfig --add vmbixd

insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: script jexec is broken: incomplete LSB comment.
insserv: missing `Required-Stop:' entry: please add even if empty.
insserv: warning: script 'zabbix_appliance_postboot' missing LSB tags and overrides
insserv: Default-Start undefined, assuming default start runlevel(s) for script `zabbix_appliance_postboot'

Note: This output shows SysV services only and does not include native
systemd services. SysV configuration data might be overridden by native
systemd configuration.



This is ok:

zabbix_get -s localhost -p 12050 -k esx.cpu.load[******,used]
1494