login vsi company logo login vsi company logo 250x40
header-02.jpg

Forum Announcement

The Login VSI forum has been disabled and now only serves as an archive. If you would like to submit a new support ticket, please send an email to support@loginvsi.com.

Analyzer issue: "Syntax error in date in query expression"

  • vjason
  • vjason's Avatar Topic Author
06 May 2013 14:56 #958

I see this often when analyzing test results (first pic).

Anyone know the cause? It usually repeats a random number of times.

For instance a recent test generated 15,542 user test loops across the 2000 desktops I tested, and I got this error 9 times while analyzer read in the test data. In addition, my VSI max graph shows only 1 desktop (second pic).

I've deleted the Login VSI mdb file in my profile dir to force it to create a new data.

Any ideas?

Thanks,

- Jason

Attachments:

Please Log in to join the conversation.

More
06 May 2013 15:04 #959

Jason,

Can you share the data with us? You can email us directly if you are not comfortable with posting the data online.

Please Log in to join the conversation.

  • vjason
  • vjason's Avatar Topic Author
06 May 2013 17:15 #962

Let me rerun the test. I've found the errors in the Zip Timer and User Loop logfiles, but correcting them wasn't enough as the session count wasn't incrementing the sessions properly in the user loop file.

I'm rebooting the NAS where the logfiles are written to (which is different from the one the desktops are on) and want to see if that fixes the issue as it appears related to the ability of the clients to write to the log files quickly enough. It isn't an IO problem as the NAS is specced to handle a lot more load than Login VSI is generating in writing the log files.

The following from the zip timer log is an example if the errors in the log files (this matches up with the sample error I pasted in the original post; it has an extra 2 at the start of the line):

22013-05-06 07:49:05,2,0,B698,VDI1698,000001,ZipTimer,2

I've been making edits to the log files and I don't want to give you the set I have because of that.

- Jason

Please Log in to join the conversation.

More
13 May 2013 11:41 #993

Hi Jason,

If you are still facing the issues, we are more than glad to help you.

But please keep in mind, it doesn't make it easier for us if the required information (like logs etc.) cant be provided from customers.

Do you still need help or have any further questions, please let us know.

Regards,

Omar

Please Log in to join the conversation.

  • vjason
  • vjason's Avatar Topic Author
13 May 2013 12:44 #994

The problem is with the ziptimer and userloop files (see attached for some examples). What is happening is that too many desktops are trying to write to those log files at once, and it is leading to errors similar to what I posted above.

Examples:

22013-05-10 22:06:47,833,1387,B831,VDI2871,000467,UserLoop,833

or

2013-05-10 15:22:17,0,2000,A988,VDI1888,001000,ZipTimer,022013-05-10 15:22:17,0,2000,A875,VDI1786,001953,ZipTimer,0

or

2013-05-10 11:12:36,829, ,B204,VDI2306,000285,UserLoop,829

You can find examples of all but #2 in the attached files.

Those are the only two files that have problems, which makes sense since the other log files are unique and tied to the individual desktop. The problem is limited to those files which are shared by desktops and written to over and over while the test is going on.

My tests are typically 2000 desktops or more so I will have a lot of desktops trying to write to those files at any given time. I did a spot check based on times and I saw up to 10 desktops writing to a log file within a given second, and that was just the first example I came across.

For what it is worth, the test scores appear similar if I proceeed with the analyzer despite the errors, or if I fix the errors and rerun the analyzer. This is probably because there are usually less than 30 or so errors for the 15000+ lines that are in my average log file.

Thanks,

Jason

Please Log in to join the conversation.

More
16 May 2013 10:25 #1011

Jason,

The reason why these errors do not influence the test result is because these specific logs are not used in the VSImax calculation. They are only used to populate the Userloop, Ziptimer and Logontimer tabs.

I recommended another customer that was experiencing this issue to look at the performance of the VSIshare. I have personally ran tests at a customer with 5000 user and did not run into this issue.

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200