Project

General

Profile

Bug #1213

After upgrade from 5.3.3 to 5.3.4 only one connection is possible, charon: 00[DMN] waiting for signal failed: Interrupted system call

Added by Michael Stiller over 3 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Category:
charon
Target version:
Start date:
20.11.2015
Due date:
Estimated time:
Affected version:
5.3.4
Resolution:
Fixed

Description

Just upgraded from 5.3.3 where everything was working to 5.3.4. Now after one connection (which is successful) no other connections are possible.
Noticed this log line which only appears using 5.3.4:

Nov 20 08:19:20 ip-172-31-20-201 charon: 00[DMN] waiting for signal failed: Interrupted system call

ipsec statusall shows no output after the successful connection, if you try to reinitiate a connection with ipsec up conn it exits with exitcode 7.
The config was not changed after upgrade. Packages were build on Ubuntu 14.04.3 LTS exactly the same way as 5.3.3 which works.
Installed packages are:

ii  libstrongswan                        5.3.4-0-2scale                       amd64        strongSwan utility and crypto library
ii  strongswan                           5.3.4-0-2scale                       all          IPsec VPN solution metapackage
ii  strongswan-ike                       5.3.4-0-2scale                       amd64        strongSwan Internet Key Exchange (v2) daemon
ii  strongswan-plugin-eap-radius         5.3.4-0-2scale                       amd64        strongSwan plugin for EAP interface to a RADIUS server
ii  strongswan-plugin-openssl            5.3.4-0-2scale                       amd64        strongSwan plugin for OpenSSL
ii  strongswan-plugin-xauth-generic      5.3.4-0-2scale                       amd64        strongSwan plugin for the generic XAuth backend
ii  strongswan-starter                   5.3.4-0-2scale                       amd64        strongSwan daemon starter and configuration file parser

Running kernel version is 3.13.0-66-generic, version was build on this machine.
Config was not changed between 5.3.3 and 5.3.4, no differences in /etc/strongswan.d/. The only thing which is configured in /etc/strongswan.d/charon is eap-radius.conf.

statusall.txt (1.69 KB) statusall.txt Michael Stiller, 20.11.2015 10:20
charon.conf (7.52 KB) charon.conf Michael Stiller, 20.11.2015 10:20
ipsec.conf (760 Bytes) ipsec.conf Michael Stiller, 20.11.2015 10:20
strongswan.conf (281 Bytes) strongswan.conf Michael Stiller, 20.11.2015 10:20

Associated revisions

Revision 88b85e02 (diff)
Added by Tobias Brunner over 3 years ago

sigwaitinfo() may fail with EINTR if interrupted by an unblocked signal not in the set

Fixes #1213.

History

#1 Updated by Tobias Brunner over 3 years ago

  • Tracker changed from Issue to Bug
  • Status changed from New to Feedback
  • Target version set to 5.3.5

Yes, noticed this too yesterday. Has been addressed with the patch in the 1213-sigwaitinfo-eintr branch.

#2 Updated by Tobias Brunner over 3 years ago

  • Description updated (diff)
  • Category set to charon
  • Assignee set to Tobias Brunner
  • Resolution set to Fixed

I've merged the fix to master.

#3 Updated by Tobias Brunner over 3 years ago

  • Status changed from Feedback to Closed

Also available in: Atom PDF