Open nielsek opened 1 month ago
@grossmj this doesn't seem to be an issue when utilizing the latest from Git :smile:
Maybe due to the update of FastAPI in https://github.com/GNS3/gns3-server/commit/a7da814b851e5b5470da9d98b8128a589c05b896 ?
Guess I was a bit too fast. Still having the issue sometimes
GNS3 version:
3.0.0rc1
Error messages
Background
I am not sure if this is only related to
PUT /v3/projects/{project_id}/nodes/{node_id}
, but the above example is from such an occasion.Afterwards the API seems to still operate normally, so it is able to create new QEMU VMs and start them and so on.
For GNS3 clients, these new VMs will appear however it will look like they are turned off even though they are not.
That seems to be because the GNS3 server is only sending out
ping
events on the notifications websocket after the error, so no morecompute.update
events, which usually comes as the second event when connecting a new client.Example from a "client" that prints all events:
If I try to shut down GNS3, then it will just wait for background tasks to complete: