search

google-code-export / hfm-net

Automatically exported from code.google.com/p/hfm-net
1 stars 0 forks source link

Problem with SMP Client Logs with mangled Project strings in post-v0.4.0 builds. #136

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Unknown
2.
3.

What is the expected output? What do you see instead?
Regular reporting of ppd and frame times

Log is current, no frame times or ppd, client reported as hung.  Perhaps a
cosmetic glitch in the log causes HFM to be unable to parse the log:

[12:49:56] Completed 30000 out of 250000 steps  (12%)
[13:21:11] Completed 32500 out of 250000 steps  (13%)
[13:43:12] - Autosending finished units... [December 22 13:43:12 UTC]
[13:43:12] Trying to send all finished work units
[13:43:12] + No unsent completed units remaining.
[13:43:12] - Autosend completed
[13:52:26] Completed 35000 out of 250000 steps  (14%)

What version of the product are you using? On what operating system?
v0.4.6 - 99

Please provide any additional information below.

Messages after a refresh of the client.  Appears it is a glitch in the log
causing HFM to report as hung.  It will probably do so every 6 hours on
autosend written to log:

[12/22/2009-9:25:57 AM] - Total Retrieval Execution Time: 23,562 ms
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.RetrievePathInstance
(LMC) FAHlog copy (start)
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.RetrievePathInstance
(LMC) FAHlog copy (file has not changed)
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.RetrievePathInstance
(LMC) UnitInfo copy (start)
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.RetrievePathInstance
(LMC) UnitInfo copy (success)
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.RetrievePathInstance
(LMC) Queue copy (start)
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.RetrievePathInstance
(LMC) Queue copy (success)
[12/22/2009-9:26:14 AM] - HFM.Instances.ClientInstance.RetrievePathInstance
(LMC) Execution Time: 78 ms
[12/22/2009-9:26:14 AM] + HFM.Instances.LogReader.ScanFAHLog (LMC)
Execution Time: 0 ms
[12/22/2009-9:26:14 AM] +
HFM.Instances.ClientInstance.ParseLogLinesBasedOnQueueIndex (LMC) Could not
find or verify log section for queue entry 0 (this is not a problem).
[12/22/2009-9:26:14 AM] +
HFM.Instances.ClientInstance.ParseLogLinesBasedOnQueueIndex (LMC) Could not
find or verify log section for queue entry 1 (this is not a problem).
[12/22/2009-9:26:14 AM] +
HFM.Instances.ClientInstance.ParseLogLinesBasedOnQueueIndex (LMC) Could not
find or verify log section for queue entry 2 (this is not a problem).
[12/22/2009-9:26:14 AM] + HFM.Instances.LogParser.ParseFAHLog (LMC)
Execution Time: 16 ms
[12/22/2009-9:26:14 AM] + HFM.Instances.LogParser.ParseFAHLog (LMC)
Execution Time: 0 ms
[12/22/2009-9:26:14 AM] ! HFM.Instances.ClientInstance.ProcessExisting
(LMC) Could not verify log section for current queue entry (5). Parsing
logs without queue.
[12/22/2009-9:26:14 AM] + HFM.Instances.LogParser.ParseFAHLog (LMC)
Execution Time: 0 ms
[12/22/2009-9:26:14 AM] + HFM.Instances.LogParser.ParseFAHLog (LMC)
Execution Time: 16 ms
[12/22/2009-9:26:14 AM] + HFM.Instances.LogParser.ParseUnitInfoFile (LMC)
Execution Time: 0 ms
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.ProcessExisting
(LMC) Execution Time: 31 ms
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.DetermineStatus (LMC)
[12/22/2009-9:26:14 AM] +  - Retrieval Time (Date) ------- : 12/22/2009
9:26:14 AM
[12/22/2009-9:26:14 AM] +  - Time Of Last Frame (TimeSpan) : 01:33:08
[12/22/2009-9:26:14 AM] +  - Offset (Minutes) ------------ : 0
[12/22/2009-9:26:14 AM] +  - Time Of Last Frame (Adjusted) : 01:33:08
[12/22/2009-9:26:14 AM] +  - Prior Day Adjustment -------- : False
[12/22/2009-9:26:14 AM] +  - Time Of Last Frame (Date) --- : 12/22/2009
1:33:08 AM
[12/22/2009-9:26:14 AM] +  - Terminal Time (Date) -------- : 12/22/2009
7:26:14 AM
[12/22/2009-9:26:14 AM] + HFM.Instances.ClientInstance.DetermineAsyncStatus
(LMC)
[12/22/2009-9:26:14 AM] +  - Retrieval Time (Date) ------- : 12/22/2009
9:26:14 AM
[12/22/2009-9:26:14 AM] +  - Time Of Last Unit Start ----- : 12/22/2009
2:16:14 AM
[12/22/2009-9:26:14 AM] +  - Time Of Last Frame Progress - : 1/1/0001
12:00:00 AM
[12/22/2009-9:26:14 AM] +  - Terminal Time (Date) -------- : 12/22/2009
7:26:14 AM
[12/22/2009-9:26:14 AM] - HFM.Instances.ClientInstance.Retrieve (LMC)
Client Status: Hung
[12/22/2009-9:26:14 AM] +
HFM.Instances.InstanceCollectionHelpers.FindDuplicates Execution Time: 0 ms
[12/22/2009-9:26:14 AM] +
HFM.Instances.ProteinBenchmarkCollection.Serialize Execution Time: 94 ms

Original issue reported on code.google.com by CRrichar...@gmail.com on 22 Dec 2009 at 2:28

GoogleCodeExporter commented 9 years ago 
HFM reported p2683 without issue.  p2681 has been reported as hung for hours.  
No
queue data is reported.

Original comment by CRrichar...@gmail.com on 22 Dec 2009 at 8:47

GoogleCodeExporter commented 9 years ago 
When the Project string from an SMP Client log is mangled (on the current 
unit), the
queue data is thrown out because the queue data Project (R/C/G) cannot be 
matched to
the FAHlog Project (R/C/G) - because it's mangled.

The UnitFrame data array is now being dynamically sized based on the 
CurrentProtein -
so when the CurrentProtein is changed, the UnitFrame data is currently being 
wiped
out because the array is being recreated.

Since v0.4.0 the unitinfo.txt file has been parsed after the FAHlog.txt file 
(which
contains no valid Project (R/C/G) - again, mangled.  When the Project (R/C/G) 
is read
from the unitinfo.txt file, it sets the CurrentProtein property, which in turn 
clears
out the UnitFrame data array (which had already been populated) - thus all the 
frame
data is "lost" and there is nothing there to gauge frame times or progress... 
thus
the client gets marked Hung.

Original comment by harlam357 on 2 Jan 2010 at 8:44

GoogleCodeExporter commented 9 years ago

Original comment by harlam357 on 2 Jan 2010 at 8:45

GoogleCodeExporter commented 9 years ago 
Marked Fixed for Revision 110.  See UnitInfo.ResizeUnitFrameData().

Original comment by harlam357 on 17 Jan 2010 at 9:58