Bug 1229766
| Summary: | Pluto crashes after stop when I use floating ip address | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Jaroslav Aster <jaster> | ||||||
| Component: | libreswan | Assignee: | Paul Wouters <pwouters> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Jaroslav Aster <jaster> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 7.2 | CC: | jaster, jkurik, jreznik, lmiksik, omoris, tmraz | ||||||
| Target Milestone: | rc | Keywords: | ZStream | ||||||
| Target Release: | --- | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||
| Doc Text: |
Cause: An IP address moves from behind the remote endpoint to be configured locally.
Consequence: pluto IKE daemon would get confused and crash and restart
Fix: re-orient the connection properly
Result: no more crash.
|
Story Points: | --- | ||||||
| Clone Of: | |||||||||
| : | 1230141 1268776 (view as bug list) | Environment: | |||||||
| Last Closed: | 2016-11-03 21:21:16 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: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1268776, 1661286 | ||||||||
| Attachments: |
|
||||||||
|
Description
Jaroslav Aster
2015-06-09 15:14:16 UTC
Created attachment 1036876 [details]
initiator pluto.log
Created attachment 1036877 [details]
responder pluto.log
Hi Paul, last build 3.15-5.el7_1 fails. There is segfault message in journal and /var/log/messages after ipsec is stopped. Oct 22 15:23:14 HOSTNAME kernel: pluto[13053]: segfault at 0 ip 00007f10c0b98ef9 sp 00007ffed2ea2e20 error 4 in pluto[7f10c0b33000+1] can you get me a stack trace? We never saw this in our tests Hi Paul, I'm afraid not. No coredump was created and I have not been able to persuade the system to create one. I have only this log message (and reproducer). 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-2016-2603.html |