-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stream manager streams visualization #40
Comments
Is stream manager installed and running without error? |
yes, there are no errors in the stream manager log and it works normally. |
When you refresh the local debug console, is it able to connect? Please show the configuration from the CLI or the local debug console of Stream manager as well as Local debug console components. |
I've attached the configuration below.
|
I mean refreshing the page in the browser, yes. The error you're getting is that the connection is being refused. This would happen if the local debug console is trying to connect to the wrong port. The Please review the logs for stream manager during its startup and try restarting the stream manager component. |
According to the stream manager documentation, the only option to configure the port is via STREAM_MANAGER_SERVER_PORT parameter, which is (in our case) set to 8088. So I don't understand what do you mean by the Attaching stream manager logs after clicking on "reinstall" in the local debug console
|
Correct, you should not configure the |
Oh I see, but what can I do with it? Maybe check is some other process is using the default 8088 port? |
This log line indicates that stream manager did update the port field in the configuration. Using the local debug console, view the configuration from stream manager and see that the port field is set to 8088. If it is not set, you could set it yourself using the local debug console and then the console will be able to successfully connect. |
I don't know why but the But sice we have this conversation here, I'd like to ask you for one more advice - what I was initially trying to achieve using the local debug console is to debug some shadow syncing problem we're facing. The thing is that I am not sure if the shadow update (initiated on cloud) is not propagated to the ShadowManager or if we're just not handling the shadow update correctly in our component. How would you troubleshoot this? What is the best way how to check the current shadow state stored in the ShadowManager? Thank you |
The local debug console cannot show anything related to Shadows directly. You can use the builtin message test console to subscribe to all local pubsub topics and then publish a message to the local shadow topic which will let you read the shadow contents the same way you would do this in a component. If you think your shadow is not syncing, then make a change and review the logs relating to shadow manager; there is probably an error which is most likely due to missing permissions. If there is no error, then the most likely cause is a misconfiguration of the shadow manager. To be clear, subscribe to
This is most likely because you restarted Stream manager and it was able to update the port field properly this time. |
Ok, I'll try to diagnose the problem this way. Ane one more question: The documentation says
And if I am not mistaken 5500 kilobits per second should be 687.5 kilobytes per second. The question is: Is there a mistake in the documentation or in the visualization of the configured value in the local debug console? |
I see what you mean. It is showing This is an error in the console's math. It is assuming bytes instead of bits. |
Ok, but when the documentation says this value is in "kilobits per second" should it be 5.37 megabits in the local debug console? |
5500 kilobits per second is 5.37 megabits per second, yes. |
I think for now all my questions were answered so thank you. |
Tracking the |
I've encountered an issue while trying to open the streams overview
aws.greengrass.Nucleus: 2.12.6
aws.greengrass.LocalDebugConsole: 2.4.2
greengrass.log
Expected behavior:
StreamManager streams are shown in the local debug console streams overview.
Thanks
Tomas
The text was updated successfully, but these errors were encountered: