Ticket #44 (reopened defect)

Opened 5 years ago

Last modified 4 years ago

arm4_control needs recovery options

Reported by: dcarter Owned by: dcarter
Priority: high Milestone:
Component: ARM4 Agent Version: Development
Severity: Operational Stability Keywords:
Cc:

Description

In the event of a daemon malfunction, restarting becomes difficult. The following things need to happen in a recovery operation:

  1. Run a Berkeley DB recovery operation
  2. Flush the queues and/or recreate the shared memory and semaphores

Change History

comment:1 Changed 5 years ago by dcarter

  • Status changed from new to assigned

comment:2 Changed 5 years ago by dcarter

  • Status changed from assigned to closed
  • Resolution set to fixed

No special command to do this was added to arm4_control. Berkeley DB recovery is handled by adding the recover option to the environment when it's created. Removal of the shared memory and semaphores is handled with the 'remove' command.

comment:3 Changed 5 years ago by dcarter

  • Status changed from closed to reopened
  • Resolution fixed deleted

Specifying DB_RECOVER every time the environment is opened causes the conditions that require a recovery. There really needs to be a separate recovery option.

comment:4 Changed 4 years ago by dcarter

  • Milestone changed from Release 0.6 to Release 0.7

comment:5 Changed 4 years ago by dcarter

  • Milestone changed from Release 0.7 to Release 0.6.1

comment:6 Changed 4 years ago by anonymous

  • Milestone Release 0.6.1 deleted

Milestone Release 0.6.1 deleted

Note: See TracTickets for help on using tickets.