localbackend: add some log to help diagnose

[D3Hunter]

What problem does this PR solve?

Issue Number: ref #63681

Problem Summary:

What changed and how does it work?

from the issue, seems pebble db is not closed completely, add some log

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No need to test. only add log

  • I checked and no code files have been changed.

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

[tiprow]

Hi @D3Hunter. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[D3Hunter]

/check-issue-triage-complete

[Benjamin2037]

LGTM

[D3Hunter]

/retest

[tiprow]

@D3Hunter: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[codecov]

Codecov Report

❌ Patch coverage is 0% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 73.4171%. Comparing base (a24f3d7) to head (afb4a93).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #63682        +/-   ##
================================================
+ Coverage   72.7573%   73.4171%   +0.6597%     
================================================
  Files          1842       1872        +30     
  Lines        498127     506269      +8142     
================================================
+ Hits         362424     371688      +9264     
+ Misses       113685     111893      -1792     
- Partials      22018      22688       +670     

Flag	Coverage Δ
integration	44.7319% <0.0000%> (?)
unit	72.3066% <0.0000%> (+0.0007%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components	Coverage Δ
dumpling	52.8700% <ø> (ø)
parser	∅ <ø> (∅)
br	46.4083% <ø> (-0.0076%)	⬇️

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Benjamin2037, GMHDBJD

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• pkg/lightning/OWNERS [Benjamin2037,GMHDBJD]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2025-09-23 04:12:13.947409398 +0000 UTC m=+329944.017903073: ☑️ agreed by Benjamin2037.
• 2025-09-23 04:54:49.95548651 +0000 UTC m=+332500.025980190: ☑️ agreed by GMHDBJD.