Skip to content
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

Unable to connect limits monitor to replay server #948

Closed
ienorand opened this issue Feb 21, 2019 · 4 comments

Comments

Projects
None yet
3 participants
@ienorand
Copy link

commented Feb 21, 2019

Using the cosmos demo configuration (version 4.3.0 on Debian 9) I am unable to connect the limits monitor to the replay server. I have tested with just the replay window open, after loading a log file for replay, and after starting active replay.

The limits monitor reports "error connecting to command and telemetry server" in the status bar. I have tried resetting and toggling replay mode with no effect.

@ienorand

This comment has been minimized.

Copy link
Author

commented Feb 21, 2019

If starting with the normal command and telemetry server and connecting to it, it seems like it is then possible to switch the limits monitor over to the replay server...

@jasonatball

This comment has been minimized.

Copy link
Collaborator

commented Feb 25, 2019

I briefly tried to reproduce and could not. Could you detail the steps which causes this error?

@ienorand

This comment has been minimized.

Copy link
Author

commented Feb 27, 2019

I tested this from a cosmos 4.3.0 install on both Debian 9 and ubuntu 14.04.

  1. ruby Launcher
  2. Start replay server
  3. Start limits monitor
    • At this point the limits monitor showed "error connecting to command and telemetry server" in the status bar, which is expected since the normal command and telemetry server is not running.
  4. Select "toggle replay mode" menu option in the limits monitor.
    • At this point the limits monitor did not show the replay mode green status indicator, nor remove the connection error in the status bar.

Here I would expect that the limits monitor would succeed in switching to replay mode and connecting to the replay server.

Further exploration:

I then started the normal command and telemetry server, which caused the limits monitor to start showing limits correctly and stop showing the connection error.

I then again selected the "toggle replay mode" menu option in the limits monitor which now did show the green replay mode green status indicator.

I then loaded the current log file in the replay server and started it with a 10ms delay, and observed that limits monitor seemed to process and display at least parts of the limits correctly

I then exited the normal command and telemetry server, and observed that the limits monitor was still able to stay connected to the replay server.

So it somehow seems that the limits monitor cannot connect to the replay server without first being connected to the command and telemetry server?

@jasonatball

This comment has been minimized.

Copy link
Collaborator

commented Mar 4, 2019

@ienorand Thank you for this report. I was unable to initially reproduce because there is a race condition between selecting Replay Mode and having it run. I guess I got lucky (unlucky?) the first few times I tried it. I also noticed that the log tab doesn't clear when going between modes which I also fixed. I opened the pull request but this will obviously be in a future release. If you want to get this change now you can create a lib/cosmos/tools/limits_monitor/limits_monitor.rb file in the base of your COSMOS configuration directory and copy in the file from the pull request. To prove you're using the new file you can add something like puts "NEW FILE" in the initialize method (line 536) and you should see a window popup with "Unexpected STDOUT output" when it starts. Note, you can alternatively add command line debugging by add STDOUT.puts anywhere in the file and then running the tool from the command line via ruby tools\LimitsMonitor. Note you may have to delete your Gemfile.lock first for this to work.

@ryanatball ryanatball added this to the v4.4.0 milestone Jul 2, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.