Facing "bitStoreService" is null

[akshay ts]

Hi all,

I am from The Australian National University. We have upgraded our dspace yesterday (20th May 2024) from DSpace 5.8 to Dspace 7.6.1.

I could see some logs

Cannot invoke "org.dspace.storage.bitstore.BitStoreService.isInitialized()" because "bitStoreService" is null

We are using local assetstores (not s3).

We are also getting white label error page. I have created a new conversation for it (subject: Whitelabel error page). Not sure if these are related to each other

Has anyone else solved this problem?

We would be glad if someone could help us with us.

Thanks and Regards,

Akshay Karthik Thana Sekar

[DSpace Technical Support]

Hi Akshay,

Usually when you get a "*Service is null" error, that's a sign that the DSpace backend didn't startup properly because of a larger problem.  The larger problem may be an issue with connecting with the Database or Solr, or it could be a sign that something in your upgrade/install didn't go properly (e.g. old libraries are still installed that are causing errors).

I'd recommend looking closely at your dspace.log file for **additional errors**.  That "bitStoreService is null" error may not be the only error, and it may be a sign that a more serious error occurred before that.  If you cannot find any additional errors, then I'd recommend sharing the full stacktrace of that "bitStoreService is Null" error.  Sometimes the entire stacktrace can give others hints as to what might be going on.

For more information on finding detailed error messages in DSpace 7, see the troubleshooting guide: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

[akshay ts]

Hi team,

Thank you for your quick reply.

I was able to figure out what was causing the issue after looking at the dspace log. We were having multiple assetstores like assetstore, assetstore2 and a few more. We forgot to configure the bitstore.xml. So, it was throwing the whitelabel error page and this bitStoreService null.

I have configured the bitstore.xml now and there are no more such errors in the logs.

Regards,

Akshay Karthik Thana Sekar