[dspace-tech] I can't upload files in dspace 7.2. Upload failed.

[Evaristo Canul López]

Migrate from dspace 6.x to 7.2

I can see everything that existed before, even download the pdfs that 
existed.

But when I want to add a new article, it gives me an error when trying to 
upload a file: "upload failed"

Does anyone know where I can check what is the error that is generated when 
trying to upload a file? In /dspace/log/dspace.log nothing appears.

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/cf9b3d84-8546-4026-a82b-b75d9dcdb144n%40googlegroups.com.

[dspace-tech] Re: DSpace 7 database migration.

['Tim Donohue' via DSpace Technical Support]

Hi Juan,

As it sounds like you discovered, that migration is NOT one that comes with 
DSpace "out of the box".  It looks like you added something custom at one 
point, and now Flyway (which DSpace uses to manage these migrations) is 
trying to find the old migration script and cannot find it.   There's a few 
possible options here..

1. You could find that old migration script and put it somewhere where 
Flyway is looking for it...mainly under 
dspace-api/src/main/resources/org/dspace/storage/rdbms/sqlmigration/postgres/  
 This will stop Flyway from complaining

2. You could try running a Flyway "repair" on the database. I think this 
will mark "missing" migrations as deleted.  Run "./dspace database repair"

3. If neither of those work you could manually modify the "schema_version" 
table in your database to remove that row.  This is the database table 
where Flyway manages all the migrations, so removing it from the table will 
make Flyway "forget" about it.   However, be VERY careful to only remove 
that row... You may want to backup before touching this table, as there's 
no easy way to revert a mistake if you remove too much.

(As a sidenote, if you know what this old migration modified in your DSpace 
database, you might want to also "undo" those changes if possible.  There's 
always a chance that custom changes to your database could impact future 
DSpace upgrades.  So,  I generally recommend to never customize your DSpace 
database unless you know what you are doing...as there's always a chance 
that even small customizations can result in database migration errors in 
the future.)

Good luck,

Tim

On Wednesday, March 30, 2022 at 2:49:00 PM UTC-5 juanlop...@gmail.com wrote:

> Forgot to mention!
>
> When I try to run a  bin/dspace database migrate to  fix the "pending" 
> migration steps, I get a similar error:
>
> bin/dspace database migrate
>
> Database URL: jdbc:postgresql://localhost:5432/prodDB
> Migrating database to latest version... (Check dspace logs for details)
> Migration exception:
>
> java.sql.SQLException: Flyway migration error occurred
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:775)
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:662)
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:637)
> at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:233)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
> Method)
> at 
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:566)
> 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: org.flywaydb.core.api.FlywayException: Validate failed: 
> Detected applied migration not resolved locally: 6.0.2017.05.15
>
> at org.flywaydb.core.Flyway.doValidate(Flyway.java:292)
> at org.flywaydb.core.Flyway.access$100(Flyway.java:73)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:166)
> at org.flywaydb.core.Flyway$1.execute(Flyway.java:158)
> at org.flywaydb.core.Flyway.execute(Flyway.java:527)
> at org.flywaydb.core.Flyway.migrate(Flyway.java:158)
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:762)
> ... 10 more
>
> El miércoles, 30 de marzo de 2022 a las 14:34:52 UTC-5, Juan López 
> escribió:
>
>> Hi!
>>
>> I've set a test environment for dspace 7 and ran a successfull migration 
>> from 6.3 to 7.0, however, now that I'm upgrading from 7 to 7.2 I've noticed 
>> that some error are thrown when I execute an "index-discover -b".
>>
>> Here's the error:
>>
>> 2022-03-30 14:26:35,118 INFO  unknown unknown 
>> org.dspace.discovery.indexobject.ItemIndexFactoryImpl @ Wrote Item: 
>> c3ec783f-517d-456b-b90b-50303f4e1bf2 to Index
>> 2022-03-30 14:26:35,126 INFO  unknown unknown 
>> org.dspace.discovery.SolrServiceImpl @ 
>> anonymous::indexed_object:Item-c3ec783f-517d-456b-b90b-50303f4e1bf2
>> 2022-03-30 14:26:35,128 INFO  unknown unknown 
>> org.dspace.storage.rdbms.DatabaseUtils @ Loading Flyway DB migrations from: 
>> classpath:org/dspace/storage/rdbms/sqlmigration/postgres, 
>> classpath:org/dspace/storage/rdbms/migration, 
>> classpath:org/dspace/storage/rdbms/xmlworkflow
>> 2022-03-30 14:26:35,131 INFO  unknown unknown 
>> org.flywaydb.core.internal.database.DatabaseFactory @ Database: 
>> jdbc:postgresql://localhost:5432/prodDB (PostgreSQL 13.2)
>> 2022-03-30 14:26:35,132 WARN  unknown unknown 
>> org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
>> recommended: Postg

[dspace-tech] Re: Return bitstreams in dspace 7.1 search

['Tim Donohue' via DSpace Technical Support]

Hi,

DSpace can search within files which support full-text indexing (e.g. PDFs, 
Word documents, etc), provided that you occasionally run the "filter-media" 
script (usually you add this to a cronjob or similar, as it is what 
generates thumbnail images & extracts text from files for search 
indexing).  See 
https://wiki.lyrasis.org/display/DSDOC7x/Mediafilters+for+Transforming+DSpace+Content#MediafiltersforTransformingDSpaceContent-Executing(viaCommandLine)

However, even when a search matches the contents of a file, the *Item* 
which includes that file is returned in the search results.  Currently, 
there's no way in DSpace to return the file (or bitstream) in a search 
results list. 

Tim

On Wednesday, March 30, 2022 at 12:23:01 PM UTC-5 fatima...@gmail.com wrote:

> Hello, I wonder if it is possible that the searches return a file. As far 
> as I know, the searches return communities, collections and items having to 
> have a handle, but I am interested in knowing if it is possible for dspace 
> to return a particular file. For example search by filename, and return the 
> file, not the item that contains that file.
> 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/02bb536c-68dc-4d91-b799-c67bd3786cc6n%40googlegroups.com.

[dspace-tech] Re: Connect Configurable Entities

['Tim Donohue' via DSpace Technical Support]

Hi Tianyi,

When you import the defined Entity model (as described in the linked docs 
below), it should automatically create the Entities along with the 
relationship between the entities (which is defined in the 
relationship-types.xml).  See the "Import entity model" step of the 
Entities Documentation:
https://wiki.lyrasis.org/display/DSDOC7x/Configurable+Entities#ConfigurableEntities-2.Importentitymodelintothedatabase

If this isn't working for you, we may need more information, as the Person 
(author) entity and Publication entity should be related automatically as 
soon as you import the default entity model provided with DSpace 7.

Tim

On Tuesday, March 29, 2022 at 3:10:22 PM UTC-5 gutia...@gmail.com wrote:

> Hello colleagues,
>
> After I initialize out of box entities, I got additional three tables: 
> Relationship, relationship_type and entity_type;
>
> I'd like to make an author connecting with two publications. However, 
> "relationship" table is empty. 
>
> How could I configure two entities reference each other?
>
> Thank you,
> Tianyi
>

-- 
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/1dac16d0-7bc0-4e9e-a703-ee595230306an%40googlegroups.com.

[dspace-tech] Re: FAIL - Application at context path [/server] could not be started

['Tim Donohue' via DSpace Technical Support]

Hi,

You'd need to check the DSpace and Tomcat logs for information about the 
error.  The message you shared just shows that it failed to start, but it 
doesn't tell us "why".  The "why" part is usually in the logs.  Here's our 
troubleshooting guide for information on finding errors in logs (and 
elsewhere): 
https://wiki.lyrasis.org/display/DSPACE/Troubleshoot+an+error#Troubleshootanerror-DSpace7.x(orabove)

Tim

On Monday, March 28, 2022 at 2:57:45 PM UTC-5 Night Librarian wrote:

> I am trying to install DSpace 7.2 on Ubuntu 20.04.3 LTS.  According to the 
> instructions in step 11 here: Installing DSpace - DSpace 7.x 
> Documentation - LYRASIS Wiki 
> , I copied 
> the "server" webapp from /dspace/webapps to /var/lib/tomcat9/webapps.  Now, 
> "server" is showing in Tomcat Web Application Manager, but when I click on 
> start next to it, the Manager says:
>
> FAIL - Application at context path [/server] could not be started 
>
> FAIL - Encountered exception [org.apache.catalina.LifecycleException: 
> Failed to start component 
> [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/server]]]  
>
>
> What could be the problem here?
>

-- 
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/85bda887-d097-4917-a656-0d1d63f1702an%40googlegroups.com.

[dspace-tech] Re: DSpace 7 database migration.

[Juan López]

Forgot to mention!

When I try to run a  bin/dspace database migrate to  fix the "pending" 
migration steps, I get a similar error:

bin/dspace database migrate

Database URL: jdbc:postgresql://localhost:5432/prodDB
Migrating database to latest version... (Check dspace logs for details)
Migration exception:
java.sql.SQLException: Flyway migration error occurred
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:775)
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:662)
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:637)
at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:233)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native 
Method)
at 
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at 
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:566)
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: org.flywaydb.core.api.FlywayException: Validate failed: 
Detected applied migration not resolved locally: 6.0.2017.05.15

at org.flywaydb.core.Flyway.doValidate(Flyway.java:292)
at org.flywaydb.core.Flyway.access$100(Flyway.java:73)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:166)
at org.flywaydb.core.Flyway$1.execute(Flyway.java:158)
at org.flywaydb.core.Flyway.execute(Flyway.java:527)
at org.flywaydb.core.Flyway.migrate(Flyway.java:158)
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:762)
... 10 more

El miércoles, 30 de marzo de 2022 a las 14:34:52 UTC-5, Juan López escribió:

> Hi!
>
> I've set a test environment for dspace 7 and ran a successfull migration 
> from 6.3 to 7.0, however, now that I'm upgrading from 7 to 7.2 I've noticed 
> that some error are thrown when I execute an "index-discover -b".
>
> Here's the error:
>
> 2022-03-30 14:26:35,118 INFO  unknown unknown 
> org.dspace.discovery.indexobject.ItemIndexFactoryImpl @ Wrote Item: 
> c3ec783f-517d-456b-b90b-50303f4e1bf2 to Index
> 2022-03-30 14:26:35,126 INFO  unknown unknown 
> org.dspace.discovery.SolrServiceImpl @ 
> anonymous::indexed_object:Item-c3ec783f-517d-456b-b90b-50303f4e1bf2
> 2022-03-30 14:26:35,128 INFO  unknown unknown 
> org.dspace.storage.rdbms.DatabaseUtils @ Loading Flyway DB migrations from: 
> classpath:org/dspace/storage/rdbms/sqlmigration/postgres, 
> classpath:org/dspace/storage/rdbms/migration, 
> classpath:org/dspace/storage/rdbms/xmlworkflow
> 2022-03-30 14:26:35,131 INFO  unknown unknown 
> org.flywaydb.core.internal.database.DatabaseFactory @ Database: 
> jdbc:postgresql://localhost:5432/prodDB (PostgreSQL 13.2)
> 2022-03-30 14:26:35,132 WARN  unknown unknown 
> org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
> recommended: PostgreSQL 13.2 is newer than this version of Flyway and 
> support has not been tested. The latest supported version of PostgreSQL is 
> 12.
> 2022-03-30 14:26:35,140 WARN  unknown unknown 
> org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
> recommended: PostgreSQL 13.2 is newer than this version of Flyway and 
> support has not been tested. The latest supported version of PostgreSQL is 
> 12.
> 2022-03-30 14:26:35,148 INFO  unknown unknown 
> org.dspace.storage.rdbms.DatabaseUtils @ Pending DSpace database schema 
> migrations:
> 2022-03-30 14:26:35,148 INFO  unknown unknown 
> *org.dspace.storage.rdbms.DatabaseUtils 
> @  7.0.2021.09.24 Move entity type from item template to collection SQL 
> PENDING*
> *2022-03-30 14:26:35,148 INFO  unknown unknown 
> org.dspace.storage.rdbms.DatabaseUtils @  7.0.2021.10.04 alter collection 
> table drop workflow stem columns SQL PENDING*
> *2022-03-30 14:26:35,148 INFO  unknown unknown 
> org.dspace.storage.rdbms.DatabaseUtils @  7.1.2021.10.18 Fix MDV place 
> after migrating from DSpace 5 SQL PENDING*
> 2022-03-30 14:26:35,150 WARN  unknown unknown 
> org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
> recommended: PostgreSQL 13.2 is newer than this version of Flyway and 
> support has not been tested. The latest supported version of PostgreSQL is 
> 12.
> 2022-03-30 14:26:35,157 FATAL unknown unknown org.dspace.core.Context @ 
> Cannot update or initialize database via Flyway!
> java.sql.SQLException: Flyway migration error occurred
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:775) 
> ~[dspace-api-7.2.jar:7.2]
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:662) 
> ~[dspace-api-7.2.jar:7.2]
> at 
> org.dspace.storage.rdbms.DatabaseUtils.updateDataba

[dspace-tech] DSpace 7 database migration.

[Juan López]

Hi!

I've set a test environment for dspace 7 and ran a successfull migration 
from 6.3 to 7.0, however, now that I'm upgrading from 7 to 7.2 I've noticed 
that some error are thrown when I execute an "index-discover -b".

Here's the error:

2022-03-30 14:26:35,118 INFO  unknown unknown 
org.dspace.discovery.indexobject.ItemIndexFactoryImpl @ Wrote Item: 
c3ec783f-517d-456b-b90b-50303f4e1bf2 to Index
2022-03-30 14:26:35,126 INFO  unknown unknown 
org.dspace.discovery.SolrServiceImpl @ 
anonymous::indexed_object:Item-c3ec783f-517d-456b-b90b-50303f4e1bf2
2022-03-30 14:26:35,128 INFO  unknown unknown 
org.dspace.storage.rdbms.DatabaseUtils @ Loading Flyway DB migrations from: 
classpath:org/dspace/storage/rdbms/sqlmigration/postgres, 
classpath:org/dspace/storage/rdbms/migration, 
classpath:org/dspace/storage/rdbms/xmlworkflow
2022-03-30 14:26:35,131 INFO  unknown unknown 
org.flywaydb.core.internal.database.DatabaseFactory @ Database: 
jdbc:postgresql://localhost:5432/prodDB (PostgreSQL 13.2)
2022-03-30 14:26:35,132 WARN  unknown unknown 
org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
recommended: PostgreSQL 13.2 is newer than this version of Flyway and 
support has not been tested. The latest supported version of PostgreSQL is 
12.
2022-03-30 14:26:35,140 WARN  unknown unknown 
org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
recommended: PostgreSQL 13.2 is newer than this version of Flyway and 
support has not been tested. The latest supported version of PostgreSQL is 
12.
2022-03-30 14:26:35,148 INFO  unknown unknown 
org.dspace.storage.rdbms.DatabaseUtils @ Pending DSpace database schema 
migrations:
2022-03-30 14:26:35,148 INFO  unknown unknown 
*org.dspace.storage.rdbms.DatabaseUtils 
@  7.0.2021.09.24 Move entity type from item template to collection SQL 
PENDING*
*2022-03-30 14:26:35,148 INFO  unknown unknown 
org.dspace.storage.rdbms.DatabaseUtils @  7.0.2021.10.04 alter collection 
table drop workflow stem columns SQL PENDING*
*2022-03-30 14:26:35,148 INFO  unknown unknown 
org.dspace.storage.rdbms.DatabaseUtils @  7.1.2021.10.18 Fix MDV place 
after migrating from DSpace 5 SQL PENDING*
2022-03-30 14:26:35,150 WARN  unknown unknown 
org.flywaydb.core.internal.database.base.Database @ Flyway upgrade 
recommended: PostgreSQL 13.2 is newer than this version of Flyway and 
support has not been tested. The latest supported version of PostgreSQL is 
12.
2022-03-30 14:26:35,157 FATAL unknown unknown org.dspace.core.Context @ 
Cannot update or initialize database via Flyway!
java.sql.SQLException: Flyway migration error occurred
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:775) 
~[dspace-api-7.2.jar:7.2]
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:662) 
~[dspace-api-7.2.jar:7.2]
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:637) 
~[dspace-api-7.2.jar:7.2]
at 
org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:616) 
~[dspace-api-7.2.jar:7.2]
at org.dspace.core.Context.updateDatabase(Context.java:213) 
[dspace-api-7.2.jar:7.2]
at org.dspace.core.Context.init(Context.java:166) 
[dspace-api-7.2.jar:7.2]
at org.dspace.core.Context.(Context.java:148) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.content.RelationshipMetadataServiceImpl.getRelationshipMetadata(RelationshipMetadataServiceImpl.java:44)
 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.content.ItemServiceImpl.getMetadata(ItemServiceImpl.java:1445) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.content.ItemServiceImpl.getMetadata(ItemServiceImpl.java:1429) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.content.ItemServiceImpl.getMetadata(ItemServiceImpl.java:72) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.SolrServiceSpellIndexingPlugin.additionalIndex(SolrServiceSpellIndexingPlugin.java:36)
 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.indexobject.DSpaceObjectIndexFactoryImpl.buildDocument(DSpaceObjectIndexFactoryImpl.java:30)
 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:134)
 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:75)
 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:165) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:155) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:322) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:309) 
[dspace-api-7.2.jar:7.2]
at 
org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:277) 
[dspace-api-7

[dspace-tech] Return bitstreams in dspace 7.1 search

[Fatima Caballero]

Hello, I wonder if it is possible that the searches return a file. As far 
as I know, the searches return communities, collections and items having to 
have a handle, but I am interested in knowing if it is possible for dspace 
to return a particular file. For example search by filename, and return the 
file, not the item that contains that file.
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/832a6d6f-60a6-4829-a781-6c66262c6650n%40googlegroups.com.

[dspace-tech] Auto Logout

[Oluwafemi Gabriel]

Hello All,
I have deployed DSpace on Google Cloud Plathform, but each time i attempt 
working with a different internet provider, i get logged out automatically 
to have to log in again before i can continue the admin task.
 Kindly assist to guide me on what i must do to deal with it.
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/cf3bb619-6728-4f70-bf56-fcf4c793d442n%40googlegroups.com.

Re: [dspace-tech] Re: Access PostgreSQL apache

[Mark H. Wood]

On Tue, Mar 29, 2022 at 09:26:07PM -0700, Phillip jan wrote:
> I have successfully setup a reverse proxy on both apache/tomcat and both 
> port 80 and 443 loads the REST API. I have already got my SSL certificate 
> from certbot and I've configured a virtualhost that listens on 443However, 
> admin login works only if i use a virtualhost that is running on port 80 
> but not when I login on a virtualhost that is running on port 443 (with 
> ssl). Basically, I can only login to my REST API only if it is on HTTP but 
> not when it is on HTTPS.
> 
> I checked my access logs and it returns: 
> 
> 127.0.0.1 - - [time/date] "POST /server/api/authn/login HTTP/1.1" 403 501 
> "https://[domainname]server/login.html"; "Mozilla/5.0 (X11; Linux x86_64) 
> AppleWebKit/537.36 (KHTML, like Gecko) Chrome/99.0.4844.88 Safari/537.36"
> 
> 
> Additional Info:
> 
> my /etc/hosts looks like,
> 
> 127.0.0.1[domain name]
> 127.0.0.1localhost
> private IPV4[domain name]

HTTP 403 means that the server is configured to refuse access to that
path by that host on that port.  Your HTTP and HTTPS configurations do
not have the same access rules set.

-- 
Mark H. Wood
Lead Technology Analyst

University Library
Indiana University - Purdue University Indianapolis
755 W. Michigan Street
Indianapolis, IN 46202
317-274-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/YkQ%2BuHGTVl74c%2BdD%40IUPUI.Edu.


signature.asc
Description: PGP signature

Re: [dspace-tech] Dspace 7.1 error.top-level-communites

[Lewatle Johannes Phaladi]

Dear Tim,

here is our solr details in dspace.cfg and local.cfg

# Solr server/webapp.
# DSpace uses Solr for all search/browse capability (and for usage 
statistics).
# Since DSpace 7, SOLR must be installed as a stand-alone service
solr.server = http://localhost:8983/solr

tomcat has been restarted and still getting similar errors , does SolrCore 
Initialization Failures  and additional information underneath not 
indicating as to what needs to be done to resolve solr errors. please see 
screenshot bellow 

[image: solr init failues.png]


On Monday, 28 March 2022 at 16:46:11 UTC+2 Tim Donohue wrote:

> Hi Lewatle,
>
> In your dspace.log, you'll notice the error says:
>
> Error from server at http://localhost:8983/solr/search
>
> followed by...  
>
> HTTP ERROR 404 Not Found
>
> That is telling you that DSpace cannot find your Solr.  It must not be 
> accessible at the URL http://localhost:8983/solr/   So, either your 
> "solr.server" setting in your local.cfg needs to be changed to the correct 
> location of Solr, or you need to review your Solr setup, which is step 13 of 
> the Backend Installation guide: 
> https://wiki.lyrasis.org/display/DSDOC7x/Installing+DSpace#InstallingDSpace-InstallingtheBackend(ServerAPI)
>
> Tim
>
> --
> *From:* dspac...@googlegroups.com  on behalf 
> of Lewatle Johannes Phaladi 
> *Sent:* Monday, March 28, 2022 8:52 AM
> *To:* DSpace Technical Support 
> *Subject:* [dspace-tech] Dspace 7.1 error.top-level-communites 
>  
> Dear DSpace Colleagues, 
>
> Just installed DSpace 7.1 on development machine, when first loaded web 
> interface it displays message "error.top-level-communites" also when trying 
> to login it keeps on loading endlessly, I have attached 2 files for help.
>
> 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...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/dspace-tech/b31c36f6-dbbe-4bdf-ab27-8d9eb2cf460an%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/4ce11d15-8d4d-4c74-b7f6-5c960b7c7674n%40googlegroups.com.