Uploaded image for project: 'Fedora Repository Project'
  1. Fedora Repository Project
  2. FCREPO-1204

Fedora 3.7.1 fails to start with legacy-fs storage option chosen

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: Fedora 3.7.1
    • Fix Version/s: Fedora 3.8.0
    • Component/s: legacy - Fedora
    • Labels:
      None
    • Environment:
      RHEL6
    • Roadmap Theme:
      Storage: Pluggability

      Description

      I just started a 3.7.1 upgrade at Tufts as well. While running the
      installer we ran into a different initial problem, and having resolved
      that have caught up the problem reported here, so first off, thanks for
      the info here in this thread. The problem we initially hit is that in our
      install we specify the low level storage option as legacy-fs, which upon
      start up results in the following error:

      ERROR 13:46:21.014 (Server) Module
      (org.fcrepo.server.storage.lowlevel.ILowlevelStorage) failed to initialize
      org.fcrepo.server.errors.ModuleInitializationException: couldn't set up
      path_algorithm for objectPaths Class
      org.fcrepo.server.storage.lowlevel.defaultstore.Store can not access a
      member of class org.fcrepo.server.storage.lowlevel.TimestampPathAlgorithm
      with modifiers "public"
              at
      org.fcrepo.server.storage.lowlevel.DefaultLowlevelStorageModule.postInitMod
      ule(DefaultLowlevelStorageModule.java:44) ~[fcrepo-server-3.7.1.jar:na]

      Looking at the fcrepo-server source it seemed to be related to this commit:

      https://github.com/fcrepo/fcrepo/commit/5ad360edf39bfeca57038974639b41073af1fd1b#diff-644ddc1704c65930c61becbd9826bee1

      Where the Store class moved from being a support within
      DefaultLowlevelStorage in the org.fcrepo.server.storage.lowlevel package
      to the org.fcrepo.server.storage.lowlevel.default package as a top level
      class.

      I confirmed that by making the TimestampPathAlgorithm class public this
      issue goes away at startup since Store would then have access. Not sure
      if this is the correct fix or if Store should've stayed in the previous
      package.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                barmintor Benjamin Armintor
                Reporter:
                mkorcy mike korcynski
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: