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

Login with username, password and session length
Advanced search  

News:

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

Author Topic: HG612 modem stats - multiple instances.  (Read 33656 times)

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33035
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: HG612 modem stats - multiple instances.
« Reply #15 on: August 24, 2013, 02:07:01 PM »

BE dont know if this helps, but you can see for the period

when I was using the fix, (13:39 to 13:41)  no data was being appended to HG612_Modem_Stats\Ongoing_Stats\modem_stats.log

13:42 is when I dropped v1.1 back in


Code: [Select]
24/08/2013 13:40:00.38 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 13:40:00.39 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 13:40:00.41 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 13:40:00.47 - About to create ONGOING-ISRUNNING-134000-462.TXT Status = 1,
24/08/2013 13:40:00.48 - ONGOING-ISRUNNING-134000-462.TXT created. Status = 1,
24/08/2013 13:40:00.60 - ONGOING-ISRUNNING-134000-462.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
24/08/2013 13:40:00.61 - ONGOING-ISRUNNING-134000-462.TXT - ** Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
24/08/2013 13:40:00.62 - ONGOING-ISRUNNING-134000-462.TXT - C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG opened for appending. Status = 1,
24/08/2013 13:40:00.64 - ONGOING-ISRUNNING-134000-462.TXT - malloc() O.K. Status = 1,
24/08/2013 13:40:00.65 - ONGOING-ISRUNNING-134000-462.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
24/08/2013 13:40:00.66 - ONGOING-ISRUNNING-134000-462.TXT - getaddrinfo() O.K. Status = 1,
24/08/2013 13:40:00.67 - ONGOING-ISRUNNING-134000-462.TXT - connect() O.K. Status = 1,
24/08/2013 13:40:00.68 - ONGOING-ISRUNNING-134000-462.TXT - ********** DEBUG VERSION - Trying the HG622 bodge. Status = 1. **********
24/08/2013 13:40:00.69 - ONGOING-ISRUNNING-134000-462.TXT - ********** The HG622 bodge worked Status = 1.                  **********
24/08/2013 13:40:00.70 - ONGOING-ISRUNNING-134000-462.TXT - About to log in to the modem. Status = 1,
24/08/2013 13:40:00.91 - ONGOING-ISRUNNING-134000-462.TXT - **** expect("gin:") O.K. Status = 1.
24/08/2013 13:40:00.93 - ONGOING-ISRUNNING-134000-462.TXT - **** reply(config.Username) O.K. Status = 1.
24/08/2013 13:40:01.14 - ONGOING-ISRUNNING-134000-462.TXT - **** expect("ssword:") O.K. Status = 1.
24/08/2013 13:40:01.16 - ONGOING-ISRUNNING-134000-462.TXT - **** reply(config.Password) O.K. Status = 1.
24/08/2013 13:40:01.37 - ONGOING-ISRUNNING-134000-462.TXT - **** expect("ATP>") O.K. Status = 1.
24/08/2013 13:40:01.39 - ONGOING-ISRUNNING-134000-462.TXT - **** reply(config.Shell) O.K. Status = 1.


24/08/2013 13:41:00.37 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 13:41:00.39 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 13:41:00.40 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 13:41:00.46 - About to create ONGOING-ISRUNNING-134100-455.TXT Status = 1,
24/08/2013 13:41:00.47 - ONGOING-ISRUNNING-134100-455.TXT created. Status = 1,
24/08/2013 13:41:00.60 - ONGOING-ISRUNNING-134100-455.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 13:41:00.61 - ONGOING-ISRUNNING-134100-455.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 13:41:00.62 - ONGOING-ISRUNNING-134100-455.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 13:41:00.63 - ONGOING-ISRUNNING-134100-455.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 13:42:00.38 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 13:42:00.39 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 13:42:00.40 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 13:42:00.46 - About to create ONGOING-ISRUNNING-134200-457.TXT Status = 1,
24/08/2013 13:42:00.47 - ONGOING-ISRUNNING-134200-457.TXT created. Status = 1,
24/08/2013 13:42:00.61 - ONGOING-ISRUNNING-134200-457.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
24/08/2013 13:42:00.62 - ONGOING-ISRUNNING-134200-457.TXT - ** Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
24/08/2013 13:42:00.63 - ONGOING-ISRUNNING-134200-457.TXT - C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG opened for appending. Status = 1,
24/08/2013 13:42:00.64 - ONGOING-ISRUNNING-134200-457.TXT - malloc() O.K. Status = 1,
24/08/2013 13:42:00.65 - ONGOING-ISRUNNING-134200-457.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
24/08/2013 13:42:00.66 - ONGOING-ISRUNNING-134200-457.TXT - getaddrinfo() O.K. Status = 1,
24/08/2013 13:42:00.67 - ONGOING-ISRUNNING-134200-457.TXT - connect() O.K. Status = 1,
24/08/2013 13:42:00.68 - ONGOING-ISRUNNING-134200-457.TXT - ********** DEBUG VERSION - Trying the HG622 bodge. Status = 1. **********
24/08/2013 13:42:00.69 - ONGOING-ISRUNNING-134200-457.TXT - ********** The HG622 bodge worked Status = 1.                  **********
24/08/2013 13:42:00.71 - ONGOING-ISRUNNING-134200-457.TXT - About to log in to the modem. Status = 1,
24/08/2013 13:42:00.91 - ONGOING-ISRUNNING-134200-457.TXT - **** expect("gin:") O.K. Status = 1.
24/08/2013 13:42:00.92 - ONGOING-ISRUNNING-134200-457.TXT - **** reply(config.Username) O.K. Status = 1.
24/08/2013 13:42:01.11 - ONGOING-ISRUNNING-134200-457.TXT - **** expect("ssword:") O.K. Status = 1.
24/08/2013 13:42:01.12 - ONGOING-ISRUNNING-134200-457.TXT - **** reply(config.Password) O.K. Status = 1.
24/08/2013 13:42:01.32 - ONGOING-ISRUNNING-134200-457.TXT - **** expect("ATP>") O.K. Status = 1.
24/08/2013 13:42:01.33 - ONGOING-ISRUNNING-134200-457.TXT - **** reply(config.Shell) O.K. Status = 1.
24/08/2013 13:42:01.53 - ONGOING-ISRUNNING-134200-457.TXT - **** expect("# ") O.K. Status = 1.
24/08/2013 13:42:01.55 - ONGOING-ISRUNNING-134200-457.TXT - **** Reaching this point means logging in to the modem was successful. Status = 1,
24/08/2013 13:42:01.56 - ONGOING-ISRUNNING-134200-457.TXT - After xdslcmd info --stats(), ERROR.LOG status = 1
24/08/2013 13:42:01.78 - ONGOING-ISRUNNING-134200-457.TXT - After xdslcmd info --pbParams(), ERROR.LOG status = 1
24/08/2013 13:42:02.18 - ONGOING-ISRUNNING-134200-457.TXT - Logged out of modem O.K. Status = 1,
24/08/2013 13:42:02.23 - ONGOING-ISRUNNING-134200-457.TXT - get_log_data() completed. Status = 1,
24/08/2013 13:42:02.26 - ONGOING-ISRUNNING-134200-457.TXT - Appending data to C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Ongoing_Stats\modem_stats.log - Status = 1,
24/08/2013 13:42:02.27 - ONGOING-ISRUNNING-134200-457.TXT - Data has now been written to MSLOGFILE (C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Ongoing_Stats\modem_stats.log) - Status = 1,
24/08/2013 13:42:02.28 - ONGOING-ISRUNNING-134200-457.TXT - Now in exit. Status = 1,
24/08/2013 13:42:02.30 - ONGOING-ISRUNNING-134200-457.TXT - ONGOING-ISRUNNING-134200-457.TXT DELETED - Status = 1,
24/08/2013 13:42:02.31 - ONGOING-ISRUNNING-134200-457.TXT - End of HG612_stats.exe. Status = 1,
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

ColinS

  • Reg Member
  • ***
  • Posts: 529
Re: HG612 modem stats - multiple instances.
« Reply #16 on: August 24, 2013, 02:08:41 PM »

Kitz, I had a similar issue with the task when I first installed v1.1 when I mistakenly assumed I should carry over the .ini file.  Although I added the extra line to the end of it as BE1 suggested I do, to be sure I used the Tasks menu of the Setting Editor to delete and (re)create the task.  It may be worth a shot if you haven't already tried this. I think the task naming was different between v1.0 & v1.1
Logged

ColinS

  • Reg Member
  • ***
  • Posts: 529
Re: HG612 modem stats - multiple instances.
« Reply #17 on: August 24, 2013, 02:23:25 PM »

While we wait for BE1 to return, some questions and something to try:
What version of Windows are you running?
What version of the HG612/firmware do you have?
Are you running HG612 in any sort of remote session?

Can you try manually logging into the HG612 with telnet - username/passord/sh/xdlscmd info --stats/exit/exit with success?
[Edit]Do you get all the expected prompts and replies, notably the # prompt missing from your failing examples above?

Here's what I get when it's working:

24/08/2013 14:17:00.31 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 14:17:00.32 - working_directory = F:\HG612\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 14:17:00.35 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 14:17:00.68 - About to create ONGOING-ISRUNNING-141700-670.TXT Status = 1,
24/08/2013 14:17:00.71 - ONGOING-ISRUNNING-141700-670.TXT created. Status = 1,
24/08/2013 14:17:01.45 - ONGOING-ISRUNNING-141700-670.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:17:01.46 - ONGOING-ISRUNNING-141700-670.TXT - ** Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
24/08/2013 14:17:01.48 - ONGOING-ISRUNNING-141700-670.TXT - F:\HG612\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG opened for appending. Status = 1,
24/08/2013 14:17:01.49 - ONGOING-ISRUNNING-141700-670.TXT - malloc() O.K. Status = 1,
24/08/2013 14:17:01.53 - ONGOING-ISRUNNING-141700-670.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
24/08/2013 14:17:01.54 - ONGOING-ISRUNNING-141700-670.TXT - getaddrinfo() O.K. Status = 1,
24/08/2013 14:17:01.57 - ONGOING-ISRUNNING-141700-670.TXT - connect() O.K. Status = 1,
24/08/2013 14:17:01.59 - ONGOING-ISRUNNING-141700-670.TXT - ********** DEBUG VERSION - Trying the HG622 bodge. Status = 1. ********
24/08/2013 14:17:01.62 - ONGOING-ISRUNNING-141700-670.TXT - ********** The HG622 bodge worked Status = 1.                  **********
24/08/2013 14:17:01.63 - ONGOING-ISRUNNING-141700-670.TXT - About to log in to the modem. Status = 1,
24/08/2013 14:17:01.67 - ONGOING-ISRUNNING-141700-670.TXT - **** expect("gin:") O.K. Status = 1.
24/08/2013 14:17:01.68 - ONGOING-ISRUNNING-141700-670.TXT - **** reply(config.Username) O.K. Status = 1.
24/08/2013 14:17:01.85 - ONGOING-ISRUNNING-141700-670.TXT - **** expect("ssword:") O.K. Status = 1.
24/08/2013 14:17:01.88 - ONGOING-ISRUNNING-141700-670.TXT - **** reply(config.Password) O.K. Status = 1.
24/08/2013 14:17:02.06 - ONGOING-ISRUNNING-141700-670.TXT - **** expect("ATP>") O.K. Status = 1.
24/08/2013 14:17:02.09 - ONGOING-ISRUNNING-141700-670.TXT - **** reply(config.Shell) O.K. Status = 1.
24/08/2013 14:17:02.26 - ONGOING-ISRUNNING-141700-670.TXT - **** expect("# ") O.K. Status = 1.
24/08/2013 14:17:02.29 - ONGOING-ISRUNNING-141700-670.TXT - **** Reaching this point means logging in to the modem was successful. Status = 1,
24/08/2013 14:17:02.31 - ONGOING-ISRUNNING-141700-670.TXT - After xdslcmd info --stats(), ERROR.LOG status = 1
24/08/2013 14:17:02.46 - ONGOING-ISRUNNING-141700-670.TXT - After xdslcmd info --pbParams(), ERROR.LOG status = 1
24/08/2013 14:17:02.87 - ONGOING-ISRUNNING-141700-670.TXT - Logged out of modem O.K. Status = 1,
24/08/2013 14:17:02.90 - ONGOING-ISRUNNING-141700-670.TXT - get_log_data() completed. Status = 1,
24/08/2013 14:17:02.93 - ONGOING-ISRUNNING-141700-670.TXT - Appending data to F:\HG612\HG612_Modem_Stats\Ongoing_Stats\modem_stats.log - Status = 1,
24/08/2013 14:17:02.95 - ONGOING-ISRUNNING-141700-670.TXT - Data has now been written to MSLOGFILE (F:\HG612\HG612_Modem_Stats\Ongoing_Stats\modem_stats.log) - Status = 1,
24/08/2013 14:17:02.96 - ONGOING-ISRUNNING-141700-670.TXT - Now in exit. Status = 1,
24/08/2013 14:17:02.99 - ONGOING-ISRUNNING-141700-670.TXT - ONGOING-ISRUNNING-141700-670.TXT DELETED - Status = 1,
24/08/2013 14:17:03.01 - ONGOING-ISRUNNING-141700-670.TXT - End of HG612_stats.exe. Status = 1,
 
« Last Edit: August 24, 2013, 02:31:27 PM by ColinS »
Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33035
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: HG612 modem stats - multiple instances.
« Reply #18 on: August 24, 2013, 02:40:31 PM »

Cheers Colin.   

I deliberately started completely afresh with v1.1 because I was doing this, which covers my exact step by step process and a new ini file was created.
(The c:\ root path was mocked just for the tutorial and I have never run from c:\  - as you can see from the setting of the directory path).

Before I started I actually cleared the task via Task Scheduler - not HG612 Editor -  because I wanted to make sure nothing was left behind.

None of the original content of v1 was retained ie the Apps and Scripts folders were brand new.   The only folders I did retain were Current_Stats & Ongoing_Stats in order to preserve previous logging data.

>>> to be sure I used the Tasks menu of the Setting Editor to delete and (re)create the task.

Ok this is the only thing I did different, as I used Windows Scheduler -  so I'll give that a shot now.




>> What version of Windows are you running?

Windows 7 Professional 64bit SP1

>> What version of the HG612/firmware do you have?

Hardware version    VER.B
Software version    V100R001C01B028SP10
Firmware version    A2pv6C030b.d22g

Not had any problem logging into the shell to get pbparams but I'll also try what you say

No problems with xdslcmd info --stats

« Last Edit: August 24, 2013, 02:47:59 PM by kitz »
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33035
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: HG612 modem stats - multiple instances.
« Reply #19 on: August 24, 2013, 03:10:45 PM »

24/08/2013 14:54 logged ok with 1.1

Task deleted, deleted 1.1 exe . 
Deleted all HG612 instances in Windows Task Manager
replaced with fix.exe

logging stops confirmed scheduled task exists - all is green

but no logging being appended to modem_stats.log


15:06 replaced fix.exe with 1.1.exe
24/08/2013 15:07 logging resumes.


Contents of ERROR.LOG_file_ERROR.TXT appended.

Code: [Select]
24/08/2013 14:56:00.36 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 14:56:00.38 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 14:56:00.39 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 14:56:00.44 - About to create ONGOING-ISRUNNING-145600-445.TXT Status = 1,
24/08/2013 14:56:00.46 - ONGOING-ISRUNNING-145600-445.TXT created. Status = 1,
24/08/2013 14:56:00.58 - ONGOING-ISRUNNING-145600-445.TXT - There are 1 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:56:00.58 - ONGOING-ISRUNNING-145600-445.TXT - ** Continuing as there are only 1 instances of HG612_stats.exe running **. Status = 1,
24/08/2013 14:56:00.60 - ONGOING-ISRUNNING-145600-445.TXT - C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Ongoing_Stats\ERROR.LOG opened for appending. Status = 1,
24/08/2013 14:56:00.61 - ONGOING-ISRUNNING-145600-445.TXT - malloc() O.K. Status = 1,
24/08/2013 14:56:00.63 - ONGOING-ISRUNNING-145600-445.TXT - WSAStartup() SUCCESSFUL!!! Status = 1,
24/08/2013 14:56:00.63 - ONGOING-ISRUNNING-145600-445.TXT - getaddrinfo() O.K. Status = 1,
24/08/2013 14:56:00.64 - ONGOING-ISRUNNING-145600-445.TXT - connect() O.K. Status = 1,
24/08/2013 14:56:00.66 - ONGOING-ISRUNNING-145600-445.TXT - ********** DEBUG VERSION - Trying the HG622 bodge. Status = 1. **********
24/08/2013 14:56:00.67 - ONGOING-ISRUNNING-145600-445.TXT - ********** The HG622 bodge worked Status = 1.                  **********
24/08/2013 14:56:00.67 - ONGOING-ISRUNNING-145600-445.TXT - About to log in to the modem. Status = 1,
24/08/2013 14:56:00.88 - ONGOING-ISRUNNING-145600-445.TXT - **** expect("gin:") O.K. Status = 1.
24/08/2013 14:56:00.89 - ONGOING-ISRUNNING-145600-445.TXT - **** reply(config.Username) O.K. Status = 1.
24/08/2013 14:56:01.10 - ONGOING-ISRUNNING-145600-445.TXT - **** expect("ssword:") O.K. Status = 1.
24/08/2013 14:56:01.11 - ONGOING-ISRUNNING-145600-445.TXT - **** reply(config.Password) O.K. Status = 1.
24/08/2013 14:56:01.35 - ONGOING-ISRUNNING-145600-445.TXT - **** expect("ATP>") O.K. Status = 1.
24/08/2013 14:56:01.38 - ONGOING-ISRUNNING-145600-445.TXT - **** reply(config.Shell) O.K. Status = 1.


24/08/2013 14:57:00.38 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 14:57:00.39 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 14:57:00.41 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 14:57:00.45 - About to create ONGOING-ISRUNNING-145700-458.TXT Status = 1,
24/08/2013 14:57:00.47 - ONGOING-ISRUNNING-145700-458.TXT created. Status = 1,
24/08/2013 14:57:00.59 - ONGOING-ISRUNNING-145700-458.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:57:00.61 - ONGOING-ISRUNNING-145700-458.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:57:00.63 - ONGOING-ISRUNNING-145700-458.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:57:00.63 - ONGOING-ISRUNNING-145700-458.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 14:58:00.39 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 14:58:00.39 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 14:58:00.40 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 14:58:00.47 - About to create ONGOING-ISRUNNING-145800-456.TXT Status = 1,
24/08/2013 14:58:00.48 - ONGOING-ISRUNNING-145800-456.TXT created. Status = 1,
24/08/2013 14:58:00.61 - ONGOING-ISRUNNING-145800-456.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:58:00.62 - ONGOING-ISRUNNING-145800-456.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:58:00.64 - ONGOING-ISRUNNING-145800-456.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:58:00.65 - ONGOING-ISRUNNING-145800-456.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 14:59:00.39 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 14:59:00.40 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 14:59:00.42 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 14:59:00.46 - About to create ONGOING-ISRUNNING-145900-469.TXT Status = 1,
24/08/2013 14:59:00.48 - ONGOING-ISRUNNING-145900-469.TXT created. Status = 1,
24/08/2013 14:59:00.61 - ONGOING-ISRUNNING-145900-469.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:59:00.62 - ONGOING-ISRUNNING-145900-469.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:59:00.62 - ONGOING-ISRUNNING-145900-469.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 14:59:00.64 - ONGOING-ISRUNNING-145900-469.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 15:00:00.38 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 15:00:00.40 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 15:00:00.40 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 15:00:00.46 - About to create ONGOING-ISRUNNING-150000-467.TXT Status = 1,
24/08/2013 15:00:00.48 - ONGOING-ISRUNNING-150000-467.TXT created. Status = 1,
24/08/2013 15:00:00.60 - ONGOING-ISRUNNING-150000-467.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:00:00.62 - ONGOING-ISRUNNING-150000-467.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:00:00.63 - ONGOING-ISRUNNING-150000-467.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:00:00.63 - ONGOING-ISRUNNING-150000-467.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 15:01:00.38 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 15:01:00.40 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 15:01:00.41 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 15:01:00.46 - About to create ONGOING-ISRUNNING-150100-465.TXT Status = 1,
24/08/2013 15:01:00.48 - ONGOING-ISRUNNING-150100-465.TXT created. Status = 1,
24/08/2013 15:01:00.60 - ONGOING-ISRUNNING-150100-465.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:01:00.62 - ONGOING-ISRUNNING-150100-465.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:01:00.63 - ONGOING-ISRUNNING-150100-465.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:01:00.63 - ONGOING-ISRUNNING-150100-465.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 15:02:00.35 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 15:02:00.36 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 15:02:00.38 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 15:02:00.43 - About to create ONGOING-ISRUNNING-150200-431.TXT Status = 1,
24/08/2013 15:02:00.44 - ONGOING-ISRUNNING-150200-431.TXT created. Status = 1,
24/08/2013 15:02:00.55 - ONGOING-ISRUNNING-150200-431.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:02:00.57 - ONGOING-ISRUNNING-150200-431.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:02:00.58 - ONGOING-ISRUNNING-150200-431.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:02:00.58 - ONGOING-ISRUNNING-150200-431.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 15:03:00.36 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 15:03:00.38 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 15:03:00.39 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 15:03:00.44 - About to create ONGOING-ISRUNNING-150300-445.TXT Status = 1,
24/08/2013 15:03:00.46 - ONGOING-ISRUNNING-150300-445.TXT created. Status = 1,
24/08/2013 15:03:00.58 - ONGOING-ISRUNNING-150300-445.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:03:00.60 - ONGOING-ISRUNNING-150300-445.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:03:00.61 - ONGOING-ISRUNNING-150300-445.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:03:00.61 - ONGOING-ISRUNNING-150300-445.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 15:04:00.36 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 15:04:00.38 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 15:04:00.39 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 15:04:00.44 - About to create ONGOING-ISRUNNING-150400-442.TXT Status = 1,
24/08/2013 15:04:00.45 - ONGOING-ISRUNNING-150400-442.TXT created. Status = 1,
24/08/2013 15:04:00.58 - ONGOING-ISRUNNING-150400-442.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:04:00.59 - ONGOING-ISRUNNING-150400-442.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:04:00.59 - ONGOING-ISRUNNING-150400-442.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:04:00.61 - ONGOING-ISRUNNING-150400-442.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 15:05:00.37 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 15:05:00.39 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 15:05:00.40 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 15:05:00.47 - About to create ONGOING-ISRUNNING-150500-456.TXT Status = 1,
24/08/2013 15:05:00.48 - ONGOING-ISRUNNING-150500-456.TXT created. Status = 1,
24/08/2013 15:05:00.61 - ONGOING-ISRUNNING-150500-456.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:05:00.61 - ONGOING-ISRUNNING-150500-456.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:05:00.62 - ONGOING-ISRUNNING-150500-456.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:05:00.64 - ONGOING-ISRUNNING-150500-456.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,


24/08/2013 15:06:00.37 - In HG612_stats.exe - After ini_parse(). ERROR.LOG status = 0,
24/08/2013 15:06:00.38 - working_directory = C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts - ERROR.LOG status = 0,
24/08/2013 15:06:00.40 - After attempting to open ERROR.LOG, ERROR.LOG status = 1
24/08/2013 15:06:00.45 - About to create ONGOING-ISRUNNING-150600-451.TXT Status = 1,
24/08/2013 15:06:00.46 - ONGOING-ISRUNNING-150600-451.TXT created. Status = 1,
24/08/2013 15:06:00.59 - ONGOING-ISRUNNING-150600-451.TXT - There are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:06:00.60 - ONGOING-ISRUNNING-150600-451.TXT - ** About to exit as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:06:00.60 - ONGOING-ISRUNNING-150600-451.TXT - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1,
24/08/2013 15:06:00.62 - ONGOING-ISRUNNING-150600-451.TXT - *** In exit_2_instances - Closing ERROR.LOG. Status = 1,
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 modem stats - multiple instances.
« Reply #20 on: August 24, 2013, 03:25:13 PM »

BE dont know if this helps, but you can see for the period

when I was using the fix, (13:39 to 13:41)  no data was being appended to HG612_Modem_Stats\Ongoing_Stats\modem_stats.log

13:42 is when I dropped v1.1 back in



I can see from the data you posted starting 13:42:00.38, the 'fix' was still in use, which appears to have completed correctly.
(unless you dropped the original v 1.1 back in after that instance had completed.


It seems the instance starting from 13:40:00.38 is the one that didn't complete as the instance starting 13:41:00.37 exited as 2 instances were detected.


FWIW, I use TextPad 5.4.2 rather than Wordpad or MS Word for viewing any of the associated text files/logs as it warns that another program (actually HG612_stats.exe - but not named) has updated the file.

The answer to "Reload it?" should be 'YES'.

According to the TextPad website,

Using TextPad means that no data is missed in modem_stats.log or any of the other text files & HG612_stats.exe shouldn't lock up.

I am also using W7 (Home Premium version) & this is the detail for my Scheduled Task (from the SEttings Editor - 'Tasks', 'Display Task Info':-


Code: [Select]

Folder: \
HostName:                             PAUL-PC
TaskName:                             \HG612 Stats Program
Next Run Time:                        24/08/2013 15:22:00
Status:                               Ready
Logon Mode:                           Interactive/Background
Last Run Time:                        24/08/2013 15:21:00
Last Result:                          0
Author:                               Paul
Task To Run:                          "C:\HG612_Modem_Stats\Scripts\HG612_Run.exe"
Start In:                             N/A
Comment:                              N/A
Scheduled Task State:                 Enabled
Idle Time:                            Disabled
Power Management:                     Stop On Battery Mode, No Start On Batteries
Run As User:                          Paul-PC\Paul
Delete Task If Not Rescheduled:       Enabled
Stop Task If Runs X Hours and X Mins: 72:00:00
Schedule:                             Scheduling data is not available in this format.
Schedule Type:                        One Time Only, Minute
Start Time:                           14:32:00
Start Date:                           24/08/2013
End Date:                             N/A
Days:                                 N/A
Months:                               N/A
Repeat: Every:                        0 Hour(s), 1 Minute(s)
Repeat: Until: Time:                  None
Repeat: Until: Duration:              Disabled
Repeat: Stop If Still Running:        Disabled



Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33035
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: HG612 modem stats - multiple instances.
« Reply #21 on: August 24, 2013, 03:30:08 PM »

and the ERROR.LOG over the above period is quite telling.  Its very obvious where the fix.exe was in use.

Code: [Select]
24/08/2013 14:54:00.358 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 14:54:00.405 - HG612_current_stats.exe was NOT running
24/08/2013 14:54:00.405 - Temp File ONGOING-ISRUNNING-145400-405.TXT was created
24/08/2013 14:54:00.467 - malloc() O.K.
24/08/2013 14:54:00.467 - Initializing Winsock
24/08/2013 14:54:00.483 - WSAStartup() SUCCESSFUL!!!
24/08/2013 14:54:00.483 - Starting getaddrinfo()
24/08/2013 14:54:00.483 - getaddrinfo() O.K.
24/08/2013 14:54:00.483 - Starting socket()
24/08/2013 14:54:00.483 - socket() O.K.
24/08/2013 14:54:00.483 - Starting connect()
24/08/2013 14:54:00.483 - connect() O.K.
24/08/2013 14:54:01.325 - About to reply(xdslcmd info --stats)
24/08/2013 14:54:01.325 - reply(xdslcmd info --stats) O.K.
24/08/2013 14:54:01.543 - get_data() O.K.
24/08/2013 14:54:01.543 - About to determine the xDSL mode
24/08/2013 14:54:01.543 - Modem in use = HG610 or HG612
24/08/2013 14:54:01.543 - About to parse_stats()
24/08/2013 14:54:01.543 - parse_stats completed
24/08/2013 14:54:01.543 - VDSL2 mode detected so about to reply(xdslcmd info --pbParams)
24/08/2013 14:54:01.543 - reply(xdslcmd info --pbParams) O.K.
24/08/2013 14:54:01.746 - get_data() O.K.
24/08/2013 14:54:01.746 - About to parse_pbParams_data()
24/08/2013 14:54:01.746 - parse_pbParams_data() completed
24/08/2013 14:54:01.746 - About to exit Busybox
24/08/2013 14:54:01.746 - Busybox exited
24/08/2013 14:54:01.965 - About to exit ATP
24/08/2013 14:54:01.965 - ATP exited
24/08/2013 14:54:01.965 - Current data harvested at 1377352440 seconds past the epoch
24/08/2013 14:54:01.965 - About to get_log_data()
24/08/2013 14:54:01.965 - Previous log stats date/time = 1377352380 seconds past the epoch
24/08/2013 14:54:01.965 - time_difference = 1 minutes
24/08/2013 14:54:01.980 - About to calc_ES_delta()
24/08/2013 14:54:01.980 - About to calc_RSCorr_delta()
24/08/2013 14:54:01.980 - ds_RSCorr_THIS_PERIOD = 0
24/08/2013 14:54:01.980 - us_RSCorr_THIS_PERIOD = 0
24/08/2013 14:54:01.980 - About to calc_RSUnCorr_delta()
24/08/2013 14:54:01.980 - About to calc_RS_delta()
24/08/2013 14:54:01.980 - About to calc_OHF_delta()
24/08/2013 14:54:01.980 - About to calc_OHFErr_delta()
24/08/2013 14:54:01.980 - About to calc_HEC_delta()
24/08/2013 14:54:01.980 - About to calc_CRC_delta()
24/08/2013 14:54:01.980 - About to calc_FEC_delta()
24/08/2013 14:54:01.996 - About to calc_Bitswap_delta()
24/08/2013 14:54:01.996 - Appending data to C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Ongoing_Stats\modem_stats.log
24/08/2013 14:54:01.996 - Closing MSLOGFILE.log
24/08/2013 14:54:01.996 - END of 1 minute sampling
24/08/2013 14:54:01.996 - About to close(sockfd)
24/08/2013 14:54:01.996 - About to freeadddrinfo(res)
24/08/2013 14:54:01.996 - About to WSACleanup()
24/08/2013 14:54:01.996 - About to free(txbuf)
24/08/2013 14:54:01.996 - About to free(rxbuf)
24/08/2013 14:54:01.996 - Current  sync speeds are     DS 79999 kbps      US 15295 kbps
24/08/2013 14:54:01.996 - Previous sync speeds are     DS 79999 kbps      US 15295 kbps
24/08/2013 14:54:01.996 - Sync speeds have NOT changed since the previous data harvest
24/08/2013 14:54:01.996 - ONGOING-ISRUNNING-145400-405.TXT DELETED
*********************************************************************************************************************
24/08/2013 14:54:01.996 - Scheduled Current_Stats logging is switched ON via the ini file
24/08/2013 14:54:01.996 - Current_Stats_Datum    = 06
24/08/2013 14:54:01.996 - Current_Stats_Interval = 8
24/08/2013 14:54:01.996 - (Time in Hours - Datum) Modulus Interval       i.e. (14 - 6) % 8 = 0
24/08/2013 14:54:01.996 - (Time in Minutes) = 54
24/08/2013 14:54:01.996 - Modulus & minutes *BOTH* have to be zero, so scheduled snapshot logging is NOT due yet
*********************************************************************************************************************
24/08/2013 14:54:01.996 - Scheduled Daily_Graphing is switched ON via the ini file
24/08/2013 14:54:01.996 - Daily_Graphing_hour    = 23
24/08/2013 14:54:01.996 - Daily_Graphing_minutes = 58
24/08/2013 14:54:01.996 - Current Time is Hours 14, Minutes 54
24/08/2013 14:54:01.996 - scheduled Daily_Graphing is NOT due yet
*********************************************************************************************************************
24/08/2013 14:54:01.996 - End of HG612_stats.exe program, EXIT error code = 0
24/08/2013 14:54:01.996 - End of HG612_stats.exe program, closing ERROR.LOG


24/08/2013 14:57:00.396 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 14:57:00.458 - HG612_current_stats.exe was NOT running
24/08/2013 14:57:00.458 - Temp File ONGOING-ISRUNNING-145700-458.TXT was created
24/08/2013 14:57:00.630 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 14:57:00.646 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 14:58:00.409 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 14:58:00.456 - HG612_current_stats.exe was NOT running
24/08/2013 14:58:00.456 - Temp File ONGOING-ISRUNNING-145800-456.TXT was created
24/08/2013 14:58:00.643 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 14:58:00.659 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 14:59:00.407 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 14:59:00.469 - HG612_current_stats.exe was NOT running
24/08/2013 14:59:00.469 - Temp File ONGOING-ISRUNNING-145900-469.TXT was created
24/08/2013 14:59:00.641 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 14:59:00.641 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:00:00.405 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:00:00.467 - HG612_current_stats.exe was NOT running
24/08/2013 15:00:00.467 - Temp File ONGOING-ISRUNNING-150000-467.TXT was created
24/08/2013 15:00:00.639 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 15:00:00.639 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:01:00.403 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:01:00.465 - HG612_current_stats.exe was NOT running
24/08/2013 15:01:00.465 - Temp File ONGOING-ISRUNNING-150100-465.TXT was created
24/08/2013 15:01:00.637 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 15:01:00.652 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:02:00.369 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:02:00.431 - HG612_current_stats.exe was NOT running
24/08/2013 15:02:00.431 - Temp File ONGOING-ISRUNNING-150200-431.TXT was created
24/08/2013 15:02:00.587 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 15:02:00.603 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:03:00.382 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:03:00.445 - HG612_current_stats.exe was NOT running
24/08/2013 15:03:00.445 - Temp File ONGOING-ISRUNNING-150300-445.TXT was created
24/08/2013 15:03:00.616 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 15:03:00.616 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:04:00.380 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:04:00.442 - HG612_current_stats.exe was NOT running
24/08/2013 15:04:00.442 - Temp File ONGOING-ISRUNNING-150400-442.TXT was created
24/08/2013 15:04:00.598 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 15:04:00.614 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:05:00.393 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:05:00.456 - HG612_current_stats.exe was NOT running
24/08/2013 15:05:00.456 - Temp File ONGOING-ISRUNNING-150500-456.TXT was created
24/08/2013 15:05:00.627 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 15:05:00.643 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:06:00.389 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:06:00.451 - HG612_current_stats.exe was NOT running
24/08/2013 15:06:00.451 - Temp File ONGOING-ISRUNNING-150600-451.TXT was created
24/08/2013 15:06:00.623 - *** Now in exit_2_instances as there are 2 instances of HG612_stats.exe running. Status = 1.
24/08/2013 15:06:00.623 - *** In exit_2_instances - Closing ERROR.LOG. Status = 1.


24/08/2013 15:07:00.371 - [ IN HG612_stats.EXE ] - Start of 1 minute sampling
24/08/2013 15:07:00.418 - HG612_current_stats.exe was NOT running
24/08/2013 15:07:00.418 - Temp File ONGOING-ISRUNNING-150700-418.TXT was created
24/08/2013 15:07:00.480 - malloc() O.K.
24/08/2013 15:07:00.480 - Initializing Winsock
24/08/2013 15:07:00.480 - WSAStartup() SUCCESSFUL!!!
24/08/2013 15:07:00.480 - Starting getaddrinfo()
24/08/2013 15:07:00.480 - getaddrinfo() O.K.
24/08/2013 15:07:00.480 - Starting socket()
24/08/2013 15:07:00.480 - socket() O.K.
24/08/2013 15:07:00.480 - Starting connect()
24/08/2013 15:07:00.480 - connect() O.K.
24/08/2013 15:07:01.338 - About to reply(xdslcmd info --stats)
24/08/2013 15:07:01.338 - reply(xdslcmd info --stats) O.K.
24/08/2013 15:07:01.541 - get_data() O.K.
24/08/2013 15:07:01.541 - About to determine the xDSL mode
24/08/2013 15:07:01.541 - Modem in use = HG610 or HG612
24/08/2013 15:07:01.541 - About to parse_stats()
24/08/2013 15:07:01.541 - parse_stats completed
24/08/2013 15:07:01.541 - VDSL2 mode detected so about to reply(xdslcmd info --pbParams)
24/08/2013 15:07:01.541 - reply(xdslcmd info --pbParams) O.K.
24/08/2013 15:07:01.759 - get_data() O.K.
24/08/2013 15:07:01.759 - About to parse_pbParams_data()
24/08/2013 15:07:01.759 - parse_pbParams_data() completed
24/08/2013 15:07:01.759 - About to exit Busybox
24/08/2013 15:07:01.759 - Busybox exited
24/08/2013 15:07:01.962 - About to exit ATP
24/08/2013 15:07:01.962 - ATP exited
24/08/2013 15:07:01.978 - Current data harvested at 1377353220 seconds past the epoch
24/08/2013 15:07:01.978 - About to get_log_data()
24/08/2013 15:07:01.978 - Previous log stats date/time = 1377352440 seconds past the epoch
24/08/2013 15:07:01.978 - time_difference = 13 minutes
24/08/2013 15:07:01.978 - WARNING!!! time_difference is more than 1 minute - Ignoring previous logged time
24/08/2013 15:07:01.993 - About to calc_ES_delta()
24/08/2013 15:07:01.993 - About to calc_RSCorr_delta()
24/08/2013 15:07:01.993 - ds_RSCorr_THIS_PERIOD = 0
24/08/2013 15:07:01.993 - us_RSCorr_THIS_PERIOD = 0
24/08/2013 15:07:01.993 - About to calc_RSUnCorr_delta()
24/08/2013 15:07:01.993 - About to calc_RS_delta()
24/08/2013 15:07:01.993 - About to calc_OHF_delta()
24/08/2013 15:07:01.993 - About to calc_OHFErr_delta()
24/08/2013 15:07:01.993 - About to calc_HEC_delta()
24/08/2013 15:07:01.993 - About to calc_CRC_delta()
24/08/2013 15:07:01.993 - About to calc_FEC_delta()
24/08/2013 15:07:02.009 - About to calc_Bitswap_delta()
24/08/2013 15:07:02.009 - Appending data to C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Ongoing_Stats\modem_stats.log
24/08/2013 15:07:02.009 - Closing MSLOGFILE.log
24/08/2013 15:07:02.009 - END of 1 minute sampling
24/08/2013 15:07:02.009 - About to close(sockfd)
24/08/2013 15:07:02.009 - About to freeadddrinfo(res)
24/08/2013 15:07:02.009 - About to WSACleanup()
24/08/2013 15:07:02.009 - About to free(txbuf)
24/08/2013 15:07:02.009 - About to free(rxbuf)
24/08/2013 15:07:02.009 - Current  sync speeds are     DS 79999 kbps      US 15295 kbps
24/08/2013 15:07:02.009 - Previous sync speeds are     DS 79999 kbps      US 15295 kbps
24/08/2013 15:07:02.009 - Sync speeds have NOT changed since the previous data harvest
24/08/2013 15:07:02.009 - ONGOING-ISRUNNING-150700-418.TXT DELETED
*********************************************************************************************************************
24/08/2013 15:07:02.009 - Scheduled Current_Stats logging is switched ON via the ini file
24/08/2013 15:07:02.009 - Current_Stats_Datum    = 06
24/08/2013 15:07:02.009 - Current_Stats_Interval = 8
24/08/2013 15:07:02.009 - (Time in Hours - Datum) Modulus Interval       i.e. (15 - 6) % 8 = 1
24/08/2013 15:07:02.009 - (Time in Minutes) = 07
24/08/2013 15:07:02.009 - Modulus & minutes *BOTH* have to be zero, so scheduled snapshot logging is NOT due yet
*********************************************************************************************************************
24/08/2013 15:07:02.009 - Scheduled Daily_Graphing is switched ON via the ini file
24/08/2013 15:07:02.009 - Daily_Graphing_hour    = 23
24/08/2013 15:07:02.009 - Daily_Graphing_minutes = 58
24/08/2013 15:07:02.009 - Current Time is Hours 15, Minutes 07
24/08/2013 15:07:02.009 - scheduled Daily_Graphing is NOT due yet
*********************************************************************************************************************
24/08/2013 15:07:02.009 - End of HG612_stats.exe program, EXIT error code = 0
24/08/2013 15:07:02.009 - End of HG612_stats.exe program, closing ERROR.LOG


Our posts have just crossed. 


>>>
FWIW, I use TextPad 5.4.2 rather than Wordpad or MS Word

I use Notepad++ which is designed for programmers.  Wouldnt dream of using Word because of the additional chars etc.   
It also warns yes for reload

This is the contents of the Task

Code: [Select]
Folder: \
HostName:                             I7
TaskName:                             \HG612 Stats Program
Next Run Time:                        24/08/2013 15:29:00
Status:                               Ready
Logon Mode:                           Interactive only
Last Run Time:                        24/08/2013 15:28:00
Last Result:                          0
Author:                               kitz
Task To Run:                          "C:\Users\kitz\Desktop\Connection\HG612_Modem_Stats\Scripts\HG612_Run.exe"
Start In:                             N/A
Comment:                              N/A
Scheduled Task State:                 Enabled
Idle Time:                            Disabled
Power Management:                     Stop On Battery Mode, No Start On Batteries
Run As User:                          I7\kitz
Delete Task If Not Rescheduled:       Enabled
Stop Task If Runs X Hours and X Mins: 72:00:00
Schedule:                             Scheduling data is not available in this format.
Schedule Type:                        One Time Only, Minute
Start Time:                           14:41:00
Start Date:                           24/08/2013
End Date:                             N/A
Days:                                 N/A
Months:                               N/A
Repeat: Every:                        0 Hour(s), 1 Minute(s)
Repeat: Until: Time:                  None
Repeat: Until: Duration:              Disabled
Repeat: Stop If Still Running:        Disabled







Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 modem stats - multiple instances.
« Reply #22 on: August 25, 2013, 09:06:06 AM »

I THINK that I may have found the cause of these issue.

For testing purposes, I had 2 separate HG612_stats.exe tasks running overnight via Task Scheduler, (staggered by 30 seconds via Task Scheduler, NOT by adding a delay option via HG612 Settings editor).

There were no issues until my AVG virus kicked in.

As expected, despite AVG being set to run at lowest resource priority, the whole PC slowed down causing another HG612_stats.exe task to start before the first one had completed.

Both instances were exited as planned & the data was not harvested for that minute.
This didn't leave any 'stuck' instances of HG612_stats.exe in Task Manager & as it only happens a couple of times during the virus scan, it isn't of great importance that a data sample is missed here & there.

When only 1 Scheduled task is running (i.e. normal operation for most users), the slowing down issue is even less of a problem.




This morning, to test things out a bit further, I forced both tasks to run at the same time i.e. bang on the minute.

By the time each instance of HG612_stats.exe had checked to see if another instance was already running, there were indeed 2 instances so both instances exited as planned, with no data harvested.
There were no 'stuck' instances of HG612_stats.exe in Task Manager.


This continued until I added a 30 second stagger again & normal service was resumed, with both instances harvesting & storing the data again.


Just for fun, I then added a 3rd Scheduled task to run HG612_stats.exe, staggered by 45 seconds past the minute.

As HG612_stats.exe normally completes in 2 or 3 seconds (when the PC isn't busy), these all worked perfectly with no 'stuck' instances.



Returning to just 2 tasks, I then fired up Eric's DSLStats & started sampling at 10 seconds past the minute.

Neither of my 2 HG612_stats.exe tasks were affected as they didn't attempt to run during DSLStat's sampling period.

DSLStats also worked perfectly.


I then stopped DSLStats from sampling, leaving the program running.
Again, there were no issues.

As a final test, I started DSLStats's sampling again, but this time ensuring sampling would start 5 seconds before one of my tasks was due to start.

When it was time for my task to run, DSLStats was still displaying the Sampling message & I can see that my task reached this point & then locked up:-

25/08/2013  8:04:31.50 - ONGOING-ISRUNNING-080430-509.TXT - **** reply(config.Shell) O.K. Status = 1.

i.e. it couldn't continue to login to the modem & ended up 'stuck' in Task Manager.

That is at exactly the same point it locked up during your testing yesterday afternoon:-

24/08/2013 14:56:01.38 - ONGOING-ISRUNNING-145600-445.TXT - **** reply(config.Shell) O.K. Status = 1.


As this left an instance of HG612_stats.exe in Task Manager, any further attempts for my tasks to run were exited.

Leaving DSLStats running & sampling switched ON, I ended the stuck process just after DSLStats had completed sampling & my first task ran correctly, harvesting & storing the data accordingly.

However, the 2nd of my tasks started during DSLStat's sampling period & the lock up occurred again.

As Eric & I have not yet discovered a method of checking if a Telnet session is already open without actually logging in to the modem, we'll have to find a workaround for when both programs are running together.
I have an idea in mind that I'll run past Eric during today.

However, if you weren't actually running DSLStats at the time HG612_stats reached this point yesterday, I'll have to discard my theory & start again:-
24/08/2013 14:56:01.38 - ONGOING-ISRUNNING-145600-445.TXT - **** reply(config.Shell) O.K. Status = 1.






Finally, as mentioned previously, there is an issue with some versions of Windows (apparently not an issue with XP), where Scheduled tasks can sometimes start more than once in the same minute.

From monitoring this, it seems that the second (spurious) instance can start as quickly as 0.15 seconds after the 'correct' instance.

HG612_stats.exe handles this by exiting one of the instances & thus allowing the other to continue (apart from when both instances start more or less together, in which case both instances exit).

This duplication of tasks is only seen occasionally, often a few hours apart but at the same minute past the hour, so again, it's not much of an issue.

There is a supposed fix for this Windows Task Scheduler issue here, but I haven't tried it yet:-
http://support.microsoft.com/kb/2461249/en-us?sd=rss&spid=14019

 

Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33035
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: HG612 modem stats - multiple instances.
« Reply #23 on: August 26, 2013, 12:03:20 PM »

Thank you BE for the further info.

>>  if you weren't actually running DSLStats at the time HG612_stats reached this point yesterday (24th)

You are correct, I was.

-------


Knowing I wouldnt have much chance to spend at the PC yesterday I'd found the old v1 zip file in my Recycle bin, so put v1 back on which ran all day yesterday.  Unfortunately though that got snarled at points too, but it would resume logging later.

~ This morning Ive done a complete re-install of v2. This logged ok but had some of the multiple instances.
~ Paused DSLstats. Dropped in the fix.  This seems to be working & logging fine
~ Resumed DSLstats and HG612stats refused any further logging of modem stats
~ Paused DSLstats, HG612stats doesnt recommence logging. 
~ Completely shut down DSLstats, HG612stats still doesnt recommence logging
It seems that whilst the fix is in place, then one bad instance will switch logging off and wont start logging again until the stuck HG612stats.exe is manually removed from Task Manager?


----

Ive also done a quick test in cmd and it would appear that the HG612 telnet allows 3 instances of the Hauwei CLI to be run at the same time, but only one instance into the Broadcom shell at any one time.  I cant see anything obvious in the CLI where the number of simultaneous access for a user can be changed.  :(

I also thought about the possibility of creating another user, but it would appear there are 3 pre-configured users
admin|support|user.    The 'user' account is crippled and doesnt allow telnet access & I dont have right password for support so there goes that idea I guess. :(



-----

I can confirm that I am also seeing the issue with Scheduled tasks starting more than one instance.   Ive had a look through the modem_stats.log and it does seem to happen rather often and can sometimes happen several times in one hour.  I cant find any distinct pattern to it.  It definitely doesn't appear to be at the same minute past the hour.

----

One thing that does puzzle me is that for several weeks the 2 ran happily side-by-side without conflict & it was only last week that I started noticing the multiple instances and all the ONGOING-ISRUNNING files in the scripts folder.   ???



>>> I have an idea in mind that I'll run past Eric during today.

Since HG612stats is run via Windows scheduler it will always commence dead-on the minute.

Could perhaps force some compatibility mode so that DSLstats always commences at 'x' seconds after the minute.  I havent checked to see if DSLstats will always run at 'x' seconds.. or if it runs 'x' seconds after the last sample has fully finished. If its the later... then eventually the 2 will coincide.



----
Edited to add.   

Ive set DSLstats to only run every 60 seconds.  I then paused it and made sure it commenced at 10 seconds past the minute.   Its now been running for about 25 mins without conflict. However I notice sampling starts at  a couple of seconds after the minute and finishes at 10 seconds.   

I'll move the time on a bit to 30 seconds past, then leave them both running whilst I go out...  and see what has happened when I get back  ;D
« Last Edit: August 26, 2013, 12:16:01 PM by kitz »
Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 modem stats - multiple instances.
« Reply #24 on: August 26, 2013, 12:39:15 PM »

Thank you BE for the further info.

>>  if you weren't actually running DSLStats at the time HG612_stats reached this point yesterday (24th)

You are correct, I was.

-------


Knowing I wouldnt have much chance to spend at the PC yesterday I'd found the old v1 zip file in my Recycle bin, so put v1 back on which ran all day yesterday.  Unfortunately though that got snarled at points too, but it would resume logging later.

~ This morning Ive done a complete re-install of v2. This logged ok but had some of the multiple instances.
~ Paused DSLstats. Dropped in the fix.  This seems to be working & logging fine
~ Resumed DSLstats and HG612stats refused any further logging of modem stats
~ Paused DSLstats, HG612stats doesnt recommence logging. 
~ Completely shut down DSLstats, HG612stats still doesnt recommence logging
It seems that whilst the fix is in place, then one bad instance will switch logging off and wont start logging again until the stuck HG612stats.exe is manually removed from Task Manager?


----



I THINK i've found a partial fix for that (yet another test version is attached if you are keen enough to try it).

As your task seems to be running in Interactive only mode, it may beep every minute with this test version.
Switching the task to Interactive/Background mode gets rid of the beep (Task Scheduler -  General tab / Run whether user is logged on or not).


Quote
Ive also done a quick test in cmd and it would appear that the HG612 telnet allows 3 instances of the Hauwei CLI to be run at the same time, but only one instance into the Broadcom shell at any one time.  I cant see anything obvious in the CLI where the number of simultaneous access for a user can be changed.  :(

I believe the attached test version deals with that.
I have temporarily removed HG622 compatibility while it is under test.


Quote
I also thought about the possibility of creating another user, but it would appear there are 3 pre-configured users
admin|support|user.    The 'user' account is crippled and doesnt allow telnet access & I dont have right password for support so there goes that idea I guess. :(

There's no need to consider doing that (if this test version works O.K. at your end).
I've been running it in tandem with DSLStats for a few hours now without any issues, even when I force the programs to clash.


Quote
I can confirm that I am also seeing the issue with Scheduled tasks starting more than one instance.   Ive had a look through the modem_stats.log and it does seem to be a regular even and can sometimes happen several times in one hour..  I cant find any distinct pattern to it.  It definitely doesnt appear to be at the same minute past the hour.

One thing that does puzzle me is that for several weeks the 2 ran happily side-by-side without conflict & it was only last week that I started noticing the multiple instances and all the ONGOING-ISRUNNING files in the scripts folder.   ???


I never used to see that at all.
I wonder if at the latest auto update, Microsoft have reintroduced a bug that a previous update had resolved?



>>> I have an idea in mind that I'll run past Eric during today.

Quote

Since HG612stats is run via Windows scheduler it will always commence dead-on the minute.



Theoretically, yes. In practice, things can be delayed on occasions (when the PC is incredibly busy doing something else - e.g. virus scanning).


Quote
Could perhaps force some compatability mode so that DSLstats always commences at 'x' seconds after the minute.  I havent checked to see if DSLstats will always run at 'x' seconds.. or if it runs 'x' seconds after the last sample has fully finished. If its the later... then eventually the 2 will co-incide.


I don't think that's necessary now.

In any case, on my PC, while I've been testing things out, I have noticed that DSLStats's timing gains approximately 1 second every minute.

e.g. I have 2 tasks running, staggered by 30 seconds.
For testing purposes I started DSLStats sampling at around 30 seconds past the minute to force it to clash with one of my tasks.
Within 30 minutes or so, it had gradually started sampling earlier & earlier until it eventually clashed with my task that runs exactly on the minute.

I haven't been watching DSLStats closely, but it is now sampling at around 45 seconds past the minute.
 
When I mention this is a partial fix, it means that my every minute start & close programs can run alongside DSLStats, but if Eric included a slight pause, whenever my programs are detected, it could improve matters even further.

My ongoing stats harvest takes around 2 to 3 seconds (depending on PC processor speed) & the scheduled current/snapshot stats take around 7 seconds - a bit longer if auto-graphing.
A 10 second delay (maximum) should be sufficient in DSLStats if either of my programs are running, rather than risk losing a DSLStats sample altogether.



If you do try this latest test version, you'll see what happens when the programs clash by looking at the "ERROR.LOG_file_ERROR.TXT" files in the Scripts folder & the Ongoing_Stats folder.
One is specific to DSLStats handling & the other is a general record of what happens whenever 2 tasks try to start at the same time.

If this test version proves reliable, I'll get rid of the temporarily created ISRUNNING files & the additional debugging logs.

The best of both worlds would be to have my programs & DSLStats working in perfect harmony & believe we are now very, very close to achieving that.

HTH  :)
« Last Edit: August 26, 2013, 12:42:23 PM by Bald_Eagle1 »
Logged

roseway

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 40922
  • Penguins CAN fly
    • DSLstats
Re: HG612 modem stats - multiple instances.
« Reply #25 on: August 26, 2013, 01:28:11 PM »

Quote
Ive also done a quick test in cmd and it would appear that the HG612 telnet allows 3 instances of the Hauwei CLI to be run at the same time, but only one instance into the Broadcom shell at any one time.  I cant see anything obvious in the CLI where the number of simultaneous access for a user can be changed.

Yesterday I did a little experiment with the HG622 that I'm currently using, and I found that it happily supports at least three simultaneous admin logins to the Broadcom CLI. This is to be expected, because it's Linux, and Linux normally has no problems with multiple logins. I'm a bit surprised to hear that the HG612 is different, but maybe it's limited by its internal memory or something of that nature.
Logged
  Eric

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 modem stats - multiple instances.
« Reply #26 on: August 26, 2013, 02:02:51 PM »

This seems to be the issue:-


If my program attempts to run at around 5 seconds into DSLStat's sampling stage, 'admin' for Username & 'admin' for Password are still O.K., but 'sh' for access to Busybox doesn't work, instead we are simply returned to the ATP> prompt.

My workaround is to keep trying to reply with 'sh' until it either works or a maximum of 50 attempts are tried & failed.

I have only seen a maximum of 31 attempts so far before 'sh' is accepted - presumably when DSLStats logs out of the modem again:-

26/08/2013 10:58:30.18 - In HG612_stats.exe - At the start of the main() function,
26/08/2013 10:58:30.32 - There are 1 instances of HG612_stats.exe running. Status = 0,
26/08/2013 10:58:31.97 - 01 trying reply(sh) again.
26/08/2013 10:58:32.19 - 02 trying reply(sh) again.
26/08/2013 10:58:32.41 - 03 trying reply(sh) again.
26/08/2013 10:58:32.64 - 04 trying reply(sh) again.
26/08/2013 10:58:32.88 - 05 trying reply(sh) again.
26/08/2013 10:58:33.13 - 06 trying reply(sh) again.
26/08/2013 10:58:33.38 - 07 trying reply(sh) again.
26/08/2013 10:58:33.63 - 08 trying reply(sh) again.
26/08/2013 10:58:33.86 - 09 trying reply(sh) again.
26/08/2013 10:58:34.11 - 10 trying reply(sh) again.
26/08/2013 10:58:34.36 - 11 trying reply(sh) again.
26/08/2013 10:58:34.62 - 12 trying reply(sh) again.
26/08/2013 10:58:34.87 - 13 trying reply(sh) again.
26/08/2013 10:58:35.12 - 14 trying reply(sh) again.
26/08/2013 10:58:35.37 - 15 trying reply(sh) again.
26/08/2013 10:58:35.62 - 16 trying reply(sh) again.
26/08/2013 10:58:35.86 - 17 trying reply(sh) again.
26/08/2013 10:58:36.11 - 18 trying reply(sh) again.
26/08/2013 10:58:36.36 - 19 trying reply(sh) again.
26/08/2013 10:58:36.59 - 20 trying reply(sh) again.
26/08/2013 10:58:36.84 - 21 trying reply(sh) again.
26/08/2013 10:58:37.07 - 22 trying reply(sh) again.
26/08/2013 10:58:37.32 - 23 trying reply(sh) again.
26/08/2013 10:58:37.56 - 24 trying reply(sh) again.
26/08/2013 10:58:37.82 - 25 trying reply(sh) again.
26/08/2013 10:58:38.06 - 26 trying reply(sh) again.
26/08/2013 10:58:38.32 - 27 trying reply(sh) again.
26/08/2013 10:58:38.57 - 28 trying reply(sh) again.
26/08/2013 10:58:38.82 - 29 trying reply(sh) again.
26/08/2013 10:58:39.09 - 30 trying reply(sh) again.
26/08/2013 10:58:39.35 - 31 trying reply(sh) again.
26/08/2013 10:58:40.46 - Normal End of In HG612_stats.exe



Fewer & fewer attempts are needed as time passes, until DSLStats eventually starts sampling at a time when Windows Task Scheduler isn't trying to start my task.


26/08/2013 11:03:30.18 - In HG612_stats.exe - At the start of the main() function,
26/08/2013 11:03:30.29 - There are 1 instances of HG612_stats.exe running. Status = 0,
26/08/2013 11:03:31.87 - 01 trying reply(sh) again.
26/08/2013 11:03:32.12 - 02 trying reply(sh) again.
26/08/2013 11:03:32.37 - 03 trying reply(sh) again.
26/08/2013 11:03:32.62 - 04 trying reply(sh) again.
26/08/2013 11:03:32.88 - 05 trying reply(sh) again.
26/08/2013 11:03:33.99 - Normal End of In HG612_stats.exe


26/08/2013 11:04:30.16 - In HG612_stats.exe - At the start of the main() function,
26/08/2013 11:04:30.27 - There are 1 instances of HG612_stats.exe running. Status = 0,
26/08/2013 11:04:31.82 - 01 trying reply(sh) again.
26/08/2013 11:04:32.69 - Normal End of In HG612_stats.exe


26/08/2013 11:05:30.15 - In HG612_stats.exe - At the start of the main() function,
26/08/2013 11:05:30.32 - There are 1 instances of HG612_stats.exe running. Status = 0,
26/08/2013 11:05:33.19 - Normal End of In HG612_stats.exe


Logged

kitz

  • Administrator
  • Senior Kitizen
  • *
  • Posts: 33035
  • Trinity: Most guys do.
    • http://www.kitz.co.uk
Re: HG612 modem stats - multiple instances.
« Reply #27 on: August 26, 2013, 02:22:15 PM »

Ive just got back in and DSLstats now commences its sample at 2 seconds past the minute, so yes like you Im seeing it gain in time, but I wasnt here to see how much...

......woah and as I type its just co-incided and clashed!!!!!
Current_stats.exe also just got stuck too @ its 14:00  run.

26/08/2013 13:59
26/08/2013 14:00
26/08/2013 14:04 <---- manually removed process from Task Manager.

Both programs normally harvest results very quickly.  HG612stats only takes 2 seconds.  DSLstats about 8 seconds.



>>> I wonder if at the latest auto update, Microsoft have reintroduced a bug that a previous update had resolved?

Possible, because I'm pretty sure I had no problem until last week.

Quote
As your task seems to be running in Interactive only mode, it may beep every minute with this test version.
Switching the task to Interactive/Background mode gets rid of the beep (Task Scheduler -  General tab / Run whether user is logged on or not).

Thank you -  running it now..  its bleeping every min.
Cant switch it to run whether user is logged in or not as I get an error
"User account restriction error.  The possible reasons are that blank passwords are not allowed."

I could possibly get around this by setting up another user specifically for running Task Scheduler - which is what I used to do when running MRTG to ignore blank password issue... but for now I'll leave it bleeping. 


Quote
but 'sh' for access to Busybox doesn't work, instead we are simply returned to the ATP> prompt.

Yes thats what I noticed this morning, when I said it would only accept one instance into the shell.


Logged
Please do not PM me with queries for broadband help as I may not be able to respond.
-----
How to get your router line stats :: ADSL Exchange Checker

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 modem stats - multiple instances.
« Reply #28 on: August 26, 2013, 02:37:29 PM »


......woah and as I type its just co-incided and clashed!!!!!
Current_stats.exe also just got stuck too @ its 14:00  run.

26/08/2013 13:59
26/08/2013 14:00
26/08/2013 14:04 <---- manually removed process from Task Manager.


Ah, I forgot about adding this workaround to HG612_current_stats.exe. I'll do that now.



Quote
Both programs normally harvest results very quickly.  HG612stats only takes 2 seconds.  DSLstats about 8 seconds.


DSLStats takes around 12-15 seconds on my PC. Your processor is faster than mine though.



Quote
>>> I wonder if at the latest auto update, Microsoft have reintroduced a bug that a previous update had resolved?

Possible, because I'm pretty sure I had no problem until last week.


I don't really have any explanation for that as I have also only recently started seeing the duplicated task issue.

Quote
Quote
As your task seems to be running in Interactive only mode, it may beep every minute with this test version.
Switching the task to Interactive/Background mode gets rid of the beep (Task Scheduler -  General tab / Run whether user is logged on or not).

Thank you -  running it now..  its bleeping every min.
Cant switch it to run whether user is logged in or not as I get an error
"User account restriction error.  The possible reasons are that blank passwords are not allowed."

I could possibly get around this by setting up another user specifically for running Task Scheduler - which is what I used to do when running MRTG to ignore blank password issue... but for now I'll leave it bleeping. 


If this test vesion seems to resolve the issue(s), I'll get rid of the bleeping in the next update.

Quote
Quote
but 'sh' for access to Busybox doesn't work, instead we are simply returned to the ATP> prompt.

Yes thats what I noticed this morning, when I said it would only accept one instance into the shell.

Hopefully, that aspect has now been dealt with.

Fingers crossed.......................... :fingers:
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 modem stats - multiple instances.
« Reply #29 on: August 26, 2013, 03:00:49 PM »

A new version of HG612_current_stats.exe is attached, also disabling HG622 compatibility for now, along with including the DSLStats partial workaround.

It doesn't include any of the extra event/error logging, but it does work O.K.



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

anything