can't console to device running QEMU nodes after upgraded to v2.0.3-95

Before posting something, READ the changelog, WATCH the videos, howto and provide following:
Your install is: Bare metal, ESXi, what CPU model, RAM, HD, what EVE version you have, output of the uname -a and any other info that might help us faster.

Moderator: mike

Post Reply
jchan
Posts: 15
Joined: Sat Aug 12, 2017 3:22 pm

can't console to device running QEMU nodes after upgraded to v2.0.3-95

Post by jchan » Mon Jan 07, 2019 1:35 am

Hi -

After upgraded to community edition v2.0.3-95, i can start CSR1kv (Denali and Everest) but can't console to it. Can someone help please?

I did further testing, it looks like i can start but can't console to any device running QEMU nodes such as CSRv, ASAv

Thanks
Last edited by jchan on Mon Jan 07, 2019 3:30 pm, edited 1 time in total.

Uldis (UD)
Posts: 5080
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: can't console to CSR1kv after upgraded to v2.0.3-95

Post by Uldis (UD) » Mon Jan 07, 2019 9:03 am

usually after any major upgrade need clean up browser cache and cookies

jchan
Posts: 15
Joined: Sat Aug 12, 2017 3:22 pm

Re: can't console to device running QEMU nodes after upgraded to v2.0.3-95

Post by jchan » Mon Jan 07, 2019 3:38 pm

Thanks,

I did clear history and cookies but with no help.

The funny thing is that i can console to other devices with no issue if they are not running QEMU images.

It looks like it only affects devices running QEMU images.

I had already upgraded to v2.0.3-95, Is there a way to reinstall v2.0.3-95 ?

Uldis (UD)
Posts: 5080
Joined: Wed Mar 15, 2017 4:44 pm
Location: London
Contact:

Re: can't console to device running QEMU nodes after upgraded to v2.0.3-95

Post by Uldis (UD) » Mon Jan 07, 2019 6:19 pm

apt install --reinstall eve-ng

Post Reply