LO70191: PANIC AFTER RECOVERY MANAGER: LOG FILE IS FULL MESSAGES

APAR status

• Closed as returned (APAR cannot be resolved without additional info from IBM or customer.)

Error description

• Domino V853 on iSeries was restarted after running compact
  against all DB's
  offline. Design and DAOS resync were started.
  
  Following errors were observed;
  
  Recovery Manager: Log File is Full
  StreamNotes:  NSFDbGetNotes()->ERROR: 13C4=Recovery Manager: Log
  File is Full
  StreamNotes: Requested 982, got 619
  01/17/2011 09:23:35   Unable to store document in
  mail/mail2117.nsf (NoteID =
  2806) from AS4085A/SVTREL06 mail2\mail2117.nsf (NoteID = 2550):
  Recovery
  Manager: Log File is Full
  01/17/2011 09:23:35   Unable to store document in
  mail/mail2117.nsf (NoteID =
  1870) from AS4085A/SVTREL06 mail2\mail2117.nsf (NoteID = 2026):
  Recovery
  Manager: Log File is Full
  Recovery Manager: Log File Full: Func=hlgWriteLogRecord
  File=rmlogger.cpp:703
  [/DOMINO/AS4085B/mail/mail3256.nsf  82736]
  NSFNoteUpdateObjectsEnd: ERROR 'Recovery Manager: Log File is
  Full' Freeing
  Object!
  01/17/2011 09:23:36 PID=1509 TID=5 RESYNC Turning on logging of
  DOI
  
  01/17/2011 09:23:36   Design error for database
  'mail2/mail1137.nsf': Recovery
  Manager: Log File is Full
  01/17/2011 09:23:36   Unable to replicate mail/mail2117.nsf:
  Recovery Manager:
  Log File is Full
  
  01/17/2011 09:23:36   1112 Transactions/Minute, 1 Notes
  Users01/17/2011
  09:23:36 PID=1509 TID=5 RESYNC No NLO's to delete
  
  01/17/2011 09:23:36   Pulling mail/mail2860.nsf from
  AS4085A/SVTREL06
  mail2\mail2860.nsf
  01/17/2011 09:23:36 PID=1509 TID=5 RESYNC Named note
  DAOS_CATALOG_NLO_DELETION_NOTE set to noteid 0
  
  01/17/2011 09:23:36 PID=1509 TID=5 RESYNC Object rebuild
  finished: 0x13C4
  01/17/2011 09:23:36 PID=1509 TID=5 Unknown Failed rebuilding the
  object
  entries/index in the DAOS catalog: 13C4
  ReplicateFolders: Terminating with error: 0x13C4=Recovery
  Manager: Log File is
  Full
  Cannot write to log file: Recovery Manager: Log File is Full
  01/17/2011 09:23:43   DAOS was unable to rebuild the list of
  external files
  while trying to resynchronize.: Recovery Manager: Log File is
  Full
  01/17/2011 09:23:43   Unable to replicate mail/mail2860.nsf:
  Recovery Manager:
  Log File is Full
  01/17/2011 09:23:43   There was an error rebuilding the
  catalog.
  01/17/2011 09:23:44   Closed session for AS4085A/SVTREL06
  Databases accessed:
  814   Documents read:     2   Documents written:  2688
  01/17/2011 09:23:45   Deleted task 13621
  RmTrace: Id=513 Rollforward complete for Granules 622840-623087
  RC=0
  01/17/2011 09:23:50   Finished replication with server
  AS4085A/SVTREL06
  01/17/2011 09:23:50   Event: Error creating a Domino Domain
  Monitoring event
  document in database ddm.nsf: Recovery Manager: Log File is
  Full
  01/17/2011 09:23:50   Event: Error creating a Domino Domain
  Monitoring event
  document in database ddm.nsf: Recovery Manager: Log File is
  Full
  01/17/2011 09:23:50   Updating 'accept.gif' into database
  'mail1139' from
  template 'Mail (R8.5)'
  
  
  This was followed by many  "Recovery Manager: Log File is Full"
  messages from
  both Design task and Agent Manager and two panic messages;
  
  Thread=[050776:01493:00082-0000005A]
  PANIC: semaphore invalid or not allocated
  
  Thread=[050778:01495:00012-00000020]
  PANIC: ASSERT(("Should not be holding object locked at
  destruction", !ref))
  failed at line 31 in file
  /local1/nightly/v8.daily.os400/nsf/rm/rmmem.hpp
  
  The NSD which ran only picked up the crash from Server (050776)
  and the Panic
  in Event (050778) was not trapped
  

Local fix

• recreate txn file and restart server
  

Problem summary

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# RCOR8DBHUZ.
  The record was returned to the person who created it for more
   information.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels