date:20230110

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

2023-01-10 Thread Rupinder Singh

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

[dspace-tech] OR2023 Call for Proposals extension - until 22nd January

2023-01-10 Thread Maureen P. Walsh

The Call for Proposals deadline has been extended by one week, until
January 22nd.

The 18th International Conference on Open Repositories (OR2023) will be
held from 12-15 June 2023 at the Lord Charles Hotel
, in Stellenbosch, South Africa. We are
pleased to invite you to contribute to the program.

The conference theme is Repositories unlocked for discovery and
interoperability

OR2023 will provide an opportunity to explore and reflect on the ways
repositories enable discoverability and interoperability of information and
data within the structured web of data. How can we better utilise
repositories for machine interoperability? How can we develop the capacity
of institutions to implement sustainable open repositories to improve data
equity worldwide?

We particularly welcome proposals on the overall “Repositories unlocked for
discovery and interoperability” theme, but also on other administrative,
organisational, or practical topics related to digital repositories. We are
interested in the following sub-themes:


   1.

Unbiased discovery of knowledge: Open repositories facilitating the
   unbiased discovery of indigenous knowledge.
   2.

   Sustainable development: Linking open repositories content to the UNESCO
   Sustainable Development Goals (SDGs).
   3.

   Linked data: Integration with other open knowledge resources (e.g.
   Wikimedia and Wikidata).
   4.

   Trust in the machine: Integrating repository content with the semantic
   web of data using the Resource Description Framework (RDF) knowledge
   representation language.
   5.

   Knowledge Organization Systems (KOS): Taxonomies and ontologies in open
   repositories to enhance the discoverability of data.
   6.

   Integrating content: Novel or complex formats, data types and sources.
   7.

   Repositioning repositories: Next gen repositories, the Pubfair framework
   and new models.


Please visit the Call for Proposals
 page to
learn more about the sub-themes and submission categories of the
conference, including a full list of submission templates and key dates for
submission deadlines and approvals.



The deadline for submissions is January 22, 2023.



We look forward to the vibrant conversations and learning opportunities of
the conference.

Submitters should note that presentations are in person and there is no
remote/pre-recorded presentation option.



Please see the registration fees on the Registration page
 (registration will open
in March 2023).



Programme Co-Chairs:



   -

   Ilkay Holt, the British Library
   -

   Mimi Seyffert-Wirth, Stellenbosch University
   -

   Wouter Klapwijk, Stellenbosch University


Contact: or23-program-cha...@googlegroups.com



For the Open Repositories Steering Committee:

Claire Knowles  and Torsten Reimer




Website and Social Media

Website: https://or2023.openrepositories.org

Twitter: https://twitter.com/OpenRepos

Hashtag: #openrepos2023

Facebook: https://www.facebook.com/ORConference

-- 
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/CAKj8zsV%3DAZhhW6jiEuvrLPynqfzaKjcVufSf7HwQMPRWJmLsjg%40mail.gmail.com.

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

2023-01-10 Thread 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

2023-01-10 Thread 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 security matters

2023-01-10 Thread 'Tim Donohue' via DSpace Technical Support

Hi,

Since you are on DSpace 6.3, I'd recommend minimally upgrading to DSpace 
6.4 as it includes a large number of security fixes to the 6.x platform.  
See the release notes at 
https://wiki.lyrasis.org/display/DSDOC6x/Release+Notes#ReleaseNotes-6.4ReleaseNotes

That said, it's worth being aware that 6.x is nearly "end of life".  
Announcements went across these mailing lists last year.  Here's the end of 
life 
information: 
https://wiki.lyrasis.org/display/DSPACE/Support+for+DSpace+5+and+6+is+ending+in+2023

The latest version of DSpace is 7.4 (and 7.5 is coming soon in February).  
It is the most secure of our releases.So, you may wish to consider an 
upgrade at some point (this is a major upgrade as there is a brand new User 
Interface, etc).  See release notes 
at https://wiki.lyrasis.org/display/DSDOC7x/Release+Notes

If you have additional questions, let us know on this list.  If you wish to 
report security issues, see our Software support policy for how to do 
so: https://wiki.lyrasis.org/display/DSPACE/DSpace+Software+Support+Policy

Thanks,

Tim Donohue

On Monday, January 9, 2023 at 6:35:12 PM UTC-6 noorhaf...@iium.edu.my wrote:

> In addition. we are running Dspace on Ubuntu 18.04.2 LTS
>
>
>
> On Tuesday, January 10, 2023 at 8:30:43 AM UTC+8 Noorhafizah Mohd Akil 
> wrote:
>
>> Hello, 
>> Dear all.
>>
>> I have a security concern with DSpace. Our web server was the victim of a 
>> web shell assault that provided backdoor access to the web server 
>> directory. We are still in the inquiry phase right now.
>>
>> Our system currently utilizes Dspace 6.3, and the most recent version I 
>> could find was 7.4.
>>
>> Does version 6.3 require any patches throughout the upgrade of the 
>> version.
>>
>> 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/83fb6838-37b5-43a9-87e0-2d8adc7cb89en%40googlegroups.com.

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

