Failed to Connect to Server on Google Cloud
Posted: Sun Feb 24, 2019 4:46 pm
I have eve-ng running on Ubuntu 16.04 as a Google Cloud VM instance.
However VNC says failed to connect to server when I try to use Windows/Linux nodes.
ON starting Linux node:
root@final:/opt/unetlab/data/Logs# Feb 24 16:44:16 final ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_0
Feb 24 16:44:16 final ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_0
Feb 24 16:44:16 final kernel: [ 569.908672] pnet1: port 1(vunl0_2_0) entered blocking state
Feb 24 16:44:16 final kernel: [ 569.908676] pnet1: port 1(vunl0_2_0) entered forwarding state
Feb 24 16:44:16 final kernel: [ 569.909164] pnet1: port 1(vunl0_2_0) entered disabled state
Feb 24 16:44:16 final kernel: [ 569.912563] device vunl0_2_0 left promiscuous mode
Feb 24 16:44:16 final kernel: [ 569.912567] pnet1: port 1(vunl0_2_0) entered disabled state
Feb 24 16:44:16 final kernel: [ 569.980674] pnet1: port 1(vunl0_2_0) entered blocking state
Feb 24 16:44:16 final kernel: [ 569.980678] pnet1: port 1(vunl0_2_0) entered disabled state
Feb 24 16:44:16 final kernel: [ 569.980799] device vunl0_2_0 entered promiscuous mode
Feb 24 16:44:16 final kernel: [ 569.980847] pnet1: port 1(vunl0_2_0) entered blocking state
Feb 24 16:44:16 final kernel: [ 569.980849] pnet1: port 1(vunl0_2_0) entered forwarding state
Feb 24 16:44:18 final ntpd[4253]: Listen normally on 19 pnet1 192.168.239.1:123
Feb 24 16:44:18 final ntpd[4253]: Listen normally on 20 pnet1 [fe80::e886:a9ff:fedc:6871%4]:123
Feb 24 16:44:18 final ntpd[4253]: new interface(s) found: waking up resolver
Config:
n1-standard-4 (4 vCPUs, 15 GB memory)
Intel Skylake
Let me know if you need any other information.
However VNC says failed to connect to server when I try to use Windows/Linux nodes.
ON starting Linux node:
root@final:/opt/unetlab/data/Logs# Feb 24 16:44:16 final ovs-vsctl: ovs|00001|vsctl|INFO|Called as ovs-vsctl del-port vunl0_2_0
Feb 24 16:44:16 final ovs-vsctl: ovs|00002|db_ctl_base|ERR|no port named vunl0_2_0
Feb 24 16:44:16 final kernel: [ 569.908672] pnet1: port 1(vunl0_2_0) entered blocking state
Feb 24 16:44:16 final kernel: [ 569.908676] pnet1: port 1(vunl0_2_0) entered forwarding state
Feb 24 16:44:16 final kernel: [ 569.909164] pnet1: port 1(vunl0_2_0) entered disabled state
Feb 24 16:44:16 final kernel: [ 569.912563] device vunl0_2_0 left promiscuous mode
Feb 24 16:44:16 final kernel: [ 569.912567] pnet1: port 1(vunl0_2_0) entered disabled state
Feb 24 16:44:16 final kernel: [ 569.980674] pnet1: port 1(vunl0_2_0) entered blocking state
Feb 24 16:44:16 final kernel: [ 569.980678] pnet1: port 1(vunl0_2_0) entered disabled state
Feb 24 16:44:16 final kernel: [ 569.980799] device vunl0_2_0 entered promiscuous mode
Feb 24 16:44:16 final kernel: [ 569.980847] pnet1: port 1(vunl0_2_0) entered blocking state
Feb 24 16:44:16 final kernel: [ 569.980849] pnet1: port 1(vunl0_2_0) entered forwarding state
Feb 24 16:44:18 final ntpd[4253]: Listen normally on 19 pnet1 192.168.239.1:123
Feb 24 16:44:18 final ntpd[4253]: Listen normally on 20 pnet1 [fe80::e886:a9ff:fedc:6871%4]:123
Feb 24 16:44:18 final ntpd[4253]: new interface(s) found: waking up resolver
Config:
n1-standard-4 (4 vCPUs, 15 GB memory)
Intel Skylake
Let me know if you need any other information.