You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One may experience several different errors while trying to restart visor in the integration env. Error may be one of these:
ERROR [transport]: Failed to register transports error="status: 500, error: ID already registered" always happens if running with stcp-startup
if we run with stcp-startup after the error above apps are working. tried restarting visor B and then running test-messaging-loop.sh
if we run with startup apps stop working, all of the described errors appear in some random order, sometimes just some of them
if we runt test-messaging-loop.sh and then restart B, for startup the picture is the same, but for stcp-startup based on logs I may assume that packets are going through but no messages displayed on the console. strange thing
These need to be investigated and fixed one way or another
The text was updated successfully, but these errors were encountered:
One may experience several different errors while trying to restart visor in the integration env. Error may be one of these:
ERROR [transport]: Failed to register transports error="status: 500, error: ID already registered"
always happens if running with stcp-startupstcp-startup
after the error above apps are working. tried restarting visor B and then runningtest-messaging-loop.sh
startup
apps stop working, all of the described errors appear in some random order, sometimes just some of themtest-messaging-loop.sh
and then restart B, forstartup
the picture is the same, but forstcp-startup
based on logs I may assume that packets are going through but no messages displayed on the console. strange thingThese need to be investigated and fixed one way or another
The text was updated successfully, but these errors were encountered: