New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ConnectionError: Socket error during eAPI connection: The read operation timed out #184
Comments
Federico, going to take a look at this issue. |
Sure! Which part of config? management API? |
Running config would be a preferred option |
andrii@arista.com to keep it private :) |
Sent. :) |
Napalm playbook worked with no issue until I enabled authorisation via TACACS+. In my lab, in order to validate your configuration ansible spent 3 min 55 sec. On the other hand, initial spin (w/o TACACS+) of your playbook executes in 23sec - I guess you might look into the options of either having local user just for napalm or disable authorisation for specific command type/users (if possible, although I didn't do a research on this one yet). |
Please, note that this BUG s related to: napalm-automation/napalm-ansible#165 (comment)
I am using NAPALM to perform config-replace on
Arista DCS-7060SX2-48YC6-R
version4.21.8M-13902577.4218M
.withpyeapi==0.8.3
The session times out no matter what timeout I configure, either http and https. I can use the library ok for other things like send commands.I can see the HTTP session up and the configure session created, however no packets are sent/received and configure session remains in
pending
The text was updated successfully, but these errors were encountered: