Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Fresh installation not working any with nos BIRD
See original GitHub issueBug Description
When I set up a new hyper glass instance I not able to setup a device using nos bird. I have used a configuration that was working before but I had to setup a new machine. I am running hyperglass as a system user and I am using a virtualenv. Installation is working fine, I can see the web GUI but when I try to submit a query I am getting “Something went wrong message” after 1 second. On the console I can see that there should be connection attempt “[INFO] 20220225 14:44:40 | scrapli.driver.base.base_driver:897 | _pre_open_closing_log → opening connection to ‘127.0.0.1’ on port ‘22’” but I do not recognize the attempt anywhere. Even tcpdump on loopback interface is not showing any incoming packets. BIRD is running on the same host, so loopback should be fine, but also the address from NIC is not working.
Expected behavior
At least a connection attempt to the server should be seen.
Steps to Reproduce
Install according to the documentation, pip3 install hyperglass should be done in an virtualenv
Local Configurations
devices.yaml
routers:
- name: New York City, NY
address: 127.0.0.1
network:
name: production
display_name: AS65000
credential:
username: hyperglass
password: hyper
port: 22
nos: bird
vrfs:
- name: global
default: true
ipv4:
source_address: 192.168.42.194
ipv6: null
hyperglass.yaml
debug: false
developer_mode: false
org_name: Beloved Hyperglass User
site_title: hyperglass
site_description: "{org_name} Network Looking Glass"
site_keywords: [hyperglass, looking glass, routing, bgp]
request_timeout: 30
listen_address: "0.0.0.0"
listen_port: 8001
Logs
The error message on the console is being seen after the timeout. The error message in the web GUI just pops up after one second.
[INFO] 20220225 14:44:40 | scrapli.driver.base.base_driver:897 | _pre_open_closing_log → opening connection to '127.0.0.1' on port '22'
[CRITICAL] 20220225 14:45:09 | hyperglass.exceptions:40 | __init__ → [DANGER] Error connecting to New York City, NY: Request timed out.
Exception in callback Loop._read_from_self
handle: <Handle Loop._read_from_self>
Traceback (most recent call last):
File "uvloop/cbhandles.pyx", line 73, in uvloop.loop.Handle._run
File "uvloop/loop.pyx", line 359, in uvloop.loop.Loop._read_from_self
File "uvloop/loop.pyx", line 364, in uvloop.loop.Loop._invoke_signals
File "uvloop/loop.pyx", line 339, in uvloop.loop.Loop._ceval_process_signals
File "/home/hyperglass/testing/lib/python3.9/site-packages/hyperglass/execution/main.py", line 39, in handler
raise DeviceTimeout(**exc_args)
hyperglass.exceptions.DeviceTimeout: Error connecting to New York City, NY: Request timed out.
I have tested fresh CentOS7 and fresh Debian Bullseye. Both show the same behavior.
Issue Analytics
- State:
- Created 2 years ago
- Comments:6
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Seems I have found the issue. If you install hyperglass currently it will install asyncssh 2.9.0. This seems not to work in this case. I have tried “pip3 remove asyncssh” and “pip3 install -Iv asyncssh==2.7.0” and with this version it is working again.
downgrade works for password authentication, private key does not work with asyncssh v2.7.0:
error message