Description of problem: iked will not run, making it impossible to use Shrew VPN client. Version-Release number of selected component (if applicable): ike-2.1.7-9.fc18.x86_64 How reproducible: It can be reproduced every time Steps to Reproduce: 1. Use systemctl to start the service: systemctl start iked.service Actual results: [root@laptop]# systemctl status iked.service iked.service - Shrew VPN Client Iked Loaded: loaded (/usr/lib/systemd/system/iked.service; disabled) Active: inactive (dead) Jan 27 09:19:49 laptop systemd[1]: Starting Shrew VPN Client Iked... Jan 27 09:19:49 laptop systemd[1]: Started Shrew VPN Client Iked. Expected results: I expect iked to run so it can be used by ikea Additional info: If I try to start the service often enough, it will occasionally cause the kernel to panic, requiring a reboot. I just installed kernel-3.7.4-204.fc18.x86_64 and have not verified if this kernel crashes as well. The iked service worked in Fedora 17, before I upgraded to Fedora 18, with the following packages: - kernel-3.6.11-1.fc17.x86_64 - ike-2.1.7-8.fc17.x86_64
I just verified that if I start iked manually, instead of using systemctl, it runs without any problems. [root@laptop]# /usr/bin/iked --config /etc/iked.conf
I will investigate.
Just wanted to confirm all points from Juan's description. Same here with 3.7.4-204.fc18.x86_64.
i know the cause there should be Type=forking iirc Type is a requirement.
Marcel's absolutely right. I made the changes and it worked. [root@laptop system]# pwd /usr/lib/systemd/system [root@laptop system]# diff -u iked.service.original iked.service --- iked.service.original 2013-02-21 20:43:21.674168807 -0500 +++ iked.service 2013-02-21 20:43:24.050185003 -0500 @@ -3,6 +3,7 @@ After=local-fs.target network.target [Service] +Type=forking ExecStart=/usr/sbin/iked --config /etc/iked.conf [Install]
this package is still not fixed. i would be willing to take co-maintainership for it if the current maintainer is too busy. if however the maintainer is unresponsive i will just follow this protocol: http://fedoraproject.org/wiki/Policy_for_nonresponsive_package_maintainers
No problem, please request co-maintainership i will approve it, do not have time to work on this at the moment.
added myself to the package as described here: https://fedoraproject.org/wiki/Policy_for_encouraging_comaintainers_of_packages?rd=PackageMaintainers/Policy/EncourageComaintainership#Procedure
ike-2.1.7-11.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ike-2.1.7-11.fc18
ike-2.1.7-11.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ike-2.1.7-11.fc19
Package ike-2.1.7-11.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing ike-2.1.7-11.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6377/ike-2.1.7-11.fc19 then log in and leave karma (feedback).
Works for me - update fixes the issue.
ike-2.2.0-4.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/ike-2.2.0-4.fc19
ike-2.2.0-4.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/ike-2.2.0-4.fc18
ike-2.2.0-4.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.