Kitz ADSL Broadband Information
adsl spacer  
Support this site
Home Broadband ISPs Tech Routers Wiki Forum
 
     
   Compare ISP   Rate your ISP
 
Please login or register.

Login with username, password and session length
Advanced search  

News:

Pages: 1 2 [3] 4 5 ... 8

Author Topic: HG612 Modem Stats Editor & GUI v5 released  (Read 33180 times)

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #30 on: May 22, 2015, 11:25:46 PM »

See if there is a 'stuck' instance of HG612_Run.exe and/or HG612_stats.exe in Windows Task Manager.
If so, end its process & see if that kickstarts the auto-logging again.

Is your GUI the same version/date as the one in my screenshot?

Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #31 on: May 22, 2015, 11:31:22 PM »

Another user had the same issue:-

https://community.plus.net/forum/index.php/topic,139651.0.html

Just checking again, it looks as though he is using a slightly older version of the GUI than mine.

Logged

tommy45

  • Reg Member
  • ***
  • Posts: 536
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #32 on: May 22, 2015, 11:48:27 PM »

I have got it going again after deleting all exceptions in my Av firewall and deleting the  scheduled task it creates,
Then i got the pop up asking to open the file every 2mins or so, so i un selected the warn me every time the file wants to open so far so good, the ongoing error log was too big for notepad ,so i deleted it since, as it be pointless having a log file that you can't read, imo  BTW all the versions are the same builds as in your SS BE, thanks for you speedy support, i think in my case something got corrupted  somehow ,
« Last Edit: May 22, 2015, 11:51:49 PM by tommy45 »
Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #33 on: May 22, 2015, 11:53:58 PM »

To keep the log files to a minimum size, you could disable the 'extra' logging (until there appears to be a program error):-

Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #34 on: May 22, 2015, 11:57:07 PM »

I have got it going again after deleting all exceptions in my Av firewall


Which AV/Firewall do you use?


Logged

tommy45

  • Reg Member
  • ***
  • Posts: 536
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #35 on: May 23, 2015, 12:13:45 AM »

Eset SS v7 Just noticed that it had stopped harvesting stats again, this time i was able to the the HG612 stats.exe process in task manager stuck as you mentioned earlier, i simply killed the process and it started  running again
What would cause it to hang?
« Last Edit: May 23, 2015, 02:20:49 AM by tommy45 »
Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #36 on: May 23, 2015, 08:23:11 AM »

If you ever have to kill its process, depending how far it got before it got stuck, a file named something like ONGOING-ISRUNNING-072713-194.TXT should be left behind in the Scripts folder.

If you haven't already deleted any of those files, could you please post the most recent one for me to look at?
It should contain a list of all the processes running at the time HG612_stats.exe started running.



Strictly speaking, if something goes wrong, HG612_stats.exe should record the problem in ONGOING_ERROR.LOG_file_ERROR.TXT & exit gracefully.

Could you please post that file for me to examine?
You may need to compress it first for it to fit within the forum's attachment file size limit.


My suspicion is that either some other program is blocking or causing HG612_stats.exe and/or HG612_Run.exe to hang or that something else is accessing the modem at the same time which would corrupt the modem's responses to HG612_stats.exe's stats data requests at an unexpected stage.


Whenever more than 1 instance of HG612_stats.exe attempt to run at the same time, possibly if the first instance has been slowed down by something else hogging all the PC's resources etc, one or both of the instances should be exited & a record of it logged in the EXIT_2_INSTANCES.LOG file.


Here are a couple of examples from when my resource hungry AV program (AVG 2015) slowed my PC down when running its daily scan:-

23/02/2015  4:09:08.66 - ONGOING-ISRUNNING-040900-398.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015  4:09:08.66 - ONGOING-ISRUNNING-040800-587.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015  4:09:08.71 - ONGOING-ISRUNNING-040800-587.TXT - ** ONGOING-ISRUNNING-040800-587.TXT DELETED - Status = 1,
23/02/2015  4:09:08.71 - ONGOING-ISRUNNING-040900-398.TXT - ** ONGOING-ISRUNNING-040900-398.TXT DELETED - Status = 1,


That tells me that the instance of HG612_stats.exe from 04:08 was still running at the time the 04:09 instance started.
Both instances needed to exit to avoid any of them hanging.
 


23/02/2015  4:33:28.83 - ONGOING-ISRUNNING-043300-298.TXT - ** Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1,
23/02/2015  4:33:28.90 - ONGOING-ISRUNNING-043300-298.TXT - ** ONGOING-ISRUNNING-043300-298.TXT DELETED - Status = 1,

