search

eclipse-sparkplug / sparkplug

Sparkplug
Eclipse Public License 2.0
114 stars 39 forks source link

Question: TCK Randomly Not Producing Logs #466

Open SarahSonnier opened 1 year ago

SarahSonnier commented 1 year ago

What do you want to know?

Hey, I have been working with the TCK for three weeks or so, and I randomly have an issue where I will start a test and nothing happens, no logging, nothing in the browser console, nothing in MQTT SPARKPLUG_TCK topic, no log file written. When I stop the test, the TCK behaves as if the test is still running (radio buttons for tests greyed out, hitting green start test will give a warning that test must be stopped, even though it was stopped, test must be re-set to continue).

Normally, if the test is not executed, or something goes wrong, there are logs recorded and displayed showing tests not executed, or tests failed, but right now I do not get any logs at all.

I am scratching my head trying to figure out what is causing this, I've re-installed everything, rebooted computer, and am wondering if this is something that sounds familiar, or if there is a quick fix you can help me find.

browser console image

MQTT Explorer image

Test that was run and manually stopped, without logs image

Is this related to a Sparkplug Listing request? If so, link the issue from https://github.com/eclipse-sparkplug/sparkplug.listings here.

No response

Version

3.0.0 (Default)

Accept EFTL Terms

bryce-nakatani commented 1 year ago

I'm seeing similar behavior with the Edge Node profile. I'm running the 3.0.0 released TCK on Ubuntu 22.04.2 (x64, 3 processors) Server running as a VM (Virtualbox on a Windows 11 Pro host). Seems that during the test, a deadlock occurs and the only recovery is to restart the whole application. But, I am unable to complete the test because eventually, the deadlock occurs. I didn't have this occur about a month ago with another product validation. I wonder if an update is causing the failure. On the VM, yarn is version 1.22.10 and java is open jdk 11.0.19 2023-04-18.

icraggs-sparkplug commented 1 year ago

So the basic problem is that the start test event is emitted, and the state of the test is updated to running regardless of the result of that event. An easy way to reproduce this is to try and start a test when the web console is not connected to the MQTT broker. One of those things that didn't get cleaned up in the squeeze to get the first release out. I'll look into making this work properly.

@bryce-nakatani I'm not sure that what you are describing is the same problem.

bryce-nakatani commented 1 year ago

That makes sense.

On a side note, I have noticed that after a period of time, the Web Console disconnects from the MQTT Server. Is that intentional?

I have a different issue. Sorry, I'm still a bit busier than I planned on. I'm hoping to get to this today.

On Thu, Aug 10, 2023 at 8:52 AM Ian Craggs @.***> wrote:

So the basic problem is that the start test event is emitted, and the state of the test is updated to running regardless of the result of that event. An easy way to reproduce this is to try and start a test when the web console is not connected to the MQTT broker. One of those things that didn't get cleaned up in the squeeze to get the first release out. I'll look into making this work properly.

@bryce-nakatani https://github.com/bryce-nakatani I'm not sure that what you are describing is the same problem.

— Reply to this email directly, view it on GitHub https://github.com/eclipse-sparkplug/sparkplug/issues/466#issuecomment-1673491399, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEF6AZUXR3VG75U7NOLG5PDXUT7VBANCNFSM6AAAAAA2D5CDMA . You are receiving this because you were mentioned.Message ID: @.***>

icraggs-sparkplug commented 1 year ago

No it's not intentional that the web console should disconnect from the MQTT server. Is it when it's running in a background tab? (Maybe the MQTT client can't keep the connection alive in that case)

bryce-nakatani commented 1 year ago

Yes, the tab is in the background. Good to know.

On Thu, Aug 10, 2023 at 10:54 AM Ian Craggs @.***> wrote:

No it's not intentional that the web console should disconnect from the MQTT server. Is it when it's running in a background tab? (Maybe the MQTT client can't keep the connection alive in that case)

— Reply to this email directly, view it on GitHub https://github.com/eclipse-sparkplug/sparkplug/issues/466#issuecomment-1673659084, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEF6AZWLGVB5DJMFIEUZSM3XUUN5VANCNFSM6AAAAAA2D5CDMA . You are receiving this because you were mentioned.Message ID: @.***>