Re: [dspace-tech] 500 - Service unavailable

['Eike Martin Löhden' via DSpace Technical Support]

Hei,

a 500 error normally means, that the backend can't reach the frontend. 
You can try to run "yarn test:rest" to check, if the backend is 
available. Apart from this further help is difficult due to the lack of 
further information. I can only recommend to follow the troubleshoot 
guide: https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error


Kind regards,
Eike Löhden.

Am 11.09.23 um 06:47 schrieb deeksha:

Hello everyone,

I'm trying to install dspace 7.5 on my system but getting a 500 error 
with my UI. Refer to

the following attachment which contains the image of the UI.
Can someone help out with this?


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/6a666812-0990-4f84-9b06-8c04e8b71acbn%40googlegroups.com 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/d1f47954-0f1a-a07a-4ee9-e0ba79b00644%40staff.uni-marburg.de.

[dspace-tech] Re: solr error importing stats

[James Holobetz]

(I sent it early be mistake)

https://mail.google.com/mail/u/0/?tab=rm#search/Exception+writing+document+id/FMfcgzGtvsbMhlrcPsHZXVSJjRcZSsvW

https://stackoverflow.com/questions/37070593/how-to-deal-with-document-contains-at-least-one-immense-term-in-solr


1) What would cause this (on the production machine)?

2) How do I resolve this issue?

Thank you

On Mon, Sep 11, 2023 at 2:46 PM James Holobetz  wrote:

> I am moving data from our production dspace 7.6 server to our development
> dspace 7.6 server and I am repeatedly receiving this error:
>
> holobetj dspace $ dsp /opt/dspace/bin/dspace solr-import-statistics -c
> No index name provided, defaulting to "statistics".
> Exception: Error from server at http://localhost:8983/solr/statistics:
> Exception writing document id 01072706-6b8a-420d-9bc0-cc637bce3df4 to the
> index; possible analysis error: Document contains at least one immense term
> in field="query" (whose UTF8 encoding is longer than the max length 32766),
> all of which were skipped.  Please correct the analyzer to not produce such
> terms.  The prefix of the first immense term is: '[117, 110, 101, 120, 105,
> 115, 116, 105, 110, 103, 47, 46, 46, 47, 46, 46, 47, 46, 46, 47, 46, 46,
> 47, 46, 46, 47, 46, 46, 47, 46]...', original message: bytes can be at most
> 32766 in length; got 34396. Perhaps the document has an indexed string
> field (solr.StrField) which is too large
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException:
> Error from server at http://localhost:8983/solr/statistics: Exception
> writing document id 01072706-6b8a-420d-9bc0-cc637bce3df4 to the index;
> possible analysis error: Document contains at least one immense term in
> field="query" (whose UTF8 encoding is longer than the max length 32766),
> all of which were skipped.  Please correct the analyzer to not produce such
> terms.  The prefix of the first immense term is: '[117, 110, 101, 120, 105,
> 115, 116, 105, 110, 103, 47, 46, 46, 47, 46, 46, 47, 46, 46, 47, 46, 46,
> 47, 46, 46, 47, 46, 46, 47, 46]...', original message: bytes can be at most
> 32766 in length; got 34396. Perhaps the document has an indexed string
> field (solr.StrField) which is too large
>
>
> Looking in  the forums here I have seen the error very rarely:
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAAosP7WobVcztc2HfkBfYy7BkJz6O6mtbYLy7895mj2crmQJiQ%40mail.gmail.com.

[dspace-tech] solr error importing stats

[James Holobetz]

I am moving data from our production dspace 7.6 server to our development
dspace 7.6 server and I am repeatedly receiving this error:

