Beantwoord

[macOS] Coderingen in de log-files van de localhost:5000/logs/app

  • 12 februari 2018
  • 6 reacties
  • 223 keer bekeken
BerendDeMeyer
Rank
Reputatie 7
Goedemorgen allemaal!

Omdat @wmuller en ik bezig zijn met het inventariseren van een aantal issuse die mogelijkerwijs verklaart kunnen worden door de log-files in de localhost:5000/logs/app, zou ik graag willen weten wat deze "[?]" betekenen:


[DetermineIndexMode] [n] Index tag "COMMON_TA#" uses binary naming convention
[2018-02-12 08:53:44.982740] [d] [0x7fd938603a90] [CreateIndexInfo] [n] Index would be opened in binary mode
[2018-02-12 08:53:44.982757] [d] [0x7fd938603a90] [CreateIndexInfo] [n] Tag "ParVer_ta#", expression "ASCEND(ParentId)+SUBSTR(Name,3,16)+ASCEND(NodeId)+DESCEND(Version)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:44.982769] [d] [0x7fd938603a90] [CreateIndexInfo] [n] Tag "NodVer_ta#", expression "ASCEND(NodeId)+ASCEND(Version)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:44.982779] [d] [0x7fd938603a90] [CreateIndexInfo] [n] Tag "Common_ta#", expression "ASCEND(NodeId)", filter "BITVAL(Flags, 9) > 0.AND.NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:44.985579] [d] [0x7fd938603a90] [DetermineIndexMode] [nm] Index tag "HASH_N_TA#" uses binary naming convention
[2018-02-12 08:53:44.985614] [d] [0x7fd938603a90] [CreateIndexInfo] [nm] Index would be opened in binary mode
[2018-02-12 08:53:44.985628] [d] [0x7fd938603a90] [CreateIndexInfo] [nm] Tag "Id2_n_ta#", expression "ASCEND(Id)", filter "Id > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:44.985638] [d] [0x7fd938603a90] [CreateIndexInfo] [nm] Tag "Hash_n_ta#", expression "Hash", filter "Id > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:44.988067] [d] [0x7fd938603a90] Table "nn" fingerprint is 936ACD7CD881A4180DC6
[2018-02-12 08:53:44.988349] [d] [0x7fd938603a90] [DetermineIndexMode] [nn] Index tag "NODE_TA#" uses binary naming convention
[2018-02-12 08:53:44.988380] [d] [0x7fd938603a90] [CreateIndexInfo] [nn] Index would be opened in binary mode
[2018-02-12 08:53:44.988396] [d] [0x7fd938603a90] [CreateIndexInfo] [nn] Tag "ParNod_ta#", expression "ASCEND(ParentId)+SUBSTR(Name_Hash,3,16)+ASCEND(NodeId)+DESCEND(RECNO())", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:44.988407] [d] [0x7fd938603a90] [CreateIndexInfo] [nn] Tag "Node_ta#", expression "ASCEND(NodeId)+DESCEND(RECNO())", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.114564] [d] [0x7fd938603a90] [DetermineIndexMode] [nr] Index tag "FILEID_TA#" uses binary naming convention
[2018-02-12 08:53:45.114608] [d] [0x7fd938603a90] [CreateIndexInfo] [nr] Index would be opened in binary mode
[2018-02-12 08:53:45.114623] [d] [0x7fd938603a90] [CreateIndexInfo] [nr] Tag "FileId_ta#", expression "SUBSTR(FileId,0,12)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.114635] [d] [0x7fd938603a90] [CreateIndexInfo] [nr] Tag "NodVer_ta#", expression "ASCEND(NodeId)+DESCEND(Version)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.115972] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component sc.d: consistent.
[2018-02-12 08:53:45.115986] [d] [0x7fd938603a90] [Component Synchronizer] Updating index component sc.x: up-to-date.
[2018-02-12 08:53:45.116199] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component p.d: consistent.
[2018-02-12 08:53:45.116212] [d] [0x7fd938603a90] [Component Synchronizer] Updating index component p.x: up-to-date.
[2018-02-12 08:53:45.116424] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component sca.d: consistent.
[2018-02-12 08:53:45.116438] [d] [0x7fd938603a90] [Component Synchronizer] Updating index component sca.x: up-to-date.
[2018-02-12 08:53:45.117394] [d] [0x7fd938603a90] [DetermineIndexMode] [p] Index tag "CAB3_TA#" uses binary naming convention
[2018-02-12 08:53:45.117427] [d] [0x7fd938603a90] [CreateIndexInfo] [p] Index would be opened in binary mode
[2018-02-12 08:53:45.117441] [d] [0x7fd938603a90] [CreateIndexInfo] [p] Tag "NOVL64_ta#", expression "ASCEND(NodeId)+ASCEND(Ordinal)+DESCEND(Version)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.117452] [d] [0x7fd938603a90] [CreateIndexInfo] [p] Tag "SlcHsh_ta#", expression "SUBSTR(SliceHash,1,4)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.117462] [d] [0x7fd938603a90] [CreateIndexInfo] [p] Tag "Cab3_ta#", expression "ASCEND(CabinetId)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.118601] [d] [0x7fd938603a90] [DetermineIndexMode] [sca] Index tag "NOVL64_TA#" uses binary naming convention
[2018-02-12 08:53:45.118630] [d] [0x7fd938603a90] [CreateIndexInfo] [sca] Index would be opened in binary mode
[2018-02-12 08:53:45.118644] [d] [0x7fd938603a90] [CreateIndexInfo] [sca] Tag "NOVL64_ta#", expression "ASCEND(NodeId)+ASCEND(Ordinal)+ASCEND(Version)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.119809] [d] [0x7fd938603a90] [DetermineIndexMode] [sc] Index tag "CAB3_TA#" uses binary naming convention
[2018-02-12 08:53:45.119840] [d] [0x7fd938603a90] [CreateIndexInfo] [sc] Index would be opened in binary mode
[2018-02-12 08:53:45.119854] [d] [0x7fd938603a90] [CreateIndexInfo] [sc] Tag "NOVL64_ta#", expression "ASCEND(NodeId)+ASCEND(Ordinal)+DESCEND(Version)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.119865] [d] [0x7fd938603a90] [CreateIndexInfo] [sc] Tag "SlcHsh_ta#", expression "SUBSTR(SliceHash,1,4)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.119874] [d] [0x7fd938603a90] [CreateIndexInfo] [sc] Tag "Cab3_ta#", expression "ASCEND(CabinetId)", filter "NodeId > 0 .AND. .NOT. DELETED()"
[2018-02-12 08:53:45.121298] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component e.e: consistent.
[2018-02-12 08:53:45.121538] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component e.d: consistent.
[2018-02-12 08:53:45.121554] [d] [0x7fd938603a90] [Component Synchronizer] Updating index component e.x: up-to-date.
[2018-02-12 08:53:45.121771] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component ed.e: consistent.
[2018-02-12 08:53:45.122002] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component ed.d: consistent.
[2018-02-12 08:53:45.122015] [d] [0x7fd938603a90] [Component Synchronizer] Updating index component ed.x: up-to-date.
[2018-02-12 08:53:45.124188] [d] [0x7fd938603a90] Table "e" fingerprint is 66919E5B92DBAD6531D9
[2018-02-12 08:53:45.124457] [d] [0x7fd938603a90] [DetermineIndexMode] [e] Index tag "ID_TA#" uses binary naming convention
[2018-02-12 08:53:45.124487] [d] [0x7fd938603a90] [CreateIndexInfo] [e] Index would be opened in binary mode
[2018-02-12 08:53:45.124500] [d] [0x7fd938603a90] [CreateIndexInfo] [e] Tag "Id_ta#", expression "ASCEND(Id)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.124510] [d] [0x7fd938603a90] [CreateIndexInfo] [e] Tag "Loc_ta#", expression "ASCEND(Location)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.126782] [d] [0x7fd938603a90] [DetermineIndexMode] [ed] Index tag "GRPID_TA#" uses binary naming convention
[2018-02-12 08:53:45.126812] [d] [0x7fd938603a90] [CreateIndexInfo] [ed] Index would be opened in binary mode
[2018-02-12 08:53:45.126824] [d] [0x7fd938603a90] [CreateIndexInfo] [ed] Tag "GrpId_ta#", expression "ASCEND(GroupId)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.126834] [d] [0x7fd938603a90] [CreateIndexInfo] [ed] Tag "SessnId_ta#", expression "ASCEND(SessionId)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.128286] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component q.e: consistent.
[2018-02-12 08:53:45.128747] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component q.d: consistent.
[2018-02-12 08:53:45.128760] [d] [0x7fd938603a90] [Component Synchronizer] Updating index component q.x: up-to-date.
[2018-02-12 08:53:45.130909] [d] [0x7fd938603a90] Table "q" fingerprint is 1265E1DFB87D28935204
[2018-02-12 08:53:45.131143] [d] [0x7fd938603a90] [DetermineIndexMode] [q] Index tag "NODEID_TA#" uses binary naming convention
[2018-02-12 08:53:45.131173] [d] [0x7fd938603a90] [CreateIndexInfo] [q] Index would be opened in binary mode
[2018-02-12 08:53:45.131188] [d] [0x7fd938603a90] [CreateIndexInfo] [q] Tag "Priort_ta#", expression "ASCEND(BucketId)+ASCEND(Priority)+ASCEND(CabinetId)+ASCEND(DataOffset)+ASCEND(Id)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.131199] [d] [0x7fd938603a90] [CreateIndexInfo] [q] Tag "NodeId_ta#", expression "ASCEND(NodeId)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.257555] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component c.d: consistent.
[2018-02-12 08:53:45.257579] [d] [0x7fd938603a90] [Component Synchronizer] Updating index component c.x: up-to-date.
[2018-02-12 08:53:45.257846] [d] [0x7fd938603a90] [Component Synchronizer] Updating data component cl.d: consistent.
[2018-02-12 08:53:45.258648] [d] [0x7fd938603a90] Table "c" fingerprint is 5303E3D82A83F9EE1AE2
[2018-02-12 08:53:45.258906] [d] [0x7fd938603a90] [DetermineIndexMode] [c] Index tag "ID_TA#" uses binary naming convention
[2018-02-12 08:53:45.258947] [d] [0x7fd938603a90] [CreateIndexInfo] [c] Index would be opened in binary mode
[2018-02-12 08:53:45.258962] [d] [0x7fd938603a90] [CreateIndexInfo] [c] Tag "Id_ta#", expression "ASCEND(Id)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.258973] [d] [0x7fd938603a90] [CreateIndexInfo] [c] Tag "SessId_ta#", expression "ASCEND(SessionId)", filter ".NOT. DELETED()"
[2018-02-12 08:53:45.259988] [d] [0x7fd938603a90] [CodeBase] File Find Error Opening File (-64) file4open (90615) [/Library/Application Support/KPN/KPN Back-up Online/storage/**********/reg/cl.x] [] []
[2018-02-12 08:53:45.260002] [d] [0x7fd938603a90] [DetermineIndexMode] [cl] Index file could not be opened (-64)
[2018-02-12 08:53:49.045203] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" is being executed...
[2018-02-12 08:53:49.045253] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" executed successfully.
[2018-02-12 08:54:50.046070] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" is being executed...
[2018-02-12 08:54:50.072214] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" executed successfully.
[2018-02-12 08:54:52.124218] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Remote commands processor task" is being executed...
[2018-02-12 08:54:52.201779] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Remote commands processor task" executed successfully.
[2018-02-12 08:55:51.033435] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" is being executed...
[2018-02-12 08:55:51.033481] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" executed successfully.
[2018-02-12 08:56:52.094619] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" is being executed...
[2018-02-12 08:56:52.094682] [d] [0x7fd93acbcff0] [Periodic Task Thread] : "Profiler controller" executed successfully.

