Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[pooclah]

I  have an issue where almost hourly HG612 Modem Stats gives the following error

“Exiting as there are 2 instances of [HG612_stats.exe] running. Status = 1”

I have checked that there is nothing else running hourly that could conflict and couldn’t find anything.

Also looking through the logs I notice that  ONGOING_ERROR.LOG and ONGOING_ERROR.LOG_file_ERROR.TXT are rather large, particularly the later at 1.82 GB.  Can I delete these files and they’ll be recreated or should I just delete the contents and leave the files intact?

Kevin

[burakkucat]

I would advise that you do not delete nor zero the contents of those two files until such time as Bald_Eagle1 has had a chance to investigate.

I'm not sure of his current whereabouts but I suspect he will soon "drop in" to perform a check for any outstanding problems . . .

[Bald_Eagle1]

Also looking through the logs I notice that  ONGOING_ERROR.LOG and ONGOING_ERROR.LOG_file_ERROR.TXT are rather large, particularly the later at 1.82 GB.  Can I delete these files and they’ll be recreated or should I just delete the contents and leave the files intact?

Yes. Just delete the files as new ones will be created at the next scheduled task time.

If your connection isn't really exhibiting any problems & if they are still enabled, you could turn off both the extra debugging info options via the GUI to avoid ending up with huge files.

 

[pooclah]

OK thanks I’ll do that and delete the files.  Disk space isn’t an issue it’s just that the size makes them difficult to open and read.

Any ideas on the 2 instances problem?

[Bald_Eagle1]

If it's not too late, you might look at ONGOING_ERROR.LOG_file_ERROR.TXT from the times that 2 instances were detected.

It's usually down to 'something else' hogging the PC's resources, such as an AV program or something else running on what might be a 'hidden' or not particularly obvious 1 hour schedule.

Which version of Windows are you using?

[pooclah]

Hi Bald_Eagle1

Nothing deleted or changed yet, I’ve been trying to track down the problem first.

Here’s a small sample from the log at the time of an error.  It shows 2 instances of HG612 Modem Stats being started – very odd.

PC details:
AMD A10-5800K 3.8 GHz CPU
8.00 GB RAM
Windows 7

Regards

Kevin

[Bald_Eagle1]

Kevin,


This seems to be an example of what happens when the known Windows Scheduled Task bug causes 2 instances of the same scheduled task to run at the same time
"(The Task Scheduler service runs the same job two times in Windows Server 2008, in Windows Vista, in Windows 7 or in Windows Server 2008 R2 ").

The early exit of HG612_stats.exe was implemented some time ago to deal with this as it previously could & did cause a permanent looping problem that could only be cured by manually 'killing' the looping instance of HG612_stats.exe.

The timing of both instances of HG612_stats.exe starting is very, very close i.e. less than 1/5 second apart (as expected with the bug mentioned above)

14/02/2016  8:52:00.12 - ONGOING-ISRUNNING-085200-096.TXT - Start of [HG612_stats.exe]
14/02/2016  8:52:00.30 - ONGOING-ISRUNNING-085200-267.TXT - Start of [HG612_stats.exe]
(The -096 & -267 relate to the particular running instance)


Ideally, only one of the instances would exit early.
However, both instances were exited in your example (quite possibly as they both started almost at the same time:-

14/02/2016  8:52:01.06 - ONGOING-ISRUNNING-085200-096.TXT - *** End of [HG612_stats.exe] - 2 OR MORE INSTANCES WERE RUNNING.
14/02/2016  8:52:01.23 - ONGOING-ISRUNNING-085200-267.TXT - *** End of [HG612_stats.exe] - 2 OR MORE INSTANCES WERE RUNNING

Therefore the data from 08:52 this morning will be missing from your modem_stats.log.

Sometimes, completely deleting the scheduled task & creating a new one resolves this issue.

Alternatively, the official Microsoft hotfix download is available here:-

https://support.microsoft.com/en-us/kb/2461249



You might also find that the issue creeps backward or forward by one minute every day or so.

[pooclah]

Thanks for that

Now that I have history enabled in Task Scheduler I can see that it is the cause of the problem and was about to do some digging – now thanks to you I don’t need to.

I’ll delete/renew the task and grab the hotfix and see how it goes.

Kevin

[pooclah]

Well over 24 hours now and no breaks in monitoring so all is good.

I’m not sure if reloading the task or the hotfix fixed things as I took the belt and braces route.

Kevin