Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
Kea
Kea
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 414
    • Issues 414
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 67
    • Merge Requests 67
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • ISC Open Source Projects
  • KeaKea
  • Issues
  • #1097

Closed
Open
Opened Jan 25, 2020 by Michael McNally@McNallyDeveloper

When launched from systemd, kea needs to be restarted twice after a DB crash

In support ticket #15937, a customer reports:

During my testing of failure scenarios I found that when the DB backend goes away, it causes the KEA service to fail (expected and desired behavior). But once the DB is back online, the very first restart of KEA service fails with "address already in use" messages.

Additional supporting evidence is available on the linked support ticket but I have omitted it here because it has not been sanitized to preserve the privacy of the customer reporting it.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
kea1.7.5
Milestone
kea1.7.5 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: isc-projects/kea#1097