FRR bfdd is not running - Ubuntu 22.04

[ibhatt1155]

---

Describe the bug
Can someone help me with this issue? I am not sure what am I doing wrong.

Installed FRRouting 8.1 on a Ubuntu 22.04 container using apt-get install frr. vtysh successfully gets to the FRR prompt. I can run show running config successfully but when I try to run the BFD command, getting below error.

I am setting bfdd=yes in /etc/frr/daemon file. Attached below. Tried restarting frr but it also fails

root@frr:/# ps -ef | grep frr
root        1054       1  0 16:28 ?        00:00:00 /usr/lib/frr/watchfrr -d -F traditional zebra staticd bfdd
frr         1112       1  0 16:29 ?        00:00:00 /usr/lib/frr/staticd -d -F traditional -A 127.0.0.1
root        1119     735  0 16:29 pts/2    00:00:00 grep --color=auto frr
root@frr:/# service frr status
 * Status of watchfrr: running
 * Status of zebra: FAILED
 * Status of staticd: running
 * Status of bfdd: FAILED
 root@frr:/# service frr restart
 * Stopped watchfrr
 * Cannot stop bfdd: pid file not found
 * Cannot stop zebra: pid file not found
 * Stopped staticd
 * Started watchfrr
 * root@frr:/# ps -ef | grep frr
root        1211       1  0 16:30 ?        00:00:00 /usr/lib/frr/watchfrr -d -F traditional zebra staticd bfdd
frr         1257       1  0 16:31 ?        00:00:00 /usr/lib/frr/staticd -d -F traditional -A 127.0.0.1
root        1268     735  0 16:33 pts/2    00:00:00 grep --color=auto frr
root@frr:/# 
root@frr:/# vtysh

Hello, this is FRRouting (version 8.1).
Copyright 1996-2005 Kunihiro Ishiguro, et al.

frr# show running-config 
Building configuration...

Current configuration:
!
frr version 8.1
frr defaults traditional
hostname frr
log syslog informational
service integrated-vtysh-config
!
end
frr# show bfd peer
bfdd is not running
frr# 

• Did you check if this is a duplicate issue?
• Did you test it on the latest FRRouting/frr master branch?

To Reproduce
install FRR via apt-get and change bfdd=yes and add --daemon to bfdd. Restart the FRR service.

I have followed tehse steps: https://docs.frrouting.org/en/latest/setup.html

Expected behavior

Screenshots

Versions
Container is running Ubuntu 2204

• OS Version:
  PRETTY_NAME="Ubuntu 22.04.3 LTS"
  NAME="Ubuntu"
  VERSION_ID="22.04"
  VERSION="22.04.3 LTS (Jammy Jellyfish)"
  VERSION_CODENAME=jammy
• FRR Version: 8.1

Additional context

[donaldsharp]

what does the FRR log file say?

[ibhatt1155]

This is from old logs

2024-01-25 15:57:06,116 INFO: Called via "Namespace(input=None, reload=True, test=False, debug=False, log_level='info', stdout=False, pathspace=None, filename='/etc/frr/frr.conf', overwrite=False, bindir='/usr/bin', confdir='/etc/frr', rundir='/var/run/frr', vty_socket=None, daemon='', test_reset=False)"
2024-01-25 15:57:06,116 INFO: Loading Config object from file /etc/frr/frr.conf
2024-01-25 15:57:06,574 INFO: Loading Config object from vtysh show running
2024-01-25 15:57:06,806 INFO: "frr version 8.1" cannot be removed
2024-01-25 15:57:06,806 INFO: "frr defaults traditional" cannot be removed
2024-01-25 15:57:06,806 INFO: "service integrated-vtysh-config" cannot be removed
2024-01-25 15:57:07,035 INFO: Executed "no hostname sriov-frr-pod"
2024-01-25 15:57:07,035 INFO: Loading Config object from vtysh show running
2024-01-25 15:57:07,265 INFO: "frr version 8.1" cannot be removed
2024-01-25 15:57:07,265 INFO: "frr defaults traditional" cannot be removed
2024-01-25 15:57:07,265 INFO: "service integrated-vtysh-config" cannot be removed

[ibhatt1155]

it looks like getting the pid not found for any feature I enable in /etc/frr/daemon. Changed bgpd=yes and now its showing up as its pid not found.

root@frr:/etc/frr# service frr restart

• Stopped watchfrr
• Cannot stop bfdd: pid file not found
• Cannot stop bgpd: pid file not found
• Cannot stop zebra: pid file not found
• Stopped staticd
• Started watchfrr

[ibhatt1155]

I think it looks like I am running into #8681. My container is created in non-privilege mode and that may be causing the issues. I do have an ability to allow NET_ADMIN but privileged and SYS_ADMIN is disabled for a container to use for security purposes.

Any workaround I can use to get past this and validate further?

[ibhatt1155]

Running the container in privileged mode resolved the issue.