Bug 1654285

Summary: Can not start strongswan-swanctl.service.
Product: [Fedora] Fedora Reporter: idcm
Component: strongswanAssignee: Pavel Šimerda <code>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 29CC: code, mikhail.zabaluev
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-27 23:20:50 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:

Description idcm 2018-11-28 12:01:59 UTC 
Description of problem:
When I run "systemctl start strongswan-swanctl.service" show error:
"Job for strongswan-swanctl.service failed because the control process exited with error code. 
See "systemctl status strongswan-swanctl.service" and "journalctl -xe" for details"
The status:
############################################
● strongswan-swanctl.service - strongSwan IPsec IKEv1/IKEv2 daemon using swanctl
   Loaded: loaded (/usr/lib/systemd/system/strongswan-swanctl.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Wed 2018-11-28 06:35:05 EST; 10min ago
  Process: 1363 ExecStartPost=/usr/sbin/swanctl --load-all --noprompt (code=exited, status=64)
  Process: 1346 ExecStart=/usr/sbin/charon-systemd (code=exited, status=0/SUCCESS)
 Main PID: 1346 (code=exited, status=0/SUCCESS)
   Status: "charon-systemd running, strongSwan 5.7.1, Linux 4.19.4-300.fc29.x86_64, x86_64"

Nov 28 06:35:05 144.202.4.66.vultr.com charon-systemd[1346]: HA config misses local/remote address
Nov 28 06:35:05 144.202.4.66.vultr.com charon-systemd[1346]: no script for ext-auth script defined, disabled
Nov 28 06:35:05 144.202.4.66.vultr.com charon-systemd[1346]: loaded plugins: charon-systemd pkcs11 tpm aesni aes des rc2 sha2 s>Nov 28 06:35:05 144.202.4.66.vultr.com charon-systemd[1346]: spawning 16 worker threads
Nov 28 06:35:05 144.202.4.66.vultr.com swanctl[1363]: no files found matching '/etc/strongswan/strongswan.conf'
Nov 28 06:35:05 144.202.4.66.vultr.com swanctl[1363]: abort initialization due to invalid configuration
Nov 28 06:35:05 144.202.4.66.vultr.com systemd[1]: strongswan-swanctl.service: Control process exited, code=exited status=64
Nov 28 06:35:05 144.202.4.66.vultr.com charon-systemd[1346]: SIGTERM received, shutting down
Nov 28 06:35:05 144.202.4.66.vultr.com systemd[1]: strongswan-swanctl.service: Failed with result 'exit-code'.
Nov 28 06:35:05 144.202.4.66.vultr.com systemd[1]: Failed to start strongSwan IPsec IKEv1/IKEv2 daemon using swanctl.

############################################


Version-Release number of selected component (if applicable):
strongSwan 5.7.1, 
Linux 4.19.4-300.fc29.x86_64

How reproducible:
run "systemctl start strongswan-swanctl.service"

Steps to Reproduce:
1.dnf update -y
2.dnf install strongswan
3.systemctl start strongswan-swanctl.service

Actual results:
Show error information 

Expected results:
strongswan-swanctl run with no error

Additional info:
when I close selinux, it works, no more error shows, swanctl runs as expected. But I do not want selinux disabled.
Comment 1 Ben Cotton 2019-10-31 18:53:24 UTC 
This message is a reminder that Fedora 29 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '29'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 29 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 2 Ben Cotton 2019-11-27 23:20:50 UTC 
Fedora 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.
Comment 3 Mikhail Zabaluev 2019-11-28 06:55:20 UTC 

*** This bug has been marked as a duplicate of bug 1773381 ***