#33 CmpLog generates errors in standard log, it won't show the CfUnit Log

xmlwriter
closed
aliazzz
None
2020-05-01
2019-12-30
aliazzz
No

Sometimes, but not always the following message shows up in the Device Log.
It severly hampers usage of the CfUnit testing Framework as we cannot look at the CfUnit Log.

<Entry severity="error" component="CmpSupervisor" user="nobody" timestamp="30-12-2019 12:30:53" infoId="0">Description=Scheduler Tick</Entry>
<Entry severity="error" component="CmpSupervisor" user="nobody" timestamp="30-12-2019 12:30:53" infoId="0">[2] Operation: CmpID=0x00000019, ID=0x1, enable=1, alive=0, timeout=10000 [FAILED]

Why can't we display the CfUnit Log anymore?
Find out root cause,
Suggest fix,
Implement fix.

Discussion

  • aliazzz

    aliazzz - 2019-12-30
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,8 +1,8 @@
-CmpLog keeps throwing errors;
-
+[UPDATE] =&gt; the SimpleExample does not show this erroneous behaviour, so it must an application setting, not library related
 Try the simple CfUnit Example and see if log also CmpLog also fails there.

-CfUnit Verifier throws errors on CmpLog component
+
+CfUnit Verifier throws errors on CmpLog component in the CfUnitVerifier project
 Find out root cause,
 Suggest fix,
 Implement fix.
     

  • aliazzz

    aliazzz - 2019-12-30
    • labels: CmpLog error --> CmpLog error, Prio 1, Help wanted
    • Description has changed:

    Diff:

    --- old
+++ new
@@ -1,9 +1,15 @@
-[UPDATE] =&gt; the SimpleExample does not show this erroneous behaviour, so it must an application setting, not library related
-Try the simple CfUnit Example and see if log also CmpLog also fails there.
+Sometimes, but not always the following message shows up in the Device Log.
+It severly hampers usage of the CfUnit testing Framework as we cannot look at the CfUnit Log.

-
-CfUnit Verifier throws errors on CmpLog component in the CfUnitVerifier project
+~~~
+&lt;Entry severity=&#34;error&#34; component=&#34;CmpSupervisor&#34; user=&#34;nobody&#34; timestamp=&#34;30-12-2019 12:30:53&#34; infoId=&#34;0&#34;&gt;Description=Scheduler Tick&lt;/Entry&gt;
+&lt;Entry severity=&#34;error&#34; component=&#34;CmpSupervisor&#34; user=&#34;nobody&#34; timestamp=&#34;30-12-2019 12:30:53&#34; infoId=&#34;0&#34;&gt;[2] Operation: CmpID=0x00000019, ID=0x1, enable=1, alive=0, timeout=10000 [FAILED]
+~~~
+Why can&#39;t we display the CfUnit Log anymore?
 Find out root cause,
 Suggest fix,
 Implement fix.

+
+
+
     

  • aliazzz

    aliazzz - 2020-01-20

    Problem Solved

     

  • aliazzz

    aliazzz - 2020-01-20
    • labels: CmpLog error, Prio 1, Help wanted -->
    • status: open --> closed
     

  • aliazzz

    aliazzz - 2020-01-20
    • summary: CmpLog generates errors in standard log, it won't show the CfUnit Log [Help Wanted] --> CmpLog generates errors in standard log, it won't show the CfUnit Log
     

Log in to post a comment.