Bug 2192228 - lldpd won't start: unable to create control socket at /runlldpd/lldpd.socket
Summary: lldpd won't start: unable to create control socket at /runlldpd/lldpd.socket
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: lldpd
Version: 37
Hardware: Unspecified
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Aaron Conole
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-30 16:53 UTC by Sam Morris
Modified: 2023-05-11 01:56 UTC (History)
1 user (show)

Fixed In Version: lldpd-1.0.16-2.fc36 lldpd-1.0.16-2.fc37 lldpd-1.0.16-2.fc38
Clone Of:
Environment:
Last Closed: 2023-05-11 01:30:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Sam Morris 2023-04-30 16:53:45 UTC
lldpd won't start, giving this message:

Apr 30 17:42:33 lldpd[513415]: unable to create control socket at /runlldpd/lldpd.socket: Read-only file system

The RPM ships a directory /runlldpd:

$ rpm -qf /runlldpd/chroot
lldpd-1.0.16-1.fc37.x86_64

I guess this is a typo in the .spec file, the correct path is /run/lldpd.

This was introduced with lldpd-1.0.16-1.fc37. Downgrading to lldpd-1.0.4-10.fc37.x86_64 fixes the problem.

Reproducible: Always

Steps to Reproduce:
1. Install lldpd
2. Start lldpd.service
3. View logs with journalctl -u lldpd -e
Actual Results:  
lldpd not running

Expected Results:  
lldpd should run

Comment 1 Fedora Update System 2023-05-02 20:47:58 UTC
FEDORA-2023-c9a3103c65 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c9a3103c65

Comment 2 Fedora Update System 2023-05-02 20:48:00 UTC
FEDORA-2023-ecc18ce3f4 has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ecc18ce3f4

Comment 3 Fedora Update System 2023-05-02 20:48:03 UTC
FEDORA-2023-ed96524ef2 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed96524ef2

Comment 4 Fedora Update System 2023-05-03 01:24:05 UTC
FEDORA-2023-c9a3103c65 has been pushed to the Fedora 38 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-c9a3103c65`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-c9a3103c65

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2023-05-03 01:29:01 UTC
FEDORA-2023-ed96524ef2 has been pushed to the Fedora 37 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-ed96524ef2`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ed96524ef2

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2023-05-03 01:33:50 UTC
FEDORA-2023-ecc18ce3f4 has been pushed to the Fedora 36 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-ecc18ce3f4`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-ecc18ce3f4

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2023-05-11 01:30:44 UTC
FEDORA-2023-ecc18ce3f4 has been pushed to the Fedora 36 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2023-05-11 01:53:01 UTC
FEDORA-2023-ed96524ef2 has been pushed to the Fedora 37 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2023-05-11 01:56:34 UTC
FEDORA-2023-c9a3103c65 has been pushed to the Fedora 38 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.