2.1.1 Canvas refresh: Start/Stop All Nodes, Node Status, Adding New Nodes

[mekisiel]

Upgraded gns3-server on remote RHEL7 server and gns3-gui on RHEL7 host to 2.1.1. From the gns3-gui, start/stop nodes does not refresh node state on the topology canvas or panes. From the gns3-server api, the project shows status 'opened' and compute nodes show status 'started.' Launching the console via right-click menu results in an error to the effect: 'node must be started first'. Starting/stopping the individual nodes via right-click start menu works and the node status is refreshed in the canvas/gui. After starting individually, the console picks right up where the original 'start all nodes' left off (i.e., not a new boot). Also dragging a new node onto the canvas does not show until the project is closed and re-opened. Via the gns3-server api, the new node is present, however. Debugs, as far as I can tell, are all clean 200 messages.

[grossmj]

How did you install GNS3? Also, can you make a small video showing the issue?

Thanks!

[mekisiel]

Upgrade was performed via pip from v2.0.3. I'll work on the video. Thanks.

On Wed, Jan 10, 2018 at 10:22 AM, Jeremy Grossmann <notifications@github.com

wrote:

How did you install GNS3? Also, can you make a small video showing the issue?

Thanks!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-gui/issues/2374#issuecomment-356634276, or mute the thread https://github.com/notifications/unsubscribe-auth/ATkVmoQ03f3iMaFsftn3pp1Dm-8zvgUFks5tJNWhgaJpZM4RLYjS .

[grossmj]

I got your video, that's helping a lot. I am going to investigate this and will let you know if I need more information. Thanks!

[grossmj]

Upgrade was performed via pip from v2.0.3.

Did you have these issues with v2.0.3?

[mekisiel]

I did not have these problems in v2.0.3. It was a very stable version for us.

On Wed, Jan 17, 2018 at 3:48 AM, Jeremy Grossmann notifications@github.com wrote:

Upgrade was performed via pip from v2.0.3.

Did you have these issues with v2.0.3?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-gui/issues/2374#issuecomment-358236652, or mute the thread https://github.com/notifications/unsubscribe-auth/ATkVmvYfXcvRklTUKhzlNwWMkUpECyF8ks5tLbPdgaJpZM4RLYjS .

[grossmj]

I am suspecting something wrong with a dependency. I would like to make sure your GNS3 GUI receives events from the server (these are sent via a Websocket).

Can you start the interface with the --debug param or alternatively you can start the application and use debug 2 in the GNS3 console to activate the debugging and debug 0 to deactivate it.

Check for the following event once you start all the nodes:

Event received: {'action': 'node.updated', 'event': {...}}

Check for this when you add a new node:

Event received: {'action': 'node.created', 'event': {...}}

Thanks!

[mekisiel]

I reverted back to 2.0.3 but, did get a snapshot of the failed instance. I'll need a few days to get something up for additional tests.

On Tue, Jan 30, 2018 at 10:09 AM, Jeremy Grossmann <notifications@github.com

wrote:

I am suspecting something wrong with a dependency. I would like to make sure your GNS3 GUI receives events from the server (these are sent via a Websocket).

Can you start the interface with the --debug param or alternatively you can start the application and use debug 2 in the GNS3 console to activate the debugging and debug 0 to deactivate it.

Check for the following event once you start all the nodes:

Event received: {'action': 'node.updated', 'event': {...}}

Check for this when you add a new node:

Event received: {'action': 'node.created', 'event': {...}}

Thanks!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-gui/issues/2374#issuecomment-361622460, or mute the thread https://github.com/notifications/unsubscribe-auth/ATkVmrPUsyiaZsmumhx8QHKHbMpA8437ks5tPzCkgaJpZM4RLYjS .

[grossmj]

Thanks Michael. I will wait for additional tests.

On Fri, Feb 2, 2018, 8:18 PM Michael notifications@github.com wrote:

I reverted back to 2.0.3 but, did get a snapshot of the failed instance. I'll need a few days to get something up for additional tests.

On Tue, Jan 30, 2018 at 10:09 AM, Jeremy Grossmann < notifications@github.com

wrote:

I am suspecting something wrong with a dependency. I would like to make sure your GNS3 GUI receives events from the server (these are sent via a Websocket).

Can you start the interface with the --debug param or alternatively you can start the application and use debug 2 in the GNS3 console to activate the debugging and debug 0 to deactivate it.

Check for the following event once you start all the nodes:

Event received: {'action': 'node.updated', 'event': {...}}

Check for this when you add a new node:

Event received: {'action': 'node.created', 'event': {...}}

Thanks!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-gui/issues/2374#issuecomment-361622460, or mute the thread < https://github.com/notifications/unsubscribe-auth/ATkVmrPUsyiaZsmumhx8QHKHbMpA8437ks5tPzCkgaJpZM4RLYjS

.

— You are receiving this because you were assigned.

Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-gui/issues/2374#issuecomment-362571499, or mute the thread https://github.com/notifications/unsubscribe-auth/AEiE5q4RWu6nffhrwKOFb-7d1uSCG6DXks5tQvz9gaJpZM4RLYjS .

[grossmj]

Hi Michael,

I think I understand what is going wrong.

Your GNS3 client doesn't receive notifications (events). Looks like the reason is that all notifications were received from an HTTP stream in version 2.0.3 (and before), then we switched to WebSocket in version 2.1

https://github.com/GNS3/gns3-gui/commit/e06cf5b9a12d0d090516ef9cb563068274caf01b#diff-62fa79df7a5d8dbec8543d09b372aab7

I cannot explain why the WebSocket notification does't work, maybe some kind of filtering or firewall between the client and the server?

One wait to double check is to install wscat (https://www.npmjs.com/package/wscat) on the same machine as the GNS3 client, find the UUID for your project in the .gns3 file (entry: "project_id": "6be0065d-3856-4edb-bff2-4e838929ace1"). Then you can use wscat to see if you received notifications:

wscat -c 'http://172.16.1.1:3080/v2/projects/6be0065d-3856-4edb-bff2-4e838929ace1/notifications/ws' (replace the IP by the one for your RHEL7 server and the UUID by the one for your project)

wscat -c 'http://172.16.1.1:3080/v2/projects/6be0065d-3856-4edb-bff2-4e838929ace1/notifications/ws'
connected (press CTRL+C to quit)
< {"action": "ping", "event": {"cpu_usage_percent": 18.2, "memory_usage_percent": 75.2}}
< {"action": "compute.updated", "event": {"capabilities": {"node_types": ["cloud", "ethernet_hub", "ethernet_switch", "nat", "vpcs", "virtualbox", "dynamips", "frame_relay_switch", "atm_switch", "qemu", "vmware", "docker", "iou"], "platform": "linux", "version": "2.1.4dev1"}, "compute_id": "local", "connected": true, "cpu_usage_percent": 9.9, "host": "172.16.1.1", "memory_usage_percent": 75.2, "name": "coruscant", "port": 3080, "protocol": "http", "user": "QDTAzWtEKgKlXwmy3Qglkmw71h5XQ5zzSKkBKxFfPvcgGVtjKliJFNaFp7FOijBq"}}
< {"action": "compute.updated", "event": {"capabilities": {"node_types": ["cloud", "ethernet_hub", "ethernet_switch", "nat", "vpcs", "virtualbox", "dynamips", "frame_relay_switch", "atm_switch", "qemu", "vmware", "docker", "iou"], "platform": "linux", "version": "2.1.3dev1"}, "compute_id": "vm", "connected": true, "cpu_usage_percent": 0.6, "host": "172.16.1.128", "memory_usage_percent": 14.2, "name": "GNS3 VM (GNS3 VM)", "port": 3080, "protocol": "http", "user": null}}
< {"action": "compute.updated", "event": {"capabilities": {"node_types": ["cloud", "ethernet_hub", "ethernet_switch", "nat", "vpcs", "virtualbox", "dynamips", "frame_relay_switch", "atm_switch", "qemu", "vmware", "docker", "iou"], "platform": "linux", "version": "2.1.4dev1"}, "compute_id": "local", "connected": true, "cpu_usage_percent": 10.9, "host": "172.16.1.1", "memory_usage_percent": 75.2, "name": "coruscant", "port": 3080, "protocol": "http", "user": "QDTAzWtEKgKlXwmy3Qglkmw71h5XQ5zzSKkBKxFfPvcgGVtjKliJFNaFp7FOijBq"}}

Let me know if you get anything.

Thanks!

[mekisiel]

Hi Jeremy - I got a chance to do some more testing on this and was able to narrow the issue down further. It appears that an upgrade to either PyQt or sip packages resolves the issues. I rev'd PyQt from 5.9 to 5.10 and sip from 4.19.3 to 4.19.7. I have not had a chance to look at their respective change logs to see if anything stuck out but, rerunning the previous start/stop all and add/delete node tests come back with expected results on both gns3-gui and gns3-server. I think we can probably close this unless you would like some more test debugs. Thanks a bunch!

On Mon, Feb 5, 2018 at 1:00 AM, Jeremy Grossmann notifications@github.com wrote:

Hi Michael,

I think I understand what is going wrong.

Your GNS3 client doesn't receive notifications (events). Looks like the reason is that all notifications were received from an HTTP stream in version 2.0.3 (and before), then we switched to WebSocket in version 2.1

e06cf5b#diff-62fa79df7a5d8dbec8543d09b372aab7 https://github.com/GNS3/gns3-gui/commit/e06cf5b9a12d0d090516ef9cb563068274caf01b#diff-62fa79df7a5d8dbec8543d09b372aab7

I cannot explain why the WebSocket notification does't work, maybe some kind of filtering or firewall between the client and the server?

One wait to double check is to install wscat (https://www.npmjs.com/ package/wscat) on the same machine as the GNS3 client, find the UUID for your project in the .gns3 file (entry: "project_id": "6be0065d-3856-4edb-bff2-4e838929ace1"). Then you can use wscat to see if you received notifications:

wscat -c 'http://172.16.1.1:3080/v2/projects/6be0065d-3856-4edb- bff2-4e838929ace1/notifications/ws' (replace the IP by the one for your RHEL7 server and the UUID by the one for your project)

wscat -c 'http://172.16.1.1:3080/v2/projects/6be0065d-3856-4edb-bff2-4e838929ace1/notifications/ws' connected (press CTRL+C to quit) < {"action": "ping", "event": {"cpu_usage_percent": 18.2, "memory_usage_percent": 75.2}} < {"action": "compute.updated", "event": {"capabilities": {"node_types": ["cloud", "ethernet_hub", "ethernet_switch", "nat", "vpcs", "virtualbox", "dynamips", "frame_relay_switch", "atm_switch", "qemu", "vmware", "docker", "iou"], "platform": "linux", "version": "2.1.4dev1"}, "compute_id": "local", "connected": true, "cpu_usage_percent": 9.9, "host": "172.16.1.1", "memory_usage_percent": 75.2, "name": "coruscant", "port": 3080, "protocol": "http", "user": "QDTAzWtEKgKlXwmy3Qglkmw71h5XQ5zzSKkBKxFfPvcgGVtjKliJFNaFp7FOijBq"}} < {"action": "compute.updated", "event": {"capabilities": {"node_types": ["cloud", "ethernet_hub", "ethernet_switch", "nat", "vpcs", "virtualbox", "dynamips", "frame_relay_switch", "atm_switch", "qemu", "vmware", "docker", "iou"], "platform": "linux", "version": "2.1.3dev1"}, "compute_id": "vm", "connected": true, "cpu_usage_percent": 0.6, "host": "172.16.1.128", "memory_usage_percent": 14.2, "name": "GNS3 VM (GNS3 VM)", "port": 3080, "protocol": "http", "user": null}} < {"action": "compute.updated", "event": {"capabilities": {"node_types": ["cloud", "ethernet_hub", "ethernet_switch", "nat", "vpcs", "virtualbox", "dynamips", "frame_relay_switch", "atm_switch", "qemu", "vmware", "docker", "iou"], "platform": "linux", "version": "2.1.4dev1"}, "compute_id": "local", "connected": true, "cpu_usage_percent": 10.9, "host": "172.16.1.1", "memory_usage_percent": 75.2, "name": "coruscant", "port": 3080, "protocol": "http", "user": "QDTAzWtEKgKlXwmy3Qglkmw71h5XQ5zzSKkBKxFfPvcgGVtjKliJFNaFp7FOijBq"}}

Let me know if you get anything.

Thanks!

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/GNS3/gns3-gui/issues/2374#issuecomment-362989342, or mute the thread https://github.com/notifications/unsubscribe-auth/ATkVmoGnU7oJtoN62PAewxm52vsBhurrks5tRpjggaJpZM4RLYjS .

[grossmj]

Noted, an upgrade to PyQt 5.10 fixed the issue for you.

Thanks!