| Summary: | conntrack -d fails to start | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | colin <bugzilla.redhat.com> | ||||
| Component: | conntrack-tools | Assignee: | Paul P Komkoff Jr <i> | ||||
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 23 | CC: | bperkins, bugzilla.redhat.com, i, pwouters, twoerner | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2016-12-19 21:27:12 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: | |||||
| Attachments: |
|
||||||
|
Description
colin
2016-04-05 20:22:32 UTC
why did you not start the service using "systemctl start conntrackd" ? that starts: conntrackd -C /etc/conntrackd/conntrackd.conf It also runs an ExecPreStart= that resolves a bug when the lockfile already exists. Still, this works for me? paul@bofh:~ $ sudo /usr/sbin/conntrackd -d paul@bofh:~ $ pidof conntrackd 10138 [root@k8 admin]# systemctl start conntrackd.service [root@k8 admin]# systemctl status -l conntrackd.service ● conntrackd.service - connection tracking daemon for debugging and High Availablity Loaded: loaded (/usr/lib/systemd/system/conntrackd.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2016-04-20 10:55:30 BST; 4s ago Process: 4714 ExecStart=/usr/sbin/conntrackd -C /etc/conntrackd/conntrackd.conf (code=exited, status=1/FAILURE) Main PID: 4714 (code=exited, status=1/FAILURE) Apr 20 10:55:30 k8.localdomain systemd[1]: Started connection tracking daemon for debugging and High Availablity. Apr 20 10:55:30 k8.localdomain systemd[1]: Starting connection tracking daemon for debugging and High Availablity... Apr 20 10:55:30 k8.localdomain conntrackd[4714]: WARNING: eth2 is an invalid interface Apr 20 10:55:30 k8.localdomain conntrackd[4714]: ERROR: conntrackd cannot start, please check the logfile for more info Apr 20 10:55:30 k8.localdomain systemd[1]: conntrackd.service: Main process exited, code=exited, status=1/FAILURE Apr 20 10:55:30 k8.localdomain systemd[1]: conntrackd.service: Unit entered failed state. Apr 20 10:55:30 k8.localdomain systemd[1]: conntrackd.service: Failed with result 'exit-code'. To improve readability, I will attach separately: [root@k8 admin]# journalctl -xe Created attachment 1148988 [details]
[root@k8 admin]# journalctl -xe
excert from system log showing
systemd fails to start conntrackd.
Just to re-iterate:
no eth2 exists on this machine.
[root@k8 admin]# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:24:1d:c0:f7:e6 brd ff:ff:ff:ff:ff:ff
3: enp4s7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 00:1c:f0:6e:c9:bf brd ff:ff:ff:ff:ff:ff
4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default qlen 1000
link/ether 52:54:00:06:55:04 brd ff:ff:ff:ff:ff:ff
5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc noqueue master virbr0 state DOWN mode DEFAULT group default qlen 500
link/ether 52:54:00:06:55:04 brd ff:ff:ff:ff:ff:ff
[root@k8 admin]#
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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. conntrack cannot work without proper configuration. You must configure it before attemping to start it. Just yum install plus service start will not work WONTFIX would seem more appropriate. Happily this NOTABUG is no longer exhibited on this very same machine, now upgraded to Fedora 24 . |