[dspace-tech] Re: Dspace 7.6.1 Batch import via SAF fails due to "invalid" imports directory

[Mohammad S. AlMutairi]

Hi Matthias,

It's not the SAF files but my guess it's happening because of a corrupted 
zip file so check it using the 7zip package. Have it install in the server 
and check the zip file for its integrity.

*** You can force the extraction of the zip file using 7zip even with the 
issue it has ( Watch for any errors during the extraction phase ) and then 
import the SAF files from a directory.

Good luck,

Mo.

On Friday, February 2, 2024 at 4:04:13 PM UTC+3 Matthias Letsch wrote:

> Hi there,
>
> I am trying to import prepared SAF files via batch import. With another 
> subset in other collections, this worked wonderfully just yesterday. So it 
> can't be the SAF files, they follow exactly the same pattern (zip with 
> folders containing xyz.pdf, dublin_core.xml and contents referring to pdf 
> file.
>
> Today, however, I get an error message (This is now a dedicated test 
> import into a newly created collection TEST):
>
> ###:~/dspace-backend/bin$ ./dspace import -a -e ###@###.de -s ~/ojs-import 
> -z 10.zip -c 12345678
> 9/5103 -m ~/ojs-import/mapfiles/test10;
> The script has started
> Destination collections:
> Owning Collection: TEST
> '/home/dspace/dspace-backend/imports' as defined by the key 
> 'org.dspace.app.batchitemimport.work.dir' in dspace.cfg is not a valid 
> directory
> Started: 1706876840214
> Ended: 1706876846622
> Elapsed time: 6 secs (6408 msecs)
> java.lang.Exception: Error committing changes to database: Error, cannot 
> open source directory 
> /home/dspace/dspace-backend/imports/importSAF/43013a47-6076-432a-959d-9805240a43ae/10.zip,
>  
> aborting most recent changes
> at 
> org.dspace.app.itemimport.ItemImport.internalRun(ItemImport.java:233)
> at org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:150)
> at 
> org.dspace.app.launcher.ScriptLauncher.executeScript(ScriptLauncher.java:154)
> at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:132)
> at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:99)
> Caused by: java.lang.Exception: Error, cannot open source directory 
> /home/dspace/dspace-backend/imports/importSAF/43013a47-6076-432a-959d-9805240a43ae/10.zip
> at 
> org.dspace.app.itemimport.ItemImportServiceImpl.addItems(ItemImportServiceImpl.java:278)
> at 
> org.dspace.app.itemimport.ItemImportCLI.process(ItemImportCLI.java:92)
> at 
> org.dspace.app.itemimport.ItemImport.internalRun(ItemImport.java:226)
> ... 4 more
>
> As I understand it, there is some problem with the folder 
> (dspace-dir)/imports, which exists exactly as it is defined in dspace.cfg.
>
> If I create a new, different folder in the backend and then change this in 
> dspace.cfg (plus restart tomcat), the result unfortunately looks exactly 
> the same.
>
> Does anyone know how to fix this problem?
>
> Thank you and kind regards
> Matthias
>

-- 
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/cea4f41e-a75e-4abb-bb0f-0c918c680712n%40googlegroups.com.

[dspace-tech] Re: Help starting Handle server automatically after reboot?

[Mohammad S. AlMutairi]

Hi Night Librarian,

Before you begin just make sure the handle server is down and just copy and 
paste the text you see in red below into the terminal and do the other 
steps to enable the service and start it. Also, make sure the owner and the 
group permissions on the dspace and the handle-server folders ( ls -ld 
/opt/dspace /opt/dspace/handle-server/ ) match the user you run the tomcat9 
service with in your server ( cat /usr/lib/systemd/system/tomcat9.service ).
 

1) sudo -i

2) 
cat << EOF > /usr/lib/systemd/system/handle-server.service
[Unit]
Description=Handle Service
After=network.target tomcat9.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/opt/dspace/bin/start-handle-server
ExecStop=/bin/kill \$MAINPID
User=tomcat
Group=tomcat

[Install]
WantedBy=multi-user.target

EOF

2) systemctl daemon-reload
3) systemctl enable handle-server.service
4) systemctl start handle-server.service
5) systemctl status handle-server.service

***  If you succussed in running the service manually as in step 4 above 
then the handle service should be started during the boot time. 
Check /opt/dspace/handle-server/logs/error.log-* for any hints about what's 
going on.

Hoe it helps.

BR,

Mo.

On Friday, August 25, 2023 at 6:50:32 PM UTC+3 Night Librarian wrote:

> Perhaps someone knows the answer to this question or could nudge me in a 
> right direction?
>
>
> On Friday, August 18, 2023 at 1:18:32 p.m. UTC-3 Night Librarian wrote:
>
> Greetings!
>
> I have DSpace 7.4 on Ubuntu 20.04.  Handle server is running fine, but 
> after a system reboot it doesn't come up automatically, so I have to start 
> it manually.  I looked at a suggestion  by Mohammad S. AlMutairi from an 
> older conversation and edited my  /etc/systemd/system/handle-server.service 
> to looks like this:
>
> ===
> [Unit]
> Description=Handle Service
> After=network.target tomcat9.service
>
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> ExecStart=/dspace/bin/start-handle-server
> ExecStop=/bin/kill $MAINPID
> User=tomcat
> Group=tomcat
>
> [Install]
> WantedBy=multi-user.target
> ===
>
> However, after the system reboot, handle-server still doesn't come up by 
> itself.  I must add that I need to add "sudo" in order to start Handle 
> server manually:
>
>  sudo /dspace/bin/start-handle-server
>
> Did I mess the handle-server.service file or is there something else I 
> need to do with permissions or otherwise?
>
>

-- 
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/f2fc2f81-ee18-4c80-b913-6b02ec33532dn%40googlegroups.com.

Re: [dspace-tech] Migration Help from 6.3 to 7.5

[Mohammad S. AlMutairi]

All you need after importing the database properly into the new server is 
to run  [dspace]/bin//dspace database migrate ignored on the new server and 
just copy the assetstore folder from the old server to the new one and 
finally do a discovery index by running [dspace]/bin/dspace index-discovery 
-b . Check Tim's comments/explanations in the following 
thread https://groups.google.com/g/dspace-tech/c/_7XI9xmwpI8/m/CH__FIU_AwAJ 
and this one 
too https://groups.google.com/g/dspace-tech/c/_7XI9xmwpI8/m/DvYbGKx3AgAJ 
... Ignore any other comments in that thread and only apply what matches 
the issue you have so you don't get it confused.

Mo.

On Tuesday, June 20, 2023 at 11:08:56 PM UTC+3 Michel Montenegro wrote:

> Mohammad S. AlMutairi I ran the instructions and the dump and restore went 
> flawlessly with no errors.
>
> When running "dspace database info" the result seems correct, however it 
> had two IGNORED instead of success. (See attached image 
> "Dump_Restore_Sucess6x_and_2Ignore.png")
>
> I attached the two logs referring to the commands "dspace database 
> update-sequences" e "dspace database migrate ignored".
>
> Em sáb., 17 de jun. de 2023 às 04:04, Mohammad S. AlMutairi <
> alo...@gmail.com> escreveu:
>
>> Correction:  # You need to change the bin folder path in step 1 & 5 to 
>> match yours.
>>
>> On Saturday, June 17, 2023 at 9:55:33 AM UTC+3 Mohammad S. AlMutairi 
>> wrote:
>>
>>> On Friday, June 16, 2023 at 11:44:22 AM UTC+3 Michel Montenegro wrote:
>>>
>>> The problem seems to be at the base of 6.3 (At this moment I don't know 
>>> how the team's DBAs solved it when generating the dump), but we managed to 
>>> start the migration, however during the migration it stopped and generated 
>>> the following error (The 6.3 database this one being migrated had nothing 
>>> added, it's the 6.3 core ):
>>>
>>>  Hi All,
>>> It seems all the issues you are facing in your migration is caused of 
>>> how the the old database is exported and imported in the new server. Just 
>>> make sure before following the steps you see below the pgcrypto extension 
>>> was created on the database in the old server and not add into the 
>>> extensions schema. Once you sucessed on importing the database follow the 
>>> other steps in the link Tim provided 
>>> https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server
>>>
>>> # You need to change the bin folder path in step 2 & 6 to match yours.
>>> 1) cd "C:\Program Files\PostgreSQL\9.13\bin"
>>> 2) .\pg_dump -U postgres -W -h localhost -Fc -v -C -E UTF8 -d dspace -f 
>>> C:\dspace-63.sql
>>> 3) Move dspace-63.sql file to the new dspace server
>>>
>>> On the new dspace server execute:
>>> 1) psql --username=postgres dspace
>>> 2) DROP EXTENSION pgcrypto;
>>> 3) DROP SCHEMA extensions;
>>> 4) \q
>>> 5) cd "C:\Program Files\PostgreSQL\13\bin"
>>> 6) .\pg_restore -U postgres -W -h localhost -v -e -c --if-exists -d 
>>> dspace C:\dspace-63.sql
>>> 7) psql --username=postgres dspace
>>> 8) \dn
>>> 9) \dx
>>> 10) \q
>>>  
>>> Hope it helps.
>>>
>>> Mo.
>>>
>>> -- 
>> 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/f26b09c5-cdfa-4970-8ea8-1076f21323abn%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dspace-tech/f26b09c5-cdfa-4970-8ea8-1076f21323abn%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>
>
> -- 
> Atenciosamente, 
> *Michel Pinheiro Montenegro*
> - *Bacharel* em Sistema de Informação
> - [Lato Sensu] *Especialista* em Engenharia de Sistemas
> - [Stricto Sensu] *Mestre* em Ciência da Computação
> - [Stricto Sensu] *Doutorando* em Ciência da Computação
>
> E-mail/Gtalk: michel.m...@gmail.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/46253e26-287c-4f80-8a4c-a81f3b41ac1fn%40googlegroups.com.

Re: [dspace-tech] Migration Help from 6.3 to 7.5

[Mohammad S. AlMutairi]

Correction:  # You need to change the bin folder path in step 1 & 5 to 
match yours.

On Saturday, June 17, 2023 at 9:55:33 AM UTC+3 Mohammad S. AlMutairi wrote:

> On Friday, June 16, 2023 at 11:44:22 AM UTC+3 Michel Montenegro wrote:
>
> The problem seems to be at the base of 6.3 (At this moment I don't know 
> how the team's DBAs solved it when generating the dump), but we managed to 
> start the migration, however during the migration it stopped and generated 
> the following error (The 6.3 database this one being migrated had nothing 
> added, it's the 6.3 core ):
>
>  Hi All,
> It seems all the issues you are facing in your migration is caused of how 
> the the old database is exported and imported in the new server. Just make 
> sure before following the steps you see below the pgcrypto extension was 
> created on the database in the old server and not add into the extensions 
> schema. Once you sucessed on importing the database follow the other steps 
> in the link Tim provided 
> https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server
>
> # You need to change the bin folder path in step 2 & 6 to match yours.
> 1) cd "C:\Program Files\PostgreSQL\9.13\bin"
> 2) .\pg_dump -U postgres -W -h localhost -Fc -v -C -E UTF8 -d dspace -f 
> C:\dspace-63.sql
> 3) Move dspace-63.sql file to the new dspace server
>
> On the new dspace server execute:
> 1) psql --username=postgres dspace
> 2) DROP EXTENSION pgcrypto;
> 3) DROP SCHEMA extensions;
> 4) \q
> 5) cd "C:\Program Files\PostgreSQL\13\bin"
> 6) .\pg_restore -U postgres -W -h localhost -v -e -c --if-exists -d dspace 
> C:\dspace-63.sql
> 7) psql --username=postgres dspace
> 8) \dn
> 9) \dx
> 10) \q
>  
> Hope it helps.
>
> Mo.
>
>

-- 
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/f26b09c5-cdfa-4970-8ea8-1076f21323abn%40googlegroups.com.

Re: [dspace-tech] Migration Help from 6.3 to 7.5

[Mohammad S. AlMutairi]

On Friday, June 16, 2023 at 11:44:22 AM UTC+3 Michel Montenegro wrote:

The problem seems to be at the base of 6.3 (At this moment I don't know how 
the team's DBAs solved it when generating the dump), but we managed to 
start the migration, however during the migration it stopped and generated 
the following error (The 6.3 database this one being migrated had nothing 
added, it's the 6.3 core ):

 Hi All,
It seems all the issues you are facing in your migration is caused of how 
the the old database is exported and imported in the new server. Just make 
sure before following the steps you see below the pgcrypto extension was 
created on the database in the old server and not add into the extensions 
schema. Once you sucessed on importing the database follow the other steps 
in the link Tim 
provided 
https://wiki.lyrasis.org/display/DSDOC7x/Migrating+DSpace+to+a+new+server

# You need to change the bin folder path in step 2 & 6 to match yours.
1) cd "C:\Program Files\PostgreSQL\9.13\bin"
2) .\pg_dump -U postgres -W -h localhost -Fc -v -C -E UTF8 -d dspace -f 
C:\dspace-63.sql
3) Move dspace-63.sql file to the new dspace server

On the new dspace server execute:
1) psql --username=postgres dspace
2) DROP EXTENSION pgcrypto;
3) DROP SCHEMA extensions;
4) \q
5) cd "C:\Program Files\PostgreSQL\13\bin"
6) .\pg_restore -U postgres -W -h localhost -v -e -c --if-exists -d dspace 
C:\dspace-63.sql
7) psql --username=postgres dspace
8) \dn
9) \dx
10) \q
 
Hope it helps.

Mo.

-- 
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/19566015-f013-4ee6-a77e-f66cd96c288an%40googlegroups.com.

[dspace-tech] Re: DSpace 7.2.1 OAI-PMH Internal Server Error 500 - Log: "OAI 2.0 wasn't correctly initialized"

[Mohammad S. AlMutairi]

Hello Matthias,

It's very likely the culprit is the DSpace version 7.2 you have installed 
and you work on. I think most of the issues including this one you reported 
will go away if you install the latest DSpace version available which is 
7.5. Check Eike Martin Löhden 
thread https://groups.google.com/g/dspace-tech/c/MuACOZ1MpbU/m/jsODicr2BQAJ

Hope it helps

Mo.

On Thursday, June 15, 2023 at 2:24:11 PM UTC+3 Matthias Letsch wrote:

> Hello there,
>
> I am setting up DSpace 7.2 as an institutional repository for a University.
>
> The OAI-PMH interface has some internal server Error. I am aware that 
> there are already some threads regarding this topic, but none of them seem 
> to quite fit my problem. I did run the ./dspace oai import -c task before 
> and that task was "successful". However, the OAI page at 
> .../server/oai/request?verb=Identify tells me:
>
> *Whitelabel Error Page*
>
> *This application has no explicit mapping for /error, so you are seeing 
> this as a fallback.*
> *Thu Jun 15 11:38:39 CEST 2023*
> *There was an unexpected error (type=Internal Server Error, status=500).*
> *An exception has occurred*
>
> The logs report the errors stated below.
>
> Among those is for example "OAI 2.0 wasn't correctly initialized, please 
> check the log for previous errors" --> I honestly don't know how to 
> "correctly initialize" OAI 2.0 and I didn't find any previous errors 
> regarding OAI. The configuration in /config/modules/oai.cfg seems to be 
> okay, also the /config/crosswalks/oai/xoai.xml, but I didn't find a xsl 
> stylesheet anywhere (xoai.xml refers to static/style.xsl)
>
> Can anyone do anything with the info here or maybe knows the problem and 
> can help me? Thanks a lot!
>
> Kind regards,
> Matthias
>
> The logs entries:
>
> 2023-06-14 
>
> 2023-06-14 10:09:04,418 ERROR unknown 84b90674-ce4a-4030-b1a9-58fde903f366 
> org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An 
> exception has occurred (status:500)
> javax.servlet.ServletException: OAI 2.0 wasn't correctly initialized, 
> please check the log for previous errors
> at (...)
> Caused by: 
> org.dspace.xoai.services.api.config.XOAIManagerResolverException: 
> com.lyncode.xoai.dataprovider.exceptions.ConfigurationException: 
> net.sf.saxon.s9api.SaxonApiException: Errors were reported during 
> stylesheet compilation
> at (...)
> Caused by: 
> com.lyncode.xoai.dataprovider.exceptions.ConfigurationException: 
> net.sf.saxon.s9api.SaxonApiException: Errors were reported during 
> stylesheet compilation
>  at (...)
> Caused by: javax.xml.transform.TransformerConfigurationException: 
> net.sf.saxon.s9api.SaxonApiException: Errors were reported during 
> stylesheet compilation
>at (...)
> Caused by: net.sf.saxon.s9api.SaxonApiException: Errors were reported 
> during stylesheet compilation
>at (...)
> Caused by: net.sf.saxon.trans.XPathException: Errors were reported during 
> stylesheet compilation
>at (...)
>
> 2023-06-14 10:51:25,071 ERROR unknown unknown 
> org.dspace.xoai.app.BasicConfiguration @ Not able to start XOAI normal 
> cache service.
> org.dspace.xoai.services.api.config.XOAIManagerResolverException: 
> com.lyncode.xoai.dataprovider.exceptions.ConfigurationException: 
> net.sf.saxon.s9api.SaxonApiException: Errors were reported during 
> stylesheet compilation
> at (...)
>
> 2023-06-12
>
> 2023-06-12 14:11:52,342 ERROR unknown f46fee61-e391-4da0-b9ea-0b032209a0ac 
> org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ An 
> exception has occurred (status:500)
> javax.servlet.ServletException: Unable to load XOAI manager, please, try 
> again.
>

-- 
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/ede88224-6b9a-4ae4-bc25-7be765a8ee11n%40googlegroups.com.

Re: [dspace-tech] DSpace 7.5 Solr Statistics migration from 5.10 with sharding by year

[Mohammad S. AlMutairi]

You might need to double check the tomcat connector settings.

# You need to replace the Catalina Connector Elements on lines 69,70 and 71 
with the connector elements you see below.
 edit /etc/tomcat9/server.xml



Hope it helps.

Mo.

On Sunday, June 11, 2023 at 11:35:12 PM UTC+3 Nicholas Woodward wrote:

> Has this approach of importing all previous year's statistics into the 
> "statistics" Solr core worked for others who have a lot of stats? For the 
> last few days I've been trying to import all of the exported statistics 
> files below after renaming the beginning of each CSV file to 
> "statistics--...", but no matter how high I set the 
> `http.socket.timeout` parameter in Solr I get the 
> SocketTimeoutException error below when importing the last ZIP file 
> (statistics.zip). 
>
> I'm working with the most recent code on the main branch of the DSpace 
> repository. I've increased the Java memory given to Solr to 2GB and added 
> the same amount to the `bin/dspace` command, but that didn't seem to help, 
> and in some cases made things worse. At the time that I get the socket 
> timeout error and the import-statistics process stops running the 
> "statistics" core usually has anywhere from 20-30 million docs in the 
> index. 
>
> Error message: 
>
> Problem encountered while trying to import index statistics.
> org.apache.solr.client.solrj.SolrServerException: Timeout occurred while 
> waiting response from server at: http://localhost:8983/solr/statistics
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:692)
>
>
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:266)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.request(HttpSolrClient.java:248)
>
> at org.apache.solr.client.solrj.SolrClient.request(SolrClient.java:1290)
> at org.dspace.util.SolrImportExport.importIndex(SolrImportExport.java:465)
>
>
> at org.dspace.util.SolrImportExport.main(SolrImportExport.java:148)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77)
> at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:568)
> at 
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:277)
> at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:133)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98)
>
> Caused by: java.net.SocketTimeoutException: Read timed out
> at java.base/sun.nio.ch.NioSocketImpl.timedRead(NioSocketImpl.java:283)
> at java.base/sun.nio.ch.NioSocketImpl.implRead(NioSocketImpl.java:309)
> at java.base/sun.nio.ch.NioSocketImpl.read(NioSocketImpl.java:350)
> at java.base/sun.nio.ch.NioSocketImpl$1.read(NioSocketImpl.java:803)
> at java.base/java.net.Socket$SocketInputStream.read(Socket.java:966)
> at 
> org.apache.http.impl.io.SessionInputBufferImpl.streamRead(SessionInputBufferImpl.java:137)
> at 
> org.apache.http.impl.io.SessionInputBufferImpl.fillBuffer(SessionInputBufferImpl.java:153)
> at 
> org.apache.http.impl.io.SessionInputBufferImpl.readLine(SessionInputBufferImpl.java:280)
> at 
> org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:138)
> at 
> org.apache.http.impl.conn.DefaultHttpResponseParser.parseHead(DefaultHttpResponseParser.java:56)
> at 
> org.apache.http.impl.io.AbstractMessageParser.parse(AbstractMessageParser.java:259)
> at 
> org.apache.http.impl.DefaultBHttpClientConnection.receiveResponseHeader(DefaultBHttpClientConnection.java:163)
> at 
> org.apache.http.impl.conn.CPoolProxy.receiveResponseHeader(CPoolProxy.java:157)
> at 
> org.apache.http.protocol.HttpRequestExecutor.doReceiveResponse(HttpRequestExecutor.java:273)
> at 
> org.apache.http.protocol.HttpRequestExecutor.execute(HttpRequestExecutor.java:125)
> at 
> org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:272)
> at 
> org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:186)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:89)
> at 
> org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:110)
> at 
> org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:185)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:83)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:56)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrClient.executeMethod(HttpSolrClient.java:571)
> ... 12 more
>
>
> Statistics files:
>
> 52MB Jun  7 08:54 statistics-2014.zip
>
> 130MB Jun  7 08:58 statistics-2015.zip
>
> 222MB Jun  7 09:05 statistics-2017.zip
>
> 46MB Jun  7 09:06 statistics-2018.zip
>
> 300MB Jun  7 09:15 statistics-2019.zip
>
> 

Re: [dspace-tech] Re: Gnome ubuntu stuck

[Mohammad S. AlMutairi]

It's an OS issue and for sure it's fixable but without more in-depth 
details I'm shooting in the dark. Trying to help. Try the steps you see 
below in the sequence you see it:

1) sudo truncate -s 0 
/var/lib/ubuntu-release-upgrader/release-upgrade-available
2) sudo dpkg-reconfigure dash
** make sure to choose no when prompted if you want to (Use dash as the 
default system shell).
3) ping changelogs.ubuntu.com (make sure if it's resolvable.). If for any 
reason it can't be resolved double check your DNS settings in 
/etc/resolv.conf. You can use google public dns server 8.8.8.8 temporarily.
4) sudo shutdown -r now
5) apt update -y && apt upgrade -y && shutdown -r now
6) You have to upgrade your server to a newer version. You need to.

Hope it helps.

Mo.
On Wednesday, June 7, 2023 at 10:23:10 AM UTC+3 Maya Zbitneva wrote:

> I have Ubuntu 18 LTS and Dspace 6 on another computer which is temporary 
> web server and not real web server. And I have not any such problem which I 
> described above.
>
> вівторок, 6 червня 2023 р. о 18:58:23 UTC+3 Mohammad S. AlMutairi пише:
>
>> Ubuntu 18.04 LTS reached end of life 6 days ago so I think that what's 
>> causing the issues you are facing. Definitely you need to upgrade to a 
>> newer Ubuntu version that still supported or as another option you can buy 
>> an extended commercial support for the 18.04 version you have to keep using 
>> it for a while but still the right decision is to upgrade both the OS and 
>> dspae since dspace 6.x will reach end of life too in less than a month from 
>> now.
>>
>> Mo.
>>
>> On Tuesday, June 6, 2023 at 10:28:05 AM UTC+3 Maya Zbitneva wrote:
>>
>>> It is not problem with Internet/network, because My Academy Dspace 6 
>>> repository has access to Internet, that is I can make access to it through 
>>> Internet from any computer. 
>>>
>>> вівторок, 6 червня 2023 р. о 09:22:39 UTC+3 Sean Carte пише:
>>>
>>>> Looks like you're not connected to the network/internet.
>>>>
>>>> Sean
>>>>
>>>> On Mon, 05 Jun 2023, 14:37 Maya Zbitneva,  wrote:
>>>>
>>>>> After entering to tty2 my login, I have error in terminal tty2 "I have 
>>>>> no name!@repository":
>>>>> [image: tty2.jpg]
>>>>>
>>>>> понедельник, 5 июня 2023 г. в 14:59:33 UTC+3, Maya Zbitneva: 
>>>>>
>>>>>> Good day!
>>>>>>
>>>>>> Help me please to solve the following problem:
>>>>>>
>>>>>> I am administrator of Academy Dspace 6 repository. I have http, not 
>>>>>> https. I have Ubuntu 18. Everything was Ok with my repository. But now I 
>>>>>> have the following problem:
>>>>>>
>>>>>> My graphical environment Gnome of  my Ubuntu systems can start, but I 
>>>>>> do not see login page. Gnome stuck. The last image which I Saw is the 
>>>>>> following:
>>>>>>
>>>>>> [image: gnome.jpg]
>>>>>>
>>>>>> I can press ctrl+C, and saw the following text:
>>>>>>
>>>>>> [image: terminal1.jpg]
>>>>>>
>>>>>> [image: terminal2.jpg]
>>>>>>
>>>>>> I do not know how to enter to graphical environment of my Ubuntu.
>>>>>> I can press Alt+F2 and enter to tty2.
>>>>>>
>>>>>> With respect,
>>>>>> Maiia,
>>>>>> Academy.
>>>>>>
>>>>> -- 
>>>>> 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/65eee39f-d64f-4492-96f1-96f161360d81n%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/dspace-tech/65eee39f-d64f-4492-96f1-96f161360d81n%40googlegroups.com?utm_medium=email_source=footer>
>>>>> .
>>>>>
>>>>

-- 
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/09c9f267-910d-4bbc-8de2-64a36861ee61n%40googlegroups.com.

Re: [dspace-tech] Re: Gnome ubuntu stuck

[Mohammad S. AlMutairi]

Ubuntu 18.04 LTS reached end of life 6 days ago so I think that what's 
causing the issues you are facing. Definitely you need to upgrade to a 
newer Ubuntu version that still supported or as another option you can buy 
an extended commercial support for the 18.04 version you have to keep using 
it for a while but still the right decision is to upgrade both the OS and 
dspae since dspace 6.x will reach end of life too in less than a month from 
now.

Mo.

On Tuesday, June 6, 2023 at 10:28:05 AM UTC+3 Maya Zbitneva wrote:

> It is not problem with Internet/network, because My Academy Dspace 6 
> repository has access to Internet, that is I can make access to it through 
> Internet from any computer. 
>
> вівторок, 6 червня 2023 р. о 09:22:39 UTC+3 Sean Carte пише:
>
>> Looks like you're not connected to the network/internet.
>>
>> Sean
>>
>> On Mon, 05 Jun 2023, 14:37 Maya Zbitneva,  wrote:
>>
>>> After entering to tty2 my login, I have error in terminal tty2 "I have 
>>> no name!@repository":
>>> [image: tty2.jpg]
>>>
>>> понедельник, 5 июня 2023 г. в 14:59:33 UTC+3, Maya Zbitneva: 
>>>
 Good day!

 Help me please to solve the following problem:

 I am administrator of Academy Dspace 6 repository. I have http, not 
 https. I have Ubuntu 18. Everything was Ok with my repository. But now I 
 have the following problem:

 My graphical environment Gnome of  my Ubuntu systems can start, but I 
 do not see login page. Gnome stuck. The last image which I Saw is the 
 following:

 [image: gnome.jpg]

 I can press ctrl+C, and saw the following text:

 [image: terminal1.jpg]

 [image: terminal2.jpg]

 I do not know how to enter to graphical environment of my Ubuntu.
 I can press Alt+F2 and enter to tty2.

 With respect,
 Maiia,
 Academy.

>>> -- 
>>> 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/65eee39f-d64f-4492-96f1-96f161360d81n%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/a6ba49f6-5c34-454c-ac3d-c0267d62dbd4n%40googlegroups.com.

[dspace-tech] Re: Possible to configure maximum embargo length?

[Mohammad S. AlMutairi]

Check line no. 38 in [dspace]/config/spring/api/access-conditions.xml

On Tuesday, June 6, 2023 at 6:18:15 PM UTC+3 tant...@umn.edu wrote:

> I would like to resurrect this question from a couple years ago.
>
> Is there a way to do this in DSpace 7.5?  We would like to enforce a 
> policy such that embargoes can be set for no more than two years.
> Thanks,
> ~~Bill
>
> On Tuesday, March 23, 2021 at 10:15:52 AM UTC-5 Gail Steinhart wrote:
>
>> Greetings, 
>>
>>
>> We are considering implementing embargoes in the user submission 
>> interface (simple, UploadWithEmbargoStep). I am wondering if it is possible 
>> to configure a maximum embargo length, say two years from current date? We 
>> don’t want submitters setting 100 year embargoes. I don’t see anything in 
>> the documentation that tells me this is possible, but wanted to check.
>>
>>  
>>
>> Thank you,
>>
>> Gail
>>
>>  
>>
>> Gail Steinhart
>>
>> Open Scholarship Services Librarian
>>
>> Cornell University Library Information Technology
>>
>> 218 Olin Library | 607.255.7251 <(607)%20255-7251>
>>
>> *https://orcid.org/-0002-2441-1651 
>> * | @gailst 
>>  
>>
>> she/her
>>
>

-- 
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/f96a67f0-fdd1-4a29-8a2a-8e80b2298965n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.4 SSL front-end problems

[Mohammad S. AlMutairi]

Hello Jorge,

That's a wrong way to access or test and chech if the handle server is 
running and the error you saw is expected just ignore it.

1) To help you make systemd take care of running the handle server at boot 
time you need to copy and paste what you see in red below into the terminal 
and just do the other steps to activate it.
sudo cat << EOF > /usr/lib/systemd/system/handle-server.service
[Unit]
Description=Handle Service
After=network.target tomcat9.service

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/opt/dspace/bin/start-handle-server
ExecStop=/bin/kill $MAINPID
User=tomcat
Group=tomcat

[Install]
WantedBy=multi-user.target

EOF

2) systemctl daemon-reload
3) systemctl enable handle-server.service
4) systemctl start handle-server.service
5) systemctl status handle-server.service

Regarding the other issues you mentioned I hope someone else step in and 
help you with them because it needs more details and debugging to approach 
it. Tim? :-).

BR,

Mo.

On Tuesday, March 28, 2023 at 5:07:29 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

> hello good.
>
> I had forgotten that when I restarted the server I had to turn on the 
> server handle again, I only have a question with handle, after configuring 
> the SSL port 8000 of handle gives me this result, could this affect my 
> dspace:
> [image: Captura de pantalla 2023-03-28 080337.png] 
> https://rd.udb.edu.sv:8000/
>
> Also sometimes Angular fails and does not load some pages, giving errors 
> like:
> [image: Captura de pantalla 2023-03-28 080512.png]
>
> and warnings like these:
>
> [image: Captura de pantalla 2023-03-28 080629.png]
>
> before the SSL did not happen, what could be the error on this occasion?
>
> El lunes, 27 de marzo de 2023 a las 15:07:53 UTC-6, Mohammad S. AlMutairi 
> escribió:
>
>> You welcome.
>> Was it stopped?. I don't see any issue with it now. 
>> http://hdl.handle.net/11715/10
>>
>> Mo.
>> On Monday, March 27, 2023 at 10:41:36 PM UTC+3 Jorge Alberto Bonilla 
>> Castaneda wrote:
>>
>>>
>>> Thank you very much , what I have noticed is that the handle does not 
>>> work for me since I made the change , if it worked before , it now throws 
>>> me this error :
>>>
>>> [image: Captura de pantalla 2023-03-27 134059.png]
>>>
>>> what could be the error ? 
>>> El lunes, 27 de marzo de 2023 a las 12:35:04 UTC-6, Mohammad S. 
>>> AlMutairi escribió:
>>>
>>>> You can safely ignore that 404 error. GA is disabled by default in 
>>>> DSpace but if you need to enable it and use it follow the instructions you 
>>>> see here 
>>>> https://wiki.lyrasis.org/display/DSDOC7x/DSpace+Google+Analytics+Statistics#DSpaceGoogleAnalyticsStatistics-GoogleAnalyticsSupport
>>>>
>>>> Mo.
>>>>
>>>> On Monday, March 27, 2023 at 9:09:56 PM UTC+3 Jorge Alberto Bonilla 
>>>> Castaneda wrote:
>>>>
>>>>> wait, I found this forum where instructions were given to fix the bug 
>>>>> I ran into and they worked for me
>>>>> https://groups.google.com/g/dspace-tech/c/ba5O8lIpH1M/m/-ZgLFBOsAgAJ
>>>>>
>>>>> Now I only get a few errors like these, which I hope are not a big deal
>>>>>
>>>>> [image: Captura de pantalla 2023-03-27 120831.png]
>>>>>
>>>>>
>>>>>
>>>>> El lunes, 27 de marzo de 2023 a las 11:24:57 UTC-6, Jorge Alberto 
>>>>> Bonilla Castaneda escribió:
>>>>>
>>>>>> Hello, apply what is mentioned in that forum that I send, that is, 
>>>>>> configure my
>>>>>>
>>>>>> front end : https://rd.udb.edu.sv
>>>>>> backend : https://rd.udb.edu.sv/server/
>>>>>>
>>>>>> with its DNS and corresponding security certificate and with its 
>>>>>> apache configuration, however the back end keeps throwing me an error 
>>>>>> that 
>>>>>> doesn't even let me do searches.
>>>>>>
>>>>>> [image: Captura de pantalla 2023-03-27 112118.png]
>>>>>> what is my mistake now?
>>>>>>
>>>>>>
>>>>>> in my dspace.cfg I have configured the following :
>>>>>> dspace.server.url = https://rd.udb.edu.sv/server
>>>>>> dspace.ui.url = https://rd.udb.edu.sv
>>>>>> rest.cors.allowed-origins = ${dspace.ui.url} 
>>>>>>
>>>>>> in my config.prod.yml the following :
>>>>

[dspace-tech] Re: pgcrypto extension is installed in PostgreSQL 14.7, but reports as not installed on this DATABASE

[Mohammad S. AlMutairi]

Hi Zikrul,

Try this in the sequence you see it.

1) su - postgres
2) psql
3) \password
4) drop database dspace;
5) drop user dspace;
6) drop extension if exists pgcrypto;
7) drop schema extensions;
8) \q
9) createuser --username=postgres --no-superuser --pwprompt dspace
10) createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
11) psql --username=postgres dspace
12) CREATE SCHEMA extensions;
13) CREATE EXTENSION pgcrypto SCHEMA extensions;
14) GRANT USAGE ON SCHEMA extensions TO dspace;
15) SELECT set_config('search_path',current_setting('search_path') || 
',extensions',false) WHERE current_setting('search_path') !~ 
'(^|,)extensions(,|$)';
16) SHOW search_path;
17) ALTER DATABASE dspace SET search_path FROM CURRENT;
18) \q
19) exit
20) systemctl enable postgresql
21) systemctl restart postgresql
22) psql -U dspace -W -h localhost
23) \conninfo
24) \q
25) exit
### Conitune DSpace installation

Hope it help

Mo.

On Tuesday, March 28, 2023 at 4:06:10 PM UTC+3 Zikrul wrote:

> Hi Mohammad,
>
> Many thanks for your prompt reply. I have tried $ant fresh_install after 
> each fix for pgcrypto you have mentioned but issue did not resolved. Any 
> other idea please?
>
> test_database:
>  [java] 2023-03-28 13:59:20,868 WARN 
>  org.dspace.servicemanager.DSpaceServiceManager @ Unable to locate bean by 
> name or id=database. Will try to look up bean by type next.
>
>  [java] 
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
> named 'database' available
>  [java] at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:872)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1344)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1160)
>  
> ~[spring-context-5.3.20.jar:5.3.20]
>  [java] at 
> org.dspace.servicemanager.DSpaceServiceManager.getServiceByName(DSpaceServiceManager.java:426)
>  
> [dspace-services-7.5.jar:7.5]
>  [java] at 
> org.dspace.scripts.ScriptServiceImpl.getScriptConfiguration(ScriptServiceImpl.java:34)
>  
> [dspace-api-7.5.jar:7.5]
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) 
> [dspace-api-7.5.jar:7.5]
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98) 
> [dspace-api-7.5.jar:7.5]
>  [java] 2023-03-28 13:59:21,165 WARN 
>  org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
> recommended: PostgreSQL 15.2 is newer than this version of Flyway and 
> support has not been tested. The latest supported version of PostgreSQL is 
> 14.
>
>  [java]
>  [java] Attempting to connect to database
>  [java] Connected successfully!
>  [java]
>  [java] Database Type: postgres
>  [java] Database URL: jdbc:postgresql://localhost:5432/dspace
>  
> Regards
> Zikrul
> On Tuesday, 28 March 2023 at 13:22:38 UTC+1 Mohammad S. AlMutairi wrote:
>
>> Hi Zikrul,
>>
>> All you need to fix it without having to recreate the pgcrypto extension 
>> using the second method is by adding it into the search path by one of 
>> these commands (  *psql --username=postgres dspace -c 'ALTER ROLE dspace 
>> IN DATABASE dspace SET search_path = "$user",public,extensions,pgcrypto;'* 
>> ) or (  *psql --username=postgres dspace -c 'ALTER DATABASE dspace SET 
>> search_path = "$user",public,extensions,pgcrypto;'* ) and then double 
>> check it to see if it's included by (  *psql --username=postgres dspace 
>> -c 'SHOW search_path;'* ).
>>
>> NB: Creating the pgcrypto extension using the second method will save you 
>> from creating it again if you later for any reason have to clean your 
>> database. Please read  *Alternative method: How to enable pgcrypto via a 
>> separate database schema.) *found in here 
>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-PostgreSQL11.x,12.xor13.x(withpgcryptoinstalled).
>>  
>> Carefully.
>>
>> Hope it help
>>
>> Mo.
>>
>>
>>
>> On Tuesday, March 28, 2023 at 2

[dspace-tech] Re: pgcrypto extension is installed in PostgreSQL 14.7, but reports as not installed on this DATABASE

[Mohammad S. AlMutairi]

  [echo] 
