| 2022-01-17 17:57:57 |
Andreas Hasenack |
bug |
|
|
added bug |
| 2022-01-17 17:58:25 |
Andreas Hasenack |
summary |
syslog lgoging does not work |
syslog logging does not work |
|
| 2022-01-18 12:14:54 |
Lucas Kanashiro |
bug |
|
|
added subscriber Ubuntu Server |
| 2022-05-12 12:46:31 |
Andreas Hasenack |
bug |
|
|
added subscriber Canonical Server Team |
| 2022-05-12 12:46:40 |
Andreas Hasenack |
tags |
|
server-todo |
|
| 2022-05-12 12:46:47 |
Andreas Hasenack |
frr (Ubuntu): status |
New |
Triaged |
|
| 2022-05-12 12:46:50 |
Andreas Hasenack |
frr (Ubuntu): importance |
Undecided |
High |
|
| 2022-05-12 12:47:00 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Jammy |
|
| 2022-05-12 12:47:00 |
Andreas Hasenack |
bug task added |
|
frr (Ubuntu Jammy) |
|
| 2022-05-12 12:47:06 |
Andreas Hasenack |
frr (Ubuntu Jammy): status |
New |
Triaged |
|
| 2022-05-12 12:47:08 |
Andreas Hasenack |
frr (Ubuntu Jammy): importance |
Undecided |
High |
|
| 2022-05-12 12:47:17 |
Andreas Hasenack |
frr (Ubuntu): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2022-05-12 12:47:19 |
Andreas Hasenack |
frr (Ubuntu Jammy): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2022-05-12 13:56:15 |
Simon Déziel |
bug |
|
|
added subscriber Simon Déziel |
| 2022-06-07 18:43:06 |
Andreas Hasenack |
frr (Ubuntu): status |
Triaged |
In Progress |
|
| 2022-06-07 20:05:22 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Focal |
|
| 2022-06-07 20:05:22 |
Andreas Hasenack |
bug task added |
|
frr (Ubuntu Focal) |
|
| 2022-06-07 20:05:22 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Impish |
|
| 2022-06-07 20:05:22 |
Andreas Hasenack |
bug task added |
|
frr (Ubuntu Impish) |
|
| 2022-06-07 20:05:22 |
Andreas Hasenack |
nominated for series |
|
Ubuntu Kinetic |
|
| 2022-06-07 20:05:22 |
Andreas Hasenack |
bug task added |
|
frr (Ubuntu Kinetic) |
|
| 2022-06-07 20:05:41 |
Andreas Hasenack |
frr (Ubuntu Impish): status |
New |
Triaged |
|
| 2022-06-07 20:05:44 |
Andreas Hasenack |
frr (Ubuntu Focal): status |
New |
Triaged |
|
| 2022-06-07 20:05:51 |
Andreas Hasenack |
frr (Ubuntu Impish): importance |
Undecided |
Medium |
|
| 2022-06-07 20:05:53 |
Andreas Hasenack |
frr (Ubuntu Focal): importance |
Undecided |
Medium |
|
| 2022-06-17 12:31:21 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/424952 |
|
| 2022-06-24 15:25:23 |
Launchpad Janitor |
frr (Ubuntu Kinetic): status |
In Progress |
Fix Released |
|
| 2022-07-19 20:38:57 |
Andreas Hasenack |
frr (Ubuntu Impish): status |
Triaged |
Won't Fix |
|
| 2022-07-19 20:39:13 |
Andreas Hasenack |
frr (Ubuntu Jammy): status |
Triaged |
In Progress |
|
| 2022-07-19 20:41:03 |
Andreas Hasenack |
frr (Ubuntu Focal): status |
Triaged |
In Progress |
|
| 2022-07-19 20:41:04 |
Andreas Hasenack |
frr (Ubuntu Focal): assignee |
|
Andreas Hasenack (ahasenack) |
|
| 2022-07-20 14:04:12 |
Andreas Hasenack |
description |
Out of the box, the frr package is set to use syslog for logging:
# cat frr.conf
# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in
# /var/log/frr/frr.log
...
log syslog informational
The packaging creates /var/log/frr owned by frr:
drwxr-x--- 2 frr frr 3 Jan 17 17:43 /var/log/frr
In Ubuntu, rsyslog runs as the unprivileged syslog user, not root (like in debian), which means it cannot write to this logging directory:
Jan 17 17:57:25 j-frr-mir rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2112.0 try https://www.rsyslog.com/e/2433 ] |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Plan]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
* if other testing is appropriate to perform before landing this update,
this should also be described here.
[Where problems could occur]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Out of the box, the frr package is set to use syslog for logging:
# cat frr.conf
# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in
# /var/log/frr/frr.log
...
log syslog informational
The packaging creates /var/log/frr owned by frr:
drwxr-x--- 2 frr frr 3 Jan 17 17:43 /var/log/frr
In Ubuntu, rsyslog runs as the unprivileged syslog user, not root (like in debian), which means it cannot write to this logging directory:
Jan 17 17:57:25 j-frr-mir rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2112.0 try https://www.rsyslog.com/e/2433 ] |
|
| 2022-07-20 14:45:41 |
Andreas Hasenack |
description |
[Impact]
* An explanation of the effects of the bug on users and
* justification for backporting the fix to the stable release.
* In addition, it is helpful, but not required, to include an
explanation of how the upload fixes this bug.
[Test Plan]
* detailed instructions how to reproduce the bug
* these should allow someone who is not familiar with the affected
package to reproduce the bug and verify that the updated package fixes
the problem.
* if other testing is appropriate to perform before landing this update,
this should also be described here.
[Where problems could occur]
* Think about what the upload changes in the software. Imagine the change is
wrong or breaks something else: how would this show up?
* It is assumed that any SRU candidate patch is well-tested before
upload and has a low overall risk of regression, but it's important
to make the effort to think about what ''could'' happen in the
event of a regression.
* This must '''never''' be "None" or "Low", or entirely an argument as to why
your upload is low risk.
* This both shows the SRU team that the risks have been considered,
and provides guidance to testers in regression-testing the SRU.
[Other Info]
* Anything else you think is useful to include
* Anticipate questions from users, SRU, +1 maintenance, security teams and the Technical Board
* and address these questions in advance
[Original Description]
Out of the box, the frr package is set to use syslog for logging:
# cat frr.conf
# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in
# /var/log/frr/frr.log
...
log syslog informational
The packaging creates /var/log/frr owned by frr:
drwxr-x--- 2 frr frr 3 Jan 17 17:43 /var/log/frr
In Ubuntu, rsyslog runs as the unprivileged syslog user, not root (like in debian), which means it cannot write to this logging directory:
Jan 17 17:57:25 j-frr-mir rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2112.0 try https://www.rsyslog.com/e/2433 ] |
[Impact]
frr is configured out of the box to use rsyslog logging into a /var/log/frr/frr.log file. This is not working because the permissions in /var/log/frr prevent the unprivileged rsyslog daemon from writing there.
In Debian this works because rsyslog there runs as root.
[Test Plan]
For each $RELEASE under testing, launch a container:
lxc launch ubuntu:$RELEASE $RELEASE-frr-logging
1) upgrade test
Then shell into it, and install frr:
lxc shell $RELEASE-frr-logging
apt update; apt install frr -y
Notice /var/log/frr is empty even after a restart, and that the frr directory is owned by frr:frr:
root@focal-frr-logging:~# systemctl restart frr
root@focal-frr-logging:~# ls -la /var/log/frr
total 0
drwxr-x--- 1 frr frr 0 Jan 20 2020 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
And /var/log/syslog should have this error:
root@focal-frr-logging:~# grep frr\\.log /var/log/syslog
Jul 20 14:09:23 focal-frr-logging rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Now install the package from proposed, and:
a) /var/log/frr ownership is changed to syslog:adm
root@focal-frr-logging:~# ls -lad /var/log/frr
drwxr-x--- 1 syslog adm 0 Jan 20 2020 /var/log/frr
b) after restarting frr, the log file is created as syslog:adm:
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:12 frr.log
c) logrotate maintains these permissions:
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:12 frr.log
root@focal-frr-logging:~# logrotate -f /etc/logrotate.conf
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 38 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 354 Jul 20 14:12 ..
-rw-r----- 1 syslog adm 0 Jul 20 14:12 frr.log
-rw-r----- 1 syslog adm 406 Jul 20 14:12 frr.log.1.gz
2) Fresh install test
In the container, install the frr package from proposed directly. The ownership of /var/log/frr should be correct from the start (syslog:adm):
root@focal-frr-logging:~# ls -lad /var/log/frr
drwxr-x--- 1 syslog adm 0 Jul 19 20:40 /var/log/frr
And upon restarting frr, the frr.log file should appear:
root@focal-frr-logging:~# systemctl restart frr
root@focal-frr-logging:~# ls -la /var/log/frr/
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:30 .
drwxrwxr-x 1 root syslog 326 Jul 20 14:28 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:30 frr.log
Finally, logrotate should also work and preserve the ownership:
root@focal-frr-logging:~# logrotate -f /etc/logrotate.conf
root@focal-frr-logging:~# ls -la /var/log/frr/
total 4
drwxr-x--- 1 syslog adm 38 Jul 20 14:30 .
drwxrwxr-x 1 root syslog 462 Jul 20 14:30 ..
-rw-r----- 1 syslog adm 0 Jul 20 14:30 frr.log
-rw-r----- 1 syslog adm 409 Jul 20 14:30 frr.log.1.gz
[Where problems could occur]
Some users might have fixed this problem on their systems manually, either following the same approach here, or doing something else. An important part of the fix from this SRU is in the frr.postinst maintainer script, which is something administrators cannot easily override. Therefore it's possible that this update might break such existing setups where users fixed the problem themselves.
It's also possible that users elected to switch to frr direct logging, bypassing rsyslog. In such case, since /var/log/frr is now owned by syslog:adm instead of frr:frr, the frr daemon won't be able to create new files in /var/log/frr anymore, nor update the existing /var/log/frr/frr.log one. The original debian packaging works both ways, since rsyslog is privileged and can chown or switch to the frr user, but that's not the case for ubuntu.
In general:
a) users who have broken logging (potentially without realizing it) will be fixed by this update, and the fix here is the intended default behavior in ubuntu as it should have been from the start
b) users who fixed their own logging in some way might have issues with this update, mainly depending if they kept using the package-provided /var/log/frr directory, which is what we are manipulating here.
Trying to cope with all possible scenarios can quickly become complex, and introduce new bugs on its own.
I *could* perhaps gate on "log syslog" being in /etc/frr/frr.conf, and do nothing if it's not there.
[Other Info]
Original MP that landed this fix in Kinetic, with some discussion:
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/424952
[Original Description]
Out of the box, the frr package is set to use syslog for logging:
# cat frr.conf
# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in
# /var/log/frr/frr.log
...
log syslog informational
The packaging creates /var/log/frr owned by frr:
drwxr-x--- 2 frr frr 3 Jan 17 17:43 /var/log/frr
In Ubuntu, rsyslog runs as the unprivileged syslog user, not root (like in debian), which means it cannot write to this logging directory:
Jan 17 17:57:25 j-frr-mir rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2112.0 try https://www.rsyslog.com/e/2433 ] |
|
| 2022-07-20 14:55:57 |
Andreas Hasenack |
description |
[Impact]
frr is configured out of the box to use rsyslog logging into a /var/log/frr/frr.log file. This is not working because the permissions in /var/log/frr prevent the unprivileged rsyslog daemon from writing there.
In Debian this works because rsyslog there runs as root.
[Test Plan]
For each $RELEASE under testing, launch a container:
lxc launch ubuntu:$RELEASE $RELEASE-frr-logging
1) upgrade test
Then shell into it, and install frr:
lxc shell $RELEASE-frr-logging
apt update; apt install frr -y
Notice /var/log/frr is empty even after a restart, and that the frr directory is owned by frr:frr:
root@focal-frr-logging:~# systemctl restart frr
root@focal-frr-logging:~# ls -la /var/log/frr
total 0
drwxr-x--- 1 frr frr 0 Jan 20 2020 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
And /var/log/syslog should have this error:
root@focal-frr-logging:~# grep frr\\.log /var/log/syslog
Jul 20 14:09:23 focal-frr-logging rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Now install the package from proposed, and:
a) /var/log/frr ownership is changed to syslog:adm
root@focal-frr-logging:~# ls -lad /var/log/frr
drwxr-x--- 1 syslog adm 0 Jan 20 2020 /var/log/frr
b) after restarting frr, the log file is created as syslog:adm:
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:12 frr.log
c) logrotate maintains these permissions:
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:12 frr.log
root@focal-frr-logging:~# logrotate -f /etc/logrotate.conf
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 38 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 354 Jul 20 14:12 ..
-rw-r----- 1 syslog adm 0 Jul 20 14:12 frr.log
-rw-r----- 1 syslog adm 406 Jul 20 14:12 frr.log.1.gz
2) Fresh install test
In the container, install the frr package from proposed directly. The ownership of /var/log/frr should be correct from the start (syslog:adm):
root@focal-frr-logging:~# ls -lad /var/log/frr
drwxr-x--- 1 syslog adm 0 Jul 19 20:40 /var/log/frr
And upon restarting frr, the frr.log file should appear:
root@focal-frr-logging:~# systemctl restart frr
root@focal-frr-logging:~# ls -la /var/log/frr/
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:30 .
drwxrwxr-x 1 root syslog 326 Jul 20 14:28 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:30 frr.log
Finally, logrotate should also work and preserve the ownership:
root@focal-frr-logging:~# logrotate -f /etc/logrotate.conf
root@focal-frr-logging:~# ls -la /var/log/frr/
total 4
drwxr-x--- 1 syslog adm 38 Jul 20 14:30 .
drwxrwxr-x 1 root syslog 462 Jul 20 14:30 ..
-rw-r----- 1 syslog adm 0 Jul 20 14:30 frr.log
-rw-r----- 1 syslog adm 409 Jul 20 14:30 frr.log.1.gz
[Where problems could occur]
Some users might have fixed this problem on their systems manually, either following the same approach here, or doing something else. An important part of the fix from this SRU is in the frr.postinst maintainer script, which is something administrators cannot easily override. Therefore it's possible that this update might break such existing setups where users fixed the problem themselves.
It's also possible that users elected to switch to frr direct logging, bypassing rsyslog. In such case, since /var/log/frr is now owned by syslog:adm instead of frr:frr, the frr daemon won't be able to create new files in /var/log/frr anymore, nor update the existing /var/log/frr/frr.log one. The original debian packaging works both ways, since rsyslog is privileged and can chown or switch to the frr user, but that's not the case for ubuntu.
In general:
a) users who have broken logging (potentially without realizing it) will be fixed by this update, and the fix here is the intended default behavior in ubuntu as it should have been from the start
b) users who fixed their own logging in some way might have issues with this update, mainly depending if they kept using the package-provided /var/log/frr directory, which is what we are manipulating here.
Trying to cope with all possible scenarios can quickly become complex, and introduce new bugs on its own.
I *could* perhaps gate on "log syslog" being in /etc/frr/frr.conf, and do nothing if it's not there.
[Other Info]
Original MP that landed this fix in Kinetic, with some discussion:
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/424952
[Original Description]
Out of the box, the frr package is set to use syslog for logging:
# cat frr.conf
# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in
# /var/log/frr/frr.log
...
log syslog informational
The packaging creates /var/log/frr owned by frr:
drwxr-x--- 2 frr frr 3 Jan 17 17:43 /var/log/frr
In Ubuntu, rsyslog runs as the unprivileged syslog user, not root (like in debian), which means it cannot write to this logging directory:
Jan 17 17:57:25 j-frr-mir rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2112.0 try https://www.rsyslog.com/e/2433 ] |
[Impact]
frr is configured out of the box to use rsyslog logging into a /var/log/frr/frr.log file. This is not working because the permissions in /var/log/frr prevent the unprivileged rsyslog daemon from writing there.
In Debian this works because rsyslog there runs as root.
[Test Plan]
For each $RELEASE under testing, launch a container:
lxc launch ubuntu:$RELEASE $RELEASE-frr-logging
1) upgrade test
Then shell into it, and install frr:
lxc shell $RELEASE-frr-logging
apt update; apt install frr -y
Notice /var/log/frr is empty even after a restart, and that the frr directory is owned by frr:frr:
root@focal-frr-logging:~# systemctl restart frr
root@focal-frr-logging:~# ls -la /var/log/frr
total 0
drwxr-x--- 1 frr frr 0 Jan 20 2020 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
And /var/log/syslog should have this error:
root@focal-frr-logging:~# grep frr\\.log /var/log/syslog
Jul 20 14:09:23 focal-frr-logging rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2001.0 try https://www.rsyslog.com/e/2433 ]
Now install the package from proposed, and:
a) /var/log/frr ownership is changed to syslog:adm
root@focal-frr-logging:~# ls -lad /var/log/frr
drwxr-x--- 1 syslog adm 0 Jan 20 2020 /var/log/frr
b) after restarting frr, the log file is created as syslog:adm:
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:12 frr.log
c) logrotate maintains these permissions:
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 274 Jul 20 14:08 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:12 frr.log
root@focal-frr-logging:~# logrotate -f /etc/logrotate.conf
root@focal-frr-logging:~# ls -la /var/log/frr
total 4
drwxr-x--- 1 syslog adm 38 Jul 20 14:12 .
drwxrwxr-x 1 root syslog 354 Jul 20 14:12 ..
-rw-r----- 1 syslog adm 0 Jul 20 14:12 frr.log
-rw-r----- 1 syslog adm 406 Jul 20 14:12 frr.log.1.gz
2) Fresh install test
In the container, install the frr package from proposed directly. The ownership of /var/log/frr should be correct from the start (syslog:adm):
root@focal-frr-logging:~# ls -lad /var/log/frr
drwxr-x--- 1 syslog adm 0 Jul 19 20:40 /var/log/frr
And upon restarting frr, the frr.log file should appear:
root@focal-frr-logging:~# systemctl restart frr
root@focal-frr-logging:~# ls -la /var/log/frr/
total 4
drwxr-x--- 1 syslog adm 14 Jul 20 14:30 .
drwxrwxr-x 1 root syslog 326 Jul 20 14:28 ..
-rw-r----- 1 syslog adm 1175 Jul 20 14:30 frr.log
Finally, logrotate should also work and preserve the ownership:
root@focal-frr-logging:~# logrotate -f /etc/logrotate.conf
root@focal-frr-logging:~# ls -la /var/log/frr/
total 4
drwxr-x--- 1 syslog adm 38 Jul 20 14:30 .
drwxrwxr-x 1 root syslog 462 Jul 20 14:30 ..
-rw-r----- 1 syslog adm 0 Jul 20 14:30 frr.log
-rw-r----- 1 syslog adm 409 Jul 20 14:30 frr.log.1.gz
[Where problems could occur]
Some users might have fixed this problem on their systems manually, either following the same approach here, or doing something else. An important part of the fix from this SRU is in the frr.postinst maintainer script, which is something administrators cannot easily override. Therefore it's possible that this update might break such existing setups where users fixed the problem themselves.
It's also possible that users elected to switch to frr direct logging, bypassing rsyslog. In such case, since /var/log/frr is now owned by syslog:adm instead of frr:frr, the frr daemon won't be able to create new files in /var/log/frr anymore, nor update the existing /var/log/frr/frr.log one. The original debian packaging works both ways, since rsyslog is privileged and can chown or switch to the frr user, but that's not the case for ubuntu.
In general:
a) users who have broken logging (potentially without realizing it) will be fixed by this update, and the fix here is the intended default behavior in ubuntu as it should have been from the start
b) users who fixed their own logging in some way might have issues with this update, mainly depending if they kept using the package-provided /var/log/frr directory, which is what we are manipulating here.
Trying to cope with all possible scenarios can quickly become complex, and introduce new bugs on its own.
I *could* perhaps gate on "log syslog" being in /etc/frr/frr.conf, and do nothing if it's not there, but it can be a slippery slope: I fear introducing more complexity.
[Other Info]
Original MP that landed this fix in Kinetic, with some discussion:
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/424952
[Original Description]
Out of the box, the frr package is set to use syslog for logging:
# cat frr.conf
# default to using syslog. /etc/rsyslog.d/45-frr.conf places the log in
# /var/log/frr/frr.log
...
log syslog informational
The packaging creates /var/log/frr owned by frr:
drwxr-x--- 2 frr frr 3 Jan 17 17:43 /var/log/frr
In Ubuntu, rsyslog runs as the unprivileged syslog user, not root (like in debian), which means it cannot write to this logging directory:
Jan 17 17:57:25 j-frr-mir rsyslogd: file '/var/log/frr/frr.log': open error: Permission denied [v8.2112.0 try https://www.rsyslog.com/e/2433 ] |
|
| 2022-07-20 19:58:48 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/427171 |
|
| 2022-07-20 19:59:48 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/427172 |
|
| 2022-08-05 21:42:03 |
Steve Langasek |
frr (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2022-08-05 21:42:06 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2022-08-05 21:42:09 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2022-08-05 21:42:13 |
Steve Langasek |
tags |
server-todo |
server-todo verification-needed verification-needed-focal |
|
| 2022-08-09 17:39:40 |
Andreas Hasenack |
tags |
server-todo verification-needed verification-needed-focal |
server-todo verification-done-focal verification-needed |
|
| 2022-08-12 23:25:30 |
Steve Langasek |
frr (Ubuntu Jammy): status |
In Progress |
Fix Committed |
|
| 2022-08-12 23:25:39 |
Steve Langasek |
tags |
server-todo verification-done-focal verification-needed |
server-todo verification-done-focal verification-needed verification-needed-jammy |
|
| 2022-08-15 13:11:55 |
Andreas Hasenack |
tags |
server-todo verification-done-focal verification-needed verification-needed-jammy |
server-todo verification-done verification-done-focal verification-done-jammy |
|
| 2022-08-22 08:58:13 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2022-08-22 08:58:12 |
Launchpad Janitor |
frr (Ubuntu Jammy): status |
Fix Committed |
Fix Released |
|
| 2022-08-22 09:17:15 |
Launchpad Janitor |
frr (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2023-01-29 20:01:04 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/436497 |
|
| 2023-01-30 21:17:13 |
Andreas Hasenack |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/436497 |
|
|
| 2023-07-26 13:56:58 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/447786 |
|
| 2023-07-26 13:57:21 |
Andreas Hasenack |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/447786 |
|
|
| 2023-07-26 20:43:34 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/447786 |
|
| 2023-09-01 19:57:43 |
Launchpad Janitor |
merge proposal linked |
|
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/450492 |
|
| 2023-09-01 20:16:08 |
Andreas Hasenack |
merge proposal unlinked |
https://code.launchpad.net/~ahasenack/ubuntu/+source/frr/+git/frr/+merge/450492 |
|
|
