Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-2522

rpm: error message in logs when uninstalling after an upgrade

    Details

    • Type: Bug
    • Status: Done
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 3.0.0
    • Fix Version/s: 3.0.0
    • Component/s: packaging
    • Labels:

      Description

      Found with OpenDJ 3.0.0 M6 rev 7878f040fe08795b08fec3bea180c0cc2951c993

      Scenario:

      Install rpm package 2.6.3:

      rpm -i opendj-2.6.3-1.noarch.rpm
      

      setup server:

      /opt/opendj/setup --acceptLicense --cli -p 1389 --adminConnectorPort 4444 -D cn=myself -w password -b dc=com -d 10 -n
      

      Upgrade with 3.0.0 M6

      rpm -U opendj-3.0.0_1.noarch.rpm
      

      Uninstall package:

      # rpm -e opendj
      Pre Uninstall - uninstall
      Stopping Server...
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=WARNING msgID=org.opends.messages.core.342 msg=An error occurred while attempting to release a shared lock for backend adminRoot: The attempt to release the lock held on /opt/opendj/locks/backend-adminRoot.lock failed because no record of a lock on that file was found. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=WARNING msgID=org.opends.messages.core.342 msg=An error occurred while attempting to release a shared lock for backend ads-truststore: The attempt to release the lock held on /opt/opendj/locks/backend-ads-truststore.lock failed because no record of a lock on that file was found. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=WARNING msgID=org.opends.messages.core.342 msg=An error occurred while attempting to release a shared lock for backend backup: The attempt to release the lock held on /opt/opendj/locks/backend-backup.lock failed because no record of a lock on that file was found. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=WARNING msgID=org.opends.messages.core.342 msg=An error occurred while attempting to release a shared lock for backend monitor: The attempt to release the lock held on /opt/opendj/locks/backend-monitor.lock failed because no record of a lock on that file was found. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=WARNING msgID=org.opends.messages.core.342 msg=An error occurred while attempting to release a shared lock for backend schema: The attempt to release the lock held on /opt/opendj/locks/backend-schema.lock failed because no record of a lock on that file was found. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=WARNING msgID=org.opends.messages.core.342 msg=An error occurred while attempting to release a shared lock for backend tasks: The attempt to release the lock held on /opt/opendj/locks/backend-tasks.lock failed because no record of a lock on that file was found. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary
      [09/Dec/2015:10:10:26 +0100] category=PLUGGABLE severity=NOTICE msgID=org.opends.messages.backend.370 msg=The backend userRoot is now taken offline
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=WARNING msgID=org.opends.messages.core.342 msg=An error occurred while attempting to release a shared lock for backend userRoot: The attempt to release the lock held on /opt/opendj/locks/backend-userRoot.lock failed because no record of a lock on that file was found. This lock should be automatically cleaned when the Directory Server process exits, so no additional action should be necessary
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=NOTICE msgID=org.opends.messages.core.141 msg=The Directory Server has started the shutdown process. The shutdown was initiated by an instance of class org.opends.server.core.DirectoryServerShutdownHook and the reason provided for the shutdown was The attempt to release the lock held on /opt/opendj/locks/server.lock failed because no record of a lock on that file was found
      [09/Dec/2015:10:10:26 +0100] category=CORE severity=NOTICE msgID=org.opends.messages.core.203 msg=The Directory Server is now stopped
      Post Uninstall - uninstall
      OpenDJ successfully removed.
      

        Attachments

          Activity

            People

            • Assignee:
              JnRouvignac Jean-Noël Rouvignac
              Reporter:
              cforel carole forel
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: