Hey there,
I'm very impressed of the new capabilities VC 2.0 provides. But I have a problem with logging of performance data. It seems that VC is only logging data when my client is running. All the other time the lines of the charts are going to zero. Do I have to configure this at the server?
What do I have to change?
Thanks for your help!
daniel
How many vpx* rows do you see now...?
Actually, that tripped me up on the upgrade. I had previously been using Windows Authentication, but during the upgrade, the database update failed. After doing a little searching, I realized I needed to switch over to SQL auth and had to run through the upgrade all over again.
We ran into this problem in the past. I think if you didn't change the default database to your VC database when you set up the ODBC connection, VC 1.x ended up not using the database you intended.
Yes, that's what I realized when I red the post from mstahl75 and came to this point while re-installing VC 2.0. Now I have the vpx_* tables in my database. Hopefully now data will be kept.
The problem being discussed in this thread is a known server problem in VC2.0. The "update vpx_sequence" solution addresses a part of this and applies only to the upgrade case and not the fresh install case. The problem will be completely fixed (upgrade and fresh install) in VC2.0.1.
So, is there any way to manually fix the issue? Or do we just live with dropped stats until that time?
I am afraid there is no way to manually fix this and stats will get dropped until you have the 2.0.1 binary.
OK. Thanks for the information. Won't worry about it until after the upgrade comes out.
Any idea why only certain people see this issue? - I have two installs, one does it, the other doesn't.
The issue is a bit non-deterministic - whether you see the bug or not (in fact to what extent you see it - some hosts may show stats while others drop them) depends on the number of hosts in the inventory and the number of stats collection threads configured (default is 2).
I tried upping that value by one but it didn't help at all. Is there a good number for that? Some kind of rule of thumb or something?
I up'ed mine to 16 yesterday. Today I can see logging statistics from yesterday to today. The strange thing is, I can now do real-time and day graphs, but the weekly, monthly, etc all show nothing. For fun, I tried a custom graph and was able to do up to 2 days. If I tried to generate a 3-day graph... nothing.
I'll up mine some more and see what happens over the weekend.
Can anyone post a link to an official VMware announcement or KB article about this bug...?!?!?
I'd like to know more specifics about the problem - as I imagine many of you would...
I upped my threads to 16 and restarted the VC service (just for good measure) last night, this morning I have stats from overnight !!
Will continue to monitor.
Can you tell me where to configure the number of stats collection threads?
Virtual Center| Administration | Server Settings | Statistics|
Stats collection thread limit --> 16.
Stats collection level (on mine) is 2nd one down.
Stats still arriving...
eliot, are you seeing the same issues as nwallaceml posted above..?
btw: This is the same symptoms I'm getting on a fresh VC2.0 install without changing the thread limit (still @ 2)...
Thank you, I will try this on monday. No possibility at the moment to reach my VC at work
I assume that the weekly/monthly stats are blank because the system hasn't been collecting the data the have anything to show.