Something is messing with my HughesNet Usage Meter

[GabeU]

Well, this is funny.  I just noticed that mine is wrong.  The data is correct, but the date isn't, which is why there is the uptick at the beginning.  It's one day off.  My data cycle is the 5th through the 4th, not the 4th through the 3rd.

The online version shows the correct dates, but it's funny that I had to look at last month's to see today's date.  When I look at this month, nothing is shown.  I should add that my billing cycle is the 4th through the 3rd, which is one day off from the data cycle.  My data resets in 51 minutes.  

What's seen below is all correct (the dates and data usage), but it should still be the "This Month", not the "Previous Month".  It shouldn't be the "Previous Month" until 45 minutes from now.

What it's showing for "This Month", which, going by the dates shown, shouldn't exist yet.  

I dumped the HughesNet Usage Meter folder and repopulated it, but it made no difference.  None of this really concerns me, or at least not at this point.  It's more of a comical anomaly.  It may be back to normal tomorrow.

[kitnbob]

---

@MarkJFine wrote:

I doubt you were getting someone else's data...... more likely that there was old data in the cache and additional data got interspersed somehow. If you've looked at the innards of the file, it's basically a SQL dump format with some whacky control characters in there.

..... I have a theory that the database queries have been getting interrupted or failing, causing other issues.......

---

I DID peek at the files. the "file_0.localxxx" is a comma delineated file and still looks like somebody elses data. Where did it come from?

I cant see anything in the cache files except those wacky control characters.

OK, Let me ask, dosen't the data originate at the modem sitting infront of me on my desktop? And if my local files get corrupted  my graphics of the HughesNet Usage Meter dont work, afterall it's just a desktop app to replace using the my.hughesnet. >Usage web portal......  here's the question..

How do we know that the "additional data got interspersed somehow." didnt get into My Account database?

When ever the HughesNet Usage meter malfunctions, locally, the web portal still seems accurate. 

I really dont NEED to know.....    getting late. Thanks!    and Good Night.

Edit:  I'm sure there are logs at both ends. 

[GabeU]

---

@kitnbob wrote: 

When ever the HughesNet Usage meter malfunctions, locally, the web portal still seems accurate.  

---

Not mine, or at least not tonight.    

[kitnbob]

---

@GabeU wrote:

I dumped the HughesNet Usage Meter folder and repopulated it, but it made no difference.  None of this really concerns me, or at least not at this point.  It's more of a comical anomaly.  It may be back to normal tomorrow.

---

When is "tomorrow" on UDT time?

concerned? with your yellow line way UP at 50GB 

Edit:  Gremlins

[kitnbob]

@GabeU

It's not tomorrow Here yet.

should be... for 9 minutes now.

[MarkJFine]

---

@kitnbob wrote:

---

How do we know that the "additional data got interspersed somehow." didnt get into My Account database?

Pretty sure access to the database is read-only outside HN's tracking mechanisms precisely for that reason.

[Liz]

Hi folks,

Thanks for discussing this, we've been keeping an eye on this and are going to escalate to our engineers. I'll keep you posted on any updates we may get, or if we could use more info from you. 

  Your cooperation, patience, and understanding are much appreciated.

[kitnbob]

@Liz 

I still have the corrupted "file_0.localstorxxx" and the new regenerated file if ya'all want to compare data.

Thanks for looking into this. 

[Liz]

You're welcome, kitnbob!  Please check your private messages (PM) in the top right corner of the community page as I've sent you a PM to further address your concerns.

[MarkJFine]

---

@kitnbob wrote:

@Liz 

I still have the corrupted "file_0.localstorxxx" and the new regenerated file if ya'all want to compare data.

---

That's awesome. I was going to suggest something like that.