2023-01-10 Thread 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
 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:

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

2023-01-10 Thread 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: Dspace Data Migration with SAF

2023-01-10 Thread Rupinder Singh

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/3a82b943-61c1-4312-ae0c-a2d3074e1c87n%40googlegroups.com.

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

2023-01-10 Thread 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: Deploy Dspace 7.4 with Add HTTPS support

2023-01-10 Thread Мухаметали Кусайынов

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 start (code=exited, 
>> status=0/SUCCESS)
>>Main PID: 1081 (apache2)
>>   Tasks: 55 (limit: 9442)
>>  Memory: 11.1M
>>  CGroup: /system.slice/apache2.service
>>  ├─1081 /usr/sbin/apache2 -k start
>>  ├─1082 /usr/sbin/apache2 -k start
>>  └─1083 /usr/sbin/apache2 -k start
>>
>> Jan 10 09:58:54 dspace7 systemd[1]: Starting The Apache HTTP Server...
>> Jan 10 09:58:56 dspace7 apachectl[1010]: AH00558: apache2: Could not 
>> reliably determine the server's fully qualified domain name, using 
>> 127.0.1.1. Set the 'ServerNam>
>> Jan 10 09:58:56 dspace7 systemd[1]: Started The Apache HTTP Server.
>>
>> I also opened port 443:
>>
>> *sudo ufw enable*
>> *sudo ufw allow ssh*
>> *sudo ufw allow 443*
>> As a result it shows:
>> Status: active
>>
>> To Action  From
>> -- --  
>> 22/tcp ALLOW   Anywhere
>> 443ALLOW   Anywhere
>>

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

2023-01-10 Thread Мухаметали Кусайынов

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 start (code=exited, 
> status=0/SUCCESS)
>Main PID: 1081 (apache2)
>   Tasks: 55 (limit: 9442)
>  Memory: 11.1M
>  CGroup: /system.slice/apache2.service
>  ├─1081 /usr/sbin/apache2 -k start
>  ├─1082 /usr/sbin/apache2 -k start
>  └─1083 /usr/sbin/apache2 -k start
>
> Jan 10 09:58:54 dspace7 systemd[1]: Starting The Apache HTTP Server...
> Jan 10 09:58:56 dspace7 apachectl[1010]: AH00558: apache2: Could not 
> reliably determine the server's fully qualified domain name, using 
> 127.0.1.1. Set the 'ServerNam>
> Jan 10 09:58:56 dspace7 systemd[1]: Started The Apache HTTP Server.
>
> I also opened port 443:
>
> *sudo ufw enable*
> *sudo ufw allow ssh*
> *sudo ufw allow 443*
> As a result it shows:
> Status: active
>
> To Action  From
> -- --  
> 22/tcp ALLOW   Anywhere
> 443ALLOW   Anywhere
> Apache FullALLOW   Anywhere
> 22/tcp (v6)ALLOW   Anywhere (v6)
> 443 (v6)   ALLOW   Anywhere (v6)
> Apache Full (v6)   ALLOW   Anywhere (v6)
>
> After this setup, when I again type localhost:4000 again in

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

2023-01-10 Thread Мухаметали Кусайынов

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:
  





**
   




* *

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 start (code=exited, 
status=0/SUCCESS)
   Main PID: 1081 (apache2)
  Tasks: 55 (limit: 9442)
 Memory: 11.1M
 CGroup: /system.slice/apache2.service
 ├─1081 /usr/sbin/apache2 -k start
 ├─1082 /usr/sbin/apache2 -k start
 └─1083 /usr/sbin/apache2 -k start

Jan 10 09:58:54 dspace7 systemd[1]: Starting The Apache HTTP Server...
Jan 10 09:58:56 dspace7 apachectl[1010]: AH00558: apache2: Could not 
reliably determine the server's fully qualified domain name, using 
127.0.1.1. Set the 'ServerNam>
Jan 10 09:58:56 dspace7 systemd[1]: Started The Apache HTTP Server.

I also opened port 443:

*sudo ufw enable*
*sudo ufw allow ssh*
*sudo ufw allow 443*
As a result it shows:
Status: active

To Action  From
-- --  
22/tcp ALLOW   Anywhere
443ALLOW   Anywhere
Apache FullALLOW   Anywhere
22/tcp (v6)ALLOW   Anywhere (v6)
443 (v6)   ALLOW   Anywhere (v6)
Apache Full (v6)   ALLOW   Anywhere (v6)

After this setup, when I again type localhost:4000 again in browsh, my site 
stops working and throws the following error:

*500*
*Service Unavailable*
*The server is temporarily unable to service your request due to 
maintenanse downtime or capasity problems. Please try again later.*


I deployed the repository for the first time and I can't fully understand 
what I'm doing wrong. I've been trying to do this for two months and 
already despaired. Can you describe step by step how to properly deploy 
Dspace 7.4? Please. Sincerely, Kusainov M.


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

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

[dspace-tech] OR2023 Call for Proposals extension - until 22nd January

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

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

[dspace-tech] Re: Dspace security matters

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

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

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

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

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

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

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

12 matches

Site Navigation

Mail list logo

Footer information