That tells me that the instance from 04:32 must have still been running when the 04:33 instance started, but this time, only the instance from 04:33 needed to exit.


Could you also post your EXIT_2_INSTANCES.LOG file so I can see what was happening at around the problematic times?


Once we can confirm what causes the issue, I can build in some code to deal with it.



EDIT:

I see that your most recent upload to MDWS was timed at 05:59 this morning so it seems the problem is still present, unless you intentionally stopped the uploads or that you PC or ROUTER went into sleep mode etc.




« Last Edit: May 23, 2015, 08:33:16 AM by Bald_Eagle1 »
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 536
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #37 on: May 23, 2015, 01:05:29 PM »

Ok i uploaded  all 3 files you requested, and yes it appears to be hanging the process for some reason , the ONGOING_ERROR.LOG_file_ERROR.TXT .zip had to be renamed from the.rar extension because we can't upload files with a .rar extension, so you may have to rename it so it becomes a .rar again
« Last Edit: May 23, 2015, 01:38:11 PM by tommy45 »
Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #38 on: May 23, 2015, 02:04:28 PM »

This MIGHT be the problem:-

23/05/2015  6:00:07.56 - ONGOING-ISRUNNING-060000-109.TXT - *** Scheduled snapshot logging IS due, running [HG612_current_stats.exe].

That should go on to record this:-

23/05/2015  6:00:05.84 - ONGOING-ISRUNNING-060000-088.TXT - Normal End of [HG612_stats.exe]
23/05/2015  6:00:07.77 - ONGOING-ISRUNNING-060000-088.TXT - Start of [Upload.exe] - **** Version 5.1.0.0 16/05/2015 ****
23/05/2015  6:00:08.18 - ONGOING-ISRUNNING-060000-088.TXT - Now exiting [Upload.exe]. Status = 1,
 
23/05/2015  6:00:08.29 - ONGOING-ISRUNNING-060000-088.TXT - End of [HG612_stats.exe] AFTER WebStats stuff



Being as the rest of the 06:00 log was missing, I suspect that HG612_current_stats.exe was 'blocked' & therefore it didn't complete.
In turn, that could have stopped HG612_stats.exe from 06:00 from completing (i.e. hanging), meaning that it was still running when the next instance was due at 06:01:-


23/05/2015  6:01:00.15 - ONGOING-ISRUNNING-060100-109.TXT - Start of [HG612_stats.exe] - **** Version 5.1.0.0 16/05/2015 ****
23/05/2015  6:01:00.82 - ONGOING-ISRUNNING-060100-109.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
23/05/2015  6:01:00.93 - ONGOING-ISRUNNING-060100-109.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
23/05/2015  6:01:00.95 - ONGOING-ISRUNNING-060100-109.TXT - About to close(sockfd). Status = 1,
23/05/2015  6:01:00.98 - ONGOING-ISRUNNING-060100-109.TXT - About to freeadddrinfo(res). Status = 1,
23/05/2015  6:01:01.03 - ONGOING-ISRUNNING-060100-109.TXT - ERROR.LOG successfully closed. Status = 0,
23/05/2015  6:01:01.04 - ONGOING-ISRUNNING-060100-109.TXT - *** End of [HG612_stats.exe] - 2 OR MORE INSTANCES WERE RUNNING. Status = 0,


There may well also be a 'stuck' instance of HG612_current_stats.exe that needs its process ending via Task Manager.


You could try running HG612_current_stats.exe manually, to see if Windows or your AV/Firewall asks if it should always be allowed or not.

If you are asked the question, select the option that always allows it or doesn't ask again.

You MAY also need to allow it via your AV/Firewall program to (hopefully) ensure this issue doesn't crop up again.


To test this out, after you are able to confirm that HG612_current_stats.exe runs all the way through to normal to completion when run manually, could you temporarily adjust the schedule interval in the GUI to 1 hour rather than the (probably) 8 hours default setting?

See the attached screenshot for where that setting is located.

It should then auto-run at the next hour & every hour following that.


Please let me know whether that resolves the issue or not in case I need to look somewhere else.





EDIT:

Some typos corrected

« Last Edit: May 23, 2015, 02:29:30 PM by Bald_Eagle1 »
Logged

tommy45

  • Reg Member
  • ***
  • Posts: 536
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #39 on: May 23, 2015, 02:43:10 PM »

The processes are all allowed  to run and have rules in the AV firewall , so nothing obvious, i have  just deleated all the fw rules and all the Hips rules that the program creates in order to run, i have also run the HG STATS.exe  manually and it appeared to run without error, no pop up prompts from my AV
Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #40 on: May 23, 2015, 02:47:17 PM »

i have also run the HG STATS.exe  manually and it appeared to run without error, no pop up prompts from my AV


Does HG612_current_stats.exe run O.K. when run manually though & are any of the programs in the Scripts folder 'stuck' in Task Manager?

Logged

tommy45

  • Reg Member
  • ***
  • Posts: 536
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #41 on: May 23, 2015, 03:36:36 PM »

It hung again, in task manager the only process related that was stuck/hung was the HG612_stats.exe process i did notice just before i killed it what i think was another instance of the  HG612_stats.exe that disappeared abruptly

As for the HG612_stats.exe running as intended or not without being able to save the data in the cmd prompt window that it opens  when i run it manually i can't say for sure, even then  if it didn't generate an error  i would be none the wiser , but the window closes quickly , the process doesn't stay in the list of processes for long afterwards

When the HG612_stats.exe  is run it also runs AcroRd32.exe which is adobe reader i'm a little puzzled as to why this is associated with HG612_stats.exe ?
« Last Edit: May 23, 2015, 04:11:33 PM by tommy45 »
Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #42 on: May 23, 2015, 04:22:44 PM »

From MDWS, it looks as though the 14:59 instance ran O.K., but the 15:00 instance didn't.

If you had indeed set the snapshot schedule to run every hour, it 'appears' that running HG612_current_stats.exe from HG612_stats.exe is the problem.


What is in CURRENT_ERROR.LOG_file_ERROR.TXT from when the problem first reared its head?

It should look something like this:-

23/05/2015  0:00:05.39 - CURRENT-ISRUNNING-000005-287 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
23/05/2015  0:00:06.11 - CURRENT-ISRUNNING-000005-287 - From IsRunningVB.exe, there are 1 instances of HG612_stats.exe running. Status = 1,
23/05/2015  0:00:10.75 - CURRENT-ISRUNNING-000005-287 - Normal End of [HG612_current_stats.exe] - Status = 0,


23/05/2015  6:00:07.60 - CURRENT-ISRUNNING-060005-907 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
23/05/2015  6:00:08.09 - CURRENT-ISRUNNING-060005-907 - From IsRunningVB.exe, there are 1 instances of HG612_stats.exe running. Status = 1,
23/05/2015  6:00:08.46 - CURRENT-ISRUNNING-060005-907 - [HG612_stats.exe] is still running
23/05/2015  6:00:12.81 - CURRENT-ISRUNNING-060005-907 - Normal End of [HG612_current_stats.exe] - Status = 0,


In my example from 00:00, HG612_stats.exe will have completed quite soon after HG612_current_stats.exe started


In the example form 06:00, when my PC was also busy doing other things, HG612_stats.exe didn't complete so quickly & HG612_current_stats.exe waited for it to complete before continuing:-

23/05/2015  6:00:08.46 - CURRENT-ISRUNNING-060005-907 - [HG612_stats.exe] is still running


It might just be that HG612_current_stats.exe waits too long on your setup?
Your CURRENT_ERROR.LOG_file_ERROR.TXT log might confirm that one way or the other

I have just noticed from MDWS that the same thing appears to have happened at 16:00, so it at least appears that we're getting close to working out what needs changing.


Logged

Bald_Eagle1

  • Moderator
  • Kitizen
  • *
  • Posts: 2719
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #43 on: May 23, 2015, 04:25:57 PM »

When the HG612_stats.exe  is run it also runs AcroRd32.exe which is adobe reader i'm a little puzzled as to why this is associated with HG612_stats.exe ?


Does AcroRd32.exe  run EVERY time HG612_stats.exe runs?

They are not associated, so that's another mystery for me to look into.

Logged

tommy45

  • Reg Member
  • ***
  • Posts: 536
Re: HG612 Modem Stats Editor & GUI v5 released
« Reply #44 on: May 23, 2015, 04:38:57 PM »

Quote
CURRENT_ERROR.LOG_file_ERROR.TXT


19/05/2015 21:00:07.82 - CURRENT-ISRUNNING-210007-732 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
19/05/2015 21:00:29.27 - CURRENT-ISRUNNING-210007-732 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  0:00:08.09 - CURRENT-ISRUNNING-000007-967 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  0:00:24.59 - CURRENT-ISRUNNING-000007-967 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  3:00:07.90 - CURRENT-ISRUNNING-030007-826 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  3:00:24.65 - CURRENT-ISRUNNING-030007-826 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  6:00:08.27 - CURRENT-ISRUNNING-060008-201 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  6:00:25.13 - CURRENT-ISRUNNING-060008-201 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015  9:00:07.85 - CURRENT-ISRUNNING-090007-779 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015  9:00:24.71 - CURRENT-ISRUNNING-090007-779 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 12:00:07.85 - CURRENT-ISRUNNING-120007-779 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 12:00:24.79 - CURRENT-ISRUNNING-120007-779 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 15:00:08.40 - CURRENT-ISRUNNING-150008-264 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 15:00:27.26 - CURRENT-ISRUNNING-150008-264 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 18:00:09.01 - CURRENT-ISRUNNING-180008-889 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 18:00:25.88 - CURRENT-ISRUNNING-180008-889 - Normal End of [HG612_current_stats.exe] - Status = 0,


20/05/2015 21:00:10.26 - CURRENT-ISRUNNING-210009-982 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
20/05/2015 21:00:29.45 - CURRENT-ISRUNNING-210009-982 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  0:00:08.24 - CURRENT-ISRUNNING-000008-107 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  0:00:24.95 - CURRENT-ISRUNNING-000008-107 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  3:00:09.65 - CURRENT-ISRUNNING-030009-467 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  3:00:27.88 - CURRENT-ISRUNNING-030009-467 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  6:00:08.26 - CURRENT-ISRUNNING-060008-154 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  6:00:25.26 - CURRENT-ISRUNNING-060008-154 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015  9:00:08.04 - CURRENT-ISRUNNING-090007-967 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015  9:00:24.79 - CURRENT-ISRUNNING-090007-967 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 12:00:08.15 - CURRENT-ISRUNNING-120008-061 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 12:00:24.57 - CURRENT-ISRUNNING-120008-061 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 15:00:09.09 - CURRENT-ISRUNNING-150008-951 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 15:00:26.51 - CURRENT-ISRUNNING-150008-951 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 18:00:08.10 - CURRENT-ISRUNNING-180007-967 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 18:00:25.02 - CURRENT-ISRUNNING-180007-967 - Normal End of [HG612_current_stats.exe] - Status = 0,


21/05/2015 21:00:08.26 - CURRENT-ISRUNNING-210008-154 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
21/05/2015 21:00:25.24 - CURRENT-ISRUNNING-210008-154 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  0:00:07.95 - CURRENT-ISRUNNING-000007-873 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  0:00:24.76 - CURRENT-ISRUNNING-000007-873 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  3:00:07.99 - CURRENT-ISRUNNING-030007-896 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  3:00:25.00 - CURRENT-ISRUNNING-030007-896 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  6:00:07.80 - CURRENT-ISRUNNING-060007-723 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  6:00:24.81 - CURRENT-ISRUNNING-060007-723 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015  9:00:07.78 - CURRENT-ISRUNNING-090007-706 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015  9:00:24.72 - CURRENT-ISRUNNING-090007-706 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 12:00:08.53 - CURRENT-ISRUNNING-120008-346 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 12:00:25.61 - CURRENT-ISRUNNING-120008-346 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 15:00:07.86 - CURRENT-ISRUNNING-150007-786 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 15:00:24.70 - CURRENT-ISRUNNING-150007-786 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 18:00:07.97 - CURRENT-ISRUNNING-180007-879 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 18:00:24.83 - CURRENT-ISRUNNING-180007-879 - Normal End of [HG612_current_stats.exe] - Status = 0,


22/05/2015 21:09:37.46 - CURRENT-ISRUNNING-210937-359 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***


22/05/2015 22:40:49.17 - CURRENT-ISRUNNING-224049-078 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
22/05/2015 22:41:01.79 - CURRENT-ISRUNNING-224049-078 - Normal End of [HG612_current_stats.exe] - Status = 0,


23/05/2015 16:15:43.92 - CURRENT-ISRUNNING-161543-843 - Start of [HG612_current_stats.exe] *** Version 5.0.0.3 - 24/04/2015 ***
23/05/2015 16:15:57.87 - CURRENT-ISRUNNING-161543-843 - Normal End of [HG612_current_stats.exe] - Status = 0,

No the adobe process doesn't appear to run every time, just sometimes when i run it manually  It also maybe related to the snapshot data logging as i have set it to 1 time every 24hrs and it so far hasn't got stuck
« Last Edit: May 23, 2015, 06:43:44 PM by tommy45 »
Logged
Pages: 1 2 [3] 4 5 ... 8
 

anything