Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

frequent run 'govc events' get no events return #948

Closed
wangweihong opened this issue Dec 6, 2017 · 4 comments
Closed

frequent run 'govc events' get no events return #948

wangweihong opened this issue Dec 6, 2017 · 4 comments

Comments

@wangweihong
Copy link

wangweihong commented Dec 6, 2017 •
edited
Loading

I' m writing a program to watching vsphere event change : every 5 second get vsphere events. At first, I can get vsphere events correctly； However, after a while , vsphere return 0 event and the api return no error.
I try to reproduce the problem in govc,run govc events quickly , this is what it displays:

wwh@wwh:~/kiongf/go/src/vmware/src$ govc events 
[Wed Dec  6 13:35:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 5:35:43 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 13:45:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 13:45:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 5:45:43 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 13:55:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 13:55:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 5:55:43 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:03:04 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged in as Go-http-client/1.1
[Wed Dec  6 14:05:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:05:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:05:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:08:06 2017] [info] Task: Revert snapshot (target=VirtualMachine ubuntu16.04)
[Wed Dec  6 14:08:07 2017] [info] The execution state of the virtual machine ubuntu16.04 on host 192.168.8.222, in compute resource 192.168.8.222 has been reverted to the state of snapshot asdf, with ID 133
[Wed Dec  6 14:08:19 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.10 logged in as Go-http-client/1.1
[Wed Dec  6 14:15:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:15:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:15:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:16:42 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged in as Go-http-client/1.1
[Wed Dec  6 14:17:34 2017] [info] Task: Create virtual machine snapshot (target=VirtualMachine ubuntu16.04)
[Wed Dec  6 14:22:41 2017] [info] vmware-vpostgres status changed from green to gray
[Wed Dec  6 14:22:42 2017] [info] Alarm 'Health status changed alarm' on 数据中心 triggered by event 4513 'vmware-vpostgres 状态已从 green 更改为 gray'
[Wed Dec  6 14:23:12 2017] [info] vmware-vpostgres status changed from gray to green
[Wed Dec  6 14:23:13 2017] [info] Alarm 'Health status changed alarm' on 数据中心 triggered by event 4515 'vmware-vpostgres 状态已从 gray 更改为 green'
[Wed Dec  6 14:25:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:25:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:25:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:28:38 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged in as govc/0.16.1
[Wed Dec  6 14:33:03 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged out (login time: Wednesday, December 06, 2017 3:44:32 AM, number of API invocations: 1,750, user agent: Go-http-client/1.1)
[Wed Dec  6 14:35:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:35:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:35:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events 
[Wed Dec  6 13:35:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 5:35:43 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 13:45:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 13:45:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 5:45:43 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 13:55:43 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 13:55:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 5:55:43 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:03:04 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged in as Go-http-client/1.1
[Wed Dec  6 14:05:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:05:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:05:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:08:06 2017] [info] Task: Revert snapshot (target=VirtualMachine ubuntu16.04)
[Wed Dec  6 14:08:07 2017] [info] The execution state of the virtual machine ubuntu16.04 on host 192.168.8.222, in compute resource 192.168.8.222 has been reverted to the state of snapshot asdf, with ID 133
[Wed Dec  6 14:08:19 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.10 logged in as Go-http-client/1.1
[Wed Dec  6 14:15:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:15:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:15:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:16:42 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged in as Go-http-client/1.1
[Wed Dec  6 14:17:34 2017] [info] Task: Create virtual machine snapshot (target=VirtualMachine ubuntu16.04)
[Wed Dec  6 14:22:41 2017] [info] vmware-vpostgres status changed from green to gray
[Wed Dec  6 14:22:42 2017] [info] Alarm 'Health status changed alarm' on 数据中心 triggered by event 4513 'vmware-vpostgres 状态已从 green 更改为 gray'
[Wed Dec  6 14:23:12 2017] [info] vmware-vpostgres status changed from gray to green
[Wed Dec  6 14:23:13 2017] [info] Alarm 'Health status changed alarm' on 数据中心 triggered by event 4515 'vmware-vpostgres 状态已从 gray 更改为 green'
[Wed Dec  6 14:25:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:25:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:25:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Wed Dec  6 14:28:38 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged in as govc/0.16.1
[Wed Dec  6 14:33:03 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged out (login time: Wednesday, December 06, 2017 3:44:32 AM, number of API invocations: 1,750, user agent: Go-http-client/1.1)
[Wed Dec  6 14:35:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Wed Dec  6 14:35:44 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 06, 2017 6:35:44 AM, number of API invocations: 1, user agent: VMware vim-java 1.0)
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events 
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events 
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events 
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events 
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events 
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events -n 1
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events -n 1
wwh@wwh:~/kiongf/go/src/vmware/src$ echo $?
0
wwh@wwh:~/kiongf/go/src/vmware/src$ govc version
govc 0.16.1

By the way, if I specify output events larger that 1000, govc events -n 1001, I got 0 event too.
@anfernee
Copy link
Contributor

@wangweihong I cannot reproduce this issue. Is it just govc events or it affects other commands. If you login thru UI, can you see those events?

@wangweihong
Copy link
Author

wangweihong commented Dec 13, 2017 •
edited
Loading

@anfernee I am not sure whether It affect other command , but govc datacenter.info seem to be ok . Events are still showed in UI. when very very quickly run govc events(less than one second, more than 10 times ),maybe it will reproduce.

wwh@wwh:~/kiongf/go/src/vmware/src$ govc events -n 10
^[[A[Thu Dec 14 01:59:10 2017] [info] VSAN datastore vsanDatastore in cluster asdfasdf in datacenter Datacenter does not have capacity
[Thu Dec 14 02:03:24 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Thu Dec 14 02:03:25 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 13, 2017 6:03:24 PM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Thu Dec 14 02:10:02 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.10 logged out (login time: Wednesday, December 13, 2017 5:09:41 PM, number of API invocations: 3,301, user agent: Go-http-client/1.1)
[Thu Dec 14 02:13:25 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged in as VMware vim-java 1.0
[Thu Dec 14 02:13:25 2017] [info] User VSPHERE.LOCAL\vsphere-webclient-9afe0280-d5e3-11e7-9f65-005056b312dd@192.168.5.200 logged out (login time: Wednesday, December 13, 2017 6:13:25 PM, number of API invocations: 1, user agent: VMware vim-java 1.0)
[Thu Dec 14 02:18:26 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.10 logged out (login time: Wednesday, December 13, 2017 5:40:10 PM, number of API invocations: 900, user agent: Go-http-client/1.1)
[Thu Dec 14 02:18:29 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.10 logged out (login time: Wednesday, December 13, 2017 5:48:28 PM, number of API invocations: 9, user agent: Go-http-client/1.1)
[Thu Dec 14 02:20:59 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.10 logged out (login time: Wednesday, December 13, 2017 5:48:33 PM, number of API invocations: 270, user agent: Go-http-client/1.1)
[Thu Dec 14 02:21:02 2017] [info] User VSPHERE.LOCAL\Administrator@192.168.6.25 logged in as govc/0.16.1
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events -n 10
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events -n 10
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events -n 10
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events -n 10

wwh@wwh:~/kiongf/go/src/vmware/src$ govc datacenter.info Datacenter
Name:                Datacenter
  Path:              /Datacenter
  Hosts:             2
  Clusters:          2
  Virtual Machines:  9
  Networks:          1
  Datastores:        3
wwh@wwh:~/kiongf/go/src/vmware/src$ govc events

@dougm
Copy link
Member

dougm commented Dec 13, 2017

Was looking at #961 , which is actually the cause of this issue. I didn't see the issue against ESX, but did against VC. Fix on the way.

dougm added a commit to dougm/govmomi that referenced this issue Dec 13, 2017
@dougm
Destroy event history collectors
4fb5034 
The EventHistoryCollector objects are tied to a session and there is a max per-session.
Without destroying the collectors, we could max out the collectors causing 'govc events' to return empty.

Fixes vmware#948
Fixes vmware#961
@dougm dougm mentioned this issue Dec 13, 2017
Merged
@anfernee
Copy link
Contributor

good, I was verifying against an esx.

dougm added a commit to dougm/govmomi that referenced this issue Dec 13, 2017
@dougm
Destroy event history collectors
475fd8f 
The EventHistoryCollector objects are tied to a session and there is a max per-session.
Without destroying the collectors, we could max out the collectors causing 'govc events' to return empty.

Fixes vmware#948
Fixes vmware#961
dougm added a commit that referenced this issue Dec 13, 2017
@dougm
Destroy event history collectors (#962)
aef2d79 
The EventHistoryCollector objects are tied to a session and there is a max per-session.
Without destroying the collectors, we could max out the collectors causing 'govc events' to return empty.

Fixes #948
Fixes #961
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dougm @anfernee @wangweihong