Bedankt alvast voor het meedenken!

Heb een fijne maandag! 😎
icon

Beste antwoord door Dennis Hoogstad 13 februari 2018, 08:56

Goedemorgen allen, ( @Lindsay, @BerendDeMeyer, @wmuller )

De betreffende codes die in de logging staan verwijzen naar bestanden uit het back-up register. Door de zeer gedetailleerde wijze van back-up door KPN Back-up Online zijn er vele tabellen (registers) die wijzigingen etc... bijhouden. Zodra 1 van deze tabellen wordt gelezen of gewijzigd (nooit verwijderd 😉 ), zal deze in de logging voorkomen.

Een overzicht van deze tabellen ligt bij de leverancier, deze geeft ze verder niet vrij voor toelichting. Een ticket wordt hierin dan ook overbodig.

Met vriendelijke groet,

Dennis
Bekijk origineel
Groet, Berend - I am an advocate of the "if it ain't broken, don't fix it" modus operandi! -

6 reacties

Lindsay
Rank
Reputatie 6
Badge +5
Hi @BerendDeMeyer, @wmuller,

Ik verwacht dat [n] staat voor 'Node' en [nm] voor 'Node Manager'.🙂

Verder zou ik het eerlijk gezegd zo niet weten. Laten jullie weten of bovenstaand heeft geholpen met het ontcijferen van de codes? Anders zou ik een ticket voor jullie kunnen aanmaken.
Met vriendelijke groet, Lindsay Kuijt | #yeswecare
BerendDeMeyer
Rank
Reputatie 7
Hi @BerendDeMeyer, @wmuller,

