WhatPulse 2.4b1 - Network on sleep

[commentator]

(03-29-2014 02:04 AM)smitmartijn Wrote:  Alright, this next build has a monitoring function built in, which should take care of the network monitoring when waking up from a hibernate.

Can you guys try this exe and see if it fixes it for you? https://dl.dropboxusercontent.com/u/7766...tpulse.exe - Just drop it in the install folder.

It hasn't gone the regular Q&A, but initial tests looking good. Thanks!

afer hybernate it is counting now !

But see something strange now

Code:

29-03-2014 17:57:44.199 DEBUG Packet capture failure detected!
29-03-2014 17:57:44.199 DEBUG pcap thread stopped on interface  "\Device\NPF_{1BCA1CF4-19CF-4AE4-B7AA-83D04229C81E}"
29-03-2014 17:58:23.561 DEBUG Removed idle thread for interface:  3
29-03-2014 17:58:23.608 DEBUG Found new interface:  3 .... "Intel WiFi Link 5300 AGN"
29-03-2014 17:58:23.608 DEBUG PcapNetworkTrafficMonitor: Starting interface  3
29-03-2014 17:58:23.624 DEBUG Couldn't open device  "\Device\NPF_{1BCA1CF4-19CF-4AE4-B7AA-83D04229C81E}" : Error opening adapter: Het systeem kan het opgegeven apparaat niet vinden. (20)
29-03-2014 17:58:53.576 DEBUG Stopping PcapNetworkTrafficMonitor..
29-03-2014 17:58:53.576 DEBUG Starting PcapNetworkTrafficMonitor..
29-03-2014 17:58:53.591 DEBUG Found new interface:  3 .... "Intel WiFi Link 5300 AGN"
29-03-2014 17:58:53.591 DEBUG PcapNetworkTrafficMonitor: Starting interface  3
29-03-2014 17:58:53.607 DEBUG Setting WinPcap buffer to 4MB:  "Success"
29-03-2014 17:58:53.607 DEBUG pcap thread started on interface  "\Device\NPF_{1BCA1CF4-19CF-4AE4-B7AA-83D04229C81E}"
29-03-2014 18:00:24.215 DEBUG GetModuleFileNameEx failed for processId:  71600 0
29-03-2014 18:01:24.174 DEBUG GetModuleFileNameEx failed for processId:  71600 0
29-03-2014 18:02:24.183 DEBUG GetModuleFileNameEx failed for processId:  71600 0
29-03-2014 18:03:24.678 DEBUG GetModuleFileNameEx failed for processId:  71600 0

What is this "GetModuleFileNameEx failed for processId"?

[smitmartijn]

Cool, I see the monitoring picks up the failure. I'd like to see if it continues to pick it up though..I'll leave it in.

The GetModuleFileNameEx warnings can be ignored. It indicates that the client couldn't access the specified process (with ID 71600) with that method. It uses three other different methods to get info if that one fails, so no reason to worry.

Reasons can be the elevation type of the application, if it's running as administrator..apps can protect themselves as well (but I don't see that one often).

[commentator]

And why is the log now in an extra subdir?
C:\Users\<user>\AppData\Local\WhatPulse\WhatPulse

Was in previous version:
C:\Users\<user>\AppData\Local\WhatPulse

[smitmartijn]

(03-30-2014 10:04 PM)commentator Wrote:  And why is the log now in an extra subdir?

It doesn't, as you can see from several logs posted by the others. There's a chance that if you lock the file and boot the client it would do that, but it's not permanent, unless you have locked the regular app.log permanently (by having it stay open in notepad or something).

[commentator]

(03-31-2014 07:14 PM)smitmartijn Wrote:  

(03-30-2014 10:04 PM)commentator Wrote:  And why is the log now in an extra subdir?

It doesn't, as you can see from several logs posted by the others. There's a chance that if you lock the file and boot the client it would do that, but it's not permanent, unless you have locked the regular app.log permanently (by having it stay open in notepad or something).

removed old logfile, shutdown client, remove new subdir, start client, subdir is there again!