Hi,
Thank you for the suggestion I've tried it.
I am re-install the yarn and also node but it still didn't fix the problem
and I just notice, every time i tried to "yarn run build:prod" the error
always different. But it still said invalid token, But the error line/file
is always different
I can confirm the same problem.
The dspace logs offer no clue -- everything looks normal there.
In the javascript console (and in the apache logs) the failing request is
the same:
https://yyy.xxx.edu/server/api/core/bitstreams/fe32d1f1-5e85-43b8-85d9-471b113d504f/content
This is the correct
Hi,
we have exactly the same problem on our DSpace CRIS 2023.01.00. I
suspect that it is a CRIS-specific problem. We currently just always
run the job with the "-b" Option, which is OK as our repo is still
quite small.
I spent some time digging and looking
Hi Gladys,
can you share your init.d script?
BR
Maruan
Gladys Vanesa Fernandez schrieb am Dienstag, 30. Januar 2024 um 15:40:29
UTC+1:
> Hi Maruan, from the directory, Solr is running correctly
>
> El martes, 30 de enero de 2024 a las 11:31:20 UTC-3, Maruan Sahyoun
> escribió:
>
>> Hello
Hi Maruan, from the directory, Solr is running correctly
El martes, 30 de enero de 2024 a las 11:31:20 UTC-3, Maruan Sahyoun
escribió:
> Hello Gladys,
>
> did you try starting SOLR manually from it's bin directory? Does that work
> without any issues?
>
> With kind regards
>
> Maruan
>
Hello Gladys,
did you try starting SOLR manually from it's bin directory? Does that work
without any issues?
With kind regards
Maruan
FileAffairs GmbH
Gladys Vanesa Fernandez schrieb am Dienstag, 30. Januar 2024 um 13:58:42
UTC+1:
> Hello everyone, I'm having an issue with Solr that stopped
Hello everyone, I'm having an issue with Solr that stopped working on its
own. I've already performed various processes, such as uninstalling and
reinstalling it, changing ownership, etc., but it always throws the same
error:
solr.service - LSB: Controls Apache Solr as a Service
Loaded:
