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.
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
Fix "Label-performaceCPU-avg-freq" doesn't exist #6
Comments
The simple solution: Popup comes from here: FirendlyNames are for example defined here: And some checks are coming from around here: |
Thanks for the hint. From where the Error come I already knew, but I didn’t know how to solve it properly. When I compiled it as release, I also got an error message but it had an other text. I think the problem was, that I have compiled it with the DLL files from nugget and not with the one from Citrix, because I didn’t get any error message now but I can’t tell it for sure. |
It's the same here in my home testlab :-| |
@borzel Do you only get it when you compile it as debug or also as Release? |
@gangsterrapper22 in both cases |
Can you post the new error message? I got the error message when connecting to a real XenServer 7.2 and then switching to the performance tab. But I got no error message from 2 "virtual" test xcp-ng servers but they only have 4 CPU and currently host no VM themself and show no performance, will try to find out more if I can. |
I used now the branded Version from @borzel which he has given me in Issue 7. When I try to open there the Performance Tab, then I get these Error message. |
OK yes I can confirm I get this from time to time. The error comes from here:
Sometimes "fivesecond" is null. It looks like "ArchiveMaintainer.Archives[ArchiveInterval.FiveSecond].Sets" is reset and returns a count of 0 items in the middle of the loop. A quick (expensive) workaround is to make a copy of the List and work with that, but maybe it should be solved by Citrix later if it is happening with the official Console.
UPDATE: just installed the official Xen Center v7.4.0 and until now it did not show this error. |
Must be because we are using unstable code base (#12 (comment)) |
@gangsterrapper22 Release shows no error because of this: XenModel\Utils\PropertyManager.cs(52):
|
I know that they will catch the error with this Line, but I think we should also fix this error. Strange is also, that it works in the Release Version if XenCenter awaits the Value of Label-performaceCPU-avg-freq. |
I also tried to add it to the Friendlynames but you I think you have to add each CPU Core to Friendlynames because XenCenter searches for this. When you only add Label-Performance.CPU-avg-freq, then this will have no effect and you get the same errors again, but your first "hack" we can use as Workarund to fix it. When you Comment out Debug, then it is just like the Release Version. :-) |
Currently I'm working on a permanent fix :-) |
No, the resx gives you a string like this "CPU {0}" and you put later the number in. |
Yes, I also tried something in the past, bit has never worked. Maybe you have more luck then I had. I am off for today. |
Please try XCP-ng Console 7.4.0.2-beta: https://github.com/xcp-ng/xenadmin/releases/tag/v7.4.0.2-beta |
Edit: I have seen that the timerange is wrong, so I think it is no bug. When I change the timerange then it works. Sorry. =============================== |
of course compiled as release version :-) |
Then it looks good so far and I think the most issues are solved for now. Then I think we can also close this case. |
I'll close this, follow up is here: #16 |
I compiled with VS 2013 the XCG-ng Center and when I am conntect
to an Server and Click on the Performance tab, then the error appears "Label-performaceCPU-avg-freq" doesn't exist. I don't know if this can be solved in the source code of XCP-ng itself or should be solved in the XCP-ng Center Application.
An Workaround where to get the Count of the CPU's and let dynamically add the Value of the Label "Label-performaceCPU-avg-freq" I have added an Screenshot of the Error message. If you click on Ignore then you will get this error message for every CPU Core.
The text was updated successfully, but these errors were encountered: