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 5

Author Topic: HG612 Modem Stats r2.0 released  (Read 29505 times)

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: HG612 Modem Stats r2.0 released
« Reply #30 on: March 11, 2014, 06:38:54 PM »

Yeah its odd, ran fine for months since you fixed this issue ages ago. 

Then I installed 2.0 in its own folder, set the folder in the gui.  Set the same options in the gui as 1.1.

Stopped the service, restarted the service from 2.0 gui.  Problems started.

Stopped the service in 2.0 and restarted it in 1.1, problems came back.

so is odd.

cant find plink log, which folder should it be in?  I guess I may need to enable the debug option as I have that disabled?
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats r2.0 released
« Reply #31 on: March 11, 2014, 07:42:18 PM »

The Plink logs are stored in date/time stamped subfolders of Current_Stats.

A copy of your HG612_stats.ini file from the Scripts folder may also be useful.

Just to ask again, were/are you using the original programs from the 2.0 release download or any of the amended 'test' programs that I have posted in this forum?
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: HG612 Modem Stats r2.0 released
« Reply #32 on: March 11, 2014, 10:12:10 PM »

I used the ones distributed with it, as I said it has its own folder.

sods law now since I enabled "enable extensive logging" its been ok.
« Last Edit: March 11, 2014, 10:17:35 PM by Chrysalis »
Logged

burakkucat

  • Respected
  • Senior Kitizen
  • *
  • Posts: 38300
  • Over the Rainbow Bridge
    • The ELRepo Project
Re: HG612 Modem Stats r2.0 released
« Reply #33 on: March 11, 2014, 10:29:53 PM »

Quote
sods law now since I enabled "enable extensive logging" its been ok.

That is an often common occurrence when attempting to debug software. The very act of "turning on" extensive logging, for example, will add to the execution time of the various code fragments. And often it is that increase in execution time, slowing down the overall process, which will allow the software in question to behave "without blemish".

Now I'm not suggesting that is what you are observing in this case but I wonder if the hardware, which you are using to "harvest" the data, incorporates a very fast, multi-core processor?
Logged
:cat:  100% Linux and, previously, Unix. Co-founder of the ELRepo Project.

Please consider making a donation to support the running of this site.

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: HG612 Modem Stats r2.0 released
« Reply #34 on: March 12, 2014, 12:31:52 AM »

it has happened again now. :(

cpu is quad core i5-750 so is fastish but is certianly faster cpus out there.
Logged

Darren

  • Member
  • **
  • Posts: 56
Re: HG612 Modem Stats r2.0 released
« Reply #35 on: March 12, 2014, 06:59:08 AM »

I just came to report the same thing, only just started logging again so wasn't aware this is a regretion. Seems to happen at the same time each hour. Using the download here on an overclocked hex. Last windows updates were 14th Feb.

Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats r2.0 released
« Reply #36 on: March 12, 2014, 07:16:06 AM »

O.K.

You could try the attached version of HG612_stats.exe.

It now has a check in it to see if a certain part of the program is stuck in an unending loop.

If that's the case, a new TXT file will be created in the Scripts folder using a name starting with "GET_DATA_ERROR-".
That should serve as a warning that the particular part of the program is stuck in a loop.

Also, with Extensive logging switched ON, some error data should be written to ERROR.LOG & ERROR.LOG_file_ERROR.TXT, both stored in the Ongoing_Stats folder.

The program should then exit (all being well) which should allow the next data harvest to run as intended.

If that wasn't the cause, I'll try something else to hopefully eliminate it.


Everything looked O.K. in the Plink & ini files, so I have no real ideas (yet) as to why this has just started to happen.
It might have to be tracked down a bit at a time until the cuplrit is found.


It might help if you could provide some of the recent data from the ERROR.LOG, ERROR.LOG_file_ERROR.TXT & Login_events.TXT files that you already have, just in case there is already a clue there.



EDIT:

As I don't know the actual cause (not seeing an issue at my end), my 'forced' error for testing purposes may be the wrong issue, but at least we should be able to eliminate it as a potential cause.


« Last Edit: March 12, 2014, 07:29:29 AM by Bald_Eagle1 »
Logged

Ronski

  • Moderator
  • Kitizen
  • *
  • Posts: 4300
Re: HG612 Modem Stats r2.0 released
« Reply #37 on: March 12, 2014, 09:28:07 AM »

I wonder if this is actually being caused by Task scheduler, especially looking at Darrens isrunning time stamps. There is a known bug with task scheduler, basically task scheduler creates a list of scheduled tasks each hour, so it's possible for a task to be at the end of that list, and be scheduled incorrectly at the start of the next list, hence Darren's isrunning files being every hour, at least that's my thinking.

This has been mentioned before, but as there was only one isrunning I'd sort of dismissed it, but the first logging task will run OK, but if another logging task fires whilst it's running that will see the other one running and leave an isrunning file.

See here for an MS Hotfix - usual caveat - users try at their own risk.

I am also one of the users that had recently had problems, I had 18,000 isrunning files on my server, the problem occurred several weeks ago and I simply hadn't noticed my logging had stopped until Saturday :-[ The fix BE has just rolled out should remedy the problem I had. It also seems my scheduled task was also running at the lower priority, using the higher priority task I've had no isrunning files in the last 24 hours.
« Last Edit: March 12, 2014, 09:34:27 AM by Ronski »
Logged
Formerly restrained by ECI and ali,  now surfing along at 390/36  ;D

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: HG612 Modem Stats r2.0 released
« Reply #38 on: March 12, 2014, 12:42:14 PM »

ronski quite possibly yes, I have what 'might' be an interesting update, didnt post at the time as was very tired but made a note of it.

When it happened before I went bed there was also a 2nd process sucking cpu, svchost.exe, I checked the pid and it is assigned to the aelookupsvc http://windows.fyicenter.com/1026_Administration_Services_What_Is_AeLookupSvc.html

Although this is the first time I noticed this I dont know if all previous lockups had the service playing up.

My OS is windows 7 64bit SP1.  Windows update last ran in january.
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats r2.0 released
« Reply #39 on: March 17, 2014, 07:21:08 AM »

I have made some adjustments to my programs as pre-release v 2.1 Beta test programs.

Hopefully they will now deal with the issues some of you have seen recently.

I'd be grateful if some of you could test them & provide feedback here.


The changes from v 2.0 are:-

=============================
  Change log from release 2.0
 =============================

* 16/03/2014 - Added US OHFErr (FEC) errors graph to FULL__MONTY montage of
               Ongoing Stats.


* 12/03/2014 - Added more error checking in get_data() function, forcing a
               controlled exit if 'stuck' in a loop attempting to
               obtain data.


* 10/03/2014 - Cosmetic graph appearance changes


* 03/03/2014 - Added HG612's firmware version to pbParams stats window.


* 19/02/2014 - Improved efficiency of snapshot graphing program (GRAPH6.exe)
               
               HG612_current_stats.exe now passes a parameter to GRAPH6.exe to
               confirm how the Plink log was generated i.e. via a scheduled or
               resync event, manually generated via HG612_current_stats.exe or
               by dragging & dropping a Plink log onto the GRAPH6.exe program
               icon.
               
               Removed automatic detection of Huawei HG622 modem again as it
          occasionally caused HG612 modems to cease logging.
               
               Added the option to choose the modem in use via the GUI or by
               manually editing the ini file, defaulting to HG612 unless
               intentionally changed by users.


* 15/02/2014 - Added support for VDSL2 Profile 8a (as used in the Isle of Man)


* 10/02/2014 - Reinstated automatic detection of Huawei HG622 modem




EDIT:

The Beta programs have been removed due to issue when using folders with spaces in their names.

Amended versions below (see Reply #50).


« Last Edit: March 17, 2014, 10:21:09 PM by Bald_Eagle1 »
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: HG612 Modem Stats r2.0 released
« Reply #40 on: March 17, 2014, 01:06:50 PM »

thanks, have popped the files in place and started the schedule.

ok more problems sadly.

it seems its failing to work at all, basically I keep getting ISRUNNING files but with no .txt extension, however there isnt a stuck process so dont know why they appearing.

Also the only log file updating is xlogfile.txt, all the other logs, error logs etc. are not been written to.  If I watch taskmanager live then the stats program very briefly appears but very quickly, much quicker than when it used to work.

The ISRUNNING files also are all empty 0bytes size.
« Last Edit: March 17, 2014, 01:17:59 PM by Chrysalis »
Logged

Bald_Eagle1

  • Helpful
  • Kitizen
  • *
  • Posts: 2721
Re: HG612 Modem Stats r2.0 released
« Reply #41 on: March 17, 2014, 01:17:19 PM »

Just a quick note to all.............................

During this pre-release testing phase, although sizes of the various logs & TXT files will increase quite rapidly, Extensive error/event logging should be enabled via the GUI/ini file in order to gain all the relevant debugging details.

The final release version will either get rid some of the files or vastly reduce their sizes.


Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: HG612 Modem Stats r2.0 released
« Reply #42 on: March 17, 2014, 01:18:33 PM »

I do have the extensive logging enabled to confirm.
Logged

Chrysalis

  • Content Team
  • Addicted Kitizen
  • *
  • Posts: 7382
  • VM Gig1 - AAISP L2TP
Re: HG612 Modem Stats r2.0 released
« Reply #43 on: March 17, 2014, 01:26:13 PM »

if I run hg612_stats.exe manually it crashes, is that expected?

fault module msvcrt.dll
Logged

Darren

  • Member
  • **
  • Posts: 56
Re: HG612 Modem Stats r2.0 released
« Reply #44 on: March 17, 2014, 01:57:16 PM »

So I tried the updated file you posted Bald_Eagle1 but it didn't solve the issue.

The Application Experience service is disabled on my system so it can be rulled out unless it's one of several triggers for this issue.

Next up is to try the hotfix posted by Ronski, which requires update 2305420 to be installed first.

I have not tried the beta yet, looks like I shuold hold off, no time to play with it atm anyway.
Logged
Pages: 1 2 [3] 4 5