FRR generates log /var/log/frr/frr.log inside bgp docker and taking lots of harddrive space #5965
Labels
Comments
This was referenced Nov 18, 2020
yxieca
added a commit
that referenced
this issue
Nov 21, 2020
- Why I did it frr is creating /var/log/frr/frr.log inside the frr docker and letting it grow. It will eventually exhaust hard drive space. To fixe issue #5965 - How I did it Remove rsyslog file outchannel so that frr won't generate /var/log/frr/frr.log inside the docker. - How to verify it Manually removed the outchannel and restart BGP docker, making sure that /var/log/frr/frr.log is no longer created inside the docker. While restarting bgp docker, observed that base image /var/log/quagga/bgpd.log continued to grow and captured all FRR logs.
abdosi
pushed a commit
that referenced
this issue
Nov 21, 2020
- Why I did it frr is creating /var/log/frr/frr.log inside the frr docker and letting it grow. It will eventually exhaust hard drive space. To fixe issue #5965 - How I did it Remove rsyslog file outchannel so that frr won't generate /var/log/frr/frr.log inside the docker. - How to verify it Manually removed the outchannel and restart BGP docker, making sure that /var/log/frr/frr.log is no longer created inside the docker. While restarting bgp docker, observed that base image /var/log/quagga/bgpd.log continued to grow and captured all FRR logs.
santhosh-kt
pushed a commit
to santhosh-kt/sonic-buildimage
that referenced
this issue
Feb 25, 2021
- Why I did it frr is creating /var/log/frr/frr.log inside the frr docker and letting it grow. It will eventually exhaust hard drive space. To fixe issue sonic-net#5965 - How I did it Remove rsyslog file outchannel so that frr won't generate /var/log/frr/frr.log inside the docker. - How to verify it Manually removed the outchannel and restart BGP docker, making sure that /var/log/frr/frr.log is no longer created inside the docker. While restarting bgp docker, observed that base image /var/log/quagga/bgpd.log continued to grow and captured all FRR logs.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Steps to reproduce the issue:
Describe the results you received:
Unable to upgrade to next image because BGP docker took too much hard drive space
Describe the results you expected:
Upgrade for nightly test goes smooth.
Additional information you deem important (e.g. issue happens only occasionally):
SONiC Software Version: SONiC.20191130.52
```
root@str-a7060cx-acs-10:/home/admin# docker exec -it bgp bash
root@str-a7060cx-acs-10:/# ls
bin boot dev etc home lib lib64 media mnt opt proc root run sbin srv sys tmp usr var
root@str-a7060cx-acs-10:/# cd var/log/
root@str-a7060cx-acs-10:/var/log# ls
alternatives.log apt btmp dpkg.log faillog frr lastlog redis supervisor wtmp
root@str-a7060cx-acs-10:/var/log# cd frr
root@str-a7060cx-acs-10:/var/log/frr# ls
frr.log
root@str-a7060cx-acs-10:/var/log/frr# du -sh .
2.1G .
```
The text was updated successfully, but these errors were encountered: