Bug 1271973
| Summary: | no more vpn dialog after previous canceling | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Vladimir Benes <vbenes> |
| Component: | NetworkManager-libreswan | Assignee: | Lubomir Rintel <lrintel> |
| Status: | CLOSED ERRATA | QA Contact: | Desktop QE <desktop-qa-list> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 7.2 | CC: | lmiksik, lrintel, rkhan |
| Target Milestone: | rc | Keywords: | Regression |
| Target Release: | 7.2 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | NetworkManager-libreswan-1.0.6-3.el7 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-11-19 11:06:21 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Attachments: | |||
|
Description
Vladimir Benes
2015-10-15 08:14:15 UTC
Created attachment 1083164 [details]
NetworkManager's log
I can't reproduce this one. Seems like the nm-libreswan-service is stuck somehow and doesn't respond. I'm wondering if you could check if it's really running and check what blocks it (attach gdb and get a traceback or maybe just strace it to see if it is caught in a loop)? (In reply to Lubomir Rintel from comment #2) > I can't reproduce this one. Seems like the nm-libreswan-service is stuck > somehow and doesn't respond. > We've reproduced together. You just need to connect, write in incorrect password and then when second dialog appears press cancel button. > I'm wondering if you could check if it's really running and check what > blocks it (attach gdb and get a traceback or maybe just strace it to see if > it is caught in a loop)? Created attachment 1085201 [details] [nm-libreswan 1/3] Early fail race fix Brew build: https://brewweb.devel.redhat.com/taskinfo?taskID=9991436 Lubo, it's slightly better as I can see another dialog after unsuccessful connection but that dialog doesn't work anymore with these errors: Oct 22 09:52:08 trautenberg NetworkManager[927]: <info> VPN plugin state changed: starting (3) Oct 22 09:52:08 trautenberg NetworkManager[927]: <info> VPN connection 'redhat' (ConnectInteractive) reply received. Oct 22 09:52:08 trautenberg NetworkManager[927]: <warn> VPN connection 'redhat' failed to connect interactively: 'Already connecting!'. Oct 22 09:52:08 trautenberg NetworkManager[927]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. Oct 22 09:52:14 trautenberg NetworkManager[927]: <info> VPN plugin state changed: starting (3) Oct 22 09:52:14 trautenberg NetworkManager[927]: <info> VPN connection 'redhat' (ConnectInteractive) reply received. Oct 22 09:52:14 trautenberg NetworkManager[927]: <warn> VPN connection 'redhat' failed to connect interactively: 'Already connecting!'. Oct 22 09:52:14 trautenberg NetworkManager[927]: <warn> error disconnecting VPN: Could not process the request because no VPN connection was active. whole log attached (3 incorrect attempts + new opening and 2 immediate failures) Created attachment 1085437 [details]
full log
and whatmore it's eating a lot of CPU: PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 3554 root 20 0 262752 3804 3012 R 100.0 0.0 0:56.65 nm-libreswan-se it sits there for 3 minutes and then goes away. I can reconnect after it's gone. Created attachment 1085489 [details]
[nm-libreswan 2/3] Fix for 100% cpu load on disconnect
Created attachment 1085491 [details]
[nm-libreswan 3/3] Fix reconnecting after a failure
Created attachment 1085494 [details]
[nm] Avoid disconnecting connection following an unsuccessful connection attempt
https://brewweb.devel.redhat.com/taskinfo?taskID=9998325 https://brewweb.devel.redhat.com/taskinfo?taskID=9998015 All patches LGTM. Didn't test though. nm-1-0: 26094b7 service: always tear down the connection on helper failure f516f6b service: watch for pty master hangups 636b2a5 service: don't delete connection while it's being upped master: 50fc66b service: always tear down the connection on helper failure 984035d service: watch for pty master hangups f58fde3 service: don't delete connection while it's being upped this works well with current libreswan and NM package. Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-2315.html |