Closed brettdaman closed 7 years ago
The one above looks more like the agile-core-http log! There was a request (REST API call) for ProtocolManager before the ProtocolManager actually started up. Currently it takes too long. For several seconds, it is just starting up, without going on the dbus. We are working on faster startup. We might also add some better error messages in the http side.
We have improved startup speed. Still, it could happen that the HTTP starts up before the protocol manager. In this case you get an error when calling GET, which to me seems correct. Can you tell me what would be the behavior you expect?
This can be closed
I rebuild the docker today with the updates and got an error after start.
I use the perservice start script, after startup I try GET /api/protocols/discovery (The other protocols endpoints also have this issue) and receive a ProtocolManager error.
The logs from agile-core-ProtocolManager
After a restart the issue was gone