Closed tufeigunchu closed 2 years ago
The cause is right there in your logs:
2021/12/15 01:07:58 BFD: [JYK95-PZFVY] bind-ip: bind: Address in use
It doesn't crash. It can't start because the address/port is already in use. Looks like you already have running bfdd
on your system sometimes.
@frrbot autoclose in 1 day
This issue will be automatically closed in the specified period unless there is further activity.
That's strange. docker container is in different namespace. No exist bfdd can affect it I think
This issue will no longer be automatically closed.
I'm not sure why this is happening on your system, but this is definitely it.
staticd
warns about the same thing:
2021/12/15 01:07:56 STATIC: [NTCMZ-C8X80][EC 100663303] Could not lock pid_file /var/run/frr/staticd.pid (Resource temporarily unavailable), exiting. Please ensure that the daemon is not already running
You need to find the reason why staticd
and bfdd
are not properly stopped before starting a new instance.
Since it can restart successfully, I close this issue now
I am running docker version of FRR 8.0.1.
enabled: bgpd staticd bfdd startup log:
frr.conf:
Not happen everytime. I can't figure out the cause.