frr: Failed to open commit history "/var/lib/frr/commit-index.dat" for writing: No such file or directory
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
When I start frr with /etc/init.d/frr start I see errors in the system log:
Wed Feb 5 18:50:56 2025 daemon.err mgmtd[3257]: libyang: Failed to open file "/var/lib/frr/commit-20250205185056384052348.json" (No such file or directory).
Wed Feb 5 18:50:56 2025 daemon.err mgmtd[3257]: [HAWY9-CP261] Failed to open commit history "/var/lib/frr/commit-index.dat" for writing: No such file or directory
Any idea what those are about? They seem alarming no matter what they are. on a 24.10.0 target there doesn't seem to be even a /var/lib/ never mind /var/lib/frr/. Should that path exist? Or should mgmtd be told somewhere else to be trying to write that data?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the /etc/init.d/frr startup path and the mgmtd log messages showing writes to /var/lib/frr/commit-*.json and commit-index.dat. Determine whether the missing directory is expected on the reported 24.10.0 target or whether mgmtd should use another location; done means the intended behavior is documented or the startup error is corrected.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100