GNS3 Error after upgrading to Linux Mint 19

[jajao555]

I did a clean install of Linux Mint 19 and when I installed GNS3 following the directions for Ubuntu I get this error when trying to add stock Ethernet switches or add Dynamips nodes. I'm able to add a VPCS nodes fine.

Error while creating node: Couldn't connect to hypervisor on 127.0.0.1:58481 :[Errno 111] Connect call failed ('127.0.0.1', 58481)

I've tried reinstalling and also making sure to add the suggested and recommended dependencies and still have the same issue.

On a side note the first install didn't point to Dynamips in /usr/bin/ and was blank and I had to browse to the file. The second install it was added already possibly because of the other dependencies I installed?

[eightyfour]

You ever figure this out I'm having the same problem.

I noticed when you run gns3 as root it works fine.

edit: solved you must install latest dynamips from github.

[rustyjarz]

I've got a problem when trying to do the initial configuration where I get the below.

I also did a GNS3 Doctor and that give me an error saying

:~$ sudo usermod -aG ubridge username
[sudo] password for:
usermod: group 'ubridge' does not exist
:~$

GNS3 management console.
Running GNS3 version 2.1.21 on Linux (64-bit) with Python 3.6.8 Qt 5.9.5 and PyQt 5.10.1.
Copyright (c) 2006-2019 GNS3 Technologies.
Use Help -> GNS3 Doctor to detect common issues.

=> Send stats to Google Analytics: v=1&tid=UA-55817127-3&cid=7c1a1596-d4ba-4e9d-8b38-022bd75840aa&aip=1&t=screenview&an=GNS3&av=2.1.21&ua=Mozilla/5.0%20%28X11%3B%20Linux%20x86_64%29%20AppleWebKit/537.36%20%28KHTML%2C%20like%20Gecko%29%20Safari/537.36%20%20GNS3/2.1.21&cd=Main%20Window&ds=gns3-gui&sr=1920x1080&ul=en_au
Send stats to Google Analytics: v=1&tid=UA-55817127-3&cid=7c1a1596-d4ba-4e9d-8b38-022bd75840aa&aip=1&t=screenview&an=GNS3&av=2.1.21&ua=Mozilla/5.0%20%28X11%3B%20Linux%20x86_64%29%20AppleWebKit/537.36%20%28KHTML%2C%20like%20Gecko%29%20Safari/537.36%20%20GNS3/2.1.21&cd=Setup%20Wizard&ds=gns3-gui&sr=1920x1080&ul=en_au
Type conversion already registered from type QSharedPointer to type QObject*
GET http://127.0.0.1:8010/v2/version
Error while connecting to local server Connection refused
GET http://127.0.0.1:8010/v2/version
Error while connecting to local server Connection refused
GET http://127.0.0.1:8010/v2/version
Error while connecting to local server Connection refused
Starting local server process with "/usr/share/gns3/gns3-gui/bin/gns3" --local --debug --log="/home/rustyjarz/.config/GNS3/gns3_server.log" --pid="/home/rustyjarz/.config/GNS3/gns3_server.pid"
Local server process has started (PID=21464)
Set worker inside a thread <class 'gns3.utils.wait_for_connection_worker.WaitForConnectionWorker'>
WaitForConnectionWorker thread started
Local server process has stopped
usage: gns3 [-h] [--version] [--debug] [-q] [--config CONFIG]
[--profile PROFILE]
[path]
gns3: error: unrecognized arguments: --local --log=/home/rustyjarz/.config/GNS3/gns3_server.log --pid=/home/rustyjarz/.config/GNS3/gns3_server.pid

WaitForConnectionWorker thread stopping with an error: Could not connect to 127.0.0.1 on port 8010: [Errno 111] Connection refused
WaitForConnectionWorker thread canceled
WaitForConnectionWorker thread is being destroyed
WaitForConnectionWorker thread destroyed
Could not connect to 127.0.0.1 on port 8010: [Errno 111] Connection refused
Stack (most recent call last):
File "/usr/share/gns3/gns3-gui/bin/gns3", line 11, in
load_entry_point('gns3-gui==2.1.21', 'gui_scripts', 'gns3')()
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/main.py", line 297, in main
exit_code = app.exec_()
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/main_window.py", line 1178, in startupLoading
self._setupWizardActionSlot()
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/main_window.py", line 909, in _setupWizardActionSlot
res = setup_wizard.exec_()
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/dialogs/setup_wizard.py", line 326, in validateCurrentPage
LocalServer.instance().localServerAutoStartIfRequire()
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/local_server.py", line 357, in localServerAutoStartIfRequire
if not progress_dialog.exec_():
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/qt/__init__.py", line 272, in func_wrapper
return func(*args, **kwargs)
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/utils/progress_dialog.py", line 183, in _error
QtWidgets.QMessageBox.critical(self.parentWidget(), "Error", "{}".format(message))
File "/usr/share/gns3/gns3-gui/lib/python3.6/site-packages/gns3/qt/__init__.py", line 121, in critical
LogQMessageBox._get_logger().critical(re.sub(r"<[^<]+?>", "", message), stack_info=LogQMessageBox.stack_info())
Section MainWindow has not changed. Skip saving configuration
GET http://127.0.0.1:8010/v2/version
Error while connecting to local server Connection refused
GET http://127.0.0.1:8010/v2/version
Error while connecting to local server Connection refused
GET http://127.0.0.1:8010/v2/version
Error while connecting to local server Connection refused
Starting local server process with "/usr/share/gns3/gns3-gui/bin/gns3" --local --debug --log="/home/rustyjarz/.config/GNS3/gns3_server.log" --pid="/home/rustyjarz/.config/GNS3/gns3_server.pid"
Local server process has started (PID=22610)
Set worker inside a thread <class 'gns3.utils.wait_for_connection_worker.WaitForConnectionWorker'>
WaitForConnectionWorker thread started
WaitForConnectionWorker thread canceled
WaitForConnectionWorker thread is being destroyed
WaitForConnectionWorker thread destroyed
Local server process has stopped
usage: gns3 [-h] [--version] [--debug] [-q] [--config CONFIG]
[--profile PROFILE]
[path]
gns3: error: unrecognized arguments: --local --log=/home/rustyjarz/.config/GNS3/gns3_server.log --pid=/home/rustyjarz/.config/GNS3/gns3_server.pid



Operating System: Linux Mint Tina
GNS3 Software Version: 2.1.21



:~$ sudo usermod -aG ubridge username
[sudo] password for:
usermod: group 'ubridge' does not exist
:~$

[jajao555]

Sorry I never did figure this out. I went back to 18.3 and haven't had any issues.