Whitelabel error page

622 views
Skip to first unread message

akshay ts

unread,
May 21, 2024, 3:24:54 AM5/21/24
to DSpace Technical Support
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.

We are getting a whitelabel error page for some items when we try to download a bitstream from the item page. We are unable to identify why only some items are impacted.

Has anyone else solved this problem?

The error message as below:

Whitelabel Error Page

This application has no explicit mapping for /error, so you are seeing this as a fallback.

Tue May 21 17:22:16 AEST 2024
There was an unexpected error (type=Internal Server Error, status=500).
An exception has occurred

Thanks and Regards,
Akshay Karthik Thana Sekar

Daan Lessing

unread,
May 21, 2024, 4:56:37 AM5/21/24
to akshay ts, dspac...@googlegroups.com
Good morning Akshay,

In your local.cfg in you dspace/config directory there is an option where you set the directory for the assetstore:

# Assetstore configurations have moved to config/modules/assetstore.cfg
# and config/spring/api/bitstore.xml.
# Additional storage options (e.g. Amazon S3) are available in `assetstore.cfg`
# assetstore.dir = ${dspace.dir}/assetstore

Do not enable it here as it is also included at the bottom of the local.cfg file:
include = ${module_dir}/assetstore.cfg

If you enabled it in both places you will get the whitelabel error.

I hope this helps.

Kind regards,
Daan





Mailtrack Sender notified by
Mailtrack
21/05/24, 10:55:00

--
All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx
---
You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/dspace-tech/9d55d095-4b0a-4c5e-8af0-12bab6b595f7n%40googlegroups.com.

akshay ts

unread,
May 21, 2024, 8:41:44 AM5/21/24
to DSpace Technical Support
Hi Daan,

Thank you for your quick update.

I double checked it. Assetstore is already commented out in my local.cfg.

I am not sure why we are still facing the issue.

I see an error "Cannot invoke "org.dspace.storage.bitstore.BitStoreService.isInitialized()" because "bitStoreService" is null". I am not sure whether it could be related to it. We use local assetstores not s3.

I shall raise a separate thread to discuss this issue.

Regards,
Akshay Karthik Thana Sekar

Michael Plate

unread,
May 21, 2024, 9:04:29 AM5/21/24
to dspac...@googlegroups.com
Try hardcoding (full path instead Variables in
config/spring/api/bitstore.xml)

Am 21.05.24 um 14:41 schrieb akshay ts:

akshay ts

unread,
May 22, 2024, 7:07:23 AM5/22/24
to DSpace Technical Support
Hi Michael,

Thank you for your reply.

I did similar to your suggestion.

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 this whitelabel error page and the bitStoreService null.

I have configured the bitstore.xml now and there is no more whitelabel error page.

Regards,
Akshay Karthik Thana Sekar
Reply all
Reply to author
Forward
0 new messages