> 
>  [echo]  The DSpace code has been installed.
>  [echo] 
> 
>  [echo]
>
> fresh_install:
>
> copy_webapps:
>..
> build_webapps_wars:
>
> check_spiders:
>
> init_spiders:
>  [echo]
>  [echo] 
> 
>  [echo]  The DSpace code has been installed.
>  [echo]
>  [echo]  To complete installation, you should do the following:
>  [echo]
>  [echo]  * Setup your Web servlet container (e.g. Tomcat) to look for 
> your
>......
>      [echo] 
> 
>  [echo]
>
> BUILD SUCCESSFUL
> Total time: 7 seconds
>
> NO Tables CREATED in DSpace during ant fresh_install:
> ###
> $ psql dspace
> psql (15.1)
> Type "help" for help.
>
> dspace=> \dt
> Did not find any relations.
> On Friday, 24 March 2023 at 11:56:52 UTC Mohammad S. AlMutairi wrote:
>
>> Hi,
>>
>> I think it can not be found because it's not included into the search 
>> path. See this old post for hints on how to fix it: 
>> https://groups.google.com/g/dspace-tech/c/Hy8lxiaxH4I/m/8yrHFW5lBgAJ or 
>> better if you recreate the pgcrypto extention using the ( *Alternative 
>> method: How to enable pgcrypto via a separate database schema.) *found in
>>  here 
>> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-PostgreSQL11.x,12.xor13.x(withpgcryptoinstalled)
>> .
>>
>>
>> Mo.
>>
>> On Friday, March 24, 2023 at 2:25:47 PM UTC+3 Baskar Selvaraj wrote:
>>
>>> Hi,
>>>
>>> OS: Ubuntu 22.04.2
>>> PostgreSQL: 14.7
>>> DSpace: 7.5
>>> pgcrypto extension: 1.3
>>>
>>> init_configs:
>>>  [copy] Copying 222 files to /home/dspace/config
>>>[delete] Deleting directory 
>>> /dspace-7.5/dspace/target/dspace-installer/config-temp
>>>  [copy] Copying 1 file to /home/dspace/config
>>>
>>> test_database:
>>>  [java] 2023-03-24 06:55:56,440 WARN 
>>>  org.dspace.servicemanager.DSpaceServiceManager @ Unable to locate bean by 
>>> name or id=database. Will try to look up bean by type next.
>>>  [java] 
>>> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
>>> named 'database' available
>>>  [java] at 
>>> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:872)
>>>  
>>> ~[spring-beans-5.3.20.jar:5.3.20]
>>>  [java] at 
>>> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1344)
>>>  
>>> ~[spring-beans-5.3.20.jar:5.3.20]
>>>  [java] at 
>>> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
>>>  
>>> ~[spring-beans-5.3.20.jar:5.3.20]
>>>  [java] at 
>>> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213)
>>>  
>>> ~[spring-beans-5.3.20.jar:5.3.20]
>>>  [java] at 
>>> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1160)
>>>  
>>> ~[spring-context-5.3.20.jar:5.3.20]
>>>  [java] at 
>>> org.dspace.servicemanager.DSpaceServiceManager.getServiceByName(DSpaceServiceManager.java:426)
>>>  
>>> [dspace-services-7.5.jar:7.5]
>>>  [java] at 
>>> org.dspace.scripts.ScriptServiceImpl.getScriptConfiguration(ScriptServiceImpl.java:34)
>>>  
>>> [dspace-api-7.5.jar:7.5]
>>>  [java] at 
>>> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125)
>>>  
>>> [dspace-api-7.5.jar:7.5]
>>>  [java] at 
>>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98) 
>>> [dspace-api-7.5.jar:7.5]
>>>  [java] 
>>>  [java] Attempting to connect to database
>>>  [java] Connected successfully!
>>>  [java] 
>>>  [java] Database Type: postgres
>>>  [java] Database URL: jdbc:postgresql://localhost:5432/dspace
>>>  [java] Database Schema: public
>>>  [java] Database Userna

[dspace-tech] Re: Dspace 7.4 SSL front-end problems

[Mohammad S. AlMutairi]

You welcome.
Was it stopped?. I don't see any issue with it now. 
http://hdl.handle.net/11715/10

Mo.
On Monday, March 27, 2023 at 10:41:36 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

>
> Thank you very much , what I have noticed is that the handle does not work 
> for me since I made the change , if it worked before , it now throws me 
> this error :
>
> [image: Captura de pantalla 2023-03-27 134059.png]
>
> what could be the error ? 
> El lunes, 27 de marzo de 2023 a las 12:35:04 UTC-6, Mohammad S. AlMutairi 
> escribió:
>
>> You can safely ignore that 404 error. GA is disabled by default in DSpace 
>> but if you need to enable it and use it follow the instructions you see 
>> here 
>> https://wiki.lyrasis.org/display/DSDOC7x/DSpace+Google+Analytics+Statistics#DSpaceGoogleAnalyticsStatistics-GoogleAnalyticsSupport
>>
>> Mo.
>>
>> On Monday, March 27, 2023 at 9:09:56 PM UTC+3 Jorge Alberto Bonilla 
>> Castaneda wrote:
>>
>>> wait, I found this forum where instructions were given to fix the bug I 
>>> ran into and they worked for me
>>> https://groups.google.com/g/dspace-tech/c/ba5O8lIpH1M/m/-ZgLFBOsAgAJ
>>>
>>> Now I only get a few errors like these, which I hope are not a big deal
>>>
>>> [image: Captura de pantalla 2023-03-27 120831.png]
>>>
>>>
>>>
>>> El lunes, 27 de marzo de 2023 a las 11:24:57 UTC-6, Jorge Alberto 
>>> Bonilla Castaneda escribió:
>>>
>>>> Hello, apply what is mentioned in that forum that I send, that is, 
>>>> configure my
>>>>
>>>> front end : https://rd.udb.edu.sv
>>>> backend : https://rd.udb.edu.sv/server/
>>>>
>>>> with its DNS and corresponding security certificate and with its apache 
>>>> configuration, however the back end keeps throwing me an error that 
>>>> doesn't 
>>>> even let me do searches.
>>>>
>>>> [image: Captura de pantalla 2023-03-27 112118.png]
>>>> what is my mistake now?
>>>>
>>>>
>>>> in my dspace.cfg I have configured the following :
>>>> dspace.server.url = https://rd.udb.edu.sv/server
>>>> dspace.ui.url = https://rd.udb.edu.sv
>>>> rest.cors.allowed-origins = ${dspace.ui.url} 
>>>>
>>>> in my config.prod.yml the following :
>>>> ui:
>>>>   ssl: false
>>>>   host: localhost
>>>>   port: 4000
>>>>   nameSpace: /
>>>>  
>>>> rest:
>>>>   ssl: true
>>>>   host: rd.udb.edu.sv
>>>>   port: 443
>>>> nameSpace: /server
>>>>
>>>>
>>>> and in apache .conf :
>>>> ProxyPass "/server" "http://localhost:8080/server;
>>>> ProxyPassReverse "/server" "http://localhost:8080/server;
>>>>
>>>> ProxyPass "/" "http://localhost:4000/;
>>>> ProxyPassReverse "/" "http://localhost:4000/;
>>>>
>>>>
>>>>
>>>> El jueves, 23 de marzo de 2023 a las 13:23:13 UTC-6, Mohammad S. 
>>>> AlMutairi escribió:
>>>>
>>>>> Hi Jorge,
>>>>>
>>>>> You need to change your setup in dspace.cfg to read what you see below 
>>>>> and then install apache or nginx and set it up as a reverse proxy. See 
>>>>> the 
>>>>> attached file in the link below for hints.
>>>>> in dspace.cfg I have defined the urls:
>>>>> dspace.server.url = https://rd.udb.edu.sv/server
>>>>> dspace.ui.url = https://rd.udb.edu.sv
>>>>>
>>>>>
>>>>> https://groups.google.com/g/dspace-tech/c/jDu1PyOEiKg/m/PdfiCloVAgAJ
>>>>>
>>>>> BR,
>>>>>
>>>>> Mo.
>>>>> On Thursday, March 23, 2023 at 8:43:07 PM UTC+3 Jorge Alberto Bonilla 
>>>>> Castaneda wrote:
>>>>>
>>>>>> hello everyone
>>>>>>
>>>>>> I had already configured my dspace on a server in the cloud and with 
>>>>>> its corresponding DNS, however, when I received the security certificate 
>>>>>> and proceeded to configure it, only the back end worked for me: 
>>>>>> https://rd.udb.edu. sv/
>>>>>>
>>>>>> however the front-end from that moment throws me an error: 
>>>>>> https://rd.udb.edu.sv:4000/
>>>>>>
>>>>>> in dspace.cfg I have defined the urls:
>>>>>> dspace.server.url = https://rd.udb.edu.sv/server
>>>>>> dspace.ui.url = https://rd.udb.edu.sv:4000
>>>>>>
>>>>>> and in config.prod.yml
>>>>>> ui:
>>>>>>ssl:true
>>>>>>host: 0.0.0.0
>>>>>>port: 4000
>>>>>>nameSpace: /
>>>>>>
>>>>>> rest:
>>>>>>ssl:true
>>>>>>host: rd.udb.edu.sv
>>>>>>port: 443
>>>>>>
>>>>>> I am doing something wrong ?
>>>>>>
>>>>>

-- 
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/4542e6b8-8341-4327-bdb3-88e53b621814n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.4 SSL front-end problems

[Mohammad S. AlMutairi]

You can safely ignore that 404 error. GA is disabled by default in DSpace 
but if you need to enable it and use it follow the instructions you see 
here 
https://wiki.lyrasis.org/display/DSDOC7x/DSpace+Google+Analytics+Statistics#DSpaceGoogleAnalyticsStatistics-GoogleAnalyticsSupport

Mo.

On Monday, March 27, 2023 at 9:09:56 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

> wait, I found this forum where instructions were given to fix the bug I 
> ran into and they worked for me
> https://groups.google.com/g/dspace-tech/c/ba5O8lIpH1M/m/-ZgLFBOsAgAJ
>
> Now I only get a few errors like these, which I hope are not a big deal
>
> [image: Captura de pantalla 2023-03-27 120831.png]
>
>
>
> El lunes, 27 de marzo de 2023 a las 11:24:57 UTC-6, Jorge Alberto Bonilla 
> Castaneda escribió:
>
>> Hello, apply what is mentioned in that forum that I send, that is, 
>> configure my
>>
>> front end : https://rd.udb.edu.sv
>> backend : https://rd.udb.edu.sv/server/
>>
>> with its DNS and corresponding security certificate and with its apache 
>> configuration, however the back end keeps throwing me an error that doesn't 
>> even let me do searches.
>>
>> [image: Captura de pantalla 2023-03-27 112118.png]
>> what is my mistake now?
>>
>>
>> in my dspace.cfg I have configured the following :
>> dspace.server.url = https://rd.udb.edu.sv/server
>> dspace.ui.url = https://rd.udb.edu.sv
>> rest.cors.allowed-origins = ${dspace.ui.url} 
>>
>> in my config.prod.yml the following :
>> ui:
>>   ssl: false
>>   host: localhost
>>   port: 4000
>>   nameSpace: /
>>  
>> rest:
>>   ssl: true
>>   host: rd.udb.edu.sv
>>   port: 443
>> nameSpace: /server
>>
>>
>> and in apache .conf :
>> ProxyPass "/server" "http://localhost:8080/server;
>> ProxyPassReverse "/server" "http://localhost:8080/server;
>>
>> ProxyPass "/" "http://localhost:4000/;
>> ProxyPassReverse "/" "http://localhost:4000/;
>>
>>
>>
>> El jueves, 23 de marzo de 2023 a las 13:23:13 UTC-6, Mohammad S. 
>> AlMutairi escribió:
>>
>>> Hi Jorge,
>>>
>>> You need to change your setup in dspace.cfg to read what you see below 
>>> and then install apache or nginx and set it up as a reverse proxy. See the 
>>> attached file in the link below for hints.
>>> in dspace.cfg I have defined the urls:
>>> dspace.server.url = https://rd.udb.edu.sv/server
>>> dspace.ui.url = https://rd.udb.edu.sv
>>>
>>>
>>> https://groups.google.com/g/dspace-tech/c/jDu1PyOEiKg/m/PdfiCloVAgAJ
>>>
>>> BR,
>>>
>>> Mo.
>>> On Thursday, March 23, 2023 at 8:43:07 PM UTC+3 Jorge Alberto Bonilla 
>>> Castaneda wrote:
>>>
>>>> hello everyone
>>>>
>>>> I had already configured my dspace on a server in the cloud and with 
>>>> its corresponding DNS, however, when I received the security certificate 
>>>> and proceeded to configure it, only the back end worked for me: 
>>>> https://rd.udb.edu. sv/
>>>>
>>>> however the front-end from that moment throws me an error: 
>>>> https://rd.udb.edu.sv:4000/
>>>>
>>>> in dspace.cfg I have defined the urls:
>>>> dspace.server.url = https://rd.udb.edu.sv/server
>>>> dspace.ui.url = https://rd.udb.edu.sv:4000
>>>>
>>>> and in config.prod.yml
>>>> ui:
>>>>ssl:true
>>>>host: 0.0.0.0
>>>>port: 4000
>>>>nameSpace: /
>>>>
>>>> rest:
>>>>ssl:true
>>>>host: rd.udb.edu.sv
>>>>port: 443
>>>>
>>>> I am doing something wrong ?
>>>>
>>>

-- 
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/14d1efe5-d5f8-4d2b-b48b-c162bf72eba8n%40googlegroups.com.

[dspace-tech] Re: Process-Cleaner

[Mohammad S. AlMutairi]

Hi Jake,

The default age for old processes to be cleaned is 14 days when 
process-cleaner is run. Have a look on [dspace]/config/dspace.cfg about 
line 1584.

#--#
#--PROCESS CLEANER SCRIPT CONFIGURATION#
#--#
# Processes older than this number of days will be deleted when the 
"process-cleaner" script is next run.
# Default is 14 (i.e. processes that are two weeks or older will be deleted)
# process-cleaner.days = 14

BR,

Mo.

On Wednesday, March 22, 2023 at 8:22:08 PM UTC+3 Cameron, Jacob wrote:

> Hi Everyone,
>
> When I run dspace process-cleaner --completed, it runs and says 0 items 
> have been removed. However, I have about 120 processes that are complete. 
> Am I missing something? Is it not working in DSpace 7.4 any longer?
>
> Jake
>
> --
> Jake Cameron, BCS(UNB)
> Systems Support Specialist III
> Information Systems and Technical Services University of Lethbridge Library
> Phone:(403)329-2756 <(403)%20329-2756>
> This e-mail, including any and all attachments, is only for the use of the 
> intended recipient(s) and may contain information that is confidential or 
> privileged. If you are not the intended recipient, you are advised that any 
> dissemination, copying or other use of this e-mail is prohibited. Please 
> notify the sender of the error in communication by return e-mail and 
> destroy all copies of this e-mail. 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/5c10e7d2-5ab8-4a94-b9c2-4af7f4532500n%40googlegroups.com.

[dspace-tech] Re: pgcrypto extension is installed in PostgreSQL 14.7, but reports as not installed on this DATABASE

[Mohammad S. AlMutairi]

Hi,

I think it can not be found because it's not included into the search path. 
See this old post for hints on how to fix 
it: https://groups.google.com/g/dspace-tech/c/Hy8lxiaxH4I/m/8yrHFW5lBgAJ or 
better if you recreate the pgcrypto extention using the ( *Alternative 
method: How to enable pgcrypto via a separate database schema.) *found in 
here 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-PostgreSQL11.x,12.xor13.x(withpgcryptoinstalled).


Mo.

On Friday, March 24, 2023 at 2:25:47 PM UTC+3 Baskar Selvaraj wrote:

> Hi,
>
> OS: Ubuntu 22.04.2
> PostgreSQL: 14.7
> DSpace: 7.5
> pgcrypto extension: 1.3
>
> init_configs:
>  [copy] Copying 222 files to /home/dspace/config
>[delete] Deleting directory 
> /dspace-7.5/dspace/target/dspace-installer/config-temp
>  [copy] Copying 1 file to /home/dspace/config
>
> test_database:
>  [java] 2023-03-24 06:55:56,440 WARN 
>  org.dspace.servicemanager.DSpaceServiceManager @ Unable to locate bean by 
> name or id=database. Will try to look up bean by type next.
>  [java] 
> org.springframework.beans.factory.NoSuchBeanDefinitionException: No bean 
> named 'database' available
>  [java] at 
> org.springframework.beans.factory.support.DefaultListableBeanFactory.getBeanDefinition(DefaultListableBeanFactory.java:872)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getMergedLocalBeanDefinition(AbstractBeanFactory.java:1344)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:309)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:213)
>  
> ~[spring-beans-5.3.20.jar:5.3.20]
>  [java] at 
> org.springframework.context.support.AbstractApplicationContext.getBean(AbstractApplicationContext.java:1160)
>  
> ~[spring-context-5.3.20.jar:5.3.20]
>  [java] at 
> org.dspace.servicemanager.DSpaceServiceManager.getServiceByName(DSpaceServiceManager.java:426)
>  
> [dspace-services-7.5.jar:7.5]
>  [java] at 
> org.dspace.scripts.ScriptServiceImpl.getScriptConfiguration(ScriptServiceImpl.java:34)
>  
> [dspace-api-7.5.jar:7.5]
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.handleScript(ScriptLauncher.java:125) 
> [dspace-api-7.5.jar:7.5]
>  [java] at 
> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:98) 
> [dspace-api-7.5.jar:7.5]
>  [java] 
>  [java] Attempting to connect to database
>  [java] Connected successfully!
>  [java] 
>  [java] Database Type: postgres
>  [java] Database URL: jdbc:postgresql://localhost:5432/dspace
>  [java] Database Schema: public
>  [java] Database Username: dspace
>  [java] Database Software: PostgreSQL version 14.7 (Ubuntu 
> 14.7-0ubuntu0.22.04.1)
>  [java] Database Driver: PostgreSQL JDBC Driver version 42.4.3
>  [java] PostgreSQL 'pgcrypto' extension installed/up-to-date? false 
> (not installed)
>  [java] FlywayDB Version: 8.4.4
>  [java] 
>  [java] WARNING: Required PostgreSQL 'pgcrypto' extension is NOT 
> INSTALLED on this database.
>  [java] 
>  [java] ** DSpace REQUIRES PostgreSQL >= 9.4 AND pgcrypto extension >= 
> 1.1 **
>  [java] 
>  [java] To install it, please connect to your DSpace database as a 
> 'superuser' and manually run the following command: 
>  [java] 
>  [java]   CREATE EXTENSION pgcrypto;
>  [java] 
>
> BUILD FAILED
> /dspace-7.5/dspace/target/dspace-installer/build.xml:770: Java returned: 1
>
> Total time: 9 seconds
>
> -
>
> pgcrypto is installed and enabled
>
> psql (14.7 (Ubuntu 14.7-0ubuntu0.22.04.1))
> Type "help" for help.
>
> postgres=# select * from pg_available_extensions;
> name| default_version | installed_version |   
>  comment 
>
> +-+---+
>
>  intagg | 1.1 |   | integer 
> aggregator and enumerator (obsolete)
>  tsm_system_rows| 1.0 |   | TABLESAMPLE 
> method which accepts number of rows as a limit
>  refint | 1.0 |   | functions for 
> implementing referential integrity (obsolete)
>  pgcrypto   | 1.3 | 1.3   | cryptographic 
> functions
>  file_fdw   | 1.0 |   | foreign-data 
> wrapper for flat file access
>  hstore | 1.8 |   | data type for 
> storing sets of (key, value) pairs
>  pg_stat_statements | 1.9 |   | track planning 
> and 

[dspace-tech] Re: We can not apply Access Conditions in Dspace 7

[Mohammad S. AlMutairi]

Hi  Zeynep,

If all you needed is to disable Administrator in all the submitting forms 
you have you can do it by commenting out the Administrator line in 
[dspace]/config/spring/api/access-conditions.xml 
on line 73. Read more about it or how to customize it to fit your 
requirments 
here 
https://wiki.lyrasis.org/display/DSDOC7x/Submission+User+Interface#SubmissionUserInterface-Modifyingaccessconditions(embargo,etc.)presentedforBitstreams

Hope it help

Mo.

On Thursday, March 23, 2023 at 2:22:12 PM UTC+3 Zeynep Şolta wrote:

> Please help on this subject!
> We upgraded to Dspace 7. After, we made editing on submission form. We 
> excluded the adinistrator option from default access conditions section. 
> Now we can not apply any access conditions type to sources. We see access 
> conditions section on the submission form, but don't apply. For example we 
> choose ambargo , and then date and send. Then, screen freezes, won't 
> progress. We also don't see access conditions section when any item files 
> editing. How we can solve this problem? Could you please share a 
> troubleshooting guide on this subject?
>
>

-- 
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/a469f70e-c856-4194-9a3f-954a31b72e50n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.4 SSL front-end problems

[Mohammad S. AlMutairi]

Hi Jorge,

You need to change your setup in dspace.cfg to read what you see below and 
then install apache or nginx and set it up as a reverse proxy. See the 
attached file in the link below for hints.
in dspace.cfg I have defined the urls:
dspace.server.url = https://rd.udb.edu.sv/server
dspace.ui.url = https://rd.udb.edu.sv


https://groups.google.com/g/dspace-tech/c/jDu1PyOEiKg/m/PdfiCloVAgAJ

BR,

Mo.
On Thursday, March 23, 2023 at 8:43:07 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

> hello everyone
>
> I had already configured my dspace on a server in the cloud and with its 
> corresponding DNS, however, when I received the security certificate and 
> proceeded to configure it, only the back end worked for me: 
> https://rd.udb.edu. sv/
>
> however the front-end from that moment throws me an error: 
> https://rd.udb.edu.sv:4000/
>
> in dspace.cfg I have defined the urls:
> dspace.server.url = https://rd.udb.edu.sv/server
> dspace.ui.url = https://rd.udb.edu.sv:4000
>
> and in config.prod.yml
> ui:
>ssl:true
>host: 0.0.0.0
>port: 4000
>nameSpace: /
>
> rest:
>ssl:true
>host: rd.udb.edu.sv
>port: 443
>
> I am doing something wrong ?
>

-- 
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/1d8f9660-0117-4775-8c41-98aec30e1078n%40googlegroups.com.

[dspace-tech] Re: handle server 7.4

[Mohammad S. AlMutairi]

Hi Jorge,

These is clear instructions to start a new installation of the handle 
server.


# Take a backup of the handle-server folder first if you already had a 
handle-server previously and do:.
1) /dspace/bin/dspace make-handle-config /dspace/handle-server/
Through what network-accessible IP address should clients connect to this 
server? [127.0.1.1]: x.x.x.x  <--- Server Public IP
If different, enter the IP address to which the server should bind. 
[159.10.178.1]: 192.168.100.x   <--- Server Private IP
Would you like to encrypt your private key?(y/n) [y]: no

<-- You should say no but you can say yes if you do, you have to enter this 
passphrase every time the handle server needs to be started (DSpace 
recommends not to encrypt it).

3) vi /dspace/handle-server/config.dct
# Add the handle storage plugin you see in red below and replace every 
occurrence of YOUR_PREFIX with your allotted prefix you have in 
dspace.cfg/local.cfg.
  "server_config" = {


*"storage_type" = "CUSTOM""storage_class" = 
"org.dspace.handle.HandlePlugin""enable_txn_queue" = "no"*
"server_admins" = (
  "300:0.NA/ *YOUR_PREFIX*"
)

"replication_admins" = (
  "300:0.NA/ *YOUR_PREFIX*"
)

"max_session_time" = "8640"
"this_server_id" = "1"
"max_auth_time" = "6"
"server_admin_full_access" = "yes"
"case_sensitive" = "no"
"auto_homed_prefixes" = (
  "0.NA/ *YOUR_PREFIX*"
)

4) chown -R tomcat:tomcat /dspace/handle-server

5) /dspace/bin/start-handle-server

6) ss -nlp | grep ":8000\|:2641"

7) Make sure port 2641/udp, 2641/tcp and 8000/tcp are opend on the public 
firewall and the server firewall if you have one running.

8) Send the generated /dspace/handle-server/sitebndl.zip to CNRI ... You 
should include your name, organization name, and your prefix that needs to 
be updated in the email.

Hope it help.

Mo.
On Monday, March 20, 2023 at 11:40:11 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

>
> hi , i wanted to configure a handle server on my dspace 7.4 , so i went to 
> consult the documentation
> https://wiki.lyrasis.org/display/DSDOC7x/Handle.Net+Registry+Support
>
> Within the first section, to locate the handle server on the same dspace 
> machine, use the first command, that is:
>
> [dspace]/bin/make-handle-config
>
> and I get the following errors:
> [image: Captura de pantalla 2023-03-20 142824.png]
>
> if it is a question of permissions, when installing dspace use
> chown -R tomcat:tomcat /dspace
>
> but it still fails, what could it be?
>
>

-- 
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/7e218bbf-d131-4cb5-b3d2-72be3d4da6ean%40googlegroups.com.

[dspace-tech] Re: error tomcat 404

[Mohammad S. AlMutairi]

Hi Matias,

You need to change docBase="dspace/webapps/server" to 
docBase="/dspace/webapps/server". The absolute path forward slash is 
missing so just add it to make it work.

Mo.

On Tuesday, March 21, 2023 at 4:20:35 AM UTC+3 Matías Javier Saavedra 
Gajardo wrote:

> When I enter the localhost/server folder it gives me a 404.
>
> create the xml file in the tomcat where it points to.
> [image: Screenshot_1.png]
> also copy the server folder to tomcat.
> [image: Screenshot_2.png]
> [image: Screenshot_3.png]
>
> I attach other images of other logs
> [image: localhost_access_log.2023-03-20.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/03dfbcaa-5311-48a3-a32f-8ea61c8ab467n%40googlegroups.com.

Re: [dspace-tech] Re: Admin user with no privileges

[Mohammad S. AlMutairi]

Hi Douglas,

You are most welcome. Happy you finally got it sorted out. I must thank you 
too for dragging me into the docker world :-). I had to build DSpace on 
docker thinking it could be part of the cause but it turned out I could've 
accomplished the final conclusion if the config file you sent was fed into 
any Nginx.DSpace 7 lacks any clear instructions or guidelines on how the 
Nginx web server reverse proxy should be set up for first-timers so I think 
it will help a lot of people if the Nginx reverse proxy is added besides 
the Apache example to give a hint of what to start with and to save someone 
else's time.

Accept my kindest regards,

Mo.

On Monday, March 20, 2023 at 8:47:53 PM UTC+3 Douglas Eder Uno Silva wrote:

Hi Mo!

Man, it worked! Thanks a lot again for the help!

The problem is about the flag *$query_string* i used after the 
*$request_uri* on *proxy_pass* in the location for the backend. I use this 
on other applications that I deploy but it seems that for Java/Tomcat works 
differently.
When I set your configuration, I tried to debug the reason why it works and 
when I set the *$query_string *in the proxy_pass, the menu did not display 
any more. I never thought that this flag could be the source of this 
problem! I could not believe it when I saw!
The forwarding of the *$query_string* to the backend container makes the 
api omit the *_embedded *on requests like 
https://dspace.uefs.br/server/api/authz/authorizations/search/object?uri=https://dspace.uefs.br/server/api/core/sites/b7f0752f-d24f-43da-9eb8-37c5eca6c101=isCommunityAdmin=feature.
 
That was the only difference between my installation and the demo 
https://demo7.dspace.org. Now we know why!

The working config is attached.

Do you think we can suggest something to improve the DSpace docs? I believe 
we can emphasize this in topic 17 of the backend installation and topic 8 
of the frontend installation in the apache/nginx configuration section.

Thank you again very much for your time, attention and patience.

Em sáb., 18 de mar. de 2023 às 02:30, Mohammad S. AlMutairi <
alo...@gmail.com> escreveu:

Hi Douglas,

I was able to replicate the issue you have with the administrator menu here 
and saw there was no menu while logged as an administrator. I can confirm 
It's caused by how the reverse proxy is configured so try the attached 
config file instead (It's a working).

Cheers,

Mo.



On Saturday, March 18, 2023 at 1:47:01 AM UTC+3 Mohammad S. AlMutairi wrote:

Hi Douglas,

Thanks for the info. After getting into docker I see my suggestions won't 
work. Setting DSpace in Docker is a bit different than how it is on 
standalone servers. I'm setting a similar environment to yours here trying 
to help.

Do you get any clues when tailing the logs of angular? (docker logs -f 
dspace-angular-container-ID)

Mo.

On Tuesday, March 14, 2023 at 3:09:26 PM UTC+3 Douglas Eder Uno Silva wrote:

Hi Mo,

Same behavior. Despite being logged in as an administrator, the 
administrative menu does not appear. No errors on browser console or in 
DSpace backend logs that could indicate clues of the problem.
[image: image.png]
The previous and updated nginx configuration file is attached.

I have this 'architecture' on the server. I removed some things to simplify 
the diagram. The server runs an NGinx, the DSpace backend and frontend are 
containers too. All containers are in the same network.
[image: image.png]

After configuring DSPACE_UI_HOST = localhost, the nginx container could not 
connect to the container of the frontend to forward the request.
Nginx could forward the request only after configuring DSPACE_UI_HOST with 
0.0.0.0.

Em ter., 14 de mar. de 2023 às 08:19, Douglas Eder Uno Silva <
deus...@uefs.br> escreveu:

Hi Mo,

I will test these changes and let you know what happens.

Em ter., 14 de mar. de 2023 às 06:34, Mohammad S. AlMutairi <
alo...@gmail.com> escreveu:

Hi Douglas,

In addition to the previous message, I noticed you are using a Squid Proxy 
in your network. You might need to bypass the proxy for the http/https 
traffic going from the frontend destined to the backend.

ENV http_proxy http://proxy.uefs.br:3128
ENV https_proxy http://proxy.uefs.br:3128
ENV NO_PROXY  localhost

https://docs.docker.com/network/proxy/

BR, 

Mo.

On Tuesday, March 14, 2023 at 12:14:53 AM UTC+3 Mohammad S. AlMutairi wrote:

Hi Douglas,

For testing to isolate the cause of this issue. Can you try running the 
frontend on / instead of the subath /app you are running on and also bind 
it on the localhost adapter?. I'm suspecting the subpath is because of this 
old issue ( https://github.com/DSpace/dspace-angular/pull/1488 ). It could 
also be caused by the reverse proxy setup you have. Just try them to know 
for sure.

  DSPACE_UI_HOST: localhost
  DSPACE_UI_PORT: '4000'
  DSPACE_UI_NAMESPACE: /

-Nginx Reverse Proxy setup-
  location /server {

proxy_set_

[dspace-tech] Re: SSL problems

[Mohammad S. AlMutairi]

You most welcome. You could've used Let's Encrypt or the self-signed certs, 
doing so will save you some extra work at a later time if your current 
implementation involve ingesting items or anything relies on the DSpace 
naming. What I mean by that is you might need to replace 
http://150.136.129.10 back to the real domain name https://example.net in 
the database).

Cheers,

Mo.

On Monday, March 20, 2023 at 6:47:43 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

> It worked!
>
> thank you very much, I changed the ip to 0.0.0.0 in the .json of the 
> front-end and it worked
>
> El lunes, 20 de marzo de 2023 a las 8:44:12 UTC-6, Mohammad S. AlMutairi 
> escribió:
>
>> Correction: port: 4000 should be  port: 80
>>
>> On Monday, March 20, 2023 at 5:42:33 PM UTC+3 Mohammad S. AlMutairi wrote:
>>
>>> Good Morning,
>>>
>>> I think the public access to your server is natted from the public IP 
>>> (150.136.129.10) to the server private IP address (unknown). You have to 
>>> find out the frontend server private IP address and use it or as an 
>>> alternative you can use 0.0.0.0 instead to have the service run on every 
>>> adapter on the frontend server. Try the setup you see below ( You have to 
>>> make sure no other service is running on port 80 "APache or Nginx" so stop 
>>> the weserver it its running).
>>>
>>> ui:
>>>   ssl: false
>>>   #host: server-private-ip-address
>>>   host: 0.0.0.0
>>>   port: 4000
>>>   nameSpace: /
>>>   useProxies: true
>>>
>>> rest:
>>>   ssl: false
>>>   host: 150.136.129.10
>>>   port: 8080
>>>   nameSpace: /server
>>>
>>> ** Make sure tomcat port 8080 do match the real port tomcat is running 
>>> on. You can find out which one is used by running (ss -nlp | grep 
>>> ":8443\|:8080")
>>>
>>> Mo.
>>> On Monday, March 20, 2023 at 4:29:09 PM UTC+3 Jorge Alberto Bonilla 
>>> Castaneda wrote:
>>>
>>>> good morning
>>>>
>>>> Well, that configuration works for me when we talk about a local 
>>>> network, but when that configuration is already used in servers hosted in 
>>>> the cloud, the front-end stops working
>>>>
>>>> verify that the required addresses are publicly accessible:
>>>> http://150.136.129.10:8983/solr/#/
>>>> http://150.136.129.10:8080/server/#/server/api
>>>>
>>>> but the front end keeps giving the same error:
>>>> http://150.136.129.10/
>>>>
>>>> [image: Sin título.png]
>>>> and my configuration is the following
>>>>
>>>> [image: Captura de pantalla 2023-03-20 072614.png]
>>>> What could it be ?
>>>>
>>>> El viernes, 17 de marzo de 2023 a las 16:37:26 UTC-6, Mohammad S. 
>>>> AlMutairi escribió:
>>>>
>>>>> You  don't need to use a self-signed certificate to continue your 
>>>>> implementation ( You can use it but you don't have to ).  Recent DSpace 
>>>>> versions are forgiving. You can configure both DSpace ends using domain 
>>>>> names using (http) or IP that's include private or public IP without SSL 
>>>>> and DSpace still works.
>>>>>
>>>>> *** You need to stop the Webserver and have port 80 and 8443 publicly 
>>>>> accessible for this to work. ***
>>>>> ** dspace.cfg or local.cfg
>>>>> dspace.server.url = http://server-public-ip:8443/server 
>>>>> <http://server-public-ip:8080/server>
>>>>> dspace.ui.url =  http://server-public-ip
>>>>>
>>>>> ** config.prod.yml
>>>>> ui:
>>>>>   ssl: false
>>>>>   host: server-private-ip
>>>>>   port: 80
>>>>>
>>>>> rest:
>>>>>   ssl: false
>>>>>   host: server-public-ip
>>>>>   port: 8080
>>>>>   nameSpace: /server
>>>>>
>>>>> 1) yarn test:rest
>>>>> 2) yarn start:prod
>>>>> 3) Access DSpace at http://server-public-ip
>>>>>
>>>>>
>>>>> The above setup should keep you going till you get your public cert 
>>>>> but If you still need to get the self-signed cert working you need to 
>>>>> post 
>>>>> the OS and the webserver you are using. Posting the reverse proxy will 
>>>>> help.
>>

[dspace-tech] Re: SSL problems

[Mohammad S. AlMutairi]

Correction: port: 4000 should be  port: 80

On Monday, March 20, 2023 at 5:42:33 PM UTC+3 Mohammad S. AlMutairi wrote:

> Good Morning,
>
> I think the public access to your server is natted from the public IP 
> (150.136.129.10) to the server private IP address (unknown). You have to 
> find out the frontend server private IP address and use it or as an 
> alternative you can use 0.0.0.0 instead to have the service run on every 
> adapter on the frontend server. Try the setup you see below ( You have to 
> make sure no other service is running on port 80 "APache or Nginx" so stop 
> the weserver it its running).
>
> ui:
>   ssl: false
>   #host: server-private-ip-address
>   host: 0.0.0.0
>   port: 4000
>   nameSpace: /
>   useProxies: true
>
> rest:
>   ssl: false
>   host: 150.136.129.10
>   port: 8080
>   nameSpace: /server
>
> ** Make sure tomcat port 8080 do match the real port tomcat is running on. 
> You can find out which one is used by running (ss -nlp | grep 
> ":8443\|:8080")
>
> Mo.
> On Monday, March 20, 2023 at 4:29:09 PM UTC+3 Jorge Alberto Bonilla 
> Castaneda wrote:
>
>> good morning
>>
>> Well, that configuration works for me when we talk about a local network, 
>> but when that configuration is already used in servers hosted in the cloud, 
>> the front-end stops working
>>
>> verify that the required addresses are publicly accessible:
>> http://150.136.129.10:8983/solr/#/
>> http://150.136.129.10:8080/server/#/server/api
>>
>> but the front end keeps giving the same error:
>> http://150.136.129.10/
>>
>> [image: Sin título.png]
>> and my configuration is the following
>>
>> [image: Captura de pantalla 2023-03-20 072614.png]
>> What could it be ?
>>
>> El viernes, 17 de marzo de 2023 a las 16:37:26 UTC-6, Mohammad S. 
>> AlMutairi escribió:
>>
>>> You  don't need to use a self-signed certificate to continue your 
>>> implementation ( You can use it but you don't have to ).  Recent DSpace 
>>> versions are forgiving. You can configure both DSpace ends using domain 
>>> names using (http) or IP that's include private or public IP without SSL 
>>> and DSpace still works.
>>>
>>> *** You need to stop the Webserver and have port 80 and 8443 publicly 
>>> accessible for this to work. ***
>>> ** dspace.cfg or local.cfg
>>> dspace.server.url = http://server-public-ip:8443/server 
>>> <http://server-public-ip:8080/server>
>>> dspace.ui.url =  http://server-public-ip
>>>
>>> ** config.prod.yml
>>> ui:
>>>   ssl: false
>>>   host: server-private-ip
>>>   port: 80
>>>
>>> rest:
>>>   ssl: false
>>>   host: server-public-ip
>>>   port: 8080
>>>   nameSpace: /server
>>>
>>> 1) yarn test:rest
>>> 2) yarn start:prod
>>> 3) Access DSpace at http://server-public-ip
>>>
>>>
>>> The above setup should keep you going till you get your public cert but 
>>> If you still need to get the self-signed cert working you need to post the 
>>> OS and the webserver you are using. Posting the reverse proxy will help.
>>>
>>> Mo.
>>>
>>> On Friday, March 17, 2023 at 5:58:41 PM UTC+3 Jorge Alberto Bonilla 
>>> Castaneda wrote:
>>>
>>>> SSL issues
>>>>
>>>> Good morning, when I hosted my dspace 7.4 on the web, I realized that 
>>>> it is not possible to use the front-end if the back-end does not have a 
>>>> secure certificate.
>>>>
>>>> At the moment we can't get this certificate, but to continue with the 
>>>> implementation and configuration of it I wanted to use a self-generated 
>>>> certificate, so in a local copy of the machine in the cloud, I started 
>>>> trying, generating the certificate with keytool and doing the 
>>>> modifications 
>>>> in the urls of dspace.cfg and config.prod.yml
>>>>
>>>> Well now my back-end was using the 8443.
>>>> [image: cer.png]
>>>>
>>>> however the front-end gave me the following error:
>>>> [image: er.png]
>>>>
>>>> what could be doing wrong? Is it because it is a self generated 
>>>> certificate? 
>>>>
>>>>

-- 
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/5dc56df0-6cd9-40d7-bb9b-3a8ea7e93a59n%40googlegroups.com.

[dspace-tech] Re: SSL problems

[Mohammad S. AlMutairi]

Good Morning,

I think the public access to your server is natted from the public IP 
(150.136.129.10) to the server private IP address (unknown). You have to 
find out the frontend server private IP address and use it or as an 
alternative you can use 0.0.0.0 instead to have the service run on every 
adapter on the frontend server. Try the setup you see below ( You have to 
make sure no other service is running on port 80 "APache or Nginx" so stop 
the weserver it its running).

ui:
  ssl: false
  #host: server-private-ip-address
  host: 0.0.0.0
  port: 4000
  nameSpace: /
  useProxies: true

rest:
  ssl: false
  host: 150.136.129.10
  port: 8080
  nameSpace: /server

** Make sure tomcat port 8080 do match the real port tomcat is running on. 
You can find out which one is used by running (ss -nlp | grep 
":8443\|:8080")

Mo.
On Monday, March 20, 2023 at 4:29:09 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

> good morning
>
> Well, that configuration works for me when we talk about a local network, 
> but when that configuration is already used in servers hosted in the cloud, 
> the front-end stops working
>
> verify that the required addresses are publicly accessible:
> http://150.136.129.10:8983/solr/#/
> http://150.136.129.10:8080/server/#/server/api
>
> but the front end keeps giving the same error:
> http://150.136.129.10/
>
> [image: Sin título.png]
> and my configuration is the following
>
> [image: Captura de pantalla 2023-03-20 072614.png]
> What could it be ?
>
> El viernes, 17 de marzo de 2023 a las 16:37:26 UTC-6, Mohammad S. 
> AlMutairi escribió:
>
>> You  don't need to use a self-signed certificate to continue your 
>> implementation ( You can use it but you don't have to ).  Recent DSpace 
>> versions are forgiving. You can configure both DSpace ends using domain 
>> names using (http) or IP that's include private or public IP without SSL 
>> and DSpace still works.
>>
>> *** You need to stop the Webserver and have port 80 and 8443 publicly 
>> accessible for this to work. ***
>> ** dspace.cfg or local.cfg
>> dspace.server.url = http://server-public-ip:8443/server 
>> <http://server-public-ip:8080/server>
>> dspace.ui.url =  http://server-public-ip
>>
>> ** config.prod.yml
>> ui:
>>   ssl: false
>>   host: server-private-ip
>>   port: 80
>>
>> rest:
>>   ssl: false
>>   host: server-public-ip
>>   port: 8080
>>   nameSpace: /server
>>
>> 1) yarn test:rest
>> 2) yarn start:prod
>> 3) Access DSpace at http://server-public-ip
>>
>>
>> The above setup should keep you going till you get your public cert but 
>> If you still need to get the self-signed cert working you need to post the 
>> OS and the webserver you are using. Posting the reverse proxy will help.
>>
>> Mo.
>>
>> On Friday, March 17, 2023 at 5:58:41 PM UTC+3 Jorge Alberto Bonilla 
>> Castaneda wrote:
>>
>>> SSL issues
>>>
>>> Good morning, when I hosted my dspace 7.4 on the web, I realized that it 
>>> is not possible to use the front-end if the back-end does not have a secure 
>>> certificate.
>>>
>>> At the moment we can't get this certificate, but to continue with the 
>>> implementation and configuration of it I wanted to use a self-generated 
>>> certificate, so in a local copy of the machine in the cloud, I started 
>>> trying, generating the certificate with keytool and doing the modifications 
>>> in the urls of dspace.cfg and config.prod.yml
>>>
>>> Well now my back-end was using the 8443.
>>> [image: cer.png]
>>>
>>> however the front-end gave me the following error:
>>> [image: er.png]
>>>
>>> what could be doing wrong? Is it because it is a self generated 
>>> certificate? 
>>>
>>>

-- 
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/31c822bf-d0d8-40f0-b6db-d5097076339an%40googlegroups.com.

Re: [dspace-tech] Re: Admin user with no privileges

[Mohammad S. AlMutairi]

Hi Douglas,

I was able to replicate the issue you have with the administrator menu here 
and saw there was no menu while logged as an administrator. I can confirm 
It's caused by how the reverse proxy is configured so try the attached 
config file instead (It's a working).

Cheers,

Mo.



On Saturday, March 18, 2023 at 1:47:01 AM UTC+3 Mohammad S. AlMutairi wrote:

> Hi Douglas,
>
> Thanks for the info. After getting into docker I see my suggestions won't 
> work. Setting DSpace in Docker is a bit different than how it is on 
> standalone servers. I'm setting a similar environment to yours here trying 
> to help.
>
> Do you get any clues when tailing the logs of angular? (docker logs -f 
> dspace-angular-container-ID)
>
> Mo.
>
> On Tuesday, March 14, 2023 at 3:09:26 PM UTC+3 Douglas Eder Uno Silva 
> wrote:
>
>> Hi Mo,
>>
>> Same behavior. Despite being logged in as an administrator, the 
>> administrative menu does not appear. No errors on browser console or in 
>> DSpace backend logs that could indicate clues of the problem.
>> [image: image.png]
>> The previous and updated nginx configuration file is attached.
>>
>> I have this 'architecture' on the server. I removed some things to 
>> simplify the diagram. The server runs an NGinx, the DSpace backend and 
>> frontend are containers too. All containers are in the same network.
>> [image: image.png]
>>
>> After configuring DSPACE_UI_HOST = localhost, the nginx container could 
>> not connect to the container of the frontend to forward the request.
>> Nginx could forward the request only after configuring DSPACE_UI_HOST 
>> with 0.0.0.0.
>>
>> Em ter., 14 de mar. de 2023 às 08:19, Douglas Eder Uno Silva <
>> deus...@uefs.br> escreveu:
>>
>>> Hi Mo,
>>>
>>> I will test these changes and let you know what happens.
>>>
>>> Em ter., 14 de mar. de 2023 às 06:34, Mohammad S. AlMutairi <
>>> alo...@gmail.com> escreveu:
>>>
>>>> Hi Douglas,
>>>>
>>>> In addition to the previous message, I noticed you are using a Squid 
>>>> Proxy in your network. You might need to bypass the proxy for the 
>>>> http/https traffic going from the frontend destined to the backend.
>>>>
>>>> ENV http_proxy http://proxy.uefs.br:3128
>>>> ENV https_proxy http://proxy.uefs.br:3128
>>>> ENV NO_PROXY  localhost
>>>>
>>>> https://docs.docker.com/network/proxy/
>>>>
>>>> BR, 
>>>>
>>>> Mo.
>>>>
>>>> On Tuesday, March 14, 2023 at 12:14:53 AM UTC+3 Mohammad S. AlMutairi 
>>>> wrote:
>>>>
>>>>> Hi Douglas,
>>>>>
>>>>> For testing to isolate the cause of this issue. Can you try running 
>>>>> the frontend on / instead of the subath /app you are running on and also 
>>>>> bind it on the localhost adapter?. I'm suspecting the subpath is because 
>>>>> of 
>>>>> this old issue ( https://github.com/DSpace/dspace-angular/pull/1488 
>>>>> ). It could also be caused by the reverse proxy setup you have. Just try 
>>>>> them to know for sure.
>>>>>
>>>>>   DSPACE_UI_HOST: localhost
>>>>>   DSPACE_UI_PORT: '4000'
>>>>>   DSPACE_UI_NAMESPACE: /
>>>>>
>>>>> -Nginx Reverse Proxy 
>>>>> setup-
>>>>>   location /server {
>>>>>
>>>>> proxy_set_header X-Forwarded-Proto https;
>>>>> proxy_set_header X-Forwarded-Host  $host;
>>>>> proxy_pass http://localhost:8080/server;
>>>>>
>>>>>   }
>>>>>
>>>>>   location / {
>>>>>
>>>>> proxy_pass http://localhost:4000;
>>>>>
>>>>>   }
>>>>> --End of Nginx Reverse Proxy 
>>>>> setup----
>>>>>
>>>>> Hope it help
>>>>>
>>>>> Mo.
>>>>>
>>>>>
>>>>> On Mon, Mar 13, 2023 at 6:49 PM Douglas Eder Uno Silva <
>>>>> deus...@uefs.br> wrote:
>>>>>
>>>>>> Hi Mohammad! Thanks in advance for the response! I will share more 
>>>>>> details about my installation.
>>>>>>
>>>>>> I created two Dockerfiles (attached), one for the frontend and 
>>

Re: [dspace-tech] Re: Admin user with no privileges

[Mohammad S. AlMutairi]

Hi Douglas,

Thanks for the info. After getting into docker I see my suggestions won't 
work. Setting DSpace in Docker is a bit different than how it is on 
standalone servers. I'm setting a similar environment to yours here trying 
to help.

Do you get any clues when tailing the logs of angular? (docker logs -f 
dspace-angular-container-ID)

Mo.

On Tuesday, March 14, 2023 at 3:09:26 PM UTC+3 Douglas Eder Uno Silva wrote:

> Hi Mo,
>
> Same behavior. Despite being logged in as an administrator, the 
> administrative menu does not appear. No errors on browser console or in 
> DSpace backend logs that could indicate clues of the problem.
> [image: image.png]
> The previous and updated nginx configuration file is attached.
>
> I have this 'architecture' on the server. I removed some things to 
> simplify the diagram. The server runs an NGinx, the DSpace backend and 
> frontend are containers too. All containers are in the same network.
> [image: image.png]
>
> After configuring DSPACE_UI_HOST = localhost, the nginx container could 
> not connect to the container of the frontend to forward the request.
> Nginx could forward the request only after configuring DSPACE_UI_HOST with 
> 0.0.0.0.
>
> Em ter., 14 de mar. de 2023 às 08:19, Douglas Eder Uno Silva <
> deus...@uefs.br> escreveu:
>
>> Hi Mo,
>>
>> I will test these changes and let you know what happens.
>>
>> Em ter., 14 de mar. de 2023 às 06:34, Mohammad S. AlMutairi <
>> alo...@gmail.com> escreveu:
>>
>>> Hi Douglas,
>>>
>>> In addition to the previous message, I noticed you are using a Squid 
>>> Proxy in your network. You might need to bypass the proxy for the 
>>> http/https traffic going from the frontend destined to the backend.
>>>
>>> ENV http_proxy http://proxy.uefs.br:3128
>>> ENV https_proxy http://proxy.uefs.br:3128
>>> ENV NO_PROXY  localhost
>>>
>>> https://docs.docker.com/network/proxy/
>>>
>>> BR, 
>>>
>>> Mo.
>>>
>>> On Tuesday, March 14, 2023 at 12:14:53 AM UTC+3 Mohammad S. AlMutairi 
>>> wrote:
>>>
>>>> Hi Douglas,
>>>>
>>>> For testing to isolate the cause of this issue. Can you try running the 
>>>> frontend on / instead of the subath /app you are running on and also bind 
>>>> it on the localhost adapter?. I'm suspecting the subpath is because of 
>>>> this 
>>>> old issue ( https://github.com/DSpace/dspace-angular/pull/1488 ). It 
>>>> could also be caused by the reverse proxy setup you have. Just try them to 
>>>> know for sure.
>>>>
>>>>   DSPACE_UI_HOST: localhost
>>>>   DSPACE_UI_PORT: '4000'
>>>>   DSPACE_UI_NAMESPACE: /
>>>>
>>>> -Nginx Reverse Proxy 
>>>> setup-
>>>>   location /server {
>>>>
>>>> proxy_set_header X-Forwarded-Proto https;
>>>> proxy_set_header X-Forwarded-Host  $host;
>>>> proxy_pass http://localhost:8080/server;
>>>>
>>>>   }
>>>>
>>>>   location / {
>>>>
>>>> proxy_pass http://localhost:4000;
>>>>
>>>>   }
>>>> --End of Nginx Reverse Proxy 
>>>> setup
>>>>
>>>> Hope it help
>>>>
>>>> Mo.
>>>>
>>>>
>>>> On Mon, Mar 13, 2023 at 6:49 PM Douglas Eder Uno Silva  
>>>> wrote:
>>>>
>>>>> Hi Mohammad! Thanks in advance for the response! I will share more 
>>>>> details about my installation.
>>>>>
>>>>> I created two Dockerfiles (attached), one for the frontend and another 
>>>>> for the backend. Frontend and backend runs is separated containers.
>>>>> Env vars are attached below too.
>>>>>
>>>>> Database migrations returns 'Success' to all. Already make database 
>>>>> clean and migrate again and problem persists.
>>>>>
>>>>> I already checked and the version is 7.5.0 on both frontend and 
>>>>> backend as can be seen on image below
>>>>>
>>>>> I'm here if you need more information..
>>>>>
>>>>> [image: versao_backend_dspace.png][image: versao_frontend_dspace.png]
>>>>> Em segunda-feira, 13 de março de 2023 às 12:19:44 UTC-3, Mohammad S. 
>>>>> AlMutairi escreveu:
>>>

[dspace-tech] Re: SSL problems

[Mohammad S. AlMutairi]

You  don't need to use a self-signed certificate to continue your 
implementation ( You can use it but you don't have to ).  Recent DSpace 
versions are forgiving. You can configure both DSpace ends using domain 
names using (http) or IP that's include private or public IP without SSL 
and DSpace still works.

*** You need to stop the Webserver and have port 80 and 8443 publicly 
accessible for this to work. ***
** dspace.cfg or local.cfg
dspace.server.url = http://server-public-ip:8443/server 

dspace.ui.url =  http://server-public-ip

** config.prod.yml
ui:
  ssl: false
  host: server-private-ip
  port: 80

rest:
  ssl: false
  host: server-public-ip
  port: 8080
  nameSpace: /server

1) yarn test:rest
2) yarn start:prod
3) Access DSpace at http://server-public-ip


The above setup should keep you going till you get your public cert but If 
you still need to get the self-signed cert working you need to post the OS 
and the webserver you are using. Posting the reverse proxy will help.

Mo.

On Friday, March 17, 2023 at 5:58:41 PM UTC+3 Jorge Alberto Bonilla 
Castaneda wrote:

> SSL issues
>
> Good morning, when I hosted my dspace 7.4 on the web, I realized that it 
> is not possible to use the front-end if the back-end does not have a secure 
> certificate.
>
> At the moment we can't get this certificate, but to continue with the 
> implementation and configuration of it I wanted to use a self-generated 
> certificate, so in a local copy of the machine in the cloud, I started 
> trying, generating the certificate with keytool and doing the modifications 
> in the urls of dspace.cfg and config.prod.yml
>
> Well now my back-end was using the 8443.
> [image: cer.png]
>
> however the front-end gave me the following error:
> [image: er.png]
>
> what could be doing wrong? Is it because it is a self generated 
> certificate? 
>
>

-- 
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/6c1f50b1-0e1d-475b-b8e5-75972f99b389n%40googlegroups.com.

Re: [dspace-tech] Re: Admin user with no privileges

[Mohammad S. AlMutairi]

Hi Douglas,

In addition to the previous message, I noticed you are using a Squid Proxy 
in your network. You might need to bypass the proxy for the http/https 
traffic going from the frontend destined to the backend.

ENV http_proxy http://proxy.uefs.br:3128
ENV https_proxy http://proxy.uefs.br:3128
ENV NO_PROXY  localhost

https://docs.docker.com/network/proxy/

BR, 

Mo.

On Tuesday, March 14, 2023 at 12:14:53 AM UTC+3 Mohammad S. AlMutairi wrote:

> Hi Douglas,
>
> For testing to isolate the cause of this issue. Can you try running the 
> frontend on / instead of the subath /app you are running on and also bind 
> it on the localhost adapter?. I'm suspecting the subpath is because of this 
> old issue ( https://github.com/DSpace/dspace-angular/pull/1488 ). It 
> could also be caused by the reverse proxy setup you have. Just try them to 
> know for sure.
>
>   DSPACE_UI_HOST: localhost
>   DSPACE_UI_PORT: '4000'
>   DSPACE_UI_NAMESPACE: /
>
> -Nginx Reverse Proxy setup-
>   location /server {
>
> proxy_set_header X-Forwarded-Proto https;
> proxy_set_header X-Forwarded-Host  $host;
> proxy_pass http://localhost:8080/server;
>
>   }
>
>   location / {
>
> proxy_pass http://localhost:4000;
>
>   }
> --End of Nginx Reverse Proxy setup
>
> Hope it help
>
> Mo.
>
>
> On Mon, Mar 13, 2023 at 6:49 PM Douglas Eder Uno Silva  
> wrote:
>
>> Hi Mohammad! Thanks in advance for the response! I will share more 
>> details about my installation.
>>
>> I created two Dockerfiles (attached), one for the frontend and another 
>> for the backend. Frontend and backend runs is separated containers.
>> Env vars are attached below too.
>>
>> Database migrations returns 'Success' to all. Already make database clean 
>> and migrate again and problem persists.
>>
>> I already checked and the version is 7.5.0 on both frontend and backend 
>> as can be seen on image below
>>
>> I'm here if you need more information..
>>
>> [image: versao_backend_dspace.png][image: versao_frontend_dspace.png]
>> Em segunda-feira, 13 de março de 2023 às 12:19:44 UTC-3, Mohammad S. 
>> AlMutairi escreveu:
>>
>>> Hi Douglas,
>>>
>>> I'm suspecting you are mixing two different versions of DSpace backend 
>>> and frontend. You need to provide more details about the OS and how you 
>>> installed the backend and most importantly how the frontend requirements 
>>> was installed for any to be able to help. 
>>>
>>> You might need to start over the installation by downloading:
>>>
>>>
>>>- Download DSpace 7.5 Backend: 
>>>https://github.com/DSpace/DSpace/releases/tag/dspace-7.5
>>>- Download DSpace 7.5 User Interface: 
>>>https://github.com/DSpace/dspace-angular/releases/tag/dspace-7.5
>>>
>>> Hope it help & Good luck.
>>>
>>> Mo.
>>>
>>>
>>>
>>>
>>>
>>> On Monday, March 13, 2023 at 3:19:16 PM UTC+3 Douglas Eder Uno Silva 
>>> wrote:
>>>
>>>> Hi again,
>>>>
>>>> Nobody faced this type of problem before? Just me?
>>>> I don't know more what to do to make this adminisration menu shows.
>>>> Lost a month on this and the problem persists.
>>>>
>>>> What am i could be doing wrong? Any ideia, guys? I need help please =(
>>>>
>>>> Em segunda-feira, 6 de março de 2023 às 15:41:28 UTC-3, Douglas Eder 
>>>> Uno Silva escreveu:
>>>>
>>>>> Hi everybody,
>>>>>
>>>>> Anyone have the problem of the admin menu showing few items or not 
>>>>> showing at all?
>>>>>
>>>>> Deploy of DSpace 7.4 results in few items on menu and DSpace 7.5 menu 
>>>>> displays nothing.
>>>>>
>>>>> Backend and frontend seems to be fine. Database migrations returns 
>>>>> Sucess on all items, can access HAL Browser, authentication, etc...
>>>>>
>>>>> The user administrator created by `/dspace/bin/dspace 
>>>>> create-administrator` is linked with a group named 'Administrator'
>>>>>
>>>>> What am i could be doing wrong?
>>>>>
>>>>> Thank you in advance for your attention and patience.
>>>>>
>>>> -- 
>> All messages to this mailing list should adhere to the Code of Conduct: 
>> https://

[dspace-tech] Re: Admin user with no privileges

[Mohammad S. AlMutairi]

Hi Douglas,

I'm suspecting you are mixing two different versions of DSpace backend and 
frontend. You need to provide more details about the OS and how you 
installed the backend and most importantly how the frontend requirements 
was installed for any to be able to help. 

You might need to start over the installation by downloading:


   - Download DSpace 7.5 Backend: 
   https://github.com/DSpace/DSpace/releases/tag/dspace-7.5
   - Download DSpace 7.5 User Interface: 
   https://github.com/DSpace/dspace-angular/releases/tag/dspace-7.5

Hope it help & Good luck.

Mo.





On Monday, March 13, 2023 at 3:19:16 PM UTC+3 Douglas Eder Uno Silva wrote:

> Hi again,
>
> Nobody faced this type of problem before? Just me?
> I don't know more what to do to make this adminisration menu shows.
> Lost a month on this and the problem persists.
>
> What am i could be doing wrong? Any ideia, guys? I need help please =(
>
> Em segunda-feira, 6 de março de 2023 às 15:41:28 UTC-3, Douglas Eder Uno 
> Silva escreveu:
>
>> Hi everybody,
>>
>> Anyone have the problem of the admin menu showing few items or not 
>> showing at all?
>>
>> Deploy of DSpace 7.4 results in few items on menu and DSpace 7.5 menu 
>> displays nothing.
>>
>> Backend and frontend seems to be fine. Database migrations returns Sucess 
>> on all items, can access HAL Browser, authentication, etc...
>>
>> The user administrator created by `/dspace/bin/dspace 
>> create-administrator` is linked with a group named 'Administrator'
>>
>> What am i could be doing wrong?
>>
>> Thank you in advance for your attention and patience.
>>
>

-- 
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/289deea0-26ca-482e-9352-f67fbde3809an%40googlegroups.com.

Re: [dspace-tech] Re: Handle Server Issue

[Mohammad S. AlMutairi]

Hi Jake,

You did not need to copy the 6 jar files (not if what you have is dspace 
version 7.4 ).The handle issue you faced and reported in this thread ( 
Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sleepycat/je/DatabaseException  ) is the exact same issue Lewatle 
faced. It's caused by a missing handle storage plugin setup in 
[dspace]/handle-server/config.dct 
and the fix to it is by adding the plugin configuration and it's totally 
different from what Fatih reported in his thread. Fatih was using DSpace 
7.3 and the 6 jar files was missing in that version and the fix is by 
adding those jars files.

BR


On Tuesday, February 28, 2023 at 1:50:10 AM UTC+3 Cameron, Jacob wrote:

Thanks Mohammad.

 

I’m not sure what was different.  Your initial instructions were the ones I 
followed when I created here.  I deleted my old handle-server folder and 
tried them again and now it works.  

 

--

Jake Cameron, BCS(UNB)

Systems Support Specialist III

Information Systems and Technical Services University of Lethbridge Library

Phone:(403)329-2756

This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please 
notify the sender of the error in communication by return e-mail and 
destroy all copies of this e-mail. Thank you.

 

*From:* dspac...@googlegroups.com  *On Behalf Of 
*Mohammad S. AlMutairi
*Sent:* February 27, 2023 2:34 PM
*To:* DSpace Technical Support 
*Subject:* [dspace-tech] Re: Handle Server Issue

 

Caution: This email was sent from someone *outside of the University of 
Lethbridge*. Do not click on links or open attachments unless you know they 
are safe. Suspicious emails should be forwarded to phis...@uleth.ca.

 

Hello Jake, 

 

See if this old post would help ( 
https://groups.google.com/g/dspace-tech/c/wiI45y7xSRs/m/XddGRNE6AQAJ ). 

BR

On Tuesday, February 28, 2023 at 12:23:38 AM UTC+3 Cameron, Jacob wrote:

Hi Everyone, 

Windows, Tomcat 9.6, DSpace 7.4 

I saw the posts https://groups.google.com/g/dspace-tech/c/7WHZ9gkMxSo and 
https://groups.google.com/g/dspace-tech/c/lr7kfeLLEjg/m/PAptuDo8BAAJ. I 
have tried replacing the JARs as suggested, even though the missing JARs 
were associated with DSpace 7.3. I also tried rebuilding the backend to 
make sure there was nothing funky there but I still get the same error with 
the handle server. Nothing is showing up in any of the other log files. 

"2023-02-27 14:17:00.660-0700" 25 Started new run. 
"2023-02-27 14:17:00.660-0700" 25 Handle.net Server Software version 9.3.0 
Exception in thread "main" java.lang.NoClassDefFoundError: 
com/sleepycat/je/DatabaseException 
at net.handle.server.HandleServer.initTxnQueue(HandleServer.java:732) 
at net.handle.server.HandleServer.(HandleServer.java:382) 
at net.handle.server.AbstractServer.getInstance(AbstractServer.java:120) 
at net.handle.server.Main.initialize(Main.java:255) 
at net.handle.server.Main.main(Main.java:122) 
Caused by: java.lang.ClassNotFoundException: 
com.sleepycat.je.DatabaseException 
at 
java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
 

at 
java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
 

at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522) 
... 5 more 

-- 
Jake Cameron, BCS(UNB) 
Systems Support Specialist III 
Information Systems and Technical Services University of Lethbridge Library 
Phone:(403)329-2756 
This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please 
notify the sender of the error in communication by return e-mail and 
destroy all copies of this e-mail. 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...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/dspace-tech/9a303d71-fec9-4a47-aca7-fafe6a606725n%40googlegroups.com
 
<https://groups.google.com/d/msgid/dspace-tech/9a303d71-fec9-4a47-aca7-fafe6a606725n%40googlegroups.com?utm_medium=email_source=footer>
.

-- 
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 Group

[dspace-tech] Re: Handle Server Issue

[Mohammad S. AlMutairi]

Hello Jake,

See if this old post would help ( 
https://groups.google.com/g/dspace-tech/c/wiI45y7xSRs/m/XddGRNE6AQAJ ). 

BR
On Tuesday, February 28, 2023 at 12:23:38 AM UTC+3 Cameron, Jacob wrote:

> Hi Everyone,
>
> Windows, Tomcat 9.6, DSpace 7.4
>
> I saw the posts https://groups.google.com/g/dspace-tech/c/7WHZ9gkMxSo and 
> https://groups.google.com/g/dspace-tech/c/lr7kfeLLEjg/m/PAptuDo8BAAJ. I 
> have tried replacing the JARs as suggested, even though the missing JARs 
> were associated with DSpace 7.3. I also tried rebuilding the backend to 
> make sure there was nothing funky there but I still get the same error with 
> the handle server. Nothing is showing up in any of the other log files.
>
> "2023-02-27 14:17:00.660-0700" 25 Started new run.
> "2023-02-27 14:17:00.660-0700" 25 Handle.net Server Software version 9.3.0
> Exception in thread "main" java.lang.NoClassDefFoundError: 
> com/sleepycat/je/DatabaseException
> at net.handle.server.HandleServer.initTxnQueue(HandleServer.java:732)
> at net.handle.server.HandleServer.(HandleServer.java:382)
> at net.handle.server.AbstractServer.getInstance(AbstractServer.java:120)
> at net.handle.server.Main.initialize(Main.java:255)
> at net.handle.server.Main.main(Main.java:122)
> Caused by: java.lang.ClassNotFoundException: 
> com.sleepycat.je.DatabaseException
> at 
> java.base/jdk.internal.loader.BuiltinClassLoader.loadClass(BuiltinClassLoader.java:581)
> at 
> java.base/jdk.internal.loader.ClassLoaders$AppClassLoader.loadClass(ClassLoaders.java:178)
> at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:522)
> ... 5 more
>
> --
> Jake Cameron, BCS(UNB)
> Systems Support Specialist III
> Information Systems and Technical Services University of Lethbridge Library
> Phone:(403)329-2756 <(403)%20329-2756>
> This e-mail, including any and all attachments, is only for the use of the 
> intended recipient(s) and may contain information that is confidential or 
> privileged. If you are not the intended recipient, you are advised that any 
> dissemination, copying or other use of this e-mail is prohibited. Please 
> notify the sender of the error in communication by return e-mail and 
> destroy all copies of this e-mail. 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/9a303d71-fec9-4a47-aca7-fafe6a606725n%40googlegroups.com.

Re: [dspace-tech] Re: DSpace7 Not accessible via IP Address

[Mohammad S. AlMutairi]

I'm linking both related posts for this same user for future searchers.
https://groups.google.com/g/dspace-tech/c/qORZonB_AYw/m/oBPhbTZJ

On Friday, February 17, 2023 at 5:04:09 PM UTC+3 Agustín Alfieri wrote:

> I may be wrong, but I'm pretty sure that it doesn't matter whether is from 
> the IP or the domain name, as long as you want to access Dspace from 
> anything that's *not localhost* you must enable HTTPS support on the 
> backend. I suggest you take a look at this.
>
> Furthermore, you need to understand that you're not giving us enough 
> information to know whats actually happening. The error 500 only indicates 
> that  "something" is wrong in the backend, but to know what that 
> "something" is you *must look at the logs*. Again,  you should take a 
> closer look at how to troubleshoot an error on Dspace 
> *https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error 
> * and the 
> common installation issues 
> *https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
>  
> .*
>
> El viernes, 17 de febrero de 2023 a la(s) 10:17:39 UTC-3, Ali Shahzad 
> escribió:
>
>> Thank you for your reply.
>> i just only want to enable the access via ip address. 
>> I don't want to access it via domain name. I just want to access it via 
>> ip address. 
>> When I access it via ip address its reaches the dspace home landing page 
>> and then redirects to 500 page services that are unavailable. 
>> I have also attached the screenshot for your reference. please help me 
>>
>> On Fri, Feb 17, 2023 at 4:23 PM 'Agustín Alfieri' via DSpace Technical 
>> Support  wrote:
>>
>>> Hi! 
>>>
>>> The first thing that comes to mind is that maybe you didn't enable HTTPS 
>>> support for the backend, as the wiki says "*If you want to run DSpace 
>>> in Production, you MUST run the backend with HTTPS support* (otherwise 
>>> logins will not work outside of your local domain)."
>>>
>>> If this is not the case you should take a closer look at how to 
>>> troubleshoot an error on Dspace 
>>> *https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error 
>>> * and 
>>> the common installation issues 
>>> *https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-CommonInstallationIssues
>>>  
>>> .
>>>  
>>> *There's not much anything anyone can do with the information you gave 
>>> us, you'll need to look at the logs.
>>>
>>> Agustín.
>>>
>>> El miércoles, 15 de febrero de 2023 a la(s) 01:57:09 UTC-3, Ali Shahzad 
>>> escribió:
>>>
 Dear Community,

 Could you help me for the setup of the Local IP Configuration? I have 
 recently installed 

 dspace7 it's working well on *Localhost:4000* but the problem is that 
 it's not working on the 

 local IP. I want to access dspace7 on the local network.

 Anyone Please help me. i already all relevant setting it reaches the 
 dspace landing page and then redirect to 500 page which is mention that 
 service is not available.
 i have also attached the screenshot for your reference. 
 hostname or ip address i got the same result, service not available.

>>> -- 
>>> 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/9b2ebbc1-9bea-4595-b6c7-25b2877b44c4n%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/f24add47-9cd2-462b-867b-9db7a0493c92n%40googlegroups.com.

[dspace-tech] Re: DSpace7 Not accessible on IP Address

[Mohammad S. AlMutairi]

You need to be polite and apologize to the community members and that's 
because of two reasons. 1) You asking for an un-supported/un-recommended 
configuration. 2) What you are trying to do is already posted in this 
thread (still on the first page) 
https://groups.google.com/g/dspace-tech/c/a3QkSg4zUSg/m/S4rcEVgYBwAJ

Warning: This is an unrecommended and unsupported configuration (I'm asking 
you not to setup it up this unless it's a day or two demonstration server).

 For this to work you must have dspace version 7.3 and above and port 
80 and 8080 should be opened and accessible from inside network or the 
public internet ( See the public access configuration at the bottom of this 
post ).

** To setup DSpace to be accessed from the local/inside/closed network on 
the IP address do:
** In local.cfg or dspace.cfg
dspace.server.url = http://server-private-ip:8080/server
dspace.ui.url =  http://server-private-ip

# In config.prod.yml
ui:
  ssl: false
  host: server-private-ip
  port: 80

rest:
  ssl: false
  host: server-private-ip
  port: 8080
  nameSpace: /server

1) yarn test:rest
2) yarn start:prod
3) Access DSpace at http://server-private-ip


 To setup DSpace to be accessed from the public Internet on the IP 
address configuration do:
** In local.cfg or dspace.cfg
dspace.server.url = http://server-public-ip:8080/server
dspace.ui.url =  http://server-public-ip

# In config.prod.yml
ui:
  ssl: false
  host: server-private-ip
  port: 80

rest:
  ssl: false
  host: server-public-ip
  port: 8080
  nameSpace: /server

1) yarn test:rest
2) yarn start:prod
3) Access DSpace at http://server-public-ip


Speechless :(

On Friday, February 17, 2023 at 8:41:53 AM UTC+3 Ali Shahzad wrote:

> useless community no one is helping ...
>
> thank you. 
>
> On Wednesday, February 15, 2023 at 9:54:41 AM UTC+5 Ali Shahzad wrote:
>
>> Hello Everyone.
>> Dear Community,
>> Could you help me for the setup of the Local IP Configuration? I have 
>> recently installed dspace7 it's working well on localhost:4000 but the 
>> problem is that it's not working on the local IP. I want to access dspace7 
>> on the local network.
>>
>> i have already configured the frontend and backend config file. when i 
>> hit the link it land on the page and the redirect me on the 500 page the 
>> service is unavailable.
>> Please see the attached image for your reference.
>>
>> Please help me...
>>
>

-- 
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/de629f64-a244-4432-adcc-b0681dc4e989n%40googlegroups.com.

[dspace-tech] Re: OAI SUPPORT

[Mohammad S. AlMutairi]

Also, Check Jakob's confirmation of how he solved his issue in his post.

 https://groups.google.com/g/dspace-tech/c/zgPQBcB4YWU/m/IXdt9mFGCQAJ

On Thursday, February 16, 2023 at 9:38:58 AM UTC+3 Mohammad S. AlMutairi 
wrote:

> Hi Nicolas,
>
> Just a suggestion. Double-check how the tomcat connector was installed. 
>
> # You need to replace the Catalina Connector Element on lines 69,70 and 71 
> with the connector settings you see below.
> 6) edit /etc/tomcat9/server.xml
> connectionTimeout="2"
>maxHttpHeaderSize="65536"
>minSpareThreads="25"
>enableLookups="false"
>disableUploadTimeout="true"
>URIEncoding="UTF-8"/>
>
>
> Hope it helps
>
> BR
>
> On Wednesday, February 15, 2023 at 9:10:57 PM UTC+3 Nicolas Battaglia 
> wrote:
>
>> Hello everyone!
>> I am trying to configure the oai server of my dspace 7. The url works 
>> fine /server/oai/request?verb=Identify but when I want to enter the records 
>> section it gives me an error. In the logs I see this: 
>> om.lyncode.xoai.dataprovider.exceptions.OAIException: 
>> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 923; Invalid 
>> byte 2 of 4-byte UTF-8 sequence.
>>
>> It seems to be some coding configuration but I can't figure it out.
>>
>> On the other hand, I have to configure a set to be able to be harvested 
>> by the national repository system of t Argentina , and I managed to find 
>> the documentation or I don't know how to find it.
>> Any help or suggestion?
>>
>> thank you so much
>>
>

-- 
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/e02bd211-5835-40a6-bf32-3ba3911327ben%40googlegroups.com.

[dspace-tech] Re: OAI SUPPORT

[Mohammad S. AlMutairi]

Hi Nicolas,

Just a suggestion. Double-check how the tomcat connector was installed. 

# You need to replace the Catalina Connector Element on lines 69,70 and 71 
with the connector settings you see below.
6) edit /etc/tomcat9/server.xml



Hope it helps

BR

On Wednesday, February 15, 2023 at 9:10:57 PM UTC+3 Nicolas Battaglia wrote:

> Hello everyone!
> I am trying to configure the oai server of my dspace 7. The url works fine 
> /server/oai/request?verb=Identify but when I want to enter the records 
> section it gives me an error. In the logs I see this: 
> om.lyncode.xoai.dataprovider.exceptions.OAIException: 
> org.xml.sax.SAXParseException; lineNumber: 1; columnNumber: 923; Invalid 
> byte 2 of 4-byte UTF-8 sequence.
>
> It seems to be some coding configuration but I can't figure it out.
>
> On the other hand, I have to configure a set to be able to be harvested by 
> the national repository system of t Argentina , and I managed to find the 
> documentation or I don't know how to find it.
> Any help or suggestion?
>
> thank you so much
>

-- 
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/22f1fa4a-531c-40a3-ab60-1773392bf899n%40googlegroups.com.

Re: [dspace-tech] DSpace 5.X: Switching auth method from LDAP to Shibboleth

[Mohammad S. AlMutairi]

You bet

** From the error message you got:
"If the user's netid has changed you will need to manually change it to the 
correct value or unset it in the database."

I think it would be much faster and easier if you can sort and unset the 
netid data for the affected AD users by nulling their netid values in the 
netid column in dapsce --> eperson --> netid column. You should test it 
first on a single user.

Best of luck

BR

On Tuesday, February 14, 2023 at 11:49:15 AM UTC+3 Evelthon Prodromou wrote:

> Hello Mohammad,
>
> No I have not. Will look into it. Thank you for the tip.
>
> E.
>
> On Tuesday, February 14, 2023 at 9:54:23 AM UTC+2 Mohammad S. AlMutairi 
> wrote:
>
>> Hello Evelthon,
>>
>> Have you thought about scripting a bulk modification of the users netid? 
>> (  [dspace]/bin/dspace user --modify -h ).
>>
>> On Tuesday, February 14, 2023 at 9:21:55 AM UTC+3 Evelthon Prodromou 
>> wrote:
>>
>>> Hello Mark,
>>> Thank you  for your reply.
>>>
>>> eduPersonPrincipalName is close but not exactly the same. Will have to 
>>> review my options.
>>>
>>> Evelthon
>>>
>>> On Friday, February 10, 2023 at 3:24:41 PM UTC+2 Mark H. Wood wrote:
>>>
>>>> On Fri, Feb 10, 2023 at 03:06:53AM -0800, Evelthon Prodromou wrote: 
>>>> > Shibboleth SP is configured properly and attributes are released. 
>>>> > 
>>>> > The problem is with Epersons that were previously created with LDAP 
>>>> > authentication. When the same user attempts to authenticate via 
>>>> Shibboleth 
>>>> > a failure occurs and the following error is logged: 
>>>> > 
>>>> > ERROR org.dspace.authenticate.ShibAuthentication @ The identified 
>>>> EPerson 
>>>> > based upon Shibboleth email header, 'mail'='us...@domain.com', is 
>>>> locked to 
>>>> > another netid: 'a_username'. This might be a possible hacking attempt 
>>>> to 
>>>> > steal another 
>>>> > users credentials. If the user's netid has changed you will need to 
>>>> > manually change it to the correct value or unset it in the database. 
>>>> > 
>>>> > What is the proper way for Identity Scheme Migration (LDAP to 
>>>> Shibboleth)? 
>>>>
>>>> I'm only guessing here, but it appears that the Shibboleth attribute 
>>>> that you are using for netid has different values for the same account 
>>>> than the LDAP attribute that you have been using. Does your IDP offer 
>>>> another attribute which tracks the LDAP service's attribute? 
>>>>
>>>> -- 
>>>> Mark H. Wood 
>>>> Lead Technology Analyst 
>>>>
>>>> University Library 
>>>> Indiana University - Purdue University Indianapolis 
>>>> 755 W. Michigan Street 
>>>> Indianapolis, IN 46202 
>>>> 317-274-0749 <(317)%20274-0749> 
>>>> www.ulib.iupui.edu 
>>>>
>>>

-- 
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/3998b1e6-be24-4b7a-abdb-a8f1b84f2f3fn%40googlegroups.com.

Re: [dspace-tech] DSpace 5.X: Switching auth method from LDAP to Shibboleth

[Mohammad S. AlMutairi]

Hello Evelthon,

Have you thought about scripting a bulk modification of the users netid? (  
[dspace]/bin/dspace user --modify -h ).

On Tuesday, February 14, 2023 at 9:21:55 AM UTC+3 Evelthon Prodromou wrote:

> Hello Mark,
> Thank you  for your reply.
>
> eduPersonPrincipalName is close but not exactly the same. Will have to 
> review my options.
>
> Evelthon
>
> On Friday, February 10, 2023 at 3:24:41 PM UTC+2 Mark H. Wood wrote:
>
>> On Fri, Feb 10, 2023 at 03:06:53AM -0800, Evelthon Prodromou wrote: 
>> > Shibboleth SP is configured properly and attributes are released. 
>> > 
>> > The problem is with Epersons that were previously created with LDAP 
>> > authentication. When the same user attempts to authenticate via 
>> Shibboleth 
>> > a failure occurs and the following error is logged: 
>> > 
>> > ERROR org.dspace.authenticate.ShibAuthentication @ The identified 
>> EPerson 
>> > based upon Shibboleth email header, 'mail'='us...@domain.com', is 
>> locked to 
>> > another netid: 'a_username'. This might be a possible hacking attempt 
>> to 
>> > steal another 
>> > users credentials. If the user's netid has changed you will need to 
>> > manually change it to the correct value or unset it in the database. 
>> > 
>> > What is the proper way for Identity Scheme Migration (LDAP to 
>> Shibboleth)? 
>>
>> I'm only guessing here, but it appears that the Shibboleth attribute 
>> that you are using for netid has different values for the same account 
>> than the LDAP attribute that you have been using. Does your IDP offer 
>> another attribute which tracks the LDAP service's attribute? 
>>
>> -- 
>> Mark H. Wood 
>> Lead Technology Analyst 
>>
>> University Library 
>> Indiana University - Purdue University Indianapolis 
>> 755 W. Michigan Street 
>> Indianapolis, IN 46202 
>> 317-274-0749 <(317)%20274-0749> 
>> www.ulib.iupui.edu 
>>
>

-- 
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/ac96c977-1568-4900-a62c-7b905e091870n%40googlegroups.com.

[dspace-tech] Re: 500 Error is showing in UI

[Mohammad S. AlMutairi]

Stop Nginx or Apache and try:

# In local.cfg or dspace.cfg
dspace.server.url = http://52.15.74.25:8080/server
dspace.ui.url =  http://52.15.74.25

# In config.prod.yml
ui:
  ssl: false
  host: Server-IP (Server Private IP)
  port: 80

rest:
  ssl: false
  host: 52.15.74.25
  port: 8080
  nameSpace: /server

1) yarn test:rest
2) yarn start:prod
3) Access DSpace at http://myIP

On Friday, February 10, 2023 at 2:58:35 PM UTC+3 AFA wrote:

> I try but it UI is not opening but back-end is working fine
>
>
> $ ts-node --project ./tsconfig.ts-node.json scripts/test-rest.ts
> Building production app config
> Overriding app config with /opt/dspace-ui/config/config.yml
> Overriding app config with /opt/dspace-ui/config/config.prod.yml
> ...Testing connection to REST API at http://52.15.74.25:8080/server/api...
>
>
> RESPONSE: 200
>
> Checking JSON returned for validity...
> "dspaceVersion" = DSpace 7.4
> "dspaceUI" = http://52.15.74.25:80
> "dspaceServer" = http://52.15.74.25:8080/server
>
> "dspaceServer" property matches UI's "rest" config? true
> Does "/api" endpoint have HAL links ("_links" section)? true
> Done in 3.40s.
>
>
> On Friday, February 10, 2023 at 4:36:43 AM UTC+5:30 Mohammad S. AlMutairi 
> wrote:
>
>> On Wednesday, February 8, 2023 at 4:02:52 PM UTC+3 AFA wrote:
>> *I install the DSpace 7.4  Backend successfully in AWS ubuntu 22.04 
>> server and It is accessible through MYIP:8080/server*
>>
>> *and I install the UI also and I did the test run it is also successful 
>> but I unable to access it through myIP:4000*
>>
>> *then it is accessible by myIP:80 but it through 500 error, Please help 
>> me to solve this issue*
>> You don't need a web server or a reverse proxy for this unrecommended or 
>> unsupported configuration. If you have to have it you can stop the 
>> webserver or disable it and change your configs as you see it below. (For 
>> this to work you must have dspace version 7.3 or above).
>>
>> # In local.cfg or dspace.cfg
>> dspace.server.url = http://myIP:8080/server
>> dspace.ui.url =  http://myIP
>>
>> # In config.prod.yml
>> ui:
>>   ssl: false
>>   host: myIP
>>   port: 80
>>
>> rest:
>>   ssl: false
>>   host: myIP
>>   port: 8080
>>   nameSpace: /server
>>
>> 1) yarn test:rest
>> 2) yarn start:prod
>> 3) Access DSpace at http://myIP
>>
>> BR
>>
>

-- 
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/22fda27a-eb5f-4960-8917-cc86aded8648n%40googlegroups.com.

[dspace-tech] Re: 500 Error is showing in UI

[Mohammad S. AlMutairi]

On Wednesday, February 8, 2023 at 4:02:52 PM UTC+3 AFA wrote:
*I install the DSpace 7.4  Backend successfully in AWS ubuntu 22.04 server 
and It is accessible through MYIP:8080/server*

*and I install the UI also and I did the test run it is also successful but 
I unable to access it through myIP:4000*

*then it is accessible by myIP:80 but it through 500 error, Please help me 
to solve this issue*
You don't need a web server or a reverse proxy for this unrecommended or 
unsupported configuration. If you have to have it you can stop the 
webserver or disable it and change your configs as you see it below. (For 
this to work you must have dspace version 7.3 or above).

# In local.cfg or dspace.cfg
dspace.server.url = http://myIP:8080/server
dspace.ui.url =  http://myIP

# In config.prod.yml
ui:
  ssl: false
  host: myIP
  port: 80

rest:
  ssl: false
  host: myIP
  port: 8080
  nameSpace: /server

1) yarn test:rest
2) yarn start:prod
3) Access DSpace at http://myIP

BR

-- 
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/6d64e76b-87c6-4144-affb-b387dc7c49d7n%40googlegroups.com.

[dspace-tech] Re: Angular is up, but Cannot Login

[Mohammad S. AlMutairi]

Hi  Agustin,

Check https://github.com/DSpace/DSpace/issues/8181

BR


On Thursday, February 9, 2023 at 2:54:48 PM UTC+3 Agustín Alfieri wrote:

> Hi Chris,
>
> I ran into a similar problem as yours. It too get this exception when 
> reindexing the statistics:
> *Exception: Error from server at http://localhost:8983/solr 
> : Path /dspace/solr/statistics must be relative 
> to SOLR_HOME, SOLR_DATA_HOME coreRootDirectory. Set system property 
> 'solr.allowPaths' to add other allowed paths.*
>
> Do you remember how were you able to fix it? Or a general idea of what was 
> the issue?
>
> Agustin.
> El jueves, 6 de enero de 2022 a la(s) 14:41:09 UTC-3, Tim Donohue escribió:
>
>> Hi Chris,
>>
>> We'd definitely appreciate feedback you have on the install instructions 
>> at https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace
>>
>> We've done our best to describe the steps (and various common issues) 
>> that everyone will need to get DSpace installed. But if you've stumbled on 
>> major gaps in our docs, please feel free to either submit them as comments 
>> on that wiki page (you can ask for a free wiki acct by emailing 
>> wiki...@lyrasis.org), or you are welcome to document the changes you'd 
>> recommend at another location & send them my way.  I'll see if I can use it 
>> to improve the main docs.  
>>
>> However, one thing to keep in mind is that we unfortunately need to keep 
>> our instructions "generic" and avoid tailoring them to a specific Operating 
>> System (as DSpace will work on any operating system, it'd be very hard to 
>> maintain / keep up to date instructions for every operating system out 
>> there). So, it's a difficult balance in giving folks the information we 
>> need, while avoiding overwhelming people with too many operating system 
>> specific notes.
>>
>> In any case, feedback is more than welcome.  And, it definitely could 
>> help us to improve these instructions for others
>>
>> Tim
>> On Thursday, January 6, 2022 at 11:16:06 AM UTC-6 Chris Clawson wrote:
>>
>>> Thanks, Tim.
>>> My installation of DSpace 7 is mostly complete. It is up and running, I 
>>> can login, add communities and items. Thanks to Mohamed AlMutairi, he has 
>>> help investigate and resolve many points I hope get into the installation 
>>> documentation. I have been trying to keep a diary on all this, and might 
>>> consider submitting it to the team for review (when ready, if I knew where 
>>> to submit it). At my skill level, there seems to be many missing points 
>>> which might be provided for future users. It is a great package and I look 
>>> forward to further development and a greater acceptance to a wider, less 
>>> technical audience. This would especially benefit small libraries, non 
>>> profit community collections and historical societies.
>>>
>>> On Thursday, January 6, 2022 at 12:05:55 PM UTC-5 Tim Donohue wrote:
>>>
 Hi Chris,

 For hints on solving CORS errors, see the notes in our "Common 
 Installation Issues" in our documentation:

 https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-%22XMLHttpRequest..hasbeenblockedbyCORSpolicy%22or%22CORSerror%22or%22InvalidCORSrequest%22

 Usually, the cause is that the *backend* (REST API) local.cfg configs 
 have the wrong dspace.ui.url setting.

 Tim

 On Monday, December 27, 2021 at 6:52:16 PM UTC-6 Chris Clawson wrote:

> Another Question: Below is the Rest portion of my environment.prods.ts 
> file in /dspace-angular. I am using port 8443, rather than 443. Might 
> this 
> be causing all the 'CORS header ‘Access-Control-Allow-Origin’ missing). 
> Status code: 403' messages?
>
>   rest: {
>   ssl: true,
>   host: 'mywebsite.com',
>   port: 8443,
>   // NOTE: Space is capitalized because 'namespace' is a reserved 
> string in TypeScript
>   nameSpace: '/server'
>   }
>
> On Monday, December 27, 2021 at 7:36:51 PM UTC-5 Chris Clawson wrote:
>
>> More reading led me to my Firefox debug console. There are messages, 
>> like "Cross-Origin Request Blocked: The Same Origin Policy disallows 
>> reading the remote resource at https://myserver.com; all over the 
>> place. I still have no idea what to do about it, but I guess this is 
>> where 
>> I keep studying..
>>
>> On Monday, December 27, 2021 at 3:41:04 PM UTC-5 Chris Clawson wrote:
>>
>>> First DSpace 7 Angular UI screen! – (but) Unable to log in.
>>>
>>> I would appreciate some guidance. I was just successful in getting a 
>>> DSpace 7 welcome screen from my remote webserver. I am unable to log in 
>>> or 
>>> browse the default database . Below the home page search box (Search 
>>> the 
>>> repository) is a message which says “error.top-level-communites “. If I 
>>> click on any of the top menus (Communities, Statistics, etc) 

[dspace-tech] Re: 7.4 workflow view document error

[Mohammad S. AlMutairi]

Hi,

It's possible you are hit by this still open 
bug https://github.com/DSpace/DSpace/issues/8378

On Tuesday, February 7, 2023 at 12:45:14 AM UTC+3 hbla...@gmail.com wrote:

> Hi all, 
> Whe i try to review a submission in STEP_3, get thw following error when 
> want to view pdf file. (Download button). appears like i nedd to have 
> permissions but im authenticated 
>
> Whitelabel Error Page
> This application has no explicit mapping for /error, so you are seeing 
> this as a fallback.
>
> Mon Feb 06 16:38:19 COT 2023
> There was an unexpected error (type=Unauthorized, status=401).
> Authentication is required
>
> The complete error trace is atached.
>

-- 
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/9435ee40-f00a-4898-9c17-6a420e764a29n%40googlegroups.com.

[dspace-tech] Re: Error 500 after enabling HTTPS in DSpace 7.4

[Mohammad S. AlMutairi]

Hi Matus,

Your frontend is trying to reach the backend on 
"'http://repozitar.fhv.uniza.sk:8080/server/; which should not happen 
because of how you tell it to reach the backend in local.cfg. Follow the 
steps you see below it should fix it for you.

** Your local.cfg and config.prod.yml is O.K so don't change them.

# Only follow these steps if DSpace is the only site configured in apache 
in your server.
1) echo "dspace-server-private-ip repozitar.fhv.uniza.sk" >> /etc/hosts
2) a2enmod proxy_http ssl headers
3) rm -rf  /etc/apache2/sites-enabled/*.conf
4) edit /etc/apache2/sites-available/dspace.conf ... Copy and past what's 
in the attached file into dspace.conf.
5) a2ensite dspace.conf
6) systemctl restart apache2

# Test & Build the Frontend
1) yarn test:rest

RESPONSE: 200  
<--- You should get the 200 response for a 
successful connection.

Checking JSON returned for validity...
"dspaceVersion" = DSpace 7.4
"dspaceUI" = https://repozitar.fhv.uniza.sk
<--- should match dspace.ui.url in local.cfg or dspace.cfg
"dspaceServer" = https://repozitar.fhv.uniza.sk/server  
  <--- should match dspace.server.url in local.cfg or dspace.cfg
"dspaceServer" property matches UI's "rest" config? true  
 <--- Should be true before proceeding to the building step
Does "/api" endpoint have HAL links ("_links" section)? true
 <--- Should be true before proceeding to the building step

2) yarn start:prod


*** Make sure tomcat is running on port 8080 and SSL is not enabled in 
Tomcat server.xml config file. SSL termination will be done on Apache 
instead. 

Good luck

On Monday, February 6, 2023 at 1:48:10 PM UTC+3 matus.f...@gmail.com wrote:

> Hi!
>
> Please, I need technical support... My Dspace 7.4 works properly on IP 
> address (without domain name). Then, I got domain name a wanted to enable 
> HTTPS (according to steps in Dspace manual). I used Certbot automatic HTTPS 
> installation. Currently, I use http proxy for front-end as well as for 
> backend, but I always get 500 error when accessing frontend ( 
> https://repozitar.fhv.uniza.sk/ ). 
> Debugging console from Chrome shows me these errors messeges:
>
>
>
>
> *polyfills.5216e8b00933a73e.js:1 Mixed Content: The page at 
> 'https://repozitar.fhv.uniza.sk/ ' was 
> loaded over HTTPS, but requested an insecure XMLHttpRequest endpoint 
> 'http://repozitar.fhv.uniza.sk:8080/server/api 
> '. This request has been 
> blocked; the content must be served over HTTPS.main.5740e328184b19c8.js:1 
> Error:  x {headers: h, status: 0, statusText: 'Unknown Error', url: 
> 'http://repozitar.fhv.uniza.sk:8080/server/api 
> ', ok: 
> false, …}main.5740e328184b19c8.js:1 {statusCode: 0, statusText: 'Unknown 
> Error', message: 'Http failure response for 
> http://repozitar.fhv.uniza.sk:8080/server/api 
> : 0 Unknown Error'}*
>
> It seems that backend (proxy to backend) works fine ( 
> https://repozitar.fhv.uniza.sk/server ). I suppose that my frontend and 
> backend are not correctly connected. Please, check my configuration:
>
> *dspace backend local.cfg contains:*
>
> dspace.server.url = https://repozitar.fhv.uniza.sk/server
> dspace.ui.url = https://repozitar.fhv.uniza.sk
> solr.server = http://localhost:8983/solr
>
> *apache2 /sites-enabled/000-default-le-ssl.conf:*
> ProxyPass /server http://localhost:8080/server
> ProxyPassReverse /server http://localhost:8080/server
> ProxyPass / http://localhost:4000/
> ProxyPassReverse / http://localhost:4000/
> SSLCertificateFile /etc/letsencrypt/live/
> repozitar.fhv.uniza.sk/fullchain.pem
> SSLCertificateKeyFile /etc/letsencrypt/live/
> repozitar.fhv.uniza.sk/privkey.pem
> SSLCertificateChainFile /etc/letsencrypt/live/
> repozitar.fhv.uniza.sk/chain.pem
> Include /etc/letsencrypt/options-ssl-apache.conf
> RequestHeader set X-Forwarded-Proto "https"
> RequestHeader set X-Forwarded-Port "443"
>
> *Dspace front-end config.prod.yml contains:*
>
> ui:
>   ssl: false
>   host: localhost
>   port: 4000
>   rateLimiter:
> windowMs: 6 # 1 minute
> max: 500 # limit each IP to 500 requests per windowMs
>   # Trust X-FORWARDED-* headers from proxies (default = true)
>   useProxies: true
>
> rest:
>   ssl: true
>   host: repozitar.fhv.uniza.sk
>   port: 443
>   nameSpace: /server
>
>  I feel consternated. ... :( Enabling HTTPS on 6.3 was much easier. 
> Thank you so much for any advice on this matter. 
>
> Matus
>
>
>
>

-- 
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 

Re: [dspace-tech] Issue with database migration 6.3 to 7.4

[Mohammad S. AlMutairi]

Hi Jake,

I don't think it's necessary to upgrade the old dspace PostgreSQL version 
because of this issue ( You already have version 13 installed on the new 
server ). This is a common issue that can be caused by several causes. It's 
not related specifically to dspace. Just try the steps you see below and 
keep us updated here in the list.

On the old dspace Server execute (Double check the pg_dump path. 9.6?):
1) cd "C:\Program Files\PostgreSQL\9.6\bin"
2) .\pg_dump -U postgres -W -h localhost -Fc -v -C -c --if-exists -E UTF8 
-d dspace -f dspace-63.sql
3) Move dspace-63.sql file to the new dspace server

On the new dspace server execute:
1) psql --username=postgres dspace
2) DROP EXTENSION pgcrypto;
3) DROP SCHEMA extensions;
4) \q
5) cd "C:\Program Files\PostgreSQL\13\bin"
6) .\pg_restore -U postgres -W -h localhost -v -e -c --if-exists -d dspace 
dspace-63.sql
7) psql --username=postgres dspace
8) \dn
9) \dx
10) \q

** The -e (--exit-on-error) you see in step 6 should give you a clue why 
the old or the new restoring was/is failing so watch for any error and post 
what it shows here to know exactly what's happening in your server 
(Hopefully not).

Regards,
  

On Friday, February 3, 2023 at 1:54:34 AM UTC+3 jacob.cameron wrote:

Hi Mohammad,

 

I’ve actually done that prior to this and still get a large number of 
errors no matter whether I import using psql or pg_restore for an sql or 
plain text dump.

 

I’m wondering if I need to upgrade from 9.6 to 13 in Postgres before it’ll 
fix it.  I’m sure I had to do that when I went from 1.8.3 to 6 originally. 
I could be wrong.  That was along time ago.  But I have something about 
that in old notes from that upgrade.

 

Jake

 

--

Jake Cameron, BCS(UNB)

Systems Support Specialist III

Information Systems and Technical Services University of Lethbridge Library

Phone:(403)329-2756

This e-mail, including any and all attachments, is only for the use of the 
intended recipient(s) and may contain information that is confidential or 
privileged. If you are not the intended recipient, you are advised that any 
dissemination, copying or other use of this e-mail is prohibited. Please 
notify the sender of the error in communication by return e-mail and 
destroy all copies of this e-mail. Thank you.

 

*From:* dspac...@googlegroups.com  *On Behalf Of 
*Mohammad S. AlMutairi
*Sent:* January 27, 2023 5:21 PM
*To:* DSpace Technical Support 
*Subject:* Re: [dspace-tech] Issue with database migration 6.3 to 7.4

 

Caution: This email was sent from someone *outside of the University of 
Lethbridge*. Do not click on links or open attachments unless you know they 
are safe. Suspicious emails should be forwarded to phis...@uleth.ca.

 

Hi all, 

 

@Tim, I think Jacob issue is caused by the way he dumped his old database 
and the way he tried to restore it.  Those " thousands of invalid command 
/N" should've not shown up if the database was dumped in a custom binary 
format and the new server database was cleaned (emptied) or even recreated 
before restoring the old database int it using pg_restore (It's a must to 
use pg_restore for any binary format dumps). There is a good chance for him 
to able to migrate unless he is affected by the known issue you mentioned.

 

https://www.pgadmin.org/docs/pgadmin4/6.18/backup_dialog.html

 

Regards

On Friday, January 27, 2023 at 11:04:41 PM UTC+3 Tim Donohue wrote:

Hi Sean,

 

This issue is a known issue which some sites encounter during the upgrade 
to DSpace 7 *if they have previously ignored migrations which never ran 
during a past 5.x ->6.x upgrade*​.  Essentially, to summarize, there are 
two "5.7" migrations which can fail during the upgrade to 7.x... these 
migrations are *obsolete*​ and can be skipped over.

 

There's a thread discussing this on dspace-tech here, along with 
"workarounds" to skip the two problematic 5.7 migrations: 
https://groups.google.com/g/dspace-tech/c/PlOA1WMvd4M/m/eBVE5RfhBgAJ

 

There's also a fix for this coming in the 7.5 release.  In 7.5 (due Feb 20) 
we have a new "./dspace database skip" command which can be used to skip 
problematic migrations.  See the PR at 
https://github.com/DSpace/DSpace/pull/8611

 

So, you are not the first person to hit this migration bug. An easier fix 
is coming in 7.5... but in the meantime, you can use the dspace-tech link 
above to workaround the issue if you want to upgrade immediately to 7.4.


Tim

*From:* dspac...@googlegroups.com  on behalf of 
Cameron, Jacob 
*Sent:* Friday, January 27, 2023 12:46 PM
*To:* Sean Carte 


*Cc:* DSpace Technical Support 

*Subject:* RE: [dspace-tech] Issue with database migration 6.3 to 7.4 

 

I’ve tried importing with the postgres account, using an elevated command 
prompt, in pgadmin and they are all giving the same errors.  It’s still 
failing.  I’m at a loss now.  There’s a ton of tables missing when it 
finishes importing.

 

--

Jake

Re: [dspace-tech] Issue with database migration 6.3 to 7.4

[Mohammad S. AlMutairi]

Hi all,

@Tim, I think Jacob issue is caused by the way he dumped his old database 
and the way he tried to restore it.  Those " thousands of invalid command 
/N" should've not shown up if the database was dumped in a custom binary 
format and the new server database was cleaned (emptied) or even recreated 
before restoring the old database int it using pg_restore (It's a must to 
use pg_restore for any binary format dumps). There is a good chance for him 
to able to migrate unless he is affected by the known issue you mentioned.

https://www.pgadmin.org/docs/pgadmin4/6.18/backup_dialog.html

Regards
On Friday, January 27, 2023 at 11:04:41 PM UTC+3 Tim Donohue wrote:

> Hi Sean,
>
> This issue is a known issue which some sites encounter during the upgrade 
> to DSpace 7 *if they have previously ignored migrations which never ran 
> during a past 5.x ->6.x upgrade*​.  Essentially, to summarize, there are 
> two "5.7" migrations which can fail during the upgrade to 7.x... these 
> migrations are *obsolete*​ and can be skipped over.
>
> There's a thread discussing this on dspace-tech here, along with 
> "workarounds" to skip the two problematic 5.7 migrations: 
> https://groups.google.com/g/dspace-tech/c/PlOA1WMvd4M/m/eBVE5RfhBgAJ
>
> There's also a fix for this coming in the 7.5 release.  In 7.5 (due Feb 
> 20) we have a new "./dspace database skip" command which can be used to 
> skip problematic migrations.  See the PR at 
> https://github.com/DSpace/DSpace/pull/8611
>
> So, you are not the first person to hit this migration bug. An easier fix 
> is coming in 7.5... but in the meantime, you can use the dspace-tech link 
> above to workaround the issue if you want to upgrade immediately to 7.4.
>
> Tim
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of Cameron, Jacob 
> *Sent:* Friday, January 27, 2023 12:46 PM
> *To:* Sean Carte 
>
> *Cc:* DSpace Technical Support 
> *Subject:* RE: [dspace-tech] Issue with database migration 6.3 to 7.4 
>  
>
> I’ve tried importing with the postgres account, using an elevated command 
> prompt, in pgadmin and they are all giving the same errors.  It’s still 
> failing.  I’m at a loss now.  There’s a ton of tables missing when it 
> finishes importing.
>
>  
>
> --
>
> Jake Cameron, BCS(UNB)
>
> Systems Support Specialist III
>
> Information Systems and Technical Services University of Lethbridge Library
>
> Phone:(403)329-2756 <(403)%20329-2756>
>
> This e-mail, including any and all attachments, is only for the use of the 
> intended recipient(s) and may contain information that is confidential or 
> privileged. If you are not the intended recipient, you are advised that any 
> dissemination, copying or other use of this e-mail is prohibited. Please 
> notify the sender of the error in communication by return e-mail and 
> destroy all copies of this e-mail. Thank you.
>
>  
>
> *From:* Sean Carte  
> *Sent:* January 27, 2023 12:31 AM
> *To:* Cameron, Jacob 
> *Cc:* DSpace Technical Support 
> *Subject:* Re: [dspace-tech] Issue with database migration 6.3 to 7.4
>
>  
>
> Caution: This email was sent from someone *outside of the University of 
> Lethbridge*. Do not click on links or open attachments unless you know 
> they are safe. Suspicious emails should be forwarded to phis...@uleth.ca.
>
>  
>
> Hi Jacob
>
>  
>
> I had a similar problem with a database I was trying to import: many /N 
> invalid commands. I gave my user superuser privileges and was able to 
> import the dump without those errors.
>
>  
>
> Sean
>
>  
>
> On Thu, 26 Jan 2023 at 23:06, Cameron, Jacob  wrote:
>
> Hi Everyone,
>
> I exported my DSpace 6.3 database, imported it on the new server running 
> 7.4.  There were thousands of invalid command /N that showed up during the 
> import and lots of other ERROR: relation "xxx" does not exist.
>
> I did try running dspace database migrate ignored afterwards and was given 
> some errors. 
>
> I checked the DSpace log and there was some messaged about being unable to 
> find the bean by name or database but that may have been when I deleted my 
> old database before recreating the new one to import to.
>
> Any thoughts or suggestions would be welcome.  I've seen a few suggestions 
> out there and I've tried them, but I haven't had any luck.
>
> C:\DSpace\bin>dspace database migrate ignored
> Using DSpace installation in: C:\DSpace
>
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Migrating database to latest version AND running previously "Ignored" 
> migrations... (Check logs for details)
> Migration exception:
> java.sql.SQLException: Flyway migration error occurred
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:785)
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:672)
> at 
> org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:195)
> at 
> 

[dspace-tech] Re: OAI-PMH showing incorrect Repository Information and contains wrong links

[Mohammad S. AlMutairi]

Glad you had your issue sorted out. It's hard to convince an old fashion 
guy not to go the manual way to avoid rebuilding the backend.


On Friday, January 20, 2023 at 5:01:10 PM UTC+3 domi...@wp.pl wrote:

> Thanks for advise, but I found (in my opinion) easier solution, just run 
> this 3 commands:
> /dspace/bin/dspace generate-sitemaps
> /dspace/bin/dspace oai clean-cache
> /dspace/bin/dspace oai import
> After that just restart tomcat and everything should works. I hope this 
> solution will help someone with familiar problem.
> piątek, 20 stycznia 2023 o 14:36:49 UTC+1 alo...@gmail.com napisał(a):
>
>> Hello Dominik,
>>
>> Try this it should take care of the issue you have.
>>
>> a) su - postgres
>> b) Dump the databse in text format ( pg_dump -c dspace > 
>> dspace-migrated.sql )
>> c) cp dspace-migrated.sql dspace-orig.sql <--- Always keep a backup of 
>> the original version of the database to revert to if you have to.
>> c) Edit dspace-migrated.sql and search for bb.ds.edu.com and replace it 
>> with aa.ds.edu.com using ( sed, awk, perl, vi or any text editor you 
>> feel comfortable with "notepad++ 
>>  for instance in Windows" ).
>> d) Restore it ( cat  dspace-migrated.sql   | psql -d dspace  )
>>
>> https://groups.google.com/g/dspace-tech/c/KLJ3moDpVp4/m/q2U_-h36BgAJ
>>
>> Hope it help you.
>> On Friday, January 20, 2023 at 2:28:41 PM UTC+3 domi...@wp.pl wrote:
>>
>>> Hello everyone,
>>> Yesterday I decided to change dspace url for example: from  *bb.ds.edu.com 
>>> * to *aa.ds.edu.com . *For 
>>> now I changed url in local.cfg, apache dspace.conf and config.prod.yml, 
>>> after that I run mvn package, ant update and yarn build:prod. Everything 
>>> works fine except OAI-PMH, I changed repository name in local.cfg but it's 
>>> not updated  also repository identifier is wrong (shows old link) and every 
>>> link in this page redirect to to old url, except that everything works if I 
>>> manualy change link for example:  from *bb.ds.edu.com 
>>> * :8080/server/oai/openaire?verb=ListSets to  
>>> *aa.ds.edu.com 
>>> * :8080/server/oai/openaire?verb=ListSets
>>> Does anyone know how to fix it?
>>> Best regards,
>>> Dominik
>>
>>

-- 
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/566c94ca-01f3-4512-9f71-4ff4d6310984n%40googlegroups.com.

[dspace-tech] Re: OAI-PMH showing incorrect Repository Information and contains wrong links

[Mohammad S. AlMutairi]

Hello Dominik,

Try this it should take care of the issue you have.

a) su - postgres
b) Dump the databse in text format ( pg_dump -c dspace > 
dspace-migrated.sql )
c) cp dspace-migrated.sql dspace-orig.sql <--- Always keep a backup of the 
original version of the database to revert to if you have to.
c) Edit dspace-migrated.sql and search for bb.ds.edu.com and replace it 
with aa.ds.edu.com using ( sed, awk, perl, vi or any text editor you feel 
comfortable with "notepad++  for 
instance in Windows" ).
d) Restore it ( cat  dspace-migrated.sql   | psql -d dspace  )

https://groups.google.com/g/dspace-tech/c/KLJ3moDpVp4/m/q2U_-h36BgAJ

Hope it help you.
On Friday, January 20, 2023 at 2:28:41 PM UTC+3 domi...@wp.pl wrote:

> Hello everyone,
> Yesterday I decided to change dspace url for example: from  *bb.ds.edu.com 
> * to *aa.ds.edu.com . *For 
> now I changed url in local.cfg, apache dspace.conf and config.prod.yml, 
> after that I run mvn package, ant update and yarn build:prod. Everything 
> works fine except OAI-PMH, I changed repository name in local.cfg but it's 
> not updated  also repository identifier is wrong (shows old link) and every 
> link in this page redirect to to old url, except that everything works if I 
> manualy change link for example:  from *bb.ds.edu.com 
> * :8080/server/oai/openaire?verb=ListSets to  
> *aa.ds.edu.com 
> * :8080/server/oai/openaire?verb=ListSets
> Does anyone know how to fix it?
> Best regards,
> Dominik

-- 
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/0616bd75-1b81-4c03-9820-b43cac0687aen%40googlegroups.com.

[dspace-tech] Re: Deploy Dspace 7.4 with Add HTTPS support

[Mohammad S. AlMutairi]

Definitely you need to execute these two commands before you execute yarn 
test:rest in my previous post.

   - echo "export NODE_EXTRA_CA_CERTS=/etc/ssl/certs/server.crt" >> 
   /etc/environment
   -  export NODE_EXTRA_CA_CERTS=/etc/ssl/certs/server.crt

### Running DSpace Frontend service using systemd 
###
1) Copy and paste into putty while logged in as root and hit enter.
cat << EOF > /lib/systemd/system/dspace-angular.service 
[Unit]
Description=DSpace Frontend Server
After=tomcat9.service

[Service]
ExecStart=/usr/bin/node dist/server/main
WorkingDirectory=/opt/dspace-angular
Restart=always
RestartSec=10
User=www-data
Group=www-data
Environment="NODE_ENV=production"
Environment="NODE_EXTRA_CA_CERTS=/etc/ssl/certs/server.crt"

[Install]
WantedBy=multi-user.target
EOF

2) chown -R www-data:www-data /opt/dspace-angular/
3) systemctl daemon-reload
4) systemctl enable dspace-angular
5) systemctl restart dspace-angular
6) systemctl status dspace-angular
### End of Running DSpace Frontend service using 
systemd ###

Cheers
On Thursday, January 19, 2023 at 8:38:17 PM UTC+3 Mohammad S. AlMutairi 
wrote:

> Hi Vinicio,
>
> I don't think it has to do with the DNS. You can easily take the DNS out 
> of the equation (override it) by adding an entry for dspace server into the 
> /etc/hosts file in the server itself and in the workstation where you are 
> accessing dspace server from (In Windows - 
> C:\Windows\System32\drivers\etc\hosts). I'm suspecting it has to do with 
> the config.yml you used or the apache webserver configuration so try the 
> steps you see below and keep us updated in the list.
>
>1. apt-get --purge remove apache2 -y (remove all old configuration)
>2. apt install apache2 -y
>3. a2enmod proxy_http ssl headers
>4. a2dissite 000-default default-ssl
>5. edit /etc/apache2/sites-available/dspace.conf and copy and past 
>what's in the attached file into  /etc/apache2/sites-available/dspace.conf
>6. openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -sha256 
>-keyout /etc/ssl/private/server.key -out /etc/ssl/certs/server.crt -subj 
>"/CN=mydomain.com" -addext "subjectAltName=DNS:mydomain.com,DNS:
>dspace.mydomain.com"
>7. echo "dspace-server-IP mydomain.com" >> /etc/hosts
>8. Open a Windows elevated command prompt on the Client/Workstation 
>and execute ( echo  dspace-server-IP  mydomain.com >> 
>C:\Windows\System32\drivers\etc\hosts )
>9. a2ensite dspace.conf
>10. systemctl enable apache2
>11. systemctl restart apache2
>12. systemctl status apache2
>13. Make sure tomcat is running on port 8080 (  journalctl -u tomcat9 
>--boot | grep "Initializing ProtocolHandler" )
>
>
> *** [dspace]/config/dspace.cfg or local.cfg
> dspace.server.url = https://mydomain.com/server
> dspace.ui.url = https://mydomain.com
> solr.server = http://localhost:8983/solr
>
> *** [dspace-angular]/config/config.prod.yml
> 1) cp  [dspace-angular]/config/config.example.yml  
> [dspace-angular]/config/config.prod.yml
> 2) edit [dspace-angular]/config/config.prod.yml
> ui:
>   ssl: false
>   host: localhost
>   port: 4000
>
> rest:
>   ssl: true
>   host: mydomain.com
>   port: 443
>   nameSpace: /server
>
> 3) yarn test:rest
> 4) yarn start:prod
>
> I Hope that help you.
>
>
> On Thursday, January 19, 2023 at 12:51:52 AM UTC+3 Vinicio Gramkow wrote:
>
>> Hi, my DSpace version is 7.4 and is running on the following 
>> configurations: 
>>
>> Ubuntu 22.04.1LTS 
>> Apache 2.4.52 
>> Node 12.22.9 
>> Tomcat 9.0.68 
>>
>> The certificate is a self-signed one generated using openssl. 
>> I have in my hosts file the IP pointed to the domain.  
>>
>>   From what I've observed, it could be something related to the DNS 
>> server redirection, but I'm not sure why this is happening, and if this is 
>> really the case.
>>
>> Em segunda-feira, 16 de janeiro de 2023 às 21:59:32 UTC-3, 
>> alo...@gmail.com escreveu:
>>
>>> Hi Vinicio,
>>>
>>> Never seen that redirection error happening in DSpace but in Wordpress 
>>> long time ago. You need to provide more information about your dspace 
>>> version and setup because everything seems right. Try the redirects.sh 
>>> script you see here 
>>> https://www.liquidweb.com/kb/troubleshooting-too-many-redirects/ ... it 
>>> should give you some hints what causing the redirection.
>>>
>>>
>>>
>>> On Tuesday, January 17, 2023 at 3:29:13 AM UTC+3 Vinicio

[dspace-tech] Re: Deploy Dspace 7.4 with Add HTTPS support

[Mohammad S. AlMutairi]

Hi Vinicio,

I don't think it has to do with the DNS. You can easily take the DNS out of 
the equation (override it) by adding an entry for dspace server into the 
/etc/hosts file in the server itself and in the workstation where you are 
accessing dspace server from (In Windows - 
C:\Windows\System32\drivers\etc\hosts). I'm suspecting it has to do with 
the config.yml you used or the apache webserver configuration so try the 
steps you see below and keep us updated in the list.

   1. apt-get --purge remove apache2 -y (remove all old configuration)
   2. apt install apache2 -y
   3. a2enmod proxy_http ssl headers
   4. a2dissite 000-default default-ssl
   5. edit /etc/apache2/sites-available/dspace.conf and copy and past 
   what's in the attached file into  /etc/apache2/sites-available/dspace.conf
   6. openssl req -x509 -nodes -days 3650 -newkey rsa:4096 -sha256 -keyout 
   /etc/ssl/private/server.key -out /etc/ssl/certs/server.crt -subj 
   "/CN=mydomain.com" -addext 
   "subjectAltName=DNS:mydomain.com,DNS:dspace.mydomain.com"
   7. echo "dspace-server-IP mydomain.com" >> /etc/hosts
   8. Open a Windows elevated command prompt on the Client/Workstation and 
   execute ( echo  dspace-server-IP  mydomain.com >> 
   C:\Windows\System32\drivers\etc\hosts )
   9. a2ensite dspace.conf
   10. systemctl enable apache2
   11. systemctl restart apache2
   12. systemctl status apache2
   13. Make sure tomcat is running on port 8080 (  journalctl -u tomcat9 
   --boot | grep "Initializing ProtocolHandler" )


*** [dspace]/config/dspace.cfg or local.cfg
dspace.server.url = https://mydomain.com/server
dspace.ui.url = https://mydomain.com
solr.server = http://localhost:8983/solr

*** [dspace-angular]/config/config.prod.yml
1) cp  [dspace-angular]/config/config.example.yml  
[dspace-angular]/config/config.prod.yml
2) edit [dspace-angular]/config/config.prod.yml
ui:
  ssl: false
  host: localhost
  port: 4000

rest:
  ssl: true
  host: mydomain.com
  port: 443
  nameSpace: /server

3) yarn test:rest
4) yarn start:prod

I Hope that help you.


On Thursday, January 19, 2023 at 12:51:52 AM UTC+3 Vinicio Gramkow wrote:

> Hi, my DSpace version is 7.4 and is running on the following 
> configurations: 
>
> Ubuntu 22.04.1LTS 
> Apache 2.4.52 
> Node 12.22.9 
> Tomcat 9.0.68 
>
> The certificate is a self-signed one generated using openssl. 
> I have in my hosts file the IP pointed to the domain.  
>
>   From what I've observed, it could be something related to the DNS 
> server redirection, but I'm not sure why this is happening, and if this is 
> really the case.
>
> Em segunda-feira, 16 de janeiro de 2023 às 21:59:32 UTC-3, 
> alo...@gmail.com escreveu:
>
>> Hi Vinicio,
>>
>> Never seen that redirection error happening in DSpace but in Wordpress 
>> long time ago. You need to provide more information about your dspace 
>> version and setup because everything seems right. Try the redirects.sh 
>> script you see here 
>> https://www.liquidweb.com/kb/troubleshooting-too-many-redirects/ ... it 
>> should give you some hints what causing the redirection.
>>
>>
>>
>> On Tuesday, January 17, 2023 at 3:29:13 AM UTC+3 Vinicio Gramkow wrote:
>>
>>>
>>> Hello everyone! I have the same problem, I performed all the steps above 
>>> and I am having the following error when trying to access dspace:
>>>
>>> ERR_TOO_MANY_REDIRECTS
>>>
>>>
>>> dspace.cfg
>>>
>>> dspace.server.url = https://mydomain.com/server
>>> dspace.ui.url = https://mydomain.com
>>>
>>> config.yml
>>>
>>> rest:
>>>ssl: true
>>>host: mydomain.com
>>>port: 443
>>>nameSpace: /server
>>>
>>> ui:
>>>ssl: false
>>>host: localhost
>>>port: 4000
>>>nameSpace: /
>>>
>>> When I use yarn test:rest I get http code 200 correctly.
>>>
>>> apache configuration file
>>>
>>> 
>>>   ServerName mydomain.com
>>>   Redirect / https://mydomain.com/
>>> 
>>>
>>> 
>>>   ServerName mydomain.com
>>>   LogLevel warn
>>>   ErrorLog ${APACHE_LOG_DIR}/mydomain.com.error.log
>>>   CustomLog ${APACHE_LOG_DIR}/mydomain.com.access.log combined
>>>   ProxyRequests on
>>>   SSLEngine on
>>>   SSLProxyEngine on
>>>   SSLCertificateFile /etc/ssl/certs/server.crt
>>>   SSLCertificateKeyFile /etc/ssl/private/server.key
>>>   SSLCompression off
>>>   SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
>>>   SSLCipherSuite 
>>> ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM>
>>>  
>>> SSLHonorCipherOrder off
>>>   SSLSessionTickets off
>>>   ProxyPreserveHost on
>>>   RequestHeader set X-Forwarded-Proto https
>>>
>>> 
>>> AddDefaultCharset Off
>>> Require all granted
>>> 
>>>
>>>   ProxyPass /server http://localhost:8080/server
>>>   ProxyPassReverse /server http://localhost:8080/server
>>>   ProxyPass / http://localhost:4000/
>>>   ProxyPassReverse / http://localhost:4000/
>>>
>>> 
>>>
>>> What could I be doing wrong? I've 

[dspace-tech] Re: Dspace Data Migration with SAF

[Mohammad S. AlMutairi]

Hello Rupinder,

I'm so glad you finally had it sorted out. You are most welcome.

Be safe & Cheers

On Wednesday, January 18, 2023 at 4:24:22 PM UTC+3 jesse...@gmail.com wrote:

> Dear Mr. AlMutairi, 
> You were right, it was an issue with assetstore folder permissions and 
> ownership. just one chown command and it was fixed. everything is now 
> working as expected. 
> But I still don't understand why AIP didn't work, and why it is so 
> complicated. Anyway, I will continue to experiment with that.   
> Thank you so much for all your help. That is all I needed, for now, to 
> migrate my repository from the old server to a new one. 
> We shall consider this case closed. 
> Thank you once again.
>
> with regards
> Rupinder Singh
> Assistant Librarian
> Central University of Punjab
>
> On Wednesday, January 11, 2023 at 9:18:23 PM UTC+5:30 alo...@gmail.com 
> wrote:
>
>> Maybe I should retire. :-)
>> [dspace]/bin/dspace index-discovery -b
>>
>> On Wednesday, January 11, 2023 at 6:44:58 PM UTC+3 Mohammad S. AlMutairi 
>> wrote:
>>
>>> Hello  Rupinder,
>>>
>>> You are almost there. You should have some clues in the log 
>>> [dspace]/log/dspace.log ... This error  ( An internal read or write 
>>> operation failed ) suggest it could be a permission problem or the the 
>>> assetstore is not where it expected to be (guessing) so check them both 
>>> also make sure dc.identifier.uri links are correct for all the moved items 
>>> and finally you need to do a discovery indexing [dspace]/bin/dspace 
>>> discovery-index -b 
>>>
>>> Good luck
>>> On Wednesday, January 11, 2023 at 3:31:47 PM UTC+3 jesse...@gmail.com 
>>> wrote:
>>>
>>>> Dear Mr. AlMutairi, 
>>>> That worked, and I was able to restore the database and the assetstore 
>>>> on my new DSpace 7  installation. I can now see all the collections, 
>>>> communities, and items on my Angular GUI. But as soon as i open any item, 
>>>> It shows the metadata of the document uploaded but gives the following 
>>>> error when is click the bitstream (a PDF dissertation in my case).
>>>>
>>>> Whitelabel Error Page
>>>>
>>>> This application has no explicit mapping for /error, so you are seeing 
>>>> this as a fallback.
>>>> Wed Jan 11 17:56:55 IST 2023
>>>> There was an unexpected error (type=Internal Server Error, status=500).
>>>> An internal read or write operation failed
>>>>
>>>> On Wednesday, January 11, 2023 at 10:43:58 AM UTC+5:30 Rupinder Singh 
>>>> wrote:
>>>>
>>>>> Dear Mr. AlMutairi, 
>>>>> I sent you copies of dspace.cfg, local.cfg, and bitstore.xml. on your 
>>>>> personal mail.
>>>>> However, after your suggestion, I checked the local.cfg file and found 
>>>>> that all the configuration settings were stored there and the assetstore 
>>>>> folder is set to  /mnt/dspace/assetstore . So I have taken a backup of 
>>>>> it, 
>>>>> and will now try restoring it on my DSPACE 7 test server as you suggested 
>>>>> in your first mail.  
>>>>> Please have a look at the config files though, we may come to find 
>>>>> something more that went unnoticed before. 
>>>>>
>>>>> Thank You 
>>>>> Rupinder Singh
>>>>>
>>>>> On Tuesday, January 10, 2023 at 8:25:51 PM UTC+5:30 alo...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> I wanted to warn you that bitstore.xml might have your 
>>>>>> Amazon awsAccessKey, awsSecretKey, and bucketName so remove them if you 
>>>>>> are 
>>>>>> going to send the files or you can take it from here and move your 
>>>>>> missing 
>>>>>> assetstore to the server filesystem and follow the usual upgrade 
>>>>>> procedure.
>>>>>>
>>>>>> On Tuesday, January 10, 2023 at 5:32:28 PM UTC+3 Mohammad S. 
>>>>>> AlMutairi wrote:
>>>>>>
>>>>>>> Please forget AIP and SAF.
>>>>>>>
>>>>>>> Can you get me privately a copy of local.cfg, dspace.cfg and  
>>>>>>> [dspace]/config/spring/api/bitstore.xml .. You can remove anything 
>>>>>>> private 
>>>>>>> data you think is worth removing ( database password, domain ..etc ).
>>

[dspace-tech] Re: Deploy Dspace 7.4 with Add HTTPS support

[Mohammad S. AlMutairi]

Hi Vinicio,

Never seen that redirection error happening in DSpace but in Wordpress long 
time ago. You need to provide more information about your dspace version 
and setup because everything seems right. Try the redirects.sh script you 
see here https://www.liquidweb.com/kb/troubleshooting-too-many-redirects/ 
... it should give you some hints what causing the redirection.



On Tuesday, January 17, 2023 at 3:29:13 AM UTC+3 Vinicio Gramkow wrote:

>
> Hello everyone! I have the same problem, I performed all the steps above 
> and I am having the following error when trying to access dspace:
>
> ERR_TOO_MANY_REDIRECTS
>
>
> dspace.cfg
>
> dspace.server.url = https://mydomain.com/server
> dspace.ui.url = https://mydomain.com
>
> config.yml
>
> rest:
>ssl: true
>host: mydomain.com
>port: 443
>nameSpace: /server
>
> ui:
>ssl: false
>host: localhost
>port: 4000
>nameSpace: /
>
> When I use yarn test:rest I get http code 200 correctly.
>
> apache configuration file
>
> 
>   ServerName mydomain.com
>   Redirect / https://mydomain.com/
> 
>
> 
>   ServerName mydomain.com
>   LogLevel warn
>   ErrorLog ${APACHE_LOG_DIR}/mydomain.com.error.log
>   CustomLog ${APACHE_LOG_DIR}/mydomain.com.access.log combined
>   ProxyRequests on
>   SSLEngine on
>   SSLProxyEngine on
>   SSLCertificateFile /etc/ssl/certs/server.crt
>   SSLCertificateKeyFile /etc/ssl/private/server.key
>   SSLCompression off
>   SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
>   SSLCipherSuite 
> ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM>
>  
> SSLHonorCipherOrder off
>   SSLSessionTickets off
>   ProxyPreserveHost on
>   RequestHeader set X-Forwarded-Proto https
>
> 
> AddDefaultCharset Off
> Require all granted
> 
>
>   ProxyPass /server http://localhost:8080/server
>   ProxyPassReverse /server http://localhost:8080/server
>   ProxyPass / http://localhost:4000/
>   ProxyPassReverse / http://localhost:4000/
>
> 
>
> What could I be doing wrong? I've been trying to do this for two weeks. 
> Grateful if anyone can help me.
> Em quarta-feira, 11 de janeiro de 2023 às 10:24:21 UTC-3, 
> m.kussai...@gmail.com escreveu:
>
>>
>> Thank you very much Sir Muhammad. Everything works great. Thanks again!
>>
>> вторник, 10 января 2023 г. в 22:01:03 UTC+6, alo...@gmail.com: 
>>
>>> I'm posting it here in a hope it will help someone else who might need 
>>> clues what should be changed.
>>>
>>>
>>>1. echo "10.17.0.12  repository.kaznu.kz" >> /etc/hosts
>>>2. a2enmod proxy_http proxy_html ssl headers
>>>3. a2dissite 000-default default-ssl
>>>4. Overwrite /etc/tomcat9/server.xml with the attached file 
>>>(server.xml).
>>>5. Overwrite /etc/apache2/sites-available/repository_kaznu_kz.conf 
>>>with the attached file (repository_kaznu_kz.conf).
>>>6. a2ensite repository_kaznu_kz.conf
>>>7. systemctl restart apache2.service
>>>8. systemctl restart tomcat9.service
>>>9. test the frontend (yarn test:rest)
>>>10. build the frontend
>>>11. access your backend by visiting 
>>>https://repository.kaznu.kz/server
>>>12. access the frontend by visiting https://repository.kaznu.kz
>>>
>>>
>>> Cheers
>>> On Tuesday, January 10, 2023 at 1:32:57 PM UTC+3 m.kussai...@gmail.com 
>>> wrote:
>>>
 I type IP adress in google chrome 10.17.0.12  Apache works

 вторник, 10 января 2023 г. в 16:32:21 UTC+6, Мухаметали Кусайынов: 

> I type IP adress in google chrome 10.17.0.12  Apache works
>
> вторник, 10 января 2023 г. в 16:20:24 UTC+6, Мухаметали Кусайынов: 
>
>> Hello everyone! I really need your help. I can't deploy the website. 
>> Please help me! My settings below:
>> Server OS:
>> *Ubuntu server without GUI*
>> Ip address server - *10.17.0.12*
>> I installed* browsh* - is  text-based browser. Dspace was running at* 
>> localhost:4000*
>> Frontend directory location:
>> *~/dspace-angular-dspace-7.4*
>> Backend directory location:
>> */dspace*
>> SSL crt. location:
>> */dspace/ssl*
>> I have included ajp connector in tomcat9 server.xml:
>>   
>>
>>
>>
>>
>>
>> *>  minSpareThreads="25"   enableLookups="false"  
>>  redirectPort="8443"   connectionTimeout="2" 
>>  
>>  disableUploadTimeout="true"   URIEncoding="UTF-8"/>*
>>
>>
>>
>>
>>
>> * >  port="8009"   redirectPort="8443"  
>>  URIEncoding="UTF-8" />*
>>
>> local.cfg location:
>> */dspace/config$*
>> *Local.cfg configuration*
>> dspace.dir=*/dspace*
>> dspace.server.url = *https://repository.kaznu.kz/server 
>> *
>> dspace.ui.url = 

Re: [dspace-tech] Re: DSpace 7.4 Windows 10

[Mohammad S. AlMutairi]

On Friday, January 13, 2023 at 10:22:00 PM UTC+3 project@gmail.com 
wrote:
But according to the site,  yarn build:prod has to be executed prior to 
that, isn't it??
Don't get it confused. ( yarn build:prod - Will build the frontend but 
won't start it ) or ( yarn start:prod - Will build the frontend and will 
start it ) comes after configuring [dspace-angular]/config/config.prod.yml 
or setting the building environment.
 


On Thu, Jan 12, 2023 at 6:53 PM Mohammad S. AlMutairi  
wrote:
You need to follow the frontend installation procedure you see here 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
 
Specially step 5. Configuration.


   1. Start a command prompt
   2. copy [dspace-angular]/config/config.example.yml  
   [dspace-angular]/config/config.prod.yml
   3. edit  [dspace-angular]/config/config.prod.yml and modify to fit your 
   environment
   4. Test & Build the Frontend by following steps in the link above.


Hope it help & Good luck


On Thursday, January 12, 2023 at 1:52:07 PM UTC+3 project@gmail.com 
wrote:
Uploaded the config.prod.yml file here.
Same error occurs.


*From,*
*Arunendra MB.*



On Wed, Jan 4, 2023 at 6:25 PM Mohammad S. AlMutairi  
wrote:
You welcome & Hello,

You need to upload  [dspace-angular]/config/config.prod.yml here in the 
group.. I think the configuration in that file is not right.

On Wednesday, January 4, 2023 at 3:01:48 PM UTC+3 project@gmail.com 
wrote:
Thanks. Overcame the issue.
Now on yarn run build:prod, I get
dspace-angular/src/environments/environment.production.ts:13:3 - error 
TS2741: Property 'useProxies' is missing in type '{ ssl: false; host: 
string; port: number; nameSpace: string; }'

ts file attached.
On Tuesday, January 3, 2023 at 1:58:52 PM UTC+5:30 alo...@gmail.com wrote:
On Tuesday, December 27, 2022 at 3:24:47 PM UTC+3 project@gmail.com 
wrote:
I faced 2 errors:
While executing yarn install, I got 
error @typescript-eslint/experimen...@5.11.0: The engine "node" is 
incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || 
>=16.0.0". Got "14.15.1"

I ignored the above error and continued:
yarn run build:prod
yarn run v1.22.19
$ yarn run build:ssr
$ ng build --configuration production && ng run 
dspace-angular:server:production
error Command failed with exit code 1

Are the two related?
What is the way out?
How did you install yarn?.

Start over and try this:

Nodejs Installation
1) Download https://nodejs.org/dist/v16.14.0/node-v16.14.0-x64.msi & 
install it.
2) node -v & npm-v
3) npm install -g yarn
4) npm install -g pm2
5) yarn -v & pm2 -v 

-- 
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/405822d8-d9a0-421a-ba16-31618a430667n%40googlegroups.com
 
<https://groups.google.com/d/msgid/dspace-tech/405822d8-d9a0-421a-ba16-31618a430667n%40googlegroups.com?utm_medium=email_source=footer>
.

-- 
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/2c0f0fd3-a515-4626-ad12-ac6d1d5fa692n%40googlegroups.com
 
<https://groups.google.com/d/msgid/dspace-tech/2c0f0fd3-a515-4626-ad12-ac6d1d5fa692n%40googlegroups.com?utm_medium=email_source=footer>
.

-- 
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/5dbc9ab4-ab7f-4b83-ad93-5e4dca825386n%40googlegroups.com.

Re: [dspace-tech] Re: DSpace 7.4 Windows 10

[Mohammad S. AlMutairi]

You need to follow the frontend installation procedure you see 
here 
https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-FrontendInstallation
 
Specially step 5. Configuration.


   1. Start a command prompt
   2. copy [dspace-angular]/config/config.example.yml  
   [dspace-angular]/config/config.prod.yml
   3. edit  [dspace-angular]/config/config.prod.yml and modify to fit your 
   environment
   4. Test & Build the Frontend by following steps in the link above.


Hope it help & Good luck


On Thursday, January 12, 2023 at 1:52:07 PM UTC+3 project@gmail.com 
wrote:

> Uploaded the config.prod.yml file here.
> Same error occurs.
>
>
> *From,*
> *Arunendra MB.*
>
>
>
> On Wed, Jan 4, 2023 at 6:25 PM Mohammad S. AlMutairi  
> wrote:
>
>> You welcome & Hello,
>>
>> You need to upload  [dspace-angular]/config/config.prod.yml here in the 
>> group.. I think the configuration in that file is not right.
>>
>> On Wednesday, January 4, 2023 at 3:01:48 PM UTC+3 project@gmail.com 
>> wrote:
>>
>>> Thanks. Overcame the issue.
>>> Now on yarn run build:prod, I get
>>> dspace-angular/src/environments/environment.production.ts:13:3 - error 
>>> TS2741: Property 'useProxies' is missing in type '{ ssl: false; host: 
>>> string; port: number; nameSpace: string; }'
>>>
>>> ts file attached.
>>> On Tuesday, January 3, 2023 at 1:58:52 PM UTC+5:30 alo...@gmail.com 
>>> wrote:
>>>
>>>> On Tuesday, December 27, 2022 at 3:24:47 PM UTC+3 project@gmail.com 
>>>> wrote:
>>>>
>>>>> I faced 2 errors:
>>>>> While executing yarn install, I got 
>>>>> error @typescript-eslint/experimen...@5.11.0: The engine "node" is 
>>>>> incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || 
>>>>> >=16.0.0". Got "14.15.1"
>>>>>
>>>>> I ignored the above error and continued:
>>>>> yarn run build:prod
>>>>> yarn run v1.22.19
>>>>> $ yarn run build:ssr
>>>>> $ ng build --configuration production && ng run 
>>>>> dspace-angular:server:production
>>>>> error Command failed with exit code 1
>>>>>
>>>>> Are the two related?
>>>>> What is the way out?
>>>>>
>>>> How did you install yarn?.
>>>>
>>>> Start over and try this:
>>>>
>>>> Nodejs Installation
>>>> 1) Download https://nodejs.org/dist/v16.14.0/node-v16.14.0-x64.msi & 
>>>> install it.
>>>> 2) node -v & npm-v
>>>> 3) npm install -g yarn
>>>> 4) npm install -g pm2
>>>> 5) yarn -v & pm2 -v 
>>>>
>>> -- 
>> 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/405822d8-d9a0-421a-ba16-31618a430667n%40googlegroups.com
>>  
>> <https://groups.google.com/d/msgid/dspace-tech/405822d8-d9a0-421a-ba16-31618a430667n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/2c0f0fd3-a515-4626-ad12-ac6d1d5fa692n%40googlegroups.com.

[dspace-tech] Re: Dspace Data Migration with SAF

[Mohammad S. AlMutairi]

Maybe I should retire. :-)
[dspace]/bin/dspace index-discovery -b

On Wednesday, January 11, 2023 at 6:44:58 PM UTC+3 Mohammad S. AlMutairi 
wrote:

> Hello  Rupinder,
>
> You are almost there. You should have some clues in the log 
> [dspace]/log/dspace.log ... This error  ( An internal read or write 
> operation failed ) suggest it could be a permission problem or the the 
> assetstore is not where it expected to be (guessing) so check them both 
> also make sure dc.identifier.uri links are correct for all the moved items 
> and finally you need to do a discovery indexing [dspace]/bin/dspace 
> discovery-index -b 
>
> Good luck
> On Wednesday, January 11, 2023 at 3:31:47 PM UTC+3 jesse...@gmail.com 
> wrote:
>
>> Dear Mr. AlMutairi, 
>> That worked, and I was able to restore the database and the assetstore on 
>> my new DSpace 7  installation. I can now see all the collections, 
>> communities, and items on my Angular GUI. But as soon as i open any item, 
>> It shows the metadata of the document uploaded but gives the following 
>> error when is click the bitstream (a PDF dissertation in my case).
>>
>> Whitelabel Error Page
>>
>> This application has no explicit mapping for /error, so you are seeing 
>> this as a fallback.
>> Wed Jan 11 17:56:55 IST 2023
>> There was an unexpected error (type=Internal Server Error, status=500).
>> An internal read or write operation failed
>>
>> On Wednesday, January 11, 2023 at 10:43:58 AM UTC+5:30 Rupinder Singh 
>> wrote:
>>
>>> Dear Mr. AlMutairi, 
>>> I sent you copies of dspace.cfg, local.cfg, and bitstore.xml. on your 
>>> personal mail.
>>> However, after your suggestion, I checked the local.cfg file and found 
>>> that all the configuration settings were stored there and the assetstore 
>>> folder is set to  /mnt/dspace/assetstore . So I have taken a backup of it, 
>>> and will now try restoring it on my DSPACE 7 test server as you suggested 
>>> in your first mail.  
>>> Please have a look at the config files though, we may come to find 
>>> something more that went unnoticed before. 
>>>
>>> Thank You 
>>> Rupinder Singh
>>>
>>> On Tuesday, January 10, 2023 at 8:25:51 PM UTC+5:30 alo...@gmail.com 
>>> wrote:
>>>
>>>> I wanted to warn you that bitstore.xml might have your 
>>>> Amazon awsAccessKey, awsSecretKey, and bucketName so remove them if you 
>>>> are 
>>>> going to send the files or you can take it from here and move your missing 
>>>> assetstore to the server filesystem and follow the usual upgrade procedure.
>>>>
>>>> On Tuesday, January 10, 2023 at 5:32:28 PM UTC+3 Mohammad S. AlMutairi 
>>>> wrote:
>>>>
>>>>> Please forget AIP and SAF.
>>>>>
>>>>> Can you get me privately a copy of local.cfg, dspace.cfg and  
>>>>> [dspace]/config/spring/api/bitstore.xml .. You can remove anything 
>>>>> private 
>>>>> data you think is worth removing ( database password, domain ..etc ).
>>>>>
>>>>> You need to read this: 
>>>>> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore
>>>>>
>>>>> On Tuesday, January 10, 2023 at 5:09:15 PM UTC+3 jesse...@gmail.com 
>>>>> wrote:
>>>>>
>>>>>> Thanks, Mr. ALMutairi, but no luck with that. 
>>>>>> Surprisingly the old Dspace 6.2 server does not have any assetstore 
>>>>>> folder, but the repository is working somehow. I checked the assetstore 
>>>>>> location from the config file too, but, it's all on default, Searched 
>>>>>> for 
>>>>>> other installation locations, but found nothing. Actually, this server 
>>>>>> was 
>>>>>> installed long back by someone, who left the organization later. So this 
>>>>>> old DSpace server was left unattended for quite a long time. 
>>>>>>
>>>>>> I created a test server with Dspace 6.2 with the same config, and 
>>>>>> tried restoring with AIP and SAF on it, Still got the same problems. AIP 
>>>>>> commands throws error
>>>>>> java.lang.UnsupportedOperationException: Could not find a parent 
>>>>>> DSpaceObject referenced as '32116/180' in the METS Manifest for object 
>>>>>> hdl:32116/181. A parent DSpaceObject must be specified from either the 
>>>>>

[dspace-tech] Re: Dspace Data Migration with SAF

[Mohammad S. AlMutairi]

Hello  Rupinder,

You are almost there. You should have some clues in the log 
[dspace]/log/dspace.log ... This error  ( An internal read or write 
operation failed ) suggest it could be a permission problem or the the 
assetstore is not where it expected to be (guessing) so check them both 
also make sure dc.identifier.uri links are correct for all the moved items 
and finally you need to do a discovery indexing [dspace]/bin/dspace 
discovery-index -b 

Good luck
On Wednesday, January 11, 2023 at 3:31:47 PM UTC+3 jesse...@gmail.com wrote:

> Dear Mr. AlMutairi, 
> That worked, and I was able to restore the database and the assetstore on 
> my new DSpace 7  installation. I can now see all the collections, 
> communities, and items on my Angular GUI. But as soon as i open any item, 
> It shows the metadata of the document uploaded but gives the following 
> error when is click the bitstream (a PDF dissertation in my case).
>
> Whitelabel Error Page
>
> This application has no explicit mapping for /error, so you are seeing 
> this as a fallback.
> Wed Jan 11 17:56:55 IST 2023
> There was an unexpected error (type=Internal Server Error, status=500).
> An internal read or write operation failed
>
> On Wednesday, January 11, 2023 at 10:43:58 AM UTC+5:30 Rupinder Singh 
> wrote:
>
>> Dear Mr. AlMutairi, 
>> I sent you copies of dspace.cfg, local.cfg, and bitstore.xml. on your 
>> personal mail.
>> However, after your suggestion, I checked the local.cfg file and found 
>> that all the configuration settings were stored there and the assetstore 
>> folder is set to  /mnt/dspace/assetstore . So I have taken a backup of it, 
>> and will now try restoring it on my DSPACE 7 test server as you suggested 
>> in your first mail.  
>> Please have a look at the config files though, we may come to find 
>> something more that went unnoticed before. 
>>
>> Thank You 
>> Rupinder Singh
>>
>> On Tuesday, January 10, 2023 at 8:25:51 PM UTC+5:30 alo...@gmail.com 
>> wrote:
>>
>>> I wanted to warn you that bitstore.xml might have your 
>>> Amazon awsAccessKey, awsSecretKey, and bucketName so remove them if you are 
>>> going to send the files or you can take it from here and move your missing 
>>> assetstore to the server filesystem and follow the usual upgrade procedure.
>>>
>>> On Tuesday, January 10, 2023 at 5:32:28 PM UTC+3 Mohammad S. AlMutairi 
>>> wrote:
>>>
>>>> Please forget AIP and SAF.
>>>>
>>>> Can you get me privately a copy of local.cfg, dspace.cfg and  
>>>> [dspace]/config/spring/api/bitstore.xml .. You can remove anything private 
>>>> data you think is worth removing ( database password, domain ..etc ).
>>>>
>>>> You need to read this: 
>>>> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore
>>>>
>>>> On Tuesday, January 10, 2023 at 5:09:15 PM UTC+3 jesse...@gmail.com 
>>>> wrote:
>>>>
>>>>> Thanks, Mr. ALMutairi, but no luck with that. 
>>>>> Surprisingly the old Dspace 6.2 server does not have any assetstore 
>>>>> folder, but the repository is working somehow. I checked the assetstore 
>>>>> location from the config file too, but, it's all on default, Searched for 
>>>>> other installation locations, but found nothing. Actually, this server 
>>>>> was 
>>>>> installed long back by someone, who left the organization later. So this 
>>>>> old DSpace server was left unattended for quite a long time. 
>>>>>
>>>>> I created a test server with Dspace 6.2 with the same config, and 
>>>>> tried restoring with AIP and SAF on it, Still got the same problems. AIP 
>>>>> commands throws error
>>>>> java.lang.UnsupportedOperationException: Could not find a parent 
>>>>> DSpaceObject referenced as '32116/180' in the METS Manifest for object 
>>>>> hdl:32116/181. A parent DSpaceObject must be specified from either the 
>>>>> 'packager' command or noted in the METS Manifest itself. 
>>>>>
>>>>> and SAF import works only till it encounters an item that is part of 
>>>>> another collection, then it gives an error saying 
>>>>> Notice
>>>>> Import failed
>>>>> Attempted to create a handle which is already in use: 32116/2483
>>>>>
>>>>>
>>>>> On Monday, January 9, 2023 at 6:25:01 PM UTC+5:30 alo...@gmail.com 
>>>>> wrote:
>>&

[dspace-tech] Re: Geoip health status not working (Reason : The required 'dbfile' configuration is missing in solr-statistics.cfg!)

[Mohammad S. AlMutairi]

Hi,

It seems you need to quote the path of the file or maybe to shorten it. Try 
it maybe that's what it is.

On Tuesday, January 10, 2023 at 6:30:24 PM UTC+3 rihs...@gmail.com wrote:

> this problem doesn't appear if i install on dspace 7.2 and 7.3. I 
> installed dspace on windows 10 platform.
> [image: 7.3.jpg][image: 7.3info.jpg]
>
>
> On Tuesday, January 10, 2023 at 12:15:34 AM UTC+7 Muntashir wrote:
>
>> Hi everyone,
>>
>> I have problem with dspace geoip on health status. i have done database 
>> location configuration in usage-statistics.cfg file. however the status 
>> still detects an error.
>>
>> Can someone please help me with this? I am using dspace 7.4 with Solr 
>> 8.11.2 and dbip-city-lite-2023-01.mmdb dbfile.
>>
>> [image: geoip.jpg][image: usage-statistics.cfg.jpg]
>>
>>
>>

-- 
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/7baef245-91de-44fa-82b6-76263af1afc4n%40googlegroups.com.

[dspace-tech] Re: Deploy Dspace 7.4 with Add HTTPS support

[Mohammad S. AlMutairi]

I'm posting it here in a hope it will help someone else who might need 
clues what should be changed.


   1. echo "10.17.0.12  repository.kaznu.kz" >> /etc/hosts
   2. a2enmod proxy_http proxy_html ssl headers
   3. a2dissite 000-default default-ssl
   4. Overwrite /etc/tomcat9/server.xml with the attached file (server.xml).
   5. Overwrite /etc/apache2/sites-available/repository_kaznu_kz.conf with 
   the attached file (repository_kaznu_kz.conf).
   6. a2ensite repository_kaznu_kz.conf
   7. systemctl restart apache2.service
   8. systemctl restart tomcat9.service
   9. test the frontend (yarn test:rest)
   10. build the frontend
   11. access your backend by visiting https://repository.kaznu.kz/server
   12. access the frontend by visiting https://repository.kaznu.kz


Cheers
On Tuesday, January 10, 2023 at 1:32:57 PM UTC+3 m.kussai...@gmail.com 
wrote:

> I type IP adress in google chrome 10.17.0.12  Apache works
>
> вторник, 10 января 2023 г. в 16:32:21 UTC+6, Мухаметали Кусайынов: 
>
>> I type IP adress in google chrome 10.17.0.12  Apache works
>>
>> вторник, 10 января 2023 г. в 16:20:24 UTC+6, Мухаметали Кусайынов: 
>>
>>> Hello everyone! I really need your help. I can't deploy the website. 
>>> Please help me! My settings below:
>>> Server OS:
>>> *Ubuntu server without GUI*
>>> Ip address server - *10.17.0.12*
>>> I installed* browsh* - is  text-based browser. Dspace was running at* 
>>> localhost:4000*
>>> Frontend directory location:
>>> *~/dspace-angular-dspace-7.4*
>>> Backend directory location:
>>> */dspace*
>>> SSL crt. location:
>>> */dspace/ssl*
>>> I have included ajp connector in tomcat9 server.xml:
>>>   
>>>
>>>
>>>
>>>
>>>
>>> *>>  minSpareThreads="25"   enableLookups="false"  
>>>  redirectPort="8443"   connectionTimeout="2"  
>>>  disableUploadTimeout="true"   URIEncoding="UTF-8"/>*
>>>
>>>
>>>
>>>
>>>
>>> * >>  port="8009"   redirectPort="8443"  
>>>  URIEncoding="UTF-8" />*
>>>
>>> local.cfg location:
>>> */dspace/config$*
>>> *Local.cfg configuration*
>>> dspace.dir=*/dspace*
>>> dspace.server.url = *https://repository.kaznu.kz/server 
>>> *
>>> dspace.ui.url = *https://repository.kaznu.kz 
>>> *
>>> dspace.name = *DSpace KazNU*
>>>
>>> *Config.prod.yml configuration*
>>> config.prod.yml location:
>>> *~/dspace-angular-dspace-7.4/config$ *
>>> *ui:*
>>>   ssl: false
>>>   host: localhost
>>>   port: 4000
>>>   nameSpace: /
>>>
>>> *rest:*
>>>   ssl: true
>>>   host: repository.kaznu.kz
>>>   port: 443
>>>   nameSpace: /server
>>>
>>> Next, I will describe in detail how I tried to create a VirtualHost for 
>>> Dspace.
>>> I copied the *default-ssl.conf *and created the 
>>> *repository_kaznu_kz.conf*  in */etc/apache2/sites-available* directory.
>>>
>>> VirtualHost apache2 located:
>>> */etc/apache2/sites-available/repository_kaznu_kz.conf*
>>> Did I write the configuration file VirtualHosts correctly?
>>> It seems to me that somewhere I could be mistaken. If I'm wrong, can you 
>>> show me how to correctly write the VirtualHost configuration? Complete 
>>> VirtualHost Configuration:
>>> *VirtualHost setting*
>>> 
>>> 
>>> ServerAdmin webmaster@localhost
>>> DocumentRoot /var/www/html
>>> 
>>> ServerName repository.kaznu.kz
>>> 
>>> ErrorLog ${APACHE_LOG_DIR}/error.log
>>> CustomLog ${APACHE_LOG_DIR}/access.log combined
>>>   
>>> SSLEngine on
>>> SSLCertificateFile  /dspace/ssl/STAR_kaznu_kz.crt
>>> SSLCertificateKeyFile /dspace/ssl/STAR_kaznu_kz.key
>>>
>>>  # Proxy all HTTPS requests to "/server" from Apache to Tomcat 
>>> via AJP connector
>>> ProxyPass /server ajp://localhost:8009/server
>>> ProxyPassReverse /server ajp://localhost:8009/server
>>>
>>> # Proxy all HTTPS requests from Apache to PM2 on localhost, port 
>>> 4000
>>> ProxyPass / http://localhost:4000/
>>> ProxyPassReverse / http://localhost:4000/
>>>
>>>  #SSLOptions +FakeBasicAuth +ExportCertData +StrictRequire
>>> 
>>> SSLOptions +StdEnvVars
>>> 
>>> 
>>> SSLOptions +StdEnvVars
>>> 
>>>
>>> 
>>>
>>>
>>> Next, I wrote the command - *sudo a2ensite repository_kaznu_kz.conf*
>>> And then, I wrote the command - *sudo systemctl restart apache2*
>>> Status apache2:
>>>
>>> ● apache2.service - The Apache HTTP Server
>>>  Loaded: loaded (/lib/systemd/system/apache2.service; enabled; 
>>> vendor preset: enabled)
>>>  Active: active (running) since Tue 2023-01-10 09:58:56 UTC; 13min 
>>> ago
>>>Docs: https://httpd.apache.org/docs/2.4/
>>> Process: 950 ExecStart=/usr/sbin/apachectl 

[dspace-tech] Re: Dspace Data Migration with SAF

[Mohammad S. AlMutairi]

I wanted to warn you that bitstore.xml might have your Amazon awsAccessKey, 
awsSecretKey, and bucketName so remove them if you are going to send the 
files or you can take it from here and move your missing assetstore to the 
server filesystem and follow the usual upgrade procedure.

On Tuesday, January 10, 2023 at 5:32:28 PM UTC+3 Mohammad S. AlMutairi 
wrote:

> Please forget AIP and SAF.
>
> Can you get me privately a copy of local.cfg, dspace.cfg and  
> [dspace]/config/spring/api/bitstore.xml .. You can remove anything private 
> data you think is worth removing ( database password, domain ..etc ).
>
> You need to read this: 
> https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore
>
> On Tuesday, January 10, 2023 at 5:09:15 PM UTC+3 jesse...@gmail.com wrote:
>
>> Thanks, Mr. ALMutairi, but no luck with that. 
>> Surprisingly the old Dspace 6.2 server does not have any assetstore 
>> folder, but the repository is working somehow. I checked the assetstore 
>> location from the config file too, but, it's all on default, Searched for 
>> other installation locations, but found nothing. Actually, this server was 
>> installed long back by someone, who left the organization later. So this 
>> old DSpace server was left unattended for quite a long time. 
>>
>> I created a test server with Dspace 6.2 with the same config, and tried 
>> restoring with AIP and SAF on it, Still got the same problems. AIP commands 
>> throws error
>> java.lang.UnsupportedOperationException: Could not find a parent 
>> DSpaceObject referenced as '32116/180' in the METS Manifest for object 
>> hdl:32116/181. A parent DSpaceObject must be specified from either the 
>> 'packager' command or noted in the METS Manifest itself. 
>>
>> and SAF import works only till it encounters an item that is part of 
>> another collection, then it gives an error saying 
>> Notice
>> Import failed
>> Attempted to create a handle which is already in use: 32116/2483
>>
>>
>> On Monday, January 9, 2023 at 6:25:01 PM UTC+5:30 alo...@gmail.com wrote:
>>
>>> Hello  Rupinder,
>>>
>>> You really don't have to use SAF or AIP for this migration since you own 
>>> both systems ( old & new ). Both should work but It's time consuming and 
>>> sometimes flaky. There is a faster and a shorter path. Try it and let us 
>>> know in the list if you still need more help. I'll walk you through.
>>>
>>> 1) Dump the old database in a binary format ( pg_dump -Fc dspace > 
>>> dspace-6x.sql ) and copy it along with the old assetstore to the new server.
>>> 2) su - posgres
>>> 3) Restore the database into the new server using ( pg_restore -v -c -d 
>>> dspace dspace-6x.sql ). You might need to run ( [dspace]/bin/dspace 
>>> database clean ) first and for this to work you need to add 
>>> ( db.cleanDisabled=false ) at the top of ( [dspace]/config/dspace.cfg ) and 
>>> no need to restart tomcat.
>>> 4) exit
>>> 5) Run [dspace]/bin/dspace database migrate ignored
>>> 6) Check [dspace]/bin/dspace status & info
>>> 7) [dspace]/bin/dspace create-administrator
>>> 8) Copy the old assetstore folder to where it should be in the new 
>>> server [dspace]/assetstore
>>> 9) Chown -R tomcat:tomcat [dspace]
>>> 10) systemctl restart tomcat & finally check if everything is O.K.
>>>
>>> ** You can if you need to or have to dump the database in a text format 
>>> and run search and replace on it for anything ( old domain and URL's that 
>>> has xmlui in it comes in mind ). Do it after finishing step 3 above.
>>> a) su - postgres
>>> b) Dump the databse in text format ( pg_dump -c dspace > 
>>> dspace-migrated.sql )
>>> c) Search and replace using ( sed, awk, perl, vi or any text edit you 
>>> feel comfortable with ).
>>> d) Restore it ( cat dspace.sql | psql -d dspace < dspace-migrated.sql )
>>>  
>>> Good luck
>>>
>>>
>>> On Monday, January 9, 2023 at 7:11:11 AM UTC+3 jesse...@gmail.com wrote:
>>>
>>>> Can someone please help me with this? 
>>>> I am planning for migration and am stuck on this. AIP backup and 
>>>> restore are of no use because it throws too many errors. I found SAF to be 
>>>> simple and reliable, but the only problem is with these conflicts of items 
>>>> appearing in multiple collections. 
>>>>
>>>> Please help 
>>>>
>>>> Thank you
>>>> Rupinder Singh
>>&g

[dspace-tech] Re: Dspace Data Migration with SAF

[Mohammad S. AlMutairi]

Please forget AIP and SAF.

Can you get me privately a copy of local.cfg, dspace.cfg and  
[dspace]/config/spring/api/bitstore.xml .. You can remove anything private 
data you think is worth removing ( database password, domain ..etc ).

You need to read 
this: 
https://wiki.lyrasis.org/display/DSDOC6x/Storage+Layer#StorageLayer-ConfiguringtheBitstreamStore

On Tuesday, January 10, 2023 at 5:09:15 PM UTC+3 jesse...@gmail.com wrote:

> Thanks, Mr. ALMutairi, but no luck with that. 
> Surprisingly the old Dspace 6.2 server does not have any assetstore 
> folder, but the repository is working somehow. I checked the assetstore 
> location from the config file too, but, it's all on default, Searched for 
> other installation locations, but found nothing. Actually, this server was 
> installed long back by someone, who left the organization later. So this 
> old DSpace server was left unattended for quite a long time. 
>
> I created a test server with Dspace 6.2 with the same config, and tried 
> restoring with AIP and SAF on it, Still got the same problems. AIP commands 
> throws error
> java.lang.UnsupportedOperationException: Could not find a parent 
> DSpaceObject referenced as '32116/180' in the METS Manifest for object 
> hdl:32116/181. A parent DSpaceObject must be specified from either the 
> 'packager' command or noted in the METS Manifest itself. 
>
> and SAF import works only till it encounters an item that is part of 
> another collection, then it gives an error saying 
> Notice
> Import failed
> Attempted to create a handle which is already in use: 32116/2483
>
>
> On Monday, January 9, 2023 at 6:25:01 PM UTC+5:30 alo...@gmail.com wrote:
>
>> Hello  Rupinder,
>>
>> You really don't have to use SAF or AIP for this migration since you own 
>> both systems ( old & new ). Both should work but It's time consuming and 
>> sometimes flaky. There is a faster and a shorter path. Try it and let us 
>> know in the list if you still need more help. I'll walk you through.
>>
>> 1) Dump the old database in a binary format ( pg_dump -Fc dspace > 
>> dspace-6x.sql ) and copy it along with the old assetstore to the new server.
>> 2) su - posgres
>> 3) Restore the database into the new server using ( pg_restore -v -c -d 
>> dspace dspace-6x.sql ). You might need to run ( [dspace]/bin/dspace 
>> database clean ) first and for this to work you need to add 
>> ( db.cleanDisabled=false ) at the top of ( [dspace]/config/dspace.cfg ) and 
>> no need to restart tomcat.
>> 4) exit
>> 5) Run [dspace]/bin/dspace database migrate ignored
>> 6) Check [dspace]/bin/dspace status & info
>> 7) [dspace]/bin/dspace create-administrator
>> 8) Copy the old assetstore folder to where it should be in the new server 
>> [dspace]/assetstore
>> 9) Chown -R tomcat:tomcat [dspace]
>> 10) systemctl restart tomcat & finally check if everything is O.K.
>>
>> ** You can if you need to or have to dump the database in a text format 
>> and run search and replace on it for anything ( old domain and URL's that 
>> has xmlui in it comes in mind ). Do it after finishing step 3 above.
>> a) su - postgres
>> b) Dump the databse in text format ( pg_dump -c dspace > 
>> dspace-migrated.sql )
>> c) Search and replace using ( sed, awk, perl, vi or any text edit you 
>> feel comfortable with ).
>> d) Restore it ( cat dspace.sql | psql -d dspace < dspace-migrated.sql )
>>  
>> Good luck
>>
>>
>> On Monday, January 9, 2023 at 7:11:11 AM UTC+3 jesse...@gmail.com wrote:
>>
>>> Can someone please help me with this? 
>>> I am planning for migration and am stuck on this. AIP backup and restore 
>>> are of no use because it throws too many errors. I found SAF to be simple 
>>> and reliable, but the only problem is with these conflicts of items 
>>> appearing in multiple collections. 
>>>
>>> Please help 
>>>
>>> Thank you
>>> Rupinder Singh
>>> On Tuesday, December 27, 2022 at 3:37:15 PM UTC+5:30 Rupinder Singh 
>>> wrote:
>>>
 I have a problem with SAF, as I am Migrating from Dspace 6.2 to DSpace 
 7.4. I exported my collections from DSpace 6.2, But as I upload the SAF 
 items to my Dspace 7.4 everything goes ok, Except for the items which are 
 part of multiple collections. The import process exists with an error 
 saying that the Item/Handle Already Exists. 
 How can I resolve this conflict? There are many items that appear is 
 more than one collection in my existing Dspace 6.2.

>>>

-- 
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/1bdc0b41-17e1-4858-b61b-cfe4fe9d0c91n%40googlegroups.com.

[dspace-tech] Re: Install Shibboleth on RedHat 9

[Mohammad S. AlMutairi]

Hi,

Shibboleth SP RHEL RPM package is based on CentOS Repo and since CentOS 
became an upstream endo of 2021 you can choose one of CentOS distro's 
replacement that is Rocky Linux so install Rocky Linux Shibboleth Repo and 
install Shibboleth SP and it's dependencies from it or you can always build 
it from the source on your RHEL 9.

On Monday, January 9, 2023 at 9:56:59 PM UTC+3 jos...@udel.edu wrote:

> Hi,
>
> I am installing Shibboleth authentication for DSpace 7 on RedHat 9. The 
> Shibboleth.net says "The official RPMs produced by the project are no 
> longer built using the OpenSUSE Build Service," Currently they support its 
> repository only up to RedHat 8. How can I set it up correctly on Redha 9? 
> Instead of using the RPM package, is there another way for that?
>
> https://shibboleth.net/downloads/service-provider/latest/RPMS/
>
> 
> Joshua Kim
> Web Developer, Library IT
> Library, Museums and Press
> University of Delaware
>
>

-- 
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/d665c348-b135-4213-bf86-7952982e9c30n%40googlegroups.com.

[dspace-tech] Re: Dspace Data Migration with SAF

[Mohammad S. AlMutairi]

Correction. I wasn't focusing ;-).
d) Restore it ( cat dspace.sql | psql -d dspace ).

On Monday, January 9, 2023 at 3:55:01 PM UTC+3 Mohammad S. AlMutairi wrote:

> Hello  Rupinder,
>
> You really don't have to use SAF or AIP for this migration since you own 
> both systems ( old & new ). Both should work but It's time consuming and 
> sometimes flaky. There is a faster and a shorter path. Try it and let us 
> know in the list if you still need more help. I'll walk you through.
>
> 1) Dump the old database in a binary format ( pg_dump -Fc dspace > 
> dspace-6x.sql ) and copy it along with the old assetstore to the new server.
> 2) su - posgres
> 3) Restore the database into the new server using ( pg_restore -v -c -d 
> dspace dspace-6x.sql ). You might need to run ( [dspace]/bin/dspace 
> database clean ) first and for this to work you need to add 
> ( db.cleanDisabled=false ) at the top of ( [dspace]/config/dspace.cfg ) and 
> no need to restart tomcat.
> 4) exit
> 5) Run [dspace]/bin/dspace database migrate ignored
> 6) Check [dspace]/bin/dspace status & info
> 7) [dspace]/bin/dspace create-administrator
> 8) Copy the old assetstore folder to where it should be in the new server 
> [dspace]/assetstore
> 9) Chown -R tomcat:tomcat [dspace]
> 10) systemctl restart tomcat & finally check if everything is O.K.
>
> ** You can if you need to or have to dump the database in a text format 
> and run search and replace on it for anything ( old domain and URL's that 
> has xmlui in it comes in mind ). Do it after finishing step 3 above.
> a) su - postgres
> b) Dump the databse in text format ( pg_dump -c dspace > 
> dspace-migrated.sql )
> c) Search and replace using ( sed, awk, perl, vi or any text edit you feel 
> comfortable with ).
> d) Restore it ( cat dspace.sql | psql -d dspace < dspace-migrated.sql )
>  
> Good luck
>
>
> On Monday, January 9, 2023 at 7:11:11 AM UTC+3 jesse...@gmail.com wrote:
>
>> Can someone please help me with this? 
>> I am planning for migration and am stuck on this. AIP backup and restore 
>> are of no use because it throws too many errors. I found SAF to be simple 
>> and reliable, but the only problem is with these conflicts of items 
>> appearing in multiple collections. 
>>
>> Please help 
>>
>> Thank you
>> Rupinder Singh
>> On Tuesday, December 27, 2022 at 3:37:15 PM UTC+5:30 Rupinder Singh wrote:
>>
>>> I have a problem with SAF, as I am Migrating from Dspace 6.2 to DSpace 
>>> 7.4. I exported my collections from DSpace 6.2, But as I upload the SAF 
>>> items to my Dspace 7.4 everything goes ok, Except for the items which are 
>>> part of multiple collections. The import process exists with an error 
>>> saying that the Item/Handle Already Exists. 
>>> How can I resolve this conflict? There are many items that appear is 
>>> more than one collection in my existing Dspace 6.2.
>>>
>>

-- 
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/ff2284f3-11be-4c86-a4e3-4d406f75fa6en%40googlegroups.com.

[dspace-tech] Re: Dspace Data Migration with SAF

[Mohammad S. AlMutairi]

Hello  Rupinder,

You really don't have to use SAF or AIP for this migration since you own 
both systems ( old & new ). Both should work but It's time consuming and 
sometimes flaky. There is a faster and a shorter path. Try it and let us 
know in the list if you still need more help. I'll walk you through.

1) Dump the old database in a binary format ( pg_dump -Fc dspace > 
dspace-6x.sql ) and copy it along with the old assetstore to the new server.
2) su - posgres
3) Restore the database into the new server using ( pg_restore -v -c -d 
dspace dspace-6x.sql ). You might need to run ( [dspace]/bin/dspace 
database clean ) first and for this to work you need to add 
( db.cleanDisabled=false ) at the top of ( [dspace]/config/dspace.cfg ) and 
no need to restart tomcat.
4) exit
5) Run [dspace]/bin/dspace database migrate ignored
6) Check [dspace]/bin/dspace status & info
7) [dspace]/bin/dspace create-administrator
8) Copy the old assetstore folder to where it should be in the new server 
[dspace]/assetstore
9) Chown -R tomcat:tomcat [dspace]
10) systemctl restart tomcat & finally check if everything is O.K.

** You can if you need to or have to dump the database in a text format and 
run search and replace on it for anything ( old domain and URL's that has 
xmlui in it comes in mind ). Do it after finishing step 3 above.
a) su - postgres
b) Dump the databse in text format ( pg_dump -c dspace > 
dspace-migrated.sql )
c) Search and replace using ( sed, awk, perl, vi or any text edit you feel 
comfortable with ).
d) Restore it ( cat dspace.sql | psql -d dspace < dspace-migrated.sql )
 
Good luck


On Monday, January 9, 2023 at 7:11:11 AM UTC+3 jesse...@gmail.com wrote:

> Can someone please help me with this? 
> I am planning for migration and am stuck on this. AIP backup and restore 
> are of no use because it throws too many errors. I found SAF to be simple 
> and reliable, but the only problem is with these conflicts of items 
> appearing in multiple collections. 
>
> Please help 
>
> Thank you
> Rupinder Singh
> On Tuesday, December 27, 2022 at 3:37:15 PM UTC+5:30 Rupinder Singh wrote:
>
>> I have a problem with SAF, as I am Migrating from Dspace 6.2 to DSpace 
>> 7.4. I exported my collections from DSpace 6.2, But as I upload the SAF 
>> items to my Dspace 7.4 everything goes ok, Except for the items which are 
>> part of multiple collections. The import process exists with an error 
>> saying that the Item/Handle Already Exists. 
>> How can I resolve this conflict? There are many items that appear is more 
>> than one collection in my existing Dspace 6.2.
>>
>

-- 
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/8f455ae0-8e69-4591-8332-32eb268d51d0n%40googlegroups.com.

[dspace-tech] Re: Automatic generation of thumbnails for image records in DSpace 7.4

[Mohammad S. AlMutairi]

Hello,

I hope I got you right. Check 
https://wiki.lyrasis.org/display/DSDOC7x/Scheduled+Tasks+via+Cron

On Thursday, January 5, 2023 at 8:26:23 PM UTC+3 jorge@udb.edu.sv wrote:

> hello.
>
> Is it possible somehow to make the thumbnail of the record be generated 
> automatically? , either with a command line or when creating the record, 
> which will take, for example, the first page of the attached pdf
>
> 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/c4744b95-16c2-46c7-8551-08b743d628d1n%40googlegroups.com.

Re: [dspace-tech] Re: Incorrect URLs in OAI-interface

[Mohammad S. AlMutairi]

at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346)
> at 
> org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:382)
> at 
> org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
> at 
> org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:888)
> at 
> org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1684)
> at 
> org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
> at 
> org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
> at java.base/java.lang.Thread.run(Thread.java:829)
> ```
>
> Kind regards,
> Eike.
>
>
>
> Am 04.01.23 um 16:48 schrieb Mohammad S. AlMutairi:
>
> Hi Eike, 
>
> May I suggest you to upgrade to DSpace 7.4 or maybe jump to 7.5-snapshot 
> version and then check to see if you still have this issue that was 
> reported by Mark last June. The version (7.2) you developing on we all had 
> a lot of issues with it at that time which were fixed in 7.3 and 7.4.
>
> Hope it help
> On Wednesday, January 4, 2023 at 6:08:33 PM UTC+3 Eike Martin Löhden wrote:
>
>> Hi, 
>>
>> I'm currently developing a DSpace-7.2 platform for medieval charters and 
>> facing an issue with the OAI-PMH interface. I think the same issue has 
>> once been reported as a bug 
>> (https://github.com/DSpace/DSpace/issues/8332), but marked as "cannot 
>> reproduce". 
>> If I open the OAI-interface under [dspace.server.url]/oai, the links to 
>> - for example - "Identify" is redirected to 
>> [dspace.server.url]/request?verb=Identify. The OAI-page also doesn't 
>> have a layout, because it can't find the necessary files like 
>> "bootstrap.min.css", "style.css" and so on. The browser console shows a 
>> 404 Error. I think, there is a problem with the oai-url, but I can't 
>> find it. 
>> I've installed DSpace on a Debian bullseye Server with JDK-11 and using 
>> a postgres database. 
>> Does anyone know this error? 
>>
>> Thanks and 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/1afaf56f-a809-47f3-9e39-10e00988fffcn%40googlegroups.com
>  
> <https://groups.google.com/d/msgid/dspace-tech/1afaf56f-a809-47f3-9e39-10e00988fffcn%40googlegroups.com?utm_medium=email_source=footer>
> .
>
>

-- 
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/662887cd-649e-4cb8-a63d-a9ae20501390n%40googlegroups.com.

[dspace-tech] Re: Incorrect URLs in OAI-interface

[Mohammad S. AlMutairi]

Hi Eike,

May I suggest you to upgrade to DSpace 7.4 or maybe jump to 7.5-snapshot 
version and then check to see if you still have this issue that was 
reported by Mark last June. The version (7.2) you developing on we all had 
a lot of issues with it at that time which were fixed in 7.3 and 7.4.

Hope it help
On Wednesday, January 4, 2023 at 6:08:33 PM UTC+3 Eike Martin Löhden wrote:

> Hi,
>
> I'm currently developing a DSpace-7.2 platform for medieval charters and 
> facing an issue with the OAI-PMH interface. I think the same issue has 
> once been reported as a bug 
> (https://github.com/DSpace/DSpace/issues/8332), but marked as "cannot 
> reproduce".
> If I open the OAI-interface under [dspace.server.url]/oai, the links to 
> - for example - "Identify" is redirected to 
> [dspace.server.url]/request?verb=Identify. The OAI-page also doesn't 
> have a layout, because it can't find the necessary files like 
> "bootstrap.min.css", "style.css" and so on. The browser console shows a 
> 404 Error. I think, there is a problem with the oai-url, but I can't 
> find it.
> I've installed DSpace on a Debian bullseye Server with JDK-11 and using 
> a postgres database.
> Does anyone know this error?
>
> Thanks and 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/1afaf56f-a809-47f3-9e39-10e00988fffcn%40googlegroups.com.

[dspace-tech] Re: DSpace 7.4 Windows 10

[Mohammad S. AlMutairi]

You welcome & Hello,

You need to upload  [dspace-angular]/config/config.prod.yml here in the 
group.. I think the configuration in that file is not right.

On Wednesday, January 4, 2023 at 3:01:48 PM UTC+3 project@gmail.com 
wrote:

> Thanks. Overcame the issue.
> Now on yarn run build:prod, I get
> dspace-angular/src/environments/environment.production.ts:13:3 - error 
> TS2741: Property 'useProxies' is missing in type '{ ssl: false; host: 
> string; port: number; nameSpace: string; }'
>
> ts file attached.
> On Tuesday, January 3, 2023 at 1:58:52 PM UTC+5:30 alo...@gmail.com wrote:
>
>> On Tuesday, December 27, 2022 at 3:24:47 PM UTC+3 project@gmail.com 
>> wrote:
>>
>>> I faced 2 errors:
>>> While executing yarn install, I got 
>>> error @typescript-eslint/experimen...@5.11.0: The engine "node" is 
>>> incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || 
>>> >=16.0.0". Got "14.15.1"
>>>
>>> I ignored the above error and continued:
>>> yarn run build:prod
>>> yarn run v1.22.19
>>> $ yarn run build:ssr
>>> $ ng build --configuration production && ng run 
>>> dspace-angular:server:production
>>> error Command failed with exit code 1
>>>
>>> Are the two related?
>>> What is the way out?
>>>
>> How did you install yarn?.
>>
>> Start over and try this:
>>
>> Nodejs Installation
>> 1) Download https://nodejs.org/dist/v16.14.0/node-v16.14.0-x64.msi & 
>> install it.
>> 2) node -v & npm-v
>> 3) npm install -g yarn
>> 4) npm install -g pm2
>> 5) yarn -v & pm2 -v 
>>
>

-- 
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/405822d8-d9a0-421a-ba16-31618a430667n%40googlegroups.com.

[dspace-tech] Re: Change end user agreement to English on user registration

[Mohammad S. AlMutairi]

Hi  Lewatle,

That text is just a space filler. Read about what it is and why it's used 
here https://www.lipsum.com ... You need to add your own end user agreement 
there or you can just disable it from appearing in config.prod.yml until 
you get your EUA ready to be added.


On Tuesday, January 3, 2023 at 2:12:09 PM UTC+3 joem...@gmail.com wrote:

> Dear DSpace Team,
>
> On DSpace 7.4, how do you change to English  for end user license, that 
> page appears when new user register account on DSpace, please see 
> screenshot below in addition : 
>
> [image: image_2023-01-03_131149002.png]
>
> Regards,
> Lewatle 
>
>
>
>

-- 
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/45c24363-80b5-49a3-ac77-c93eb660a3a0n%40googlegroups.com.

[dspace-tech] Re: DSpace 7.4 Windows 10

[Mohammad S. AlMutairi]

On Tuesday, December 27, 2022 at 3:24:47 PM UTC+3 project@gmail.com 
wrote:

> I faced 2 errors:
> While executing yarn install, I got 
> error @typescript-eslint/experimen...@5.11.0: The engine "node" is 
> incompatible with this module. Expected version "^12.22.0 || ^14.17.0 || 
> >=16.0.0". Got "14.15.1"
>
> I ignored the above error and continued:
> yarn run build:prod
> yarn run v1.22.19
> $ yarn run build:ssr
> $ ng build --configuration production && ng run 
> dspace-angular:server:production
> error Command failed with exit code 1
>
> Are the two related?
> What is the way out?
>
How did you install yarn?.

Start over and try this:

Nodejs Installation
1) Download https://nodejs.org/dist/v16.14.0/node-v16.14.0-x64.msi & 
install it.
2) node -v & npm-v
3) npm install -g yarn
4) npm install -g pm2
5) yarn -v & pm2 -v 

-- 
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/4ffea3ff-da32-4678-8efb-f03082a15cdbn%40googlegroups.com.

Re: [dspace-tech] Re: I cant create administrator dspace 7.4

[Mohammad S. AlMutairi]

My pleasure to be able to help. You are welcome.


On Tue, Jan 3, 2023 at 10:05 AM Мухаметали Кусайынов <
m.kussaiynov1...@gmail.com> wrote:

> Thank you very much! Problem solved! I had to run as sudo. Thank you again!
>
>
> пн, 2 янв. 2023 г. в 22:58, Mohammad S. AlMutairi :
>
>> On Monday, January 2, 2023 at 6:05:39 PM UTC+3 m.kussai...@gmail.com
>> wrote:
>>
>>> Hello everyone. I need your help. I have two questions.
>>> *1)*
>>> I installed dspace 7.4. And created a dspace administrator.
>>> e-mail: dspace_admin
>>> passwd:dspace
>>> But I can't login with this username. Is it mandatory to enter an email
>>> address?
>>>
>> You should've added it but it's not mandatory. To keep it short you
>> should be able to login with dspace_admin if it was created as an
>> administrator unless the login issue you have is caused by something else.
>> Check [dspace]/log/dspace.log you should find some clue why.
>>
>> make sure you see the administrator account you created by running.
>> [dspace]/bin/dspace user --list
>>
>> *2)*
>>> when I want to create a new administrator , I run the command:
>>> *dspace@dspace7:/opt/solr-8.11.2/bin$ /dspace/bin/dspace
>>> create-administrator *
>>> it gives the following error:
>>> *-bash: /dspace/bin/dspace: Permission denied*
>>> What's my mistake?
>>>
>> I think you are logged in with a user which has no permission to execute
>> [dspace]/bin/dspace .. Check who you are by invoking whoami command and
>> then check who is the owner if the dspace folde. A simple ls -al should
>> show it.
>>
>>
>>>
>>> How to create a DSpace administrator correctly?
>>>
>> You done it right. ( /dspace/bin/dspace create-administrator ).
>>
>> Is it possible to create multiple administrators?
>>>
>> Yes you can and you can also overwrite the same admin user by creating it
>> again.
>>
>>
>>>
>>> With best regards. Kussaynov M.
>>>
>>
>> Cheers
>>
>> --
>> 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 a topic in the
>> Google Groups "DSpace Technical Support" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/dspace-tech/h5t6P4K224Q/unsubscribe.
>> To unsubscribe from this group and all its topics, 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/bd226c01-8d64-4cab-a876-8ff8b049ab39n%40googlegroups.com
>> <https://groups.google.com/d/msgid/dspace-tech/bd226c01-8d64-4cab-a876-8ff8b049ab39n%40googlegroups.com?utm_medium=email_source=footer>
>> .
>>
>

-- 
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/CAESrwAY1Pnr61Ea46j3nkUwhObY1XK_6x1K7c-qfX0WTzT3HaQ%40mail.gmail.com.

[dspace-tech] Re: I cant create administrator dspace 7.4

[Mohammad S. AlMutairi]

On Monday, January 2, 2023 at 6:05:39 PM UTC+3 m.kussai...@gmail.com wrote:

> Hello everyone. I need your help. I have two questions.
> *1)*
> I installed dspace 7.4. And created a dspace administrator. 
> e-mail: dspace_admin
> passwd:dspace
> But I can't login with this username. Is it mandatory to enter an email 
> address?
>
You should've added it but it's not mandatory. To keep it short you should 
be able to login with dspace_admin if it was created as an administrator 
unless the login issue you have is caused by something else. Check 
[dspace]/log/dspace.log you should find some clue why.

make sure you see the administrator account you created by running.
[dspace]/bin/dspace user --list 

*2)*
> when I want to create a new administrator , I run the command:
> *dspace@dspace7:/opt/solr-8.11.2/bin$ /dspace/bin/dspace 
> create-administrator *
> it gives the following error:
> *-bash: /dspace/bin/dspace: Permission denied*
> What's my mistake?
>
I think you are logged in with a user which has no permission to execute 
[dspace]/bin/dspace .. Check who you are by invoking whoami command and 
then check who is the owner if the dspace folde. A simple ls -al should 
show it.
 

>
> How to create a DSpace administrator correctly?
>
You done it right. ( /dspace/bin/dspace create-administrator ).

Is it possible to create multiple administrators?
>
Yes you can and you can also overwrite the same admin user by creating it 
again.
 

>
> With best regards. Kussaynov M.
>

Cheers 

-- 
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/bd226c01-8d64-4cab-a876-8ff8b049ab39n%40googlegroups.com.

[dspace-tech] Re: DSpace 7: Hot to add a language tag to a metadata field.

[Mohammad S. AlMutairi]

Hi,

That would explains it & glad you had it resolved. It's good to know that 
I'm not alone in making typos everywhere ;-). Check the subject of this 
thread "Hot to add a language tag to a metadata field." :-).

Cheers

On Thursday, December 29, 2022 at 11:56:41 AM UTC+3 hipot...@gmail.com 
wrote:

> Hi  " alo...@gmail.com"
>
> There was an error un my code:
>
> I wrote "value-pairsname", instead of "value-pairs-name"
>
> Now it works properly:
> [image: Screenshot_01_02.png]
>
>
> Thank you for your help.
>
>
>
>
> On Tuesday, 27 December 2022 at 17:46:17 UTC+1 alo...@gmail.com wrote:
>
>> On Tuesday, December 27, 2022 at 1:41:22 PM UTC+3 hipot...@gmail.com 
>> wrote:
>>
>>> Why am I getting this error?
>>>
>>> Thanks.
>>>
>> You got everything right except the missing value-pairs by the name 
>> (common_iso_languages2). You can use the built-in common_iso_languages but 
>> if you must use the one you picked to customize it just create it in 
>> submission file as below:
>>
>> > dc-term="language_iso">
>> 
>> N/A
>> 
>> 
>> 
>> English (United States)
>> en_US
>> 
>> 
>> English
>> en
>> 
>> 
>> Spanish
>> es
>> 
>> 
>> German
>> 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/b98e4d42-a1b4-4390-89f3-e9437acfa0d6n%40googlegroups.com.

[dspace-tech] Re: DSpace 7: Hot to add a language tag to a metadata field.

[Mohammad S. AlMutairi]

On Tuesday, December 27, 2022 at 1:41:22 PM UTC+3 hipot...@gmail.com wrote:

> Why am I getting this error?
>
> Thanks.
>
You got everything right except the missing value-pairs by the name 
(common_iso_languages2). You can use the built-in common_iso_languages but 
if you must use the one you picked to customize it just create it in 
submission file as below:



N/A



English (United States)
en_US


English
en


Spanish
es


German
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/96bff55b-39a8-4c56-ac0a-485da2e61964n%40googlegroups.com.

[dspace-tech] Re: DSpace 7: Hot to add a language tag to a metadata field.

[Mohammad S. AlMutairi]

Hello,

Try this. It should work for you.


dc
description

true
false
Language
dropdown
Select the language of the main content of the 
item. If the language does not appear in the
list, please select 'Other'. If the content does 
not really have a language (for example, if it
is a dataset or an image) please select 'N/A'.




It think it failed with an error ( field description.null has no language 
attribute ) because there was no value-pairs-name with the 
name common_iso_languages2. If it has to be a custom value-pairs-name that 
you need to use then just create it and customize with any language you 
want and add it to the bottom of submission file somewhere near the other  
value-pairs-names and reference it in the above field.


Hope it help you.
On Tuesday, December 27, 2022 at 1:41:22 PM UTC+3 hipot...@gmail.com wrote:

> Hello everyone,
> I'm using DSpace 7.4
>
> My goal is to add a language tag to a metadata field.
>
> According to the DSpace 7.4 manual (pdf version):
>
> [image: Screenshot_01_01.png]
>
> Therefore I have written the following code.
>
> 
> 
> dc
> description
> 
>  value-pairsname="common_iso_languages2">true
> false
> Description
> textarea
> Enter any other description or comments in this 
> box.
> 
> 
> 
>
> However, I got the following error: (...field description.null has no 
> language attribute)
>
> 2022-12-27 10:10:22,450 ERROR unknown unknown 
> org.springframework.boot.SpringApplication @ Application run failed
> java.lang.RuntimeException: Failure during ServletContext initialisation: 
> Error creating bean with name 'patchConfigurationService' defined in URL 
> [jar:file:/var/lib/tomcat9/webapps/server/WEB-INF/lib/dspace-server-webapp-7.4-classes.jar!/spring/spring-dspace-core-services.xml]:
>  
> Cannot create inner bean 
> 'org.dspace.app.rest.submit.factory.impl.BitstreamMetadataValueMovePatchOperation#1dff5a71'
>  
> of type 
> [org.dspace.app.rest.submit.factory.impl.BitstreamMetadataValueMovePatchOperation]
>  
> while setting bean property 'map' with key [TypedStringValue: value [move], 
> target type [null]] with key [TypedStringValue: value [bitstreammetadata], 
> target type [null]]; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 
> 'org.dspace.app.rest.submit.factory.impl.BitstreamMetadataValueMovePatchOperation#1dff5a71'
>  
> defined in URL 
> [jar:file:/var/lib/tomcat9/webapps/server/WEB-INF/lib/dspace-server-webapp-7.4-classes.jar!/spring/spring-dspace-core-services.xml]:
>  
> Cannot resolve reference to bean 
> 'org.dspace.app.rest.utils.BitstreamMetadataValuePathUtils' while setting 
> bean property 'bitstreamMetadataValuePathUtils'; nested exception is 
> org.springframework.beans.factory.BeanCreationException: Error creating 
> bean with name 'org.dspace.app.rest.utils.BitstreamMetadataValuePathUtils' 
> defined in URL 
> [jar:file:/var/lib/tomcat9/webapps/server/WEB-INF/lib/dspace-server-webapp-7.4-classes.jar!/spring/spring-dspace-core-services.xml]:
>  
> Instantiation of bean failed; nested exception is 
> org.springframework.beans.BeanInstantiationException: Failed to instantiate 
> [org.dspace.app.rest.utils.BitstreamMetadataValuePathUtils]: Constructor 
> threw exception; nested exception is 
> org.dspace.app.util.DCInputsReaderException: Error creating submission 
> forms: org.xml.sax.SAXException: Form traditionalpagetwo, field 
> description.null has no language attribute
>
> Why am I getting this error?
>
> Thanks.
>
>
>

-- 
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/46f2b8dc-7942-4bea-b9fa-df056d598ad1n%40googlegroups.com.

Re: [dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

[Mohammad S. AlMutairi]

Hello Alex,

I need you to send me these files. I'll modify them for you.


   1. /etc/tomcat9/server.xml
   2. local.cfg
   3. config.prod.yml
   4. dspace.conf


Cheers

On Tuesday, December 27, 2022 at 1:29:54 AM UTC+3 aperez...@gmail.com wrote:

>
>
> [image: error3.PNG]
> El lunes, 26 de diciembre de 2022 a las 15:35:49 UTC-6, Alex Perez 
> escribió:
>
>>  Dspace 7.4 CORS error.mp4 
>> 
>> Problem Blocked CORS  https / http
>>
>>
>> Hello friends I hope you are very well, I would like to ask for help with 
>> the following already set up my DSpace server in a test environment and 
>> then get to do production and works well the backend communicates well with 
>> the frontend on port 8443 I set it in Tomcat 9. 58 and use the Reverse 
>> Proxy for port 4000 in Apache2 and pass the address of locahost:4000 add 
>> the module a2enmod headers to send the policy "X-Forwarded-Proto: https" so 
>> far so good but when loading the site https://ride2.tse.go.cr where the 
>> proxy is responsible for redirecting to port 4000 the CORS policy blocks me 
>> from sites like "https://api7.dspace.org/server/api;, 
>> https://api7.dspace.org/server/api/config/properties/registration.verification.enabled
>>  
>> ".  
>>  I do not know what else can be changed to correct this blocking CORS and 
>> already load my site as it does instantly and then already sends an error 
>> 500 that I could not correct in this version in 7.2 I did not pass that and 
>> worked fine.
>>
>> thank you very much in advance for the help you can give me
>>
>>
>>
>> El vie, 25 nov 2022 a las 7:05, Alex Perez () 
>> escribió:
>>
>>> Hello friends, I followed the steps you indicate me I reinstalled the 
>>> frontend and the video gave me an idea of what to do and work correctly 
>>> thank you very much for the help.
>>>
>>> Regards
>>>
>>>
>>> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, 
>>> alo...@gmail.com escribió:
>>>
 I had to try it on DSpace version 7.5-SNAPSHOT and it's working just 
 fine without any SSL configuration (HTTP Setup) so it's not hard coded as 
 I 
 thought. See the attached video as a confirmation. Try to pull a fresh 
 copy 
 of dspace-angular and start a front end fresh installation.

 Settings in dspace.cfg
 dspace.server.url = http:// 192.168.100.212:8080/server
 dspace.ui.url = http://192.168.100.212:4000

 Settings in config.prod.yml:
 ui:
   ssl: false
   host: 192.168.100.212
   port: 4000
   nameSpace: /

 rest:
   ssl: false
   host: 192.168.100.212
   port: 8080
   nameSpace: /server

 -- 
>>> 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/dd632e3d-837a-44aa-90e7-e37cf6671e70n%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/61fc0f80-a417-453a-bbe0-f2f1fd26ef1dn%40googlegroups.com.

[dspace-tech] Re: Filter-media identify error

[Mohammad S. AlMutairi]

Glad it was of a help to you and thanks for confirming.

Cheers 

On Tuesday, December 13, 2022 at 6:26:25 AM UTC+3 Jordan Gamonal Pérez 
wrote:

> Hi,
>
> I would like to inform you that the indicated steps helped me to solve the 
> problem, and I thank you very much.
>
> Regarding the routes, I use the common slashes, I have already tried the 
> backslashes before and they need to be escaped, which is not very readable 
> in the end.
>
> El Tuesday, December 13, 2022 a la(s) 12:09:30 AM UTC-3, alo...@gmail.com 
> escribió:
>
>> There was a typo in step 4. I'm not sure if dspace or im4java are 
>> forgiving about the backslash so it it's safer to always use forward slash.
>> 4) edit dspace.cfg and set the value for 
>> (org.dspace.app.mediafilter.ImageMagickThumbnailFilter.ProcessStarter =  'c:
>> */*imagemagick') and Restart Tomcat.
>>
>> On Sunday, December 11, 2022 at 9:50:29 AM UTC+3 Mohammad S. AlMutairi 
>> wrote:
>>
>>> You can try the steps you see below if the above suggestion didn't fix 
>>> the issue you have (Not much information provided about the server setup so 
>>> I'm guessing here). Anyway, Try the steps you see below. it should fix it 
>>> no matter what was the cause of the issue you have.
>>>
>>> 1) Uninstall the old ImageMagick you have.
>>> 2) Remove the IM4JAVA_TOOLPATH environment variable if you had it set.
>>> 3) Download the latest ImageMagick version 
>>> <https://imagemagick.org/script/download.php#windows> and install it 
>>> with the legacy utilities option. NB: You must choose the installation path 
>>> to be (c:\imagemagick) or (C:\dspace\dspace_63\imagemagick). The idea 
>>> of the path part is to avoid spaces in the folders names.
>>> 4) edit dspace.cfg and set the value for 
>>> (org.dspace.app.mediafilter.ImageMagickThumbnailFilter.ProcessStarter 
>>> =  'c:\imagemagick') and Restart Tomcat.
>>> 5) Create the IM4JAVA_TOOLPATH environment in the system environment 
>>> using (setx /m IM4JAVA_TOOLPATH "c:\imagemagick") or in the logged in 
>>> user environment using (setx IM4JAVA_TOOLPATH "c:\imagemagick").
>>> 6) Restart the server or just Logged out log back in and try it.
>>>
>>> Hope it helps you.
>>> On Sunday, December 11, 2022 at 6:28:57 AM UTC+3 Mohammad S. AlMutairi 
>>> wrote:
>>>
>>>> Hello,
>>>>
>>>> I see the issue you have now "There was three issues in the first post" 
>>>> :-). It seems identify.exe is not installed on your Windows 10. Can you 
>>>> make sure you see it in the ImageMagick installation folder first? (dir 
>>>> C:\Path-to-ImageMagick\identify.exe) or (dir /s \identify.exe). If it can 
>>>> not be found you need to reinstall the ImageMagick package again but this 
>>>> time make sure "Install legacy utilities (e.g Convert)" is ticked to 
>>>> have it installed and just try it after rebooting your server to be sure. 
>>>> Here is the ImageMagick download link: 
>>>> https://imagemagick.org/script/download.php#windows
>>>>
>>>> Cheers 
>>>>
>>>> Hope it help.
>>>>
>>>>
>>>> On Saturday, December 10, 2022 at 10:29:39 PM UTC+3 Jordan Gamonal 
>>>> Pérez wrote:
>>>>
>>>>> Hello,
>>>>>
>>>>> I tried to do this forcing the command but i receive the same message 
>>>>> error about not find an identify
>>>>>
>>>>>- .\dspace filter-media -f -i 11626/117
>>>>>- ERROR filtering, skipping bitstream:
>>>>>- org.im4java.core.InfoException: 
>>>>>org.im4java.core.CommandException: java.io.FileNotFoundException: 
>>>>> identify
>>>>>
>>>>> I also verified that the imagemagick and ghostscript system variables 
>>>>> were declared and discoverable by *dspace.cfg* Additionally, I run 
>>>>> commands for the creation of covers from pdf to jpg through cmd and they 
>>>>> are solved without problems.
>>>>>
>>>>> Note: Now written from my email, by accident I had responded by my 
>>>>> company email.
>>>>>
>>>>> El Saturday, December 10, 2022 a la(s) 10:00:44 AM UTC-3, 
>>>>> alo...@gmail.com escribió:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> Try to force it with -f: ( C:\dspace\dspace_63\b

[dspace-tech] Re: Filter-media identify error

[Mohammad S. AlMutairi]

There was a typo in step 4. I'm not sure if dspace or im4java are forgiving 
about the backslash so it it's safer to always use forward slash.
4) edit dspace.cfg and set the value for 
(org.dspace.app.mediafilter.ImageMagickThumbnailFilter.ProcessStarter =  'c:
*/*imagemagick') and Restart Tomcat.

On Sunday, December 11, 2022 at 9:50:29 AM UTC+3 Mohammad S. AlMutairi 
wrote:

> You can try the steps you see below if the above suggestion didn't fix the 
> issue you have (Not much information provided about the server setup so I'm 
> guessing here). Anyway, Try the steps you see below. it should fix it no 
> matter what was the cause of the issue you have.
>
> 1) Uninstall the old ImageMagick you have.
> 2) Remove the IM4JAVA_TOOLPATH environment variable if you had it set.
> 3) Download the latest ImageMagick version 
> <https://imagemagick.org/script/download.php#windows> and install it with 
> the legacy utilities option. NB: You must choose the installation path to 
> be (c:\imagemagick) or (C:\dspace\dspace_63\imagemagick). The idea of the 
> path part is to avoid spaces in the folders names.
> 4) edit dspace.cfg and set the value for 
> (org.dspace.app.mediafilter.ImageMagickThumbnailFilter.ProcessStarter 
> =  'c:\imagemagick') and Restart Tomcat.
> 5) Create the IM4JAVA_TOOLPATH environment in the system environment using 
> (setx /m IM4JAVA_TOOLPATH "c:\imagemagick") or in the logged in user 
> environment using (setx IM4JAVA_TOOLPATH "c:\imagemagick").
> 6) Restart the server or just Logged out log back in and try it.
>
> Hope it helps you.
> On Sunday, December 11, 2022 at 6:28:57 AM UTC+3 Mohammad S. AlMutairi 
> wrote:
>
>> Hello,
>>
>> I see the issue you have now "There was three issues in the first post" 
>> :-). It seems identify.exe is not installed on your Windows 10. Can you 
>> make sure you see it in the ImageMagick installation folder first? (dir 
>> C:\Path-to-ImageMagick\identify.exe) or (dir /s \identify.exe). If it can 
>> not be found you need to reinstall the ImageMagick package again but this 
>> time make sure "Install legacy utilities (e.g Convert)" is ticked to 
>> have it installed and just try it after rebooting your server to be sure. 
>> Here is the ImageMagick download link: 
>> https://imagemagick.org/script/download.php#windows
>>
>> Cheers 
>>
>> Hope it help.
>>
>>
>> On Saturday, December 10, 2022 at 10:29:39 PM UTC+3 Jordan Gamonal Pérez 
>> wrote:
>>
>>> Hello,
>>>
>>> I tried to do this forcing the command but i receive the same message 
>>> error about not find an identify
>>>
>>>- .\dspace filter-media -f -i 11626/117
>>>- ERROR filtering, skipping bitstream:
>>>- org.im4java.core.InfoException: org.im4java.core.CommandException: 
>>>java.io.FileNotFoundException: identify
>>>
>>> I also verified that the imagemagick and ghostscript system variables 
>>> were declared and discoverable by *dspace.cfg* Additionally, I run 
>>> commands for the creation of covers from pdf to jpg through cmd and they 
>>> are solved without problems.
>>>
>>> Note: Now written from my email, by accident I had responded by my 
>>> company email.
>>>
>>> El Saturday, December 10, 2022 a la(s) 10:00:44 AM UTC-3, 
>>> alo...@gmail.com escribió:
>>>
>>>> Hi,
>>>>
>>>> Try to force it with -f: ( C:\dspace\dspace_63\bin\dspace filter-media 
>>>> -h ).
>>>> On Saturday, December 10, 2022 at 7:24:37 AM UTC+3 Jordan Gamonal Pérez 
>>>> wrote:
>>>>
>>>>> Greeting,
>>>>>
>>>>> I have the following problem when running a *filter-media -i 
>>>>> 11626/117*. The process starts running but stops suddenly with the 
>>>>> following error message in *dspace.log*
>>>>>
>>>>>
>>>>>- SKIPPED: bitstream 8524934d-a163-42df-8da7-9b3232f1fc02 (item: 
>>>>>11626/117) because 'Document_for_testing.pdf.txt' already exists
>>>>>- ERROR filtering, skipping bitstream:
>>>>>- Caused by: java.io.FileNotFoundException: identify
>>>>>
>>>>> My installation have the next configurations:
>>>>>
>>>>>- Windows 10
>>>>>- DSpace 6.3
>>>>>- PostgreSQL 9.6
>>>>>
>>>>> I'm using a user with sufficient permissions and the item was 
>>>>> successfully imported by Batch.
>>>>>
>>>>> Thanks for your time.
>>>>>
>>>>

-- 
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/b93b807d-d392-46bc-a485-7b14b638d442n%40googlegroups.com.

[dspace-tech] Re: Dspace7 works with ip but not with fqdn

[Mohammad S. AlMutairi]

On Monday, December 12, 2022 at 3:18:33 PM UTC+3 jorge...@gmail.com wrote:

> http://[domain name]:4000/home
> gets me 500 Service Unavailable
>
Do you have any specific reason to run it on port 4000?. If you don't just 
change port 4000 to port 80 and access it without having to write the port 
something like this ( http://[domain name]/home ).

-- 
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/62338880-f980-4edf-bf55-5bdecb6e33b1n%40googlegroups.com.

[dspace-tech] Re: Dspace7 works with ip but not with fqdn

[Mohammad S. AlMutairi]

Check your settings in local.cfg or dspace.cfg and config.prod.yml or post 
them here.

On Monday, December 12, 2022 at 3:18:33 PM UTC+3 jorge...@gmail.com wrote:

> http://[ip]:4000/home works just fine.
> ITs integrated with my AD
> I can log in , browse , deposit , delete etc
>
> http://[domain name]:4000/home
> gets me 500 Service Unavailable
>
> /etc/hosts has an entry for the domain name to its ip
>
> The dns server has an entry
>
> What did I miss ?
> Thanks
>

-- 
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/858bbee5-4090-4002-aa2b-2b2dc9f5ffbdn%40googlegroups.com.

[dspace-tech] Re: Filter-media identify error

[Mohammad S. AlMutairi]

You can try the steps you see below if the above suggestion didn't fix the 
issue you have (Not much information provided about the server setup so I'm 
guessing here). Anyway, Try the steps you see below. it should fix it no 
matter what was the cause of the issue you have.

1) Uninstall the old ImageMagick you have.
2) Remove the IM4JAVA_TOOLPATH environment variable if you had it set.
3) Download the latest ImageMagick version 
<https://imagemagick.org/script/download.php#windows> and install it with 
the legacy utilities option. NB: You must choose the installation path to 
be (c:\imagemagick) or (C:\dspace\dspace_63\imagemagick). The idea of the 
path part is to avoid spaces in the folders names.
4) edit dspace.cfg and set the value for 
(org.dspace.app.mediafilter.ImageMagickThumbnailFilter.ProcessStarter 
=  'c:\imagemagick') and Restart Tomcat.
5) Create the IM4JAVA_TOOLPATH environment in the system environment using 
(setx 
/m IM4JAVA_TOOLPATH "c:\imagemagick") or in the logged in user environment 
using (setx IM4JAVA_TOOLPATH "c:\imagemagick").
6) Restart the server or just Logged out log back in and try it.

Hope it helps you.
On Sunday, December 11, 2022 at 6:28:57 AM UTC+3 Mohammad S. AlMutairi 
wrote:

> Hello,
>
> I see the issue you have now "There was three issues in the first post" 
> :-). It seems identify.exe is not installed on your Windows 10. Can you 
> make sure you see it in the ImageMagick installation folder first? (dir 
> C:\Path-to-ImageMagick\identify.exe) or (dir /s \identify.exe). If it can 
> not be found you need to reinstall the ImageMagick package again but this 
> time make sure "Install legacy utilities (e.g Convert)" is ticked to have 
> it installed and just try it after rebooting your server to be sure. Here 
> is the ImageMagick download link: 
> https://imagemagick.org/script/download.php#windows
>
> Cheers 
>
> Hope it help.
>
>
> On Saturday, December 10, 2022 at 10:29:39 PM UTC+3 Jordan Gamonal Pérez 
> wrote:
>
>> Hello,
>>
>> I tried to do this forcing the command but i receive the same message 
>> error about not find an identify
>>
>>- .\dspace filter-media -f -i 11626/117
>>- ERROR filtering, skipping bitstream:
>>- org.im4java.core.InfoException: org.im4java.core.CommandException: 
>>java.io.FileNotFoundException: identify
>>
>> I also verified that the imagemagick and ghostscript system variables 
>> were declared and discoverable by *dspace.cfg* Additionally, I run 
>> commands for the creation of covers from pdf to jpg through cmd and they 
>> are solved without problems.
>>
>> Note: Now written from my email, by accident I had responded by my 
>> company email.
>>
>> El Saturday, December 10, 2022 a la(s) 10:00:44 AM UTC-3, 
>> alo...@gmail.com escribió:
>>
>>> Hi,
>>>
>>> Try to force it with -f: ( C:\dspace\dspace_63\bin\dspace filter-media 
>>> -h ).
>>> On Saturday, December 10, 2022 at 7:24:37 AM UTC+3 Jordan Gamonal Pérez 
>>> wrote:
>>>
>>>> Greeting,
>>>>
>>>> I have the following problem when running a *filter-media -i 11626/117*. 
>>>> The process starts running but stops suddenly with the following error 
>>>> message in *dspace.log*
>>>>
>>>>
>>>>- SKIPPED: bitstream 8524934d-a163-42df-8da7-9b3232f1fc02 (item: 
>>>>11626/117) because 'Document_for_testing.pdf.txt' already exists
>>>>- ERROR filtering, skipping bitstream:
>>>>- Caused by: java.io.FileNotFoundException: identify
>>>>
>>>> My installation have the next configurations:
>>>>
>>>>- Windows 10
>>>>- DSpace 6.3
>>>>- PostgreSQL 9.6
>>>>
>>>> I'm using a user with sufficient permissions and the item was 
>>>> successfully imported by Batch.
>>>>
>>>> Thanks for your time.
>>>>
>>>

-- 
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/057e88d8-0cfc-4585-ba86-b1c6e5e49523n%40googlegroups.com.

[dspace-tech] Re: Filter-media identify error

[Mohammad S. AlMutairi]

Hello,

I see the issue you have now "There was three issues in the first post" 
:-). It seems identify.exe is not installed on your Windows 10. Can you 
make sure you see it in the ImageMagick installation folder first? (dir 
C:\Path-to-ImageMagick\identify.exe) or (dir /s \identify.exe). If it can 
not be found you need to reinstall the ImageMagick package again but this 
time make sure "Install legacy utilities (e.g Convert)" is ticked to have 
it installed and just try it after rebooting your server to be sure. Here 
is the ImageMagick download link: 
https://imagemagick.org/script/download.php#windows

Cheers 

Hope it help.


On Saturday, December 10, 2022 at 10:29:39 PM UTC+3 Jordan Gamonal Pérez 
wrote:

> Hello,
>
> I tried to do this forcing the command but i receive the same message 
> error about not find an identify
>
>- .\dspace filter-media -f -i 11626/117
>- ERROR filtering, skipping bitstream:
>- org.im4java.core.InfoException: org.im4java.core.CommandException: 
>java.io.FileNotFoundException: identify
>
> I also verified that the imagemagick and ghostscript system variables were 
> declared and discoverable by *dspace.cfg* Additionally, I run commands 
> for the creation of covers from pdf to jpg through cmd and they are solved 
> without problems.
>
> Note: Now written from my email, by accident I had responded by my company 
> email.
>
> El Saturday, December 10, 2022 a la(s) 10:00:44 AM UTC-3, alo...@gmail.com 
> escribió:
>
>> Hi,
>>
>> Try to force it with -f: ( C:\dspace\dspace_63\bin\dspace filter-media -h 
>> ).
>> On Saturday, December 10, 2022 at 7:24:37 AM UTC+3 Jordan Gamonal Pérez 
>> wrote:
>>
>>> Greeting,
>>>
>>> I have the following problem when running a *filter-media -i 11626/117*. 
>>> The process starts running but stops suddenly with the following error 
>>> message in *dspace.log*
>>>
>>>
>>>- SKIPPED: bitstream 8524934d-a163-42df-8da7-9b3232f1fc02 (item: 
>>>11626/117) because 'Document_for_testing.pdf.txt' already exists
>>>- ERROR filtering, skipping bitstream:
>>>- Caused by: java.io.FileNotFoundException: identify
>>>
>>> My installation have the next configurations:
>>>
>>>- Windows 10
>>>- DSpace 6.3
>>>- PostgreSQL 9.6
>>>
>>> I'm using a user with sufficient permissions and the item was 
>>> successfully imported by Batch.
>>>
>>> Thanks for your time.
>>>
>>

-- 
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/020cad20-c875-4189-b601-5cfd4f4b5f7bn%40googlegroups.com.

[dspace-tech] Re: Filter-media identify error

[Mohammad S. AlMutairi]

Hi,

Try to force it with -f: ( C:\dspace\dspace_63\bin\dspace filter-media -h ).
On Saturday, December 10, 2022 at 7:24:37 AM UTC+3 Jordan Gamonal Pérez 
wrote:

> Greeting,
>
> I have the following problem when running a *filter-media -i 11626/117*. 
> The process starts running but stops suddenly with the following error 
> message in *dspace.log*
>
>
>- SKIPPED: bitstream 8524934d-a163-42df-8da7-9b3232f1fc02 (item: 
>11626/117) because 'Document_for_testing.pdf.txt' already exists
>- ERROR filtering, skipping bitstream:
>- Caused by: java.io.FileNotFoundException: identify
>
> My installation have the next configurations:
>
>- Windows 10
>- DSpace 6.3
>- PostgreSQL 9.6
>
> I'm using a user with sufficient permissions and the item was successfully 
> imported by Batch.
>
> Thanks for your time.
>

-- 
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/2b09661d-1eac-4e57-afcf-f8d3bee4e574n%40googlegroups.com.

[dspace-tech] Re: How to disable klaro?

[Mohammad S. AlMutairi]

You got the 404 page not found error because you needed to run 
[dspace]/index-discovery after the change you have made to this item. Try 
the steps you see below. It should fix it.
1) /dspace/bin/dspace database migrate
2) /dspace/bin/dspace database validate
3) /dspace/bin/dspace database status
4) Change using pgAdmin https://hdl.handle.net/your-handle-prefix/1916 to 
https://your-server-domain-name/handle/your-handle-prefix/1916
5) /dspace/bin/dspace index-discovery -f -i 
e56a5422-b32b-4000-95dd-86467ef21c35
6) Copy over the old assetstore folder from the old server to the new 
Ubuntu server into /dspace/assetstore folder.
7) Try to access this item you changed and try download to PDF file.

You are a stubborn man I must admin :-).
Hop it helps you.
On Saturday, November 26, 2022 at 2:47:04 AM UTC+3 Night Librarian wrote:

> Thank you for the suggestion.  I changed the dc.identifier.uri from 
> https://hdl.handle.net/your-handle-prefix/1916 by 
> https://my-server-domain-name/handle/my-handle-prefix/1916. Now, if I try 
> to open 
> https://my-server-domain-name/handle/my-handle-prefix/1916 in the 
> browser, I get 404 page not found.  If I search for the item's title in all 
> of DSpace, and then try to download the pdf from there, I still can see the 
> pdf in the browser, but downloading it still doesn't work.
>
> In terms of Handle server, I wonder whether copy/pasting 
> [dspace]/handle-server directory's content from someone who has 7.4 on 
> Ubuntu 20.04 would fix my issue?
> On Friday, November 25, 2022 at 4:53:06 p.m. UTC-4 alo...@gmail.com wrote:
>
>> You should completely ignore that suggestion and here is why (  
>> https://github.com/kiprotect/klaro ). I think the issue you have is 
>> caused by how the migration from the Windows server to the Linux was done 
>> and is related to the handle server specifically because it's down. As a 
>> suggestion try to change one of the the items 
>> (e56a5422-b32b-4000-95dd-86467ef21c35) dc.​identifier.​uri from 
>> https://hdl.handle.net/your-handle-prefix/1916 to 
>> https://your-server-domain-name/handle/your-handle-prefix/1916 and try 
>> to access it and download it and see if that helps isolate the handle 
>> server is the cause.
>>
>> Hope It help.
>>
>> On Friday, November 25, 2022 at 10:20:58 PM UTC+3 Night Librarian wrote:
>>
>>> I had a suggestion to disable klaro to solve a downloading problem on my 
>>> DSpace 7.4, but I am not sure how to do that.  Can someone give me a hint?
>>
>>

-- 
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/f5288c03-fea6-493a-941b-7db582a084a6n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.4 backend pgcrypto extension not installed error

[Mohammad S. AlMutairi]

@Tim I hope you see this to fix/add an extra missing step to the 
pgcrypto extention creation in the domcumentation so no user will face the 
warning message Jeff posted if the user chose to create the extention on 
the dspace database instead of adding it to a schema.

Executing psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;" 
alone won't work unless the search_path is set to include the pgcrypto 
extention in it.

# This should work
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
2) psql --username=postgres dspace -c 'ALTER ROLE dspace IN DATABASE dspace 
SET search_path = "$user",public,extensions,pgcrypto;'
3) psql --username=postgres dspace -c 'SHOW search_path;'

# Or this one
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
2) psql --username=postgres dspace -c 'ALTER DATABASE dspace SET 
search_path = "$user",public,extensions,pgcrypto;'
3) psql --username=postgres dspace -c 'SHOW search_path;'

# Or this one if the search path is set globally in the main postgresql 
configuration file.
1) vi /path-to/postgresql.conf
search_path = '$user",public,extensions,pgcrypto'

# Or this one if the dspace script/scripts sets the search_path in them 
(SET search_path = "$user",public,extensions,pgcrypto;).
1) psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"

Trying to help.

On Sunday, December 4, 2022 at 4:26:32 AM UTC+3 Mohammad S. AlMutairi wrote:

> Hi Jeff,
>
> It is created but it can not be found because it's not included in the 
> search path. One way of fixing this is to create a schema for all 
> extensions first and then create the pgcrypto extension and add it to that 
> schema. Just follow the steps you see below to pass the error.
>
> 1) su - postgres
> 2) createuser --username=postgres --no-superuser --pwprompt dspace
> 3) createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
> 4) psql --username=postgres dspace
> 5) CREATE SCHEMA extensions;
> 6) CREATE EXTENSION pgcrypto SCHEMA extensions;
> 7) GRANT USAGE ON SCHEMA extensions TO dspace;
> 8) SELECT set_config('search_path',current_setting('search_path') || 
> ',extensions',false) WHERE current_setting('search_path') !~ 
> '(^|,)extensions(,|$)';
> 9) SHOW search_path;
> 10) ALTER DATABASE dspace SET search_path FROM CURRENT;
> 11) \q
> 12) exit
>
> Good luck
> On Friday, December 2, 2022 at 8:49:34 PM UTC+3 Jeff Mitchell wrote:
>
>> Just to clarify I had run this already and restarted PSQL as well before 
>> running the build and install
>>
>> # Login to the database as a superuser, and enable the pgcrypto extension 
>> on this database
>> psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
>> On Friday, December 2, 2022 at 11:19:20 AM UTC-6 Jeff Mitchell wrote:
>>
>>> Hello all,
>>>
>>> I just finished the build section of the configuration but when I got to 
>>> run the ant fresh_install I get:
>>>
>>>  [java] WARNING: Required PostgreSQL 'pgcrypto' extension is NOT 
>>> INSTALLED on this database.
>>>
>>>  [java] 
>>>  [java] ** DSpace REQUIRES PostgreSQL >= 9.4 AND pgcrypto extension 
>>> >= 1.1 ** 
>>>
>>> However, when I check to see what extensions are installed it shows me 
>>> that pgcrypto 1.3 is installed and yes I installed it as postgres and 
>>> dspace db users. I'm running PSQL 13 if that helps.
>>>
>>> Thanks in advance!
>>>
>>> Jeff
>>>
>>>

-- 
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/7687d570-43e0-4a24-8a8c-40e13726e311n%40googlegroups.com.

[dspace-tech] Re: Dspace 7.4 backend pgcrypto extension not installed error

[Mohammad S. AlMutairi]

Hi Jeff,

It is created but it can not be found because it's not included in the 
search path. One way of fixing this is to create a schema for all 
extensions first and then create the pgcrypto extension and add it to that 
schema. Just follow the steps you see below to pass the error.

1) su - postgres
2) createuser --username=postgres --no-superuser --pwprompt dspace
3) createdb --username=postgres --owner=dspace --encoding=UNICODE dspace
4) psql --username=postgres dspace
5) CREATE SCHEMA extensions;
6) CREATE EXTENSION pgcrypto SCHEMA extensions;
7) GRANT USAGE ON SCHEMA extensions TO dspace;
8) SELECT set_config('search_path',current_setting('search_path') || 
',extensions',false) WHERE current_setting('search_path') !~ 
'(^|,)extensions(,|$)';
9) SHOW search_path;
10) ALTER DATABASE dspace SET search_path FROM CURRENT;
11) \q
12) exit

Good luck
On Friday, December 2, 2022 at 8:49:34 PM UTC+3 Jeff Mitchell wrote:

> Just to clarify I had run this already and restarted PSQL as well before 
> running the build and install
>
> # Login to the database as a superuser, and enable the pgcrypto extension 
> on this database
> psql --username=postgres dspace -c "CREATE EXTENSION pgcrypto;"
> On Friday, December 2, 2022 at 11:19:20 AM UTC-6 Jeff Mitchell wrote:
>
>> Hello all,
>>
>> I just finished the build section of the configuration but when I got to 
>> run the ant fresh_install I get:
>>
>>  [java] WARNING: Required PostgreSQL 'pgcrypto' extension is NOT 
>> INSTALLED on this database.
>>
>>  [java] 
>>  [java] ** DSpace REQUIRES PostgreSQL >= 9.4 AND pgcrypto extension 
>> >= 1.1 ** 
>>
>> However, when I check to see what extensions are installed it shows me 
>> that pgcrypto 1.3 is installed and yes I installed it as postgres and 
>> dspace db users. I'm running PSQL 13 if that helps.
>>
>> Thanks in advance!
>>
>> Jeff
>>
>>

-- 
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/4be28d0e-42ec-47ce-9db7-538136b00800n%40googlegroups.com.

Re: [dspace-tech] Re: How to disable klaro?

[Mohammad S. AlMutairi]

-  1 root   tomcat  1.4M Nov  8 11:45 spring-boot-2.6.8.jar
>>> -rw-r--r--  1 root   tomcat  1.6M Nov  8 11:45
>>> spring-boot-autoconfigure-2.6.8.jar
>>> -rw-r--r--  1 root   tomcat   86K Aug 23 22:30
>>> spring-boot-configuration-processor-2.0.0.RELEASE.jar
>>> -rw-r--r--  1 root   tomcat  4.7K Nov  8 11:45
>>> spring-boot-starter-2.6.8.jar
>>> -rw-r--r--  1 root   tomcat  4.7K Nov  8 11:45
>>> spring-boot-starter-cache-2.6.8.jar
>>> -rw-r--r--  1 root   tomcat  4.7K Nov  8 11:44
>>> spring-boot-starter-log4j2-2.6.8.jar
>>> -rw-r--r--  1 root   tomcat  1.3M Nov  8 11:44 spring-context-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  183K Nov  8 11:44
>>> spring-context-support-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  1.5M Nov  8 11:44 spring-core-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  283K Nov  8 11:44
>>> spring-expression-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat   24K Nov  8 11:44 spring-jcl-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  419K Nov  8 11:45 spring-jdbc-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  200K Nov  8 11:45 spring-orm-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  326K Nov  8 11:45 spring-tx-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  1.6M Nov  8 11:48 spring-web-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat 1005K Nov  8 11:48 spring-webmvc-5.3.20.jar
>>> -rw-r--r--  1 root   tomcat  192K Nov  8 11:45 stax2-api-4.2.1.jar
>>> -rw-r--r--  1 root   tomcat   36K Aug 23 22:24 stax-ex-1.8.jar
>>> -rw-r--r--  1 root   tomcat  202K Aug 23 22:24
>>> taglibs-standard-impl-1.2.5.jar
>>> -rw-r--r--  1 root   tomcat   40K Aug 23 22:24
>>> taglibs-standard-spec-1.2.5.jar
>>> -rw-r--r--  1 root   tomcat   89K Aug 23 22:24 tagsoup-1.2.1.jar
>>> -rw-r--r--  1 root   tomcat  647K Nov  8 11:45 tika-core-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   59K Nov  8 11:45
>>> tika-parser-apple-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   66K Nov  8 11:45
>>> tika-parser-audiovideo-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   18K Nov  8 11:45
>>> tika-parser-cad-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   29K Nov  8 11:45
>>> tika-parser-code-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   20K Nov  8 11:45
>>> tika-parser-crypto-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   18K Nov  8 11:45
>>> tika-parser-digest-commons-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   14K Nov  8 11:45
>>> tika-parser-font-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   15K Nov  8 11:45
>>> tika-parser-html-commons-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   52K Nov  8 11:45
>>> tika-parser-html-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   52K Nov  8 11:45
>>> tika-parser-image-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat  9.7K Nov  8 11:45
>>> tika-parser-mail-commons-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   29K Nov  8 11:45
>>> tika-parser-mail-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat  650K Nov  8 11:45
>>> tika-parser-microsoft-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat  146K Nov  8 11:45
>>> tika-parser-miscoffice-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   20K Nov  8 11:45
>>> tika-parser-news-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   39K Nov  8 11:45
>>> tika-parser-ocr-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   95K Nov  8 11:45
>>> tika-parser-pdf-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   26K Nov  8 11:45
>>> tika-parser-pkg-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat  1.4M Nov  8 11:45
>>> tika-parsers-standard-package-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat  120K Nov  8 11:45
>>> tika-parser-text-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   36K Nov  8 11:45
>>> tika-parser-xml-module-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   16K Nov  8 11:45
>>> tika-parser-xmp-commons-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   40K Nov  8 11:45
>>> tika-parser-zip-commons-2.3.0.jar
>>> -rw-r--r--  1 root   tomcat   69K Aug 23 22:24 txw2-2.3.1.jar
>>> -rw-r--r--  1 root   tomcat   91K Aug 23 22:24
>>> validation-api-2.0.1.Final.jar
>>> -rw-r--r--  1 root   tomcat  519K Nov  8 11:45
>>> velocity-engine-core-2.3.jar
>>> -rw-r--r--  1 root   tomcat  119K Aug 23 22:24 vorbis-java-core-0.8.jar
>>> -rw-r--r--  1 root   tomcat   25K Aug 23 22:24 vorbis-java-tika-0.8.jar
>>> -rw-r--r--  1 root   tomcat  1.6M Nov  8 11:45 woodstox-core-6.2.4.jar
>>> -rw-r--r--  1 root   tomcat  1.4M Nov  8 11:45 xercesImpl-2.12.2.jar
>>> -rw-r--r--  1 root   tomcat  216K Aug 23 22:24 xml-apis-1.4.01.jar
>>> -rw-r--r--  1 root   tomcat  2.1M Nov  8 11:45 xmlbeans-5.0.3.jar
>>> -rw-r--r--  1 root   tomcat  130K Nov  8 11:45 xmpbox-2.0.25.jar
>>> -rw-r--r--  1 root   tomcat  140K Nov  8 11:45 xmpcore-6.1.11.jar
>>> -rw-r--r--  1 root   tomcat  319K Aug 23 22:30 xoai-3.3.0.jar
>>> -rw-r--r--  1 root   tomcat  114K Aug 23 22:38 xz-1.9.jar
>>> -rw-r--r--  1 root   tomcat  1.2M Nov  8 11:45 zookeeper-3.6.2.jar
>>> -rw-r--r--  1 root   tomcat  245K Aug 23 22:24 zookeeper-jute-3.6.2.jar
>>>
>>> Once again, thank you for your help!
>>> On Saturday, November 26, 2022 at 1:56:35 p.m. UTC-4 alo...@gmail.com
>>> wrote:
>>>
>>>> One thing I noticed you should take care of too is If the handle server
>>>> you trying to start is installed on the same server you installed DSpace on
>>>> you need to open port 2641 and port 8000 on the public firewall and on the
>>>> server too if you have a firewall running on your Ubuntu server. ( These
>>>> ports are blocked right now and inaccessible so you have to open them to
>>>> complete your handle server setup).
>>>>
>>>> Good luck
>>>>
>>>> On Saturday, November 26, 2022 at 4:12:32 AM UTC+3 Mohammad S.
>>>> AlMutairi wrote:
>>>>
>>>>> On Saturday, November 26, 2022 at 2:47:04 AM UTC+3 Night Librarian
>>>>> wrote:
>>>>>
>>>>>> In terms of Handle server, I wonder whether copy/pasting
>>>>>> [dspace]/handle-server directory's content from someone who has 7.4 on
>>>>>> Ubuntu 20.04 would fix my issue?
>>>>>>
>>>>> My English is becoming a barrier to read things the right way or
>>>>> convey the ideas in a good way (Sorry about that). Copying the folder from
>>>>> someone else's server won't help or do much but copying your old working
>>>>> handle-server folder from the Windows server to the new Ubuntu server will
>>>>> do so just follow the steps you see in the previous post if you still have
>>>>> access to your old server and can get a copy of the old handle-server
>>>>> folder.
>>>>>
>>>> --
> 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 a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/wiI45y7xSRs/unsubscribe.
> To unsubscribe from this group and all its topics, 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/9006d4a6-7fa3-4f88-9db4-6fc5824fad7fn%40googlegroups.com
> <https://groups.google.com/d/msgid/dspace-tech/9006d4a6-7fa3-4f88-9db4-6fc5824fad7fn%40googlegroups.com?utm_medium=email_source=footer>
> .
>

-- 
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/CAESrwAYo6-e-Qopn%2B35SRjaMs7dMqUOxa6MKtNh2M5akvt8%2B5g%40mail.gmail.com.

[dspace-tech] Re: File upload error on Dspace 7.4

[Mohammad S. AlMutairi]

You are most welcome. Very happy for you got it working.

On Wednesday, November 30, 2022 at 4:09:04 PM UTC+3 jesse...@gmail.com 
wrote:

> Wonderful my friend. 
> You are one great soul on earth. It worked like a charm. 
> I was so desperate to see my installation working, and with this error, I 
> was feeling helpless.  Even the error logs didn't show any detail. 
> But you gave the precise solution for my issue. 
> Thank You so much. 
>
> Rupinder Singh
>
> On Wednesday, November 30, 2022 at 5:49:11 PM UTC+5:30 alo...@gmail.com 
> wrote:
>
>> Never mind: You need to find the tomcat systemd unit file 
>> (tomcat9.service) if you install the default Ubuntu tomcat package and make 
>> sure tomcat user you see in the unit file has write permission over the 
>> DSpace folder and need to tell tomcat it can write into DSpace folder as 
>> you see it highlted in red.
>>
>> [Service]
>>
>> # Configuration
>> Environment="CATALINA_HOME=/usr/share/tomcat9"
>> Environment="CATALINA_BASE=/var/lib/tomcat9"
>> Environment="CATALINA_TMPDIR=/tmp"
>> Environment="JAVA_OPTS=-Djava.awt.headless=true -Dfile.encoding=UTF-8"
>>
>> # Lifecycle
>> Type=simple
>> ExecStartPre=+/usr/libexec/tomcat9/tomcat-update-policy.sh
>> ExecStart=/bin/sh /usr/libexec/tomcat9/tomcat-start.sh
>> SuccessExitStatus=143
>> Restart=on-abort
>>
>> # Logging
>> SyslogIdentifier=tomcat9
>>
>> # Security
>> *User=tomcat*
>> Group=tomcat
>> PrivateTmp=yes
>> AmbientCapabilities=CAP_NET_BIND_SERVICE
>> NoNewPrivileges=true
>> CacheDirectory=tomcat9
>> CacheDirectoryMode=750
>> ProtectSystem=strict
>> ReadWritePaths=/etc/tomcat9/Catalina/
>> ReadWritePaths=/var/lib/tomcat9/webapps/
>> ReadWritePaths=/var/log/tomcat9/
>> *ReadWritePaths=/opt/dspace*
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> On Wednesday, November 30, 2022 at 3:06:23 PM UTC+3 Mohammad S. AlMutairi 
>> wrote:
>>
>>> Which Operating System are you using?
>>>
>>> On Wednesday, November 30, 2022 at 2:47:53 PM UTC+3 jesse...@gmail.com 
>>> wrote:
>>>
>>>> Hi, 
>>>> I am struggling to get this software to work for the last 2 months, and 
>>>> still no success. 
>>>> I did the Dspace 7.4 backend installation on my Ubuntu 22.04 computer, 
>>>> installed Solr from source, installed tomcat9 from the apt package 
>>>> manager, 
>>>> and compiled the DSpace code for the backend. 
>>>> Everything is running under a dedicated 'DSpace' system user. It went 
>>>> well and I can access the backend HAL interface on localhost:8080/server. 
>>>>
>>>> Further, I went to install the frontend on the same machine, under the 
>>>> same user (i.e., dspace), and installed node js, yarn, and everything as 
>>>> mentioned in DSpace wiki, it also went well and I could see my DSpace 7 
>>>> home screen for the first time. It was beautiful and I was happy, I logged 
>>>> in with my administrative users, and created some communities and 
>>>> collections. it is all working. BUT I CAN NOT UPLOAD ANY FILE, NOT EVEN 
>>>> THE 
>>>> COMMUNITY LOGO's. 
>>>> I am so fed up with this software, Error logs are of no help. i thought 
>>>> it would be a permission issue, but my system user 'dspace' is the owner 
>>>> of 
>>>> both dspace backend folder, and also dspace-angular, tomcat9, Solr, and 
>>>> yarn both are running under 'dsapce' system user. still, I can't upload 
>>>> anything. I can't figure out what I did wrong, and where I'm missing 
>>>> something, and at this point, I'm too tired to re-install it again and 
>>>> again (like I've been doing for the last 2 months). 
>>>>
>>>> Seriously!!, please help, I need to get this working.  
>>>>
>>>>
>>>> Thank You
>>>>
>>>> Rupinder Singh 
>>>>
>>>>

-- 
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/060813ca-3360-4bce-9a82-f548a526194fn%40googlegroups.com.

Re: [dspace-tech] Re: File upload error on Dspace 7.4

[Mohammad S. AlMutairi]

You are most welcome. Very happy you got it working. Please close it in the
thread so other community members who might fall into the same won't spend
much time as you did.

Cheers

On Wed, Nov 30, 2022 at 4:09 PM Rupinder Singh 
wrote:

> Wonderful my friend.
> You are one great soul on earth. It worked like a charm.
> I was so desperate to see my installation working, and with this error, I
> was feeling helpless.  Even the error logs didn't show any detail.
> But you gave the precise solution for my issue.
> Thank You so much.
>
> Rupinder Singh
>
> On Wednesday, November 30, 2022 at 5:49:11 PM UTC+5:30 alo...@gmail.com
> wrote:
>
>> Never mind: You need to find the tomcat systemd unit file
>> (tomcat9.service) if you install the default Ubuntu tomcat package and make
>> sure tomcat user you see in the unit file has write permission over the
>> DSpace folder and need to tell tomcat it can write into DSpace folder as
>> you see it highlted in red.
>>
>> [Service]
>>
>> # Configuration
>> Environment="CATALINA_HOME=/usr/share/tomcat9"
>> Environment="CATALINA_BASE=/var/lib/tomcat9"
>> Environment="CATALINA_TMPDIR=/tmp"
>> Environment="JAVA_OPTS=-Djava.awt.headless=true -Dfile.encoding=UTF-8"
>>
>> # Lifecycle
>> Type=simple
>> ExecStartPre=+/usr/libexec/tomcat9/tomcat-update-policy.sh
>> ExecStart=/bin/sh /usr/libexec/tomcat9/tomcat-start.sh
>> SuccessExitStatus=143
>> Restart=on-abort
>>
>> # Logging
>> SyslogIdentifier=tomcat9
>>
>> # Security
>> *User=tomcat*
>> Group=tomcat
>> PrivateTmp=yes
>> AmbientCapabilities=CAP_NET_BIND_SERVICE
>> NoNewPrivileges=true
>> CacheDirectory=tomcat9
>> CacheDirectoryMode=750
>> ProtectSystem=strict
>> ReadWritePaths=/etc/tomcat9/Catalina/
>> ReadWritePaths=/var/lib/tomcat9/webapps/
>> ReadWritePaths=/var/log/tomcat9/
>> *ReadWritePaths=/opt/dspace*
>>
>> [Install]
>> WantedBy=multi-user.target
>>
>> On Wednesday, November 30, 2022 at 3:06:23 PM UTC+3 Mohammad S. AlMutairi
>> wrote:
>>
>>> Which Operating System are you using?
>>>
>>> On Wednesday, November 30, 2022 at 2:47:53 PM UTC+3 jesse...@gmail.com
>>> wrote:
>>>
>>>> Hi,
>>>> I am struggling to get this software to work for the last 2 months, and
>>>> still no success.
>>>> I did the Dspace 7.4 backend installation on my Ubuntu 22.04 computer,
>>>> installed Solr from source, installed tomcat9 from the apt package manager,
>>>> and compiled the DSpace code for the backend.
>>>> Everything is running under a dedicated 'DSpace' system user. It went
>>>> well and I can access the backend HAL interface on localhost:8080/server.
>>>>
>>>> Further, I went to install the frontend on the same machine, under the
>>>> same user (i.e., dspace), and installed node js, yarn, and everything as
>>>> mentioned in DSpace wiki, it also went well and I could see my DSpace 7
>>>> home screen for the first time. It was beautiful and I was happy, I logged
>>>> in with my administrative users, and created some communities and
>>>> collections. it is all working. BUT I CAN NOT UPLOAD ANY FILE, NOT EVEN THE
>>>> COMMUNITY LOGO's.
>>>> I am so fed up with this software, Error logs are of no help. i thought
>>>> it would be a permission issue, but my system user 'dspace' is the owner of
>>>> both dspace backend folder, and also dspace-angular, tomcat9, Solr, and
>>>> yarn both are running under 'dsapce' system user. still, I can't upload
>>>> anything. I can't figure out what I did wrong, and where I'm missing
>>>> something, and at this point, I'm too tired to re-install it again and
>>>> again (like I've been doing for the last 2 months).
>>>>
>>>> Seriously!!, please help, I need to get this working.
>>>>
>>>>
>>>> Thank You
>>>>
>>>> Rupinder Singh
>>>>
>>>> --
> 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 a topic in the
> Google Groups "DSpace Technical Support" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/dspace-tech/mSneVhXMRSA/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> dspace-tech+unsubscr...@googlegr

[dspace-tech] Re: File upload error on Dspace 7.4

[Mohammad S. AlMutairi]

Never mind: You need to find the tomcat systemd unit file (tomcat9.service) 
if you install the default Ubuntu tomcat package and make sure tomcat user 
you see in the unit file has write permission over the DSpace folder and 
need to tell tomcat it can write into DSpace folder as you see it highlted 
in red.

[Service]

# Configuration
Environment="CATALINA_HOME=/usr/share/tomcat9"
Environment="CATALINA_BASE=/var/lib/tomcat9"
Environment="CATALINA_TMPDIR=/tmp"
Environment="JAVA_OPTS=-Djava.awt.headless=true -Dfile.encoding=UTF-8"

# Lifecycle
Type=simple
ExecStartPre=+/usr/libexec/tomcat9/tomcat-update-policy.sh
ExecStart=/bin/sh /usr/libexec/tomcat9/tomcat-start.sh
SuccessExitStatus=143
Restart=on-abort

# Logging
SyslogIdentifier=tomcat9

# Security
*User=tomcat*
Group=tomcat
PrivateTmp=yes
AmbientCapabilities=CAP_NET_BIND_SERVICE
NoNewPrivileges=true
CacheDirectory=tomcat9
CacheDirectoryMode=750
ProtectSystem=strict
ReadWritePaths=/etc/tomcat9/Catalina/
ReadWritePaths=/var/lib/tomcat9/webapps/
ReadWritePaths=/var/log/tomcat9/
*ReadWritePaths=/opt/dspace*

[Install]
WantedBy=multi-user.target

On Wednesday, November 30, 2022 at 3:06:23 PM UTC+3 Mohammad S. AlMutairi 
wrote:

> Which Operating System are you using?
>
> On Wednesday, November 30, 2022 at 2:47:53 PM UTC+3 jesse...@gmail.com 
> wrote:
>
>> Hi, 
>> I am struggling to get this software to work for the last 2 months, and 
>> still no success. 
>> I did the Dspace 7.4 backend installation on my Ubuntu 22.04 computer, 
>> installed Solr from source, installed tomcat9 from the apt package manager, 
>> and compiled the DSpace code for the backend. 
>> Everything is running under a dedicated 'DSpace' system user. It went 
>> well and I can access the backend HAL interface on localhost:8080/server. 
>>
>> Further, I went to install the frontend on the same machine, under the 
>> same user (i.e., dspace), and installed node js, yarn, and everything as 
>> mentioned in DSpace wiki, it also went well and I could see my DSpace 7 
>> home screen for the first time. It was beautiful and I was happy, I logged 
>> in with my administrative users, and created some communities and 
>> collections. it is all working. BUT I CAN NOT UPLOAD ANY FILE, NOT EVEN THE 
>> COMMUNITY LOGO's. 
>> I am so fed up with this software, Error logs are of no help. i thought 
>> it would be a permission issue, but my system user 'dspace' is the owner of 
>> both dspace backend folder, and also dspace-angular, tomcat9, Solr, and 
>> yarn both are running under 'dsapce' system user. still, I can't upload 
>> anything. I can't figure out what I did wrong, and where I'm missing 
>> something, and at this point, I'm too tired to re-install it again and 
>> again (like I've been doing for the last 2 months). 
>>
>> Seriously!!, please help, I need to get this working.  
>>
>>
>> Thank You
>>
>> Rupinder Singh 
>>
>>

-- 
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/fcfcb4fb-262a-4bc3-95c0-ffeafb8f5334n%40googlegroups.com.

[dspace-tech] Re: File upload error on Dspace 7.4

[Mohammad S. AlMutairi]

Which Operating System are you using?

On Wednesday, November 30, 2022 at 2:47:53 PM UTC+3 jesse...@gmail.com 
wrote:

> Hi, 
> I am struggling to get this software to work for the last 2 months, and 
> still no success. 
> I did the Dspace 7.4 backend installation on my Ubuntu 22.04 computer, 
> installed Solr from source, installed tomcat9 from the apt package manager, 
> and compiled the DSpace code for the backend. 
> Everything is running under a dedicated 'DSpace' system user. It went well 
> and I can access the backend HAL interface on localhost:8080/server. 
>
> Further, I went to install the frontend on the same machine, under the 
> same user (i.e., dspace), and installed node js, yarn, and everything as 
> mentioned in DSpace wiki, it also went well and I could see my DSpace 7 
> home screen for the first time. It was beautiful and I was happy, I logged 
> in with my administrative users, and created some communities and 
> collections. it is all working. BUT I CAN NOT UPLOAD ANY FILE, NOT EVEN THE 
> COMMUNITY LOGO's. 
> I am so fed up with this software, Error logs are of no help. i thought it 
> would be a permission issue, but my system user 'dspace' is the owner of 
> both dspace backend folder, and also dspace-angular, tomcat9, Solr, and 
> yarn both are running under 'dsapce' system user. still, I can't upload 
> anything. I can't figure out what I did wrong, and where I'm missing 
> something, and at this point, I'm too tired to re-install it again and 
> again (like I've been doing for the last 2 months). 
>
> Seriously!!, please help, I need to get this working.  
>
>
> Thank You
>
> Rupinder Singh 
>
>

-- 
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/96d3e670-6a92-47c5-89c7-b0a813f5ffc7n%40googlegroups.com.

[dspace-tech] Re: Deposit files 7.4 for a long time

[Mohammad S. AlMutairi]

You should've checked the tomcat logs too (You could've found it there). 
You dropped a very valuable piece of information for any one who is willing 
to help which is the OS you are using. It could be a permission problem 
related to tomcat user not being able to write to DSpace installation 
folder.

On Wednesday, November 30, 2022 at 12:24:02 PM UTC+3 vzapate...@gmail.com 
wrote:

> I've installed Dspace 7.4 backend and front end in the same linux server. 
> I've created some collections.
>
> When I deposit one file there is no error but it takes long time. I've 
> been watching backend logs while deposit file with DEBUG detail option I 
> have no error but I don't find nothing special. I've been watching 'top' 
> linux command and I don't find nothing special. It's so quiet.
>
> Deposit process takes 2-3 minutes aprrox with no error. Any idea?
>

-- 
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/613e6b71-578e-4826-9e3a-8db6c36bb0ean%40googlegroups.com.

[dspace-tech] Re: How to disable klaro?

[Mohammad S. AlMutairi]

akeyaml-1.29.jar
> -rw-r--r--  1 root   tomcat  1.9M Aug 23 22:24 snappy-java-1.1.7.6.jar
> -rw-r--r--  1 root   tomcat  2.3M Nov  8 11:45 solr-solrj-8.11.1.jar
> -rw-r--r--  1 root   tomcat   24K Aug 23 22:24 SparseBitSet-1.2.jar
> -rw-r--r--  1 root   tomcat  375K Nov  8 11:44 spring-aop-5.3.20.jar
> -rw-r--r--  1 root   tomcat  683K Nov  8 11:44 spring-beans-5.3.20.jar
> -rw-r--r--  1 root   tomcat  1.4M Nov  8 11:45 spring-boot-2.6.8.jar
> -rw-r--r--  1 root   tomcat  1.6M Nov  8 11:45 
> spring-boot-autoconfigure-2.6.8.jar
> -rw-r--r--  1 root   tomcat   86K Aug 23 22:30 
> spring-boot-configuration-processor-2.0.0.RELEASE.jar
> -rw-r--r--  1 root   tomcat  4.7K Nov  8 11:45 
> spring-boot-starter-2.6.8.jar
> -rw-r--r--  1 root   tomcat  4.7K Nov  8 11:45 
> spring-boot-starter-cache-2.6.8.jar
> -rw-r--r--  1 root   tomcat  4.7K Nov  8 11:44 
> spring-boot-starter-log4j2-2.6.8.jar
> -rw-r--r--  1 root   tomcat  1.3M Nov  8 11:44 spring-context-5.3.20.jar
> -rw-r--r--  1 root   tomcat  183K Nov  8 11:44 
> spring-context-support-5.3.20.jar
> -rw-r--r--  1 root   tomcat  1.5M Nov  8 11:44 spring-core-5.3.20.jar
> -rw-r--r--  1 root   tomcat  283K Nov  8 11:44 spring-expression-5.3.20.jar
> -rw-r--r--  1 root   tomcat   24K Nov  8 11:44 spring-jcl-5.3.20.jar
> -rw-r--r--  1 root   tomcat  419K Nov  8 11:45 spring-jdbc-5.3.20.jar
> -rw-r--r--  1 root   tomcat  200K Nov  8 11:45 spring-orm-5.3.20.jar
> -rw-r--r--  1 root   tomcat  326K Nov  8 11:45 spring-tx-5.3.20.jar
> -rw-r--r--  1 root   tomcat  1.6M Nov  8 11:48 spring-web-5.3.20.jar
> -rw-r--r--  1 root   tomcat 1005K Nov  8 11:48 spring-webmvc-5.3.20.jar
> -rw-r--r--  1 root   tomcat  192K Nov  8 11:45 stax2-api-4.2.1.jar
> -rw-r--r--  1 root   tomcat   36K Aug 23 22:24 stax-ex-1.8.jar
> -rw-r--r--  1 root   tomcat  202K Aug 23 22:24 
> taglibs-standard-impl-1.2.5.jar
> -rw-r--r--  1 root   tomcat   40K Aug 23 22:24 
> taglibs-standard-spec-1.2.5.jar
> -rw-r--r--  1 root   tomcat   89K Aug 23 22:24 tagsoup-1.2.1.jar
> -rw-r--r--  1 root   tomcat  647K Nov  8 11:45 tika-core-2.3.0.jar
> -rw-r--r--  1 root   tomcat   59K Nov  8 11:45 
> tika-parser-apple-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   66K Nov  8 11:45 
> tika-parser-audiovideo-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   18K Nov  8 11:45 
> tika-parser-cad-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   29K Nov  8 11:45 
> tika-parser-code-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   20K Nov  8 11:45 
> tika-parser-crypto-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   18K Nov  8 11:45 
> tika-parser-digest-commons-2.3.0.jar
> -rw-r--r--  1 root   tomcat   14K Nov  8 11:45 
> tika-parser-font-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   15K Nov  8 11:45 
> tika-parser-html-commons-2.3.0.jar
> -rw-r--r--  1 root   tomcat   52K Nov  8 11:45 
> tika-parser-html-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   52K Nov  8 11:45 
> tika-parser-image-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat  9.7K Nov  8 11:45 
> tika-parser-mail-commons-2.3.0.jar
> -rw-r--r--  1 root   tomcat   29K Nov  8 11:45 
> tika-parser-mail-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat  650K Nov  8 11:45 
> tika-parser-microsoft-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat  146K Nov  8 11:45 
> tika-parser-miscoffice-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   20K Nov  8 11:45 
> tika-parser-news-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   39K Nov  8 11:45 
> tika-parser-ocr-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   95K Nov  8 11:45 
> tika-parser-pdf-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   26K Nov  8 11:45 
> tika-parser-pkg-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat  1.4M Nov  8 11:45 
> tika-parsers-standard-package-2.3.0.jar
> -rw-r--r--  1 root   tomcat  120K Nov  8 11:45 
> tika-parser-text-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   36K Nov  8 11:45 
> tika-parser-xml-module-2.3.0.jar
> -rw-r--r--  1 root   tomcat   16K Nov  8 11:45 
> tika-parser-xmp-commons-2.3.0.jar
> -rw-r--r--  1 root   tomcat   40K Nov  8 11:45 
> tika-parser-zip-commons-2.3.0.jar
> -rw-r--r--  1 root   tomcat   69K Aug 23 22:24 txw2-2.3.1.jar
> -rw-r--r--  1 root   tomcat   91K Aug 23 22:24 
> validation-api-2.0.1.Final.jar
> -rw-r--r--  1 root   tomcat  519K Nov  8 11:45 velocity-engine-core-2.3.jar
> -rw-r--r--  1 root   tomcat  119K Aug 23 22:24 vorbis-java-core-0.8.jar
> -rw-r--r--  1 root   tomcat   25K Aug 23 22:24 vorbis-java-tika-0.8.jar
> -rw-r--r--  1 root   tomcat  1.6M Nov  8 11:45 woodstox-core-6.2.4.jar
> -rw-r--r--  1 root   tomcat  1.4M Nov  8 11:45 xercesImpl-2.12.2.jar
> -rw-r--r--  1 root   tomcat  216K Aug 23 22:24 xml-apis-1.4.01.jar
> -rw-r--r--  1 root   tomcat  2.1M Nov  8 11:45 xmlbeans-5.0.3

[dspace-tech] Re: How to disable klaro?

[Mohammad S. AlMutairi]

One thing I noticed you should take care of too is If the handle server you 
trying to start is installed on the same server you installed DSpace on you 
need to open port 2641 and port 8000 on the public firewall and on the 
server too if you have a firewall running on your Ubuntu server. ( These 
ports are blocked right now and inaccessible so you have to open them to 
complete your handle server setup).

Good luck 

On Saturday, November 26, 2022 at 4:12:32 AM UTC+3 Mohammad S. AlMutairi 
wrote:

> On Saturday, November 26, 2022 at 2:47:04 AM UTC+3 Night Librarian wrote:
>
>> In terms of Handle server, I wonder whether copy/pasting 
>> [dspace]/handle-server directory's content from someone who has 7.4 on 
>> Ubuntu 20.04 would fix my issue?
>>
> My English is becoming a barrier to read things the right way or convey 
> the ideas in a good way (Sorry about that). Copying the folder from someone 
> else's server won't help or do much but copying your old working 
> handle-server folder from the Windows server to the new Ubuntu server will 
> do so just follow the steps you see in the previous post if you still have 
> access to your old server and can get a copy of the old handle-server 
> folder.
>

-- 
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/6d016d39-20b9-4f64-ab9d-284a44ad9612n%40googlegroups.com.

[dspace-tech] Re: Error in Starting Solr whilw Installting Dspace 7 on Ubuntu 22.04

[Mohammad S. AlMutairi]

Hello Nadeems,

Some tutorials you find on the net are total mess. It will make things more 
complicated instead of making simpler and easier. You need to go back and 
remove Java and Solr and start over by following the steps you see below in 
the sequence you see them.

### Java OpenJDK 11 Installation ###
1) apt install default-jdk -y
2) java -version
3) echo "export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/" >> 
/etc/environment
4) export JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64/
### End of Java OpenJDK 11 installation 
###

### Apache Maven and Ant Installation 
###
1) apt install maven ant ant-optional -y
2) mvn -v
3) ant -version
### End of Apache Maven and Ant installation 


### Solr 8.11.1 Installation ###
1) mkdir /build
2) cd /build
3) apt install lsof -y
4) wget https://downloads.apache.org/lucene/solr/8.11.2/solr-8.11.2.tgz
5) tar xzf solr-8.11.2.tgz solr-8.11.2/bin/install_solr_service.sh 
--strip-components=2
6) bash ./install_solr_service.sh solr-8.11.2.tgz -f
7) cp -r /opt/dspace/solr/* /var/solr/data/ # Do this step after installing 
dspace backend (REST API server). You need to change /opt/dspace to the 
folder you installed dspace backend into.
8) chown -R solr:solr /var/solr/data/
9) systemctl enable solr
10) systemctl restart solr
### End of Solr 8.11.1 installation 
###

Good luck

On Saturday, November 26, 2022 at 9:16:30 AM UTC+3 nadeems...@gmail.com 
wrote:

> Dear All Friends,
> I am installing Dspace 7 on cloud server Ubuntu 22.04. I am facing a 
> problem to starting solr:
> when I run the command : 
> root@repository:~# cd /opt
> root@repository:/opt# su dspace
> $ /opt/solr/bin/solr start
> The currently defined JAVA_HOME (”/usr/lib/jvm/java-11-openjdk-amd64”) 
> refers
> to a location where Java could not be found.  Aborting.
> Either fix the JAVA_HOME variable or remove it from the
> environment so that the system PATH will be searched.
>
> *While I am following the instruction as:*
> Solr Installation
>
> Solr is an open-source search platform, written in Java. Its major 
> features include full-text search, hit highlighting, faceted search, 
> real-time indexing, dynamic clustering, database integration, NoSQL 
> features, and rich document handling.
>
> Download the Solr software package from the website and save it to the opt 
> folder in the operating system. 
>
> Enter into the /opt folder.
>
> *cd /opt*
>
> Download the Solr (version 8) package using the following command line,
>
> *sudo wget 
> https://www.apache.org/dyn/closer.lua/lucene/solr/8.11.1/solr-8.11.1.zip?action=download
>  
> *
>
> Rename the Zip file,
>
> *sudo mv solr-8.11.1.zip\?action\=download solr-8.11.1.zip*
>
> Unzip the package,
>
> *sudo unzip solr-8.11.1.zip*
>
> Rename Solr directory
>
> *sudo mv solr-8.11.1 solr*
>
> Downloaded Solr ZIP files not required, delete it,
>
> *sudo rm solr-8.11.1.zip*
>
> Apply the following command to check Solr directory available at /opt
>
> *ls*
>
> Change the folder permission to Dspace user,
>
> *sudo chown -R dspace:dspace solr*
>
> Check whether the folder permission changed or not.
>
> *ls -la*
>
> Login to the dspace user account to start Solr.
>
> *su dspace*
>
> Start Solr by applying the command,
>
> */opt/solr/bin/solr start*
> Please may anyone guide me how to reslove this error?
>
> With kindest regards,
> 
> *Nadeem Sohail*
> Head
> Learning Resource Center (LRC)
> University of Management , Sialkot Campus
> Site: http://www.skt.umt.edu.pk/lrc/Home.aspx
> Email: nadeem...@skt.umt.edu.pk
> Office Ph: +92 523575234-6 Ext. 118
>
>
>
>

-- 
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/4bf50ec2-ce66-459e-acaf-52968b0d60dfn%40googlegroups.com.

[dspace-tech] Re: How to disable klaro?

[Mohammad S. AlMutairi]

On Saturday, November 26, 2022 at 2:47:04 AM UTC+3 Night Librarian wrote:

> In terms of Handle server, I wonder whether copy/pasting 
> [dspace]/handle-server directory's content from someone who has 7.4 on 
> Ubuntu 20.04 would fix my issue?
>
My English is becoming a barrier to read things the right way or convey the 
ideas in a good way (Sorry about that). Copying the folder from someone 
else's server won't help or do much but copying your old working 
handle-server folder from the Windows server to the new Ubuntu server will 
do so just follow the steps you see in the previous post if you still have 
access to your old server and can get a copy of the old handle-server 
folder.

-- 
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/9e7a330c-2fc7-4180-b9e5-152a485727c2n%40googlegroups.com.

[dspace-tech] Re: How to disable klaro?

[Mohammad S. AlMutairi]

On Saturday, November 26, 2022 at 2:47:04 AM UTC+3 Night Librarian wrote:

> Thank you for the suggestion.  I changed the dc.identifier.uri from 
> https://hdl.handle.net/your-handle-prefix/1916 by 
> https://my-server-domain-name/handle/my-handle-prefix/1916. Now, if I try 
> to open 
> https://my-server-domain-name/handle/my-handle-prefix/1916 in the 
> browser, I get 404 page not found.  If I search for the item's title in all 
> of DSpace, and then try to download the pdf from there, I still can see the 
> pdf in the browser, but downloading it still doesn't work.
>
 For this debugging session try to comment out *handle.canonical.prefix = 
https://hdl.handle.net/* in dspace.cfg and restart tomcat and see if that's 
help.

 

> In terms of Handle server, I wonder whether copy/pasting 
> [dspace]/handle-server directory's content from someone who has 7.4 on 
> Ubuntu 20.04 would fix my issue?
>
That's actually how I moved the handle server from the old server to the 
newer one not long ago and it worked. It will save you sending a newer 
generated sitebndl.zip to the HNR folks.

1) Copy the old [dspace]/handle-server folder from the old Windows server 
to the newer ubuntu server.
2) chown -R tomcat-user:tomcat-user [dspace]/handle-server
3) Check and change the private IP to the new private IP if it was changed 
in [dspace]/handle-server/config.dct
3) Check and change the public IP and the Private IP to match the new ones 
in [dspace]/handle-server/local_addresses
4) run [dspace]/bin/make-handle-config
5) start the handle server
6) check the handle server logs or run this command to see if it's running 
using ( ss -nlp | grep ":8000\|:2641" )

Hope it help

On Friday, November 25, 2022 at 4:53:06 p.m. UTC-4 alo...@gmail.com wrote:
>
>> You should completely ignore that suggestion and here is why (  
>> https://github.com/kiprotect/klaro ). I think the issue you have is 
>> caused by how the migration from the Windows server to the Linux was done 
>> and is related to the handle server specifically because it's down. As a 
>> suggestion try to change one of the the items 
>> (e56a5422-b32b-4000-95dd-86467ef21c35) dc.​identifier.​uri from 
>> https://hdl.handle.net/your-handle-prefix/1916 to 
>> https://your-server-domain-name/handle/your-handle-prefix/1916 and try 
>> to access it and download it and see if that helps isolate the handle 
>> server is the cause.
>>
>> Hope It help.
>>
>> On Friday, November 25, 2022 at 10:20:58 PM UTC+3 Night Librarian wrote:
>>
>>> I had a suggestion to disable klaro to solve a downloading problem on my 
>>> DSpace 7.4, but I am not sure how to do that.  Can someone give me a hint?
>>
>>

-- 
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/e3e1c136-c70b-4176-a50b-65430b8ade99n%40googlegroups.com.

[dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

[Mohammad S. AlMutairi]

Hello Alex,

Glad you had it worked & You welcome. You might need to use a reverse proxy 
in your environment instead. That's what DSpace documentation recommends 
and that's how most of the people using DSpace 7 are setting it up.

On Friday, November 25, 2022 at 4:04:58 PM UTC+3 aperez...@gmail.com wrote:

> Hello friends, I followed the steps you indicate me I reinstalled the 
> frontend and the video gave me an idea of what to do and work correctly 
> thank you very much for the help.
>
> Regards
>
>
> El martes, 22 de noviembre de 2022 a las 17:03:18 UTC-6, alo...@gmail.com 
> escribió:
>
>> I had to try it on DSpace version 7.5-SNAPSHOT and it's working just fine 
>> without any SSL configuration (HTTP Setup) so it's not hard coded as I 
>> thought. See the attached video as a confirmation. Try to pull a fresh copy 
>> of dspace-angular and start a front end fresh installation.
>>
>> Settings in dspace.cfg
>> dspace.server.url = http:// 192.168.100.212:8080/server
>> dspace.ui.url = http://192.168.100.212:4000
>>
>> Settings in config.prod.yml:
>> ui:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 4000
>>   nameSpace: /
>>
>> rest:
>>   ssl: false
>>   host: 192.168.100.212
>>   port: 8080
>>   nameSpace: /server
>>
>>

-- 
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/fc740f3c-622e-4ad1-9ed5-247dad8b5caen%40googlegroups.com.

[dspace-tech] Re: How to disable klaro?

[Mohammad S. AlMutairi]

You should completely ignore that suggestion and here is why (  
https://github.com/kiprotect/klaro ). I think the issue you have is caused 
by how the migration from the Windows server to the Linux was done and is 
related to the handle server specifically because it's down. As a 
suggestion try to change one of the the items 
(e56a5422-b32b-4000-95dd-86467ef21c35) dc.​identifier.​uri 
from https://hdl.handle.net/your-handle-prefix/1916 
to https://your-server-domain-name/handle/your-handle-prefix/1916 and try 
to access it and download it and see if that helps isolate the handle 
server is the cause.

Hope It help.

On Friday, November 25, 2022 at 10:20:58 PM UTC+3 Night Librarian wrote:

> I had a suggestion to disable klaro to solve a downloading problem on my 
> DSpace 7.4, but I am not sure how to do that.  Can someone give me a hint?

-- 
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/619279c9-fdc2-4922-a1f2-797041a3b17an%40googlegroups.com.

[dspace-tech] Re: Can view PDFs in browser (DSpace 7.4), but can't download

[Mohammad S. AlMutairi]

klaro is a suspect. Disable it and check.

On Wednesday, November 23, 2022 at 7:12:35 AM UTC+3 Night Librarian wrote:

> Turns out, the problem is not limited to pdf.  All accdb, docx, mp3, pptx, 
> xlsx files also fail to download.  Their download completion goes to near 
> 100%, after which I get an error.  So, none of our items is downloadable!
>
> At the same time, css, html and xml files (we had a couple of these in one 
> submission) download w/o problems.
>
> On Tuesday, November 22, 2022 at 11:36:59 p.m. UTC-4 Night Librarian wrote:
>
>> Thank you for the suggestion.  I tried downloading the file in Edge, 
>> Chrome and Firefox on a Windows PC from home (via VPN) and on the Ubuntu 
>> machine itself that runs DSpace.  I did it before and after logging as 
>> admin.  I tried inPrivate/Incognito mode. In all cases, the pdf opens in 
>> the browser and I can read it in its entirety, but when I click "Download", 
>> it goes to 773 kb out of 776, and then I get a finelename.pdf.crdownload 
>> file downloaded and a message that the browser couldn't download the file.
>>
>> When I try in Safari and Chrome on iPhone, after viewing the PDF, when I 
>> click on download, I see "err_connection_closed", but that probably doesn't 
>> explain why it wouldn't download even on the server itself.  dspace.log has 
>> many lines, including these:
>>
>> INFO  3834015a-5783-403d-ba1b-085b68787b0e 
>> 64a217ee-6830-48b5-8558-d6140a123bc9 
>> org.dspace.usage.LoggerUsageEventListener @ 
>> ad...@mydomain.com::view_item:handle=12345/1916
>>
>> INFO  unknown 778fd02b-07ff-4e37-a846-561a88054545 
>> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
>> [GET /server/opensearch/search/search] originated from unknown
>>
>> INFO  08de3499-a27b-474b-aa4c-07fbf0f066cf 
>> 5d55a1b2-1984-4213-a061-39e7a6e4cff2 
>> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
>> [GET /server/api/system/scripts/metadata-import] originated from /
>>
>> WARN  08de3499-a27b-474b-aa4c-07fbf0f066cf 
>> 5d55a1b2-1984-4213-a061-39e7a6e4cff2 
>> org.dspace.app.rest.exception.DSpaceApiExceptionControllerAdvice @ 
>> Authentication is required (status:401 exception: Access is denied at: 
>> org.springframework.security.access.vote.AffirmativeBased.decide(AffirmativeBased.java:73))
>>
>> INFO  08de3499-a27b-474b-aa4c-07fbf0f066cf 
>> a300fb4f-141b-42b9-a403-1352ba5844a1 
>> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
>> [GET /server/api/core/items/6a40502a-a91b-4154-8f5f-19fd4ed69288] 
>> originated from /
>>
>> INFO  08de3499-a27b-474b-aa4c-07fbf0f066cf 
>> 98bdb7b6-51ff-4b43-91dc-d36d1a40d668 
>> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
>> [GET /server/api/authz/authorizations/search/object] originated from 
>> /items/6a40502a-a91b-4154-8f5f-19fd4ed69288/full
>>
>> WARN  unknown unknown org.dspace.app.rest.security.jwt.JWTTokenHandler @ 
>> XXX.XXX.XXX.XXX tried to use an expired or non-valid token
>>
>> INFO  unknown 21ea0a82-e9a2-4235-89a9-2043f6411e07 
>> org.dspace.app.rest.utils.DSpaceAPIRequestLoggingFilter @ Before request 
>> [GET 
>> /server/api/core/bitstreams/137aabe1-6fb9-49d9-8fe6-e3ff81332964/content] 
>> originated from 
>> https://mydomain.com/server/api/core/bitstreams/137aabe1-6fb9-49d9-8fe6-e3ff81332964/content?authentication-token=eyJhbGciOiJIUzI1NiJ9.eyJlaWQiOiJiZWMwYWNmMS04NDFjLTRiNmQtYmM5Yi02OTQ0OWU2OWRjMWIiLCJzZyI6W10sImF1dGhlbnRpY2F0aW9uTWV0aG9kIjoicGFzc3dvcmQiLCJleHAiOjE2NjkxNzA2NDB9.0jKqlv027PbO4QTgGWx06swXby_oKee-qsIRsUmlPRM
>>
>>
>> Finally, browser's console shows these 2 lines:
>>
>> The response for '
>> https://mydomain.com/server/api/discover/search?configuration=default' 
>> has the self link 'https://ec.msvu.ca/server/api/discover/search'. These 
>> don't match. This could mean there's an issue with the REST endpoint 
>> main.3bafce0befaeaf6e.js:1:181849
>>
>> The response for '
>> https://mydomain.com/server/api/core/items/e56a5422-b32b-4000-95dd-86467ef21c35/bundles?size='
>>  
>> has the self link '
>> https://ec.msvu.ca/server/api/core/items/e56a5422-b32b-4000-…es?embed=primaryBitstream=bitstreams/format=1000'.
>>  
>> These don't match. This could mean there's an issue with the REST endpoint 
>> main.3bafce0befaeaf6e.js:1:181849
>>
>> Can any of this be relevant?
>> On Tuesday, November 22, 2022 at 3:57:25 p.m. UTC-4 alo...@gmail.com 
>> wrote:
>>
>>> Seems like it is either a browser or a connection issue. Try another 
>>> browser or go into Incognito/InPrivate/Private mode and try it.
>>>
>>> On Tuesday, November 22, 2022 at 10:13:28 PM UTC+3 Night Librarian wrote:
>>>
 I have 7.4 on Ubuntu 20.04, with Tomcat 9. I can view pdfs in the 
 browser but downloading doesn't work and I end up with 
 finelename.pdf.crdownload files.  I don't see errors in dspace.log, only 
 [info] and [warn] entries.

 Where should I look first to fix it?

>>>

-- 
All messages to this mailing 

[dspace-tech] Re: change localhost to the server ip when listening DSpace 7.4 !

[Mohammad S. AlMutairi]

Hello

I think it got hard coded to use localhost in recent versions so just leave 
it running on the loopback adapter and use a reverse proxy to talk to it. 
Use the steps you see in the attached file as hints and make sure tomcat is 
set to run on port 8080.

Good luck

On Tuesday, November 22, 2022 at 7:46:14 PM UTC+3 aperez...@gmail.com wrote:

> Hello everyone, I ask for your help with the following case that I find 
> myself in. I already have a version of DSpace 7.2.1 with Ubuntu Server 
> 20.04 LTS, it was already implemented in July 2022 and it works correctly, 
> it already has https through port 8443 and everything is fine with this 
> server, but it happens that we have decided to update to version DSpace 7.4 
> with Ubuntu Server 22.04 LTS already has many improvements according to the 
> documentation https://wiki.lyrasis.org everything was going well with the 
> installation and configuration until I get to the part where it should see 
> the published port 4000 to connect to the external as this should work like 
> this for a published government institution.
>
> But in this installation, port 4000 is only listening on the (127.0.0.1) 
> localhost and I can have it, but only locally, as seen in the photo that I 
> attached.
>
>
> [image: DSpace.PNG]
>
> [image: Listen localhost.PNG][image: Listen IP address.PNG]
>
> My question would be how do I change that the listener is the IP address 
> of the server, in this case 192.168.100.118 and not the localhost.
>
> After several attempts I have not been able to change it and make it 
> listen:
>
> 192.168.100.118:4000 instead of 127.0.0.1:4000 as it currently is.
>
> I already changed the parameters of my files local.cfg, config.prod.yml, 
> allow cors, etc/hosts etc
>
>
>
> Thank you very much in advance for any help you can give me.
>
>
>
>

-- 
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/57e08056-671f-445f-9b86-49b61236cf01n%40googlegroups.com.
1) Settings in dspace.cfg or local.cfg:
dspace.server.url = https://dspace.example.org/server
dspace.ui.url = https://dspace.example.org
solr.server = http://localhost:8983/solr

2) Settings in config.prod.yml:
ui:
  ssl: false  
  host: localhost
  port: 4000
  nameSpace: /

rest:
  ssl: true
  host: dspace.example.org
  port: 443
  nameSpace: /server

3) a2enmod proxy_http proxy_html ssl headers
4) a2dissite 000-default default-ssl
5) vi /etc/apache2/sites-available/dspace.conf

 ServerName dspace.example.org
 Redirect / https://dspace.example.org



 ServerName dspace.example.org
 LogLevel warn
 ErrorLog ${APACHE_LOG_DIR}/dspace.example.org.error.log
 CustomLog ${APACHE_LOG_DIR}/dspace.example.org.access.log combined
 ProxyRequests on
 SSLEngine on
 SSLProxyEngine on
 SSLCertificateFile /etc/letsencrypt/live/dspace.example.org/fullchain.pem
 SSLCertificateKeyFile /etc/letsencrypt/live/dspace.example.org/privkey.pem
 SSLCompression off
 SSLProtocol all -SSLv3 -TLSv1 -TLSv1.1
 SSLCipherSuite  
ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384
 SSLHonorCipherOrder off
 SSLSessionTickets   off
 ProxyPreserveHost on
 RequestHeader set X-Forwarded-Proto https

   
   AddDefaultCharset Off
   Require all granted
   

 ProxyPass /server http://localhost:8080/server
 ProxyPassReverse /server http://localhost:8080/server
 ProxyPass / http://localhost:4000/
 ProxyPassReverse / http://localhost:4000/



6) a2ensite dspace.conf
7) ufw allow 'OpenSSH'
8) ufw allow 'Apache Full'
9) ufw enable
10) ufw status
11) systemctl restart apache2

[dspace-tech] Re: disable self-registration on DSpace 7

[Mohammad S. AlMutairi]

Hi Jashua,

It's a known bug but you can try 
this https://github.com/DSpace/DSpace/issues/8499 until it get officially 
fixed.

On Tuesday, November 22, 2022 at 7:40:36 PM UTC+3 jos...@udel.edu wrote:

> Hi,
>
> In DSpace 7, self-registration (password authentication) is enabled by 
> default. Is there a way to disable the self-registration on DSpace 7?
>
> 
> Joshua Kim
> Web Developer, Library IT
> Library, Museums and Press
> University of Delaware
>
>

-- 
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/f1832a44-5cc2-436d-9f42-2ab46606f87an%40googlegroups.com.