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
Can't say if this is a problem with the GUI or the server.
GNS3 version and operating system (please complete the following information):
GNS3: 2.2.38
Client: Windows 11 Pro, Standalone GUI
Server: Separate physical server, Ubuntu 20.04 directly installed, fully updated
Logs also included in the community post
Logs
Logs from the server (/var/log/gns3/)
The raw log file, and split into parts
Part 1 is starting gns3/loading topology
Part 2 is after I start moving the mouse/zooming etc
@grossmj is there any update or hotfix that can be applied to workaround this issue? I have a number of topologies that crash when you zoom in/out, and I can't figure out any settings that affect it.
My band-aid fix for this was to increase the timeout value in /usr/share/gns3/gns3-server/lib/python3.10/site-packages/gns3server/controller/compute.py method _run_http_query.
Describe the bug
After the topology is loaded, zooming or panning the canvas in topology crashes GNS3
Message on the console dock/alert window:
Timeout error for PUT call to http://127.0.0.1:3080/v2/compute/projects/d444ef1c-cd37-4dd9-99db-a9a2cbc51a14 after 20s
Can't say if this is a problem with the GUI or the server.
GNS3 version and operating system (please complete the following information):
GNS3: 2.2.38
Client: Windows 11 Pro, Standalone GUI
Server: Separate physical server, Ubuntu 20.04 directly installed, fully updated
Logs also included in the community post
To Reproduce
Steps to reproduce the behavior:
Additional context
Community link: https://gns3.com/community/support/problem-with-big-topologies
Logs
Logs from the server (/var/log/gns3/)
The raw log file, and split into parts
Part 1 is starting gns3/loading topology
Part 2 is after I start moving the mouse/zooming etc
gns3.log
gns3_log_part1.txt
gns3_log_part2.txt
The text was updated successfully, but these errors were encountered: