Bug 2329450 - Kea unable to write to log files
Summary: Kea unable to write to log files
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kea
Version: 41
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Petr Dancak
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-11-29 08:37 UTC by Marek Greško
Modified: 2025-03-15 00:25 UTC (History)
5 users (show)

Fixed In Version: kea-2.6.1-5.fc41 kea-2.6.1-7.fc42
Clone Of:
Environment:
Last Closed: 2025-02-17 14:34:25 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Marek Greško 2024-11-29 08:37:03 UTC
Since Fedora 41 runs as kea user. Since that change it is not possible to wite to /var/log/kea* files.

I placed a workaround to create /var/log/kea directory owned by kea and reconfigured the kea to place the log files into that directory.

If this would be considered as a final solution, please, do not forget to configure logrotate for the new log files.

Reproducible: Always

Comment 1 Petr Dancak 2025-01-14 16:07:40 UTC
I have managed to reproduce the issue. When "keactrl start" is called under user root the logging works fine, but when the kea-*.service is started it uses kea user, which can't log into the /var/log/. When the dir /var/log/kea is created, owner of dir is changed to the kea and default logging is set to the /var/log/kea then the logging works fine.

Comment 2 Petr Dancak 2025-01-16 11:51:18 UTC
After deeper investigation I am not sure if this is the problem you have. I have used keactrl start under root user and it created files under root, so owner is root. With that the user kea can't change the content of the log files. Can you be more specific about the command you used, version of kea, the problem you have and what you expect?

Comment 3 Marek Greško 2025-01-16 18:27:56 UTC
Hello,

yes, you identified it correctly. I used systemctl enable kea-dhcp4.service and systemctl kea-dhcp6.service. Thus the kea runs under user kea.

Marek

Comment 5 Fedora Update System 2025-02-18 15:47:41 UTC
FEDORA-2025-2ff5c93709 (kea-2.6.1-7.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-2ff5c93709

Comment 6 Fedora Update System 2025-02-19 03:28:56 UTC
FEDORA-2025-2ff5c93709 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-2ff5c93709`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2ff5c93709

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

Comment 7 Fedora Update System 2025-02-24 07:22:54 UTC
FEDORA-2025-87d2d63dab (kea-2.6.1-5.fc41) has been submitted as an update to Fedora 41.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-87d2d63dab

Comment 8 Fedora Update System 2025-02-25 01:41:56 UTC
FEDORA-2025-87d2d63dab has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-87d2d63dab`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-87d2d63dab

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

Comment 9 Fedora Update System 2025-03-05 01:14:24 UTC
FEDORA-2025-87d2d63dab (kea-2.6.1-5.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 Fedora Update System 2025-03-15 00:25:20 UTC
FEDORA-2025-2ff5c93709 (kea-2.6.1-7.fc42) has been pushed to the Fedora 42 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.