holobetj dspace $ dsp /opt/dspace/bin/dspace solr-import-statistics -c
No index name provided, defaulting to "statistics".
Exception: Error from server at http://localhost:8983/solr/statistics:
Exception writing document id 01072706-6b8a-420d-9bc0-cc637bce3df4 to the
index; possible analysis error: Document contains at least one immense term
in field="query" (whose UTF8 encoding is longer than the max length 32766),
all of which were skipped.  Please correct the analyzer to not produce such
terms.  The prefix of the first immense term is: '[117, 110, 101, 120, 105,
115, 116, 105, 110, 103, 47, 46, 46, 47, 46, 46, 47, 46, 46, 47, 46, 46,
47, 46, 46, 47, 46, 46, 47, 46]...', original message: bytes can be at most
32766 in length; got 34396. Perhaps the document has an indexed string
field (solr.StrField) which is too large
org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error
from server at http://localhost:8983/solr/statistics: Exception writing
document id 01072706-6b8a-420d-9bc0-cc637bce3df4 to the index; possible
analysis error: Document contains at least one immense term in
field="query" (whose UTF8 encoding is longer than the max length 32766),
all of which were skipped.  Please correct the analyzer to not produce such
terms.  The prefix of the first immense term is: '[117, 110, 101, 120, 105,
115, 116, 105, 110, 103, 47, 46, 46, 47, 46, 46, 47, 46, 46, 47, 46, 46,
47, 46, 46, 47, 46, 46, 47, 46]...', original message: bytes can be at most
32766 in length; got 34396. Perhaps the document has an indexed string
field (solr.StrField) which is too large


Looking in  the forums here I have seen the error very rarely:

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAAosP7WAoGGjXx_dCn%3DQzv1LQ%2Bxukv27RRR43WKLC40Ngp2fxg%40mail.gmail.com.

[dspace-tech] Customize Messages.properties

[Lucas Silveira]

Dear colleagues,
In version 6, if it was necessary to customize the labels, simply take the 
file for example: Messages_pt_BR.properties, customize it and then place 
the file in dspaceDir/webbapps/jspui/WEB-INF/classes
I'm assuming that dspaceDir is where dspace was installed.
In version 7, does this continue the same way or does it need to be done 
differently?

Thanks in advance.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/f4dae64d-57bc-43eb-8975-26f4a0e8d7a0n%40googlegroups.com.

[dspace-tech] Link/USL to bitstreams missing in simple page

[Mustaqeem Abdullah]

Hi,

The situation is, when i go to certain record, I can see the download link 
from simple page, just under the thumbnail. but after that if i come again 
to the record or try to open another records, the download link just 
dissapear. I try reload the page, it does appear for just a moment before 
went missing again. do anyone here know why is this happening?

for your information, i already try clearing cache, browser history, using 
private browser. it is always working for a while before it comes again.

Thank you!

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/cd84947a-9671-482a-a740-77cfe4deea46n%40googlegroups.com.

[dspace-tech] Test running handle server in Dspace

[dataquest]

Hello everybody.

I tried to run DSpace handle server (with current codebase from GitHub)
according to the guide
https://wiki.lyrasis.org/display/DSDOC7x/Handle.Net+Registry+Support

I failed to make it run, due to NullPointerException in HandlePlugin class:

"2023-09-08 16:50:33.267+0200" 25 Handle.net Server Software version 9.3.0
java.lang.NullPointerException
at org.dspace.handle.HandlePlugin.haveNA(HandlePlugin.java:397)
at net.handle.server.HandleServer.storageHaveNA(HandleServer.java:3640)
at
net.handle.server.HandleServer.applyAutoHomedPrefixes(HandleServer.java:692)
at net.handle.server.HandleServer.start(HandleServer.java:639)
at net.handle.server.Main.start(Main.java:288)
at net.handle.server.Main.main(Main.java:123)
Shutting down...

I wanted to run it with some random handle prefix as a test. I am not sure
if that is possible,
and if it could be causing this error.

My questions therefore are:

   1. What could cause this problem? Can it be non-existent/invalid handle
   prefix?
   2. Is it possible to somehow test run the handle server?
   3. If I manage to get it up running, how can I check if it works?

I failed to find that information in the guide. It might be also useful to
specify a bit more
clearly how to edit config.dct or perhaps add an example with specific
handle.

When I tried to find information about this, I only found old and/or not
relevant
mails and articles. If such resource exists, please just point me in the
right direction.
Many thanks in advance.

With regards,
Majo Berger


marian.ber...@dataquest.sk 

dataquest s.r.o.

Veľká Okružná 26A, 010 01 Žilina

www.dataquest.sk



[image: image.png]

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/CAJ98do7nYkoTqwaNPp14%3DvGYPOj%3D2cUTvDdgutgQMuin751jzw%40mail.gmail.com.

Re: [dspace-tech] Large number of info-messages in log-file after accessing a collection.

['Eike Martin Löhden' via DSpace Technical Support]

Hei,

a short update to the problem. The error message at the end had nothing 
to do with the initial problem. It was just a wrong configuration in my 
virtual-medata.xml.


Kind regards,
Eike.

Am 11.09.23 um 08:52 schrieb 'Eike Martin Löhden' via DSpace Technical 
Support:


God morning!

I'm currently stuck on a problem with my dspace 7.6 instance. After a 
migration to a new server, I discovered the following problem. If I 
tried to access a collection with 100 or more items, the loading 
process became quite long and my backend logs (dspace.log) started to 
fire a hundreds of /INFO/ messages, with the following content:


2023-09-08 07:33:52,598 INFO 5b4796a9-01a8-4695-b036-db4bfe7a0687 
0c6004e9-b0ba-4cb4-a7b7-42079b79c761 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before 
request [GET /server/api/core/relationships/search/byLabel] originated 
from /collections/b52738a9-790d-44f7-b9e9-1e07977b8dd8


and one /ERROR/ at the end:

2023-09-08 07:34:30,393 ERROR 5b4796a9-01a8-4695-b036-db4bfe7a0687 
7077926b-486b-4002-87f9-7e6258ba13f7 
org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue 
was attempted to construct with MetadataField for parameters: 
metadataschema: person, metadataelement: contributor, 
metadataqualifier: other


I looked through the logs of the DB, SOLR and the browser console, but 
I did not find anything like a Warning or Error. DSpace runs in a 
docker-based container setting and I'm using postgresql 15.2 and solr 
9.3. I already redid the migration process (based on the descriptions 
in the DSpace-Wiki).


Has anyone seen or experienced something similar?

Kind regards,
Eike.

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/691d6eb2-071d-49df-2689-3b1699a0cb62%40staff.uni-marburg.de 
.


--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/53ce9cee-90cb-703c-2fc9-33a4bc1fe7d5%40staff.uni-marburg.de.

[dspace-tech] Large number of info-messages in log-file after accessing a collection.

['Eike Martin Löhden' via DSpace Technical Support]

God morning!

I'm currently stuck on a problem with my dspace 7.6 instance. After a 
migration to a new server, I discovered the following problem. If I 
tried to access a collection with 100 or more items, the loading process 
became quite long and my backend logs (dspace.log) started to fire a 
hundreds of /INFO/ messages, with the following content:


2023-09-08 07:33:52,598 INFO 5b4796a9-01a8-4695-b036-db4bfe7a0687 
0c6004e9-b0ba-4cb4-a7b7-42079b79c761 
org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
[GET /server/api/core/relationships/search/byLabel] originated from 
/collections/b52738a9-790d-44f7-b9e9-1e07977b8dd8


and one /ERROR/ at the end:

2023-09-08 07:34:30,393 ERROR 5b4796a9-01a8-4695-b036-db4bfe7a0687 
7077926b-486b-4002-87f9-7e6258ba13f7 
org.dspace.content.RelationshipMetadataServiceImpl @ A MetadataValue was 
attempted to construct with MetadataField for parameters: 
metadataschema: person, metadataelement: contributor, metadataqualifier: 
other


I looked through the logs of the DB, SOLR and the browser console, but I 
did not find anything like a Warning or Error. DSpace runs in a 
docker-based container setting and I'm using postgresql 15.2 and solr 
9.3. I already redid the migration process (based on the descriptions in 
the DSpace-Wiki).


Has anyone seen or experienced something similar?

Kind regards,
Eike.

--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/691d6eb2-071d-49df-2689-3b1699a0cb62%40staff.uni-marburg.de.


smime.p7s
Description: S/MIME Cryptographic Signature