-
Bug
-
Resolution: Unresolved
-
Major
-
rhel-9.4.z
-
frr-8.5.3-4.el9_4.3
-
No
-
Important
-
ZStream
-
rhel-sst-cs-net-perf-services
-
ssg_core_services
-
3
-
False
-
-
None
-
None
-
Pass
-
RegressionOnly
-
Unspecified
-
Unspecified
-
Unspecified
-
None
What were you trying to do that didn't work?
Configuring FRR with `log stdout` and starting it as a daemon, using `/usr/libexec/frr/frrinit.sh start` does not work properly because when frr is started as a daemon, it is unable to write logs to stdout.
This was fixed here:
[1] https://github.com/FRRouting/frr/pull/12050/commits/4d28aea95851dc14b3987b004f457d7a4a1535f8
What is the impact of this issue to you?
In RHOSO (Openstack), we need FRR to write logs on stdout because that's the way the container where it runs will write those logs to journal.
Please provide the package NVR for which the bug is seen:
rhel9.4 with frr-8.5.3-4.el9.x86_64
How reproducible is this bug?:
100%
Steps to reproduce
- add `log stdout` to frr.conf
- start frr with `/usr/libexec/frr/frrinit.sh start`
Expected results
frr logs are written to stdout
Actual results
frr logs can't be seen in stdout
- is depended on by
-
OSPRH-10204 frr should log to journal
-
- Review
-
- links to
-
RHBA-2025:147954 frr update
- mentioned on