Ik verwacht dat [n] staat voor 'Node' en [nm] voor 'Node Manager'.🙂

Verder zou ik het eerlijk gezegd zo niet weten. Laten jullie weten of bovenstaand heeft geholpen met het ontcijferen van de codes? Anders zou ik een ticket voor jullie kunnen aanmaken.
Goedemiddag Lindsay - @Lindsay!

Bedankt voor je reactie en poging deze Davinci-Code te breken! 😂

Zou je een ticket willen aanmaken hiervoor, het zou mooi zijn als we een conversielijst kunnen krijgen voor alle mogelijke [letter-combinaties] in deze logs.

Heb een fijne avond! 😎
Groet, Berend - I am an advocate of the "if it ain't broken, don't fix it" modus operandi! -
Dennis Hoogstad
Rank
Reputatie 3
Badge +2
Goedemorgen allen, ( @Lindsay, @BerendDeMeyer, @wmuller )

De betreffende codes die in de logging staan verwijzen naar bestanden uit het back-up register. Door de zeer gedetailleerde wijze van back-up door KPN Back-up Online zijn er vele tabellen (registers) die wijzigingen etc... bijhouden. Zodra 1 van deze tabellen wordt gelezen of gewijzigd (nooit verwijderd 😉 ), zal deze in de logging voorkomen.

Een overzicht van deze tabellen ligt bij de leverancier, deze geeft ze verder niet vrij voor toelichting. Een ticket wordt hierin dan ook overbodig.

Met vriendelijke groet,

Dennis
BerendDeMeyer
Rank
Reputatie 7
Goedemorgen allen, ( @Lindsay, @BerendDeMeyer, @wmuller )

De betreffende codes die in de logging staan verwijzen naar bestanden uit het back-up register. Door de zeer gedetailleerde wijze van back-up door KPN Back-up Online zijn er vele tabellen (registers) die wijzigingen etc... bijhouden. Zodra 1 van deze tabellen wordt gelezen of gewijzigd (nooit verwijderd 😉 ), zal deze in de logging voorkomen.

Een overzicht van deze tabellen ligt bij de leverancier, deze geeft ze verder niet vrij voor toelichting. Een ticket wordt hierin dan ook overbodig.
Goedemiddag Dennis - @Dennis Hoogstad!

Bedankt voor je snelle reactie en inhoudelijke beantwoording. Naar aanleiding hiervan ben ik ook even op zoek gegaan op mijn Mac. Je refereert dus hoogstwaarschijnlijk naar onderstaande register tabellen?


Weer wat geleerd!

Heb een fijne avond allemaal! 😎
Groet, Berend - I am an advocate of the "if it ain't broken, don't fix it" modus operandi! -
Lindsay
Rank
Reputatie 6
Badge +5
Goedemorgen allen, ( @Lindsay, @BerendDeMeyer, @wmuller )

De betreffende codes die in de logging staan verwijzen naar bestanden uit het back-up register. Door de zeer gedetailleerde wijze van back-up door KPN Back-up Online zijn er vele tabellen (registers) die wijzigingen etc... bijhouden. Zodra 1 van deze tabellen wordt gelezen of gewijzigd (nooit verwijderd 😉 ), zal deze in de logging voorkomen.

Een overzicht van deze tabellen ligt bij de leverancier, deze geeft ze verder niet vrij voor toelichting. Een ticket wordt hierin dan ook overbodig.

Met vriendelijke groet,

Dennis Bedankt voor de verduidelijking Dennis!
Met vriendelijke groet, Lindsay Kuijt | #yeswecare
Dennis Hoogstad
Rank
Reputatie 3
Badge +2
Graag gedaan :)

Met vriendelijke groet,

Dennis

Reageer