subject:"\[dspace\-tech\] Re\: index\-discovery"

[dspace-tech] Re: index-discovery

2023-05-02 Thread darryl....@usask.ca


Are you sure your Solr server is running on port 8080?  I think the default 
port is 8983.

- Darryl


On Tuesday, May 2, 2023 at 1:54:09 PM UTC-6 Matías Javier Saavedra Gajardo 
wrote:

> Help I don't know how to solve this error with solr when indexing my 
> database.
>
> Exception: Server refused connection at: http://localhost:8080/solr/search
> org.dspace.discovery.SearchServiceException: Server refused connection at: 
> http://localhost:8080/solr/search
> at 
> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:494)
> at org.dspace.discovery.IndexClient.main(IndexClient.java:151)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
> Caused by: org.apache.solr.client.solrj.SolrServerException: Server 
> refused connection at: http://localhost:8080/solr/search
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:559)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
> at 
> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
> at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310)
> at 
> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:465)
> ... 7 more
> Caused by: java.net.ConnectException: Conexión rehusada (Connection 
> refused)
> at java.net.PlainSocketImpl.socketConnect(Native Method)
> at 
> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
> at 
> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
> at 
> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
> at java.net.Socket.connect(Socket.java:607)
> at 
> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
> at 
> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
> at 
> org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
> at 
> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
> at 
> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
> at 
> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:882)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at 
> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at 
> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:448)
> ... 12 more
>

-- 
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/d9b0967e-4e29-4a4f-a340-15111d935a9an%40googlegroups.com.

[dspace-tech] Re: index-discovery

2023-05-03 Thread 'Matías Javier Saavedra Gajardo' via DSpace Technical Support


If I'm sure, don't install solr, solr was installed by default and it gave 
me port 8080, I understood that it was 8983, but I don't know why it left 
that port

Matias.

El martes, 2 de mayo de 2023 a las 19:25:18 UTC-4, darryl@usask.ca 
escribió:

>
> Are you sure your Solr server is running on port 8080?  I think the 
> default port is 8983.
>
> - Darryl
>
>
> On Tuesday, May 2, 2023 at 1:54:09 PM UTC-6 Matías Javier Saavedra Gajardo 
> wrote:
>
>> Help I don't know how to solve this error with solr when indexing my 
>> database.
>>
>> Exception: Server refused connection at: 
>> http://localhost:8080/solr/search
>> org.dspace.discovery.SearchServiceException: Server refused connection 
>> at: http://localhost:8080/solr/search
>> at 
>> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:494)
>> at org.dspace.discovery.IndexClient.main(IndexClient.java:151)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at 
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>> at 
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at 
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
>> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
>> Caused by: org.apache.solr.client.solrj.SolrServerException: Server 
>> refused connection at: http://localhost:8080/solr/search
>> at 
>> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:559)
>> at 
>> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:210)
>> at 
>> org.apache.solr.client.solrj.impl.HttpSolrServer.request(HttpSolrServer.java:206)
>> at 
>> org.apache.solr.client.solrj.request.QueryRequest.process(QueryRequest.java:91)
>> at org.apache.solr.client.solrj.SolrServer.query(SolrServer.java:310)
>> at 
>> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:465)
>> ... 7 more
>> Caused by: java.net.ConnectException: Conexión rehusada (Connection 
>> refused)
>> at java.net.PlainSocketImpl.socketConnect(Native Method)
>> at 
>> java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350)
>> at 
>> java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206)
>> at 
>> java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188)
>> at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
>> at java.net.Socket.connect(Socket.java:607)
>> at 
>> org.apache.http.conn.scheme.PlainSocketFactory.connectSocket(PlainSocketFactory.java:117)
>> at 
>> org.apache.http.impl.conn.DefaultClientConnectionOperator.openConnection(DefaultClientConnectionOperator.java:177)
>> at 
>> org.apache.http.impl.conn.ManagedClientConnectionImpl.open(ManagedClientConnectionImpl.java:304)
>> at 
>> org.apache.http.impl.client.DefaultRequestDirector.tryConnect(DefaultRequestDirector.java:611)
>> at 
>> org.apache.http.impl.client.DefaultRequestDirector.execute(DefaultRequestDirector.java:446)
>> at 
>> org.apache.http.impl.client.AbstractHttpClient.doExecute(AbstractHttpClient.java:882)
>> at 
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
>> at 
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
>> at 
>> org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
>> at 
>> org.apache.solr.client.solrj.impl.HttpSolrServer.executeMethod(HttpSolrServer.java:448)
>> ... 12 more
>>
>

-- 
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/f8b3e738-5847-4e7a-ab12-64a2d7e05c6fn%40googlegroups.com.

[dspace-tech] Re: index-discovery error

2023-03-21 Thread 'Tim Donohue' via DSpace Technical Support


Hi,

Based on that error message, it sounds like you somehow have invalid data 
in your "workspaceitem" database table (this table is used to store 
information about in-progress submissions).  The error seems to be saying 
that you have two different entries in the "workspaceitem" table which 
reference the *same* "item_id".  That shouldn't be possible, as each 
WorkspaceItem should have a *unique* "item_id".

I'm not sure how that could have occurred. But if you can find the 
duplicate entry in "workspaceitem", then it should be possible to just 
remove one of the entries.  I'd recommend making a copy of the database 
before doing this, as it's possible there could be side effects that I'm 
not foreseeing.  Once that duplicate entry is removed though, I suspect the 
indexing will work properly.

Tim
On Monday, March 20, 2023 at 2:30:32 AM UTC-5 Andrew K wrote:

> Hello!
>
> I have a 7.5 server updated from 5.4.
> The database update process finished OK.
> But the index-discovery fails. 
>
> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started 
> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index 
> 2023-03-20 09:24:43.049 ERROR index-discovery - 4 @ null 2023-03-20 
> 09:24:43.050 ERROR index-discovery - 4 @ 
> java.lang.IllegalArgumentException: More than one result found at 
> org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
>  
> at 
> org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)
>  
> at 
> org.dspace.content.WorkspaceItemServiceImpl.findByItem(WorkspaceItemServiceImpl.java:243)
>  
> at 
> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:1408) 
> at 
> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:92) 
> at 
> org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:129)
>  
> at 
> org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
>  
> at 
> org.dspace.discovery.indexobject.InprogressSubmissionIndexFactoryImpl.buildDocument(InprogressSubmissionIndexFactoryImpl.java:51)
>  
> at 
> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:63)
>  
> at 
> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:30)
>  
> at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at 
> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159) 
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:344) 
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:331) 
> at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:130) at 
> org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) at 
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>  
> at 
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>  
> at java.base/java.lang.Thread.run(Thread.java:829)The database info
> Database Type: postgres
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Database Schema: public
> Database Username: dspace
> Database Software: PostgreSQL version 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
> Database Driver: PostgreSQL JDBC Driver version 42.4.3
> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
> FlywayDB Version: 8.4.4
>
>
> +---++--+--+-+--+
> | Category  | Version| Description 
>  | Type | Installed On| State|
>
> +---++--+--+-+--+
> |   | 1  | << Flyway Init >>   
>  | BASELINE | 2016-02-15 00:03:53 | Baseline |
> | Versioned | 1.1| Initial DSpace 1.1 database schema 
>   | SQL  | 2016-02-15 00:03:53 | Success  |
> | Versioned | 1.2| Upgrade to DSpace 1.2 schema   
>   | SQL  | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.3| Upgrade to DSpace 1.3 schema   
>   | SQL  | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.3.9  | Drop constraint for DSpace 1 4 schema   
>  | JDBC | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.4| Upgrade to DSpace 1.4 schema   
>   | SQL  | 2016-02-15 00:03:54 | Success  |
> | Versioned | 1.5| Upgrade to DSpace 1.5 schema   
>

[dspace-tech] Re: index-discovery failed

2024-06-25 Thread DSpace Technical Support

Hi Alexis,

If you are still encountering this issue, then we may need more 
information.  Are there any other error messages that occur *before* that 
error in your logs?  Essentially, could you share more of the logs?

The error you shared isn't clear to me, but it almost looks like the 
indexing process is encountering bad data (it seems to be claiming that it 
is encountering a Bitstream which is thinks should exist, but is "null" 
instead).  So, you also may want to verify that the "dspace database 
migrate ignored" command didn't log any errors in the dspace.log file.

I'm not sure if that will help, but this error does seem confusing to me.  
So, any more information you can share might help us to narrow down the 
cause.

Tim

On Tuesday, June 18, 2024 at 7:42:44 AM UTC-5 afe...@unc.edu.ar wrote:

> Good morning DSpace team,
>  
> I'm having problems with index-discovery after upgrading from DSpace 
> version 6.3 to 7.6.1.
>
> First, I run *dspace database migrate ignored* without problems.
>
> Then I run *index-discovery -b* but it gives me the following error:
>
> java.lang.NullPointerException
> at 
> org.dspace.discovery.SolrServiceFileInfoPlugin.additionalIndex(SolrServiceFileInfoPlugin.java:55)
> at 
> org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
> at 
> org.dspace.discovery.indexobject.DSpaceObjectIndexFactoryImpl.buildDocument(DSpaceObjectIndexFactoryImpl.java:30)
> at 
> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:146)
> at 
> org.dspace.discovery.indexobject.ItemIndexFactoryImpl.buildDocument(ItemIndexFactoryImpl.java:81)
> at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169)
> at 
> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159)
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:349)
> at 
> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:336)
> at 
> org.dspace.discovery.SolrServiceImpl.createIndex(SolrServiceImpl.java:304)
> at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:117)
> 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)
>
> At the moment, I have not found any solution.
>
> If you have any solution, welcome.
>
> Greetings and thanks!
>
> Alexis
>
>
>
>
>

-- 
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/4046ac8f-bff8-477d-af05-204d31e02ba0n%40googlegroups.com.

Re: [dspace-tech] Re: index-discovery error

2023-03-21 Thread Andrew K

Hi Tim,

Thanks a lot for your reply!

I exported the table *workspaceitem* and found no identical "item_id"
numbers. Since I do not care about those old (partially) submitted items, I
wanted to delete everything in the admin/workflow zone on the website, but
somehow it's not possible for those old submissions.
So I just truncated the *workspaceitem* table in the database. And it
worked! Now index-discovery goes smoothly. Yay!

Can I also ask you if it's possible to keep the old handle-type URLs in
DSpace 7 ?

Best regards,
Andrew

вт, 21 бер. 2023 р. о 18:34 'Tim Donohue' via DSpace Technical Support <
dspace-tech@googlegroups.com> пише:

>
> Hi,
>
> Based on that error message, it sounds like you somehow have invalid data
> in your "workspaceitem" database table (this table is used to store
> information about in-progress submissions).  The error seems to be saying
> that you have two different entries in the "workspaceitem" table which
> reference the *same* "item_id".  That shouldn't be possible, as each
> WorkspaceItem should have a *unique* "item_id".
>
> I'm not sure how that could have occurred. But if you can find the
> duplicate entry in "workspaceitem", then it should be possible to just
> remove one of the entries.  I'd recommend making a copy of the database
> before doing this, as it's possible there could be side effects that I'm
> not foreseeing.  Once that duplicate entry is removed though, I suspect the
> indexing will work properly.
>
> Tim
> On Monday, March 20, 2023 at 2:30:32 AM UTC-5 Andrew K wrote:
>
>> Hello!
>>
>> I have a 7.5 server updated from 5.4.
>> The database update process finished OK.
>> But the index-discovery fails.
>>
>> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started
>> 2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index
>> 2023-03-20 09:24:43.049 ERROR index-discovery - 4 @ null 2023-03-20
>> 09:24:43.050 ERROR index-discovery - 4 @
>> java.lang.IllegalArgumentException: More than one result found at
>> org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
>> at
>> org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)
>> at
>> org.dspace.content.WorkspaceItemServiceImpl.findByItem(WorkspaceItemServiceImpl.java:243)
>> at
>> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:1408)
>> at
>> org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:92)
>> at
>> org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:129)
>> at
>> org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
>> at
>> org.dspace.discovery.indexobject.InprogressSubmissionIndexFactoryImpl.buildDocument(InprogressSubmissionIndexFactoryImpl.java:51)
>> at
>> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:63)
>> at
>> org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:30)
>> at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at
>> org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159)
>> at
>> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:344)
>> at
>> org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:331)
>> at org.dspace.discovery.IndexClient.internalRun(IndexClient.java:130) at
>> org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) at
>> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
>> at
>> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
>> at java.base/java.lang.Thread.run(Thread.java:829)The database info
>> Database Type: postgres
>> Database URL: jdbc:postgresql://localhost:5432/dspace
>> Database Schema: public
>> Database Username: dspace
>> Database Software: PostgreSQL version 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
>> Database Driver: PostgreSQL JDBC Driver version 42.4.3
>> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
>> FlywayDB Version: 8.4.4
>>
>>
>> +---++--+--+-+--+
>> | Category  | Version| Description
>>| Type | Installed On| State|
>>
>> +---++--+--+-+--+
>> |   | 1  | << Flyway Init >>
>>| BASELINE | 2016-02-15 00:03:53 | Baseline |
>> | Versioned | 1.1| Initial DSpace 1.1 database schema
>>   | SQL  | 2016-02-15 00:03:53 | Success  |
>> | Versioned | 1.2| Upgrade to DSpace 1.2 schema
>>   | SQL

Re: [dspace-tech] Re: index-discovery error

2023-03-21 Thread 'Tim Donohue' via DSpace Technical Support

Hi Andrew,

Glad to hear you figured it out.

Regarding your other URL question, I just answered it in your other email 
thread: https://groups.google.com/g/dspace-tech/c/cLFoNivftB4/m/mjajzzydAAAJ

Tim

From: dspace-tech@googlegroups.com  on behalf of 
Andrew K 
Sent: Tuesday, March 21, 2023 2:53 PM
To: DSpace Technical Support 
Subject: Re: [dspace-tech] Re: index-discovery error

Hi Tim,

Thanks a lot for your reply!

I exported the table workspaceitem and found no identical "item_id" numbers. 
Since I do not care about those old (partially) submitted items, I wanted to 
delete everything in the admin/workflow zone on the website, but somehow it's 
not possible for those old submissions.
So I just truncated the workspaceitem table in the database. And it worked! Now 
index-discovery goes smoothly. Yay!

Can I also ask you if it's possible to keep the old handle-type URLs in DSpace 
7 ?

Best regards,
Andrew

вт, 21 бер. 2023 р. о 18:34 'Tim Donohue' via DSpace Technical Support 
mailto:dspace-tech@googlegroups.com>> пише:

Hi,

Based on that error message, it sounds like you somehow have invalid data in 
your "workspaceitem" database table (this table is used to store information 
about in-progress submissions).  The error seems to be saying that you have two 
different entries in the "workspaceitem" table which reference the *same* 
"item_id".  That shouldn't be possible, as each WorkspaceItem should have a 
*unique* "item_id".

I'm not sure how that could have occurred. But if you can find the duplicate 
entry in "workspaceitem", then it should be possible to just remove one of the 
entries.  I'd recommend making a copy of the database before doing this, as 
it's possible there could be side effects that I'm not foreseeing.  Once that 
duplicate entry is removed though, I suspect the indexing will work properly.

Tim
On Monday, March 20, 2023 at 2:30:32 AM UTC-5 Andrew K wrote:
Hello!

I have a 7.5 server updated from 5.4.
The database update process finished OK.
But the index-discovery fails.

2023-03-20 09:24:03.611 INFO index-discovery - 4 @ The script has started 
2023-03-20 09:24:03.611 INFO index-discovery - 4 @ Updating Index 2023-03-20 
09:24:43.049 ERROR index-discovery - 4 @ null 2023-03-20 09:24:43.050 ERROR 
index-discovery - 4 @ java.lang.IllegalArgumentException: More than one result 
found at 
org.dspace.core.AbstractHibernateDAO.uniqueResult(AbstractHibernateDAO.java:242)
 at 
org.dspace.content.dao.impl.WorkspaceItemDAOImpl.findByItem(WorkspaceItemDAOImpl.java:81)
 at 
org.dspace.content.WorkspaceItemServiceImpl.findByItem(WorkspaceItemServiceImpl.java:243)
 at 
org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:1408) 
at org.dspace.content.ItemServiceImpl.getParentObject(ItemServiceImpl.java:92) 
at 
org.dspace.discovery.SolrServiceResourceRestrictionPlugin.additionalIndex(SolrServiceResourceRestrictionPlugin.java:129)
 at 
org.dspace.discovery.indexobject.IndexFactoryImpl.buildDocument(IndexFactoryImpl.java:67)
 at 
org.dspace.discovery.indexobject.InprogressSubmissionIndexFactoryImpl.buildDocument(InprogressSubmissionIndexFactoryImpl.java:51)
 at 
org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:63)
 at 
org.dspace.discovery.indexobject.WorkspaceItemIndexFactoryImpl.buildDocument(WorkspaceItemIndexFactoryImpl.java:30)
 at org.dspace.discovery.SolrServiceImpl.update(SolrServiceImpl.java:169) at 
org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:159) at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:344) at 
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:331) at 
org.dspace.discovery.IndexClient.internalRun(IndexClient.java:130) at 
org.dspace.scripts.DSpaceRunnable.run(DSpaceRunnable.java:104) at 
java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
 at 
java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
 at java.base/java.lang.Thread.run(Thread.java:829)The database info
Database Type: postgres
Database URL: jdbc:postgresql://localhost:5432/dspace
Database Schema: public
Database Username: dspace
Database Software: PostgreSQL version 14.7 (Ubuntu 14.7-0ubuntu0.22.04.1)
Database Driver: PostgreSQL JDBC Driver version 42.4.3
PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3)
FlywayDB Version: 8.4.4

+---++--+--+-+--+
| Category  | Version| Description  
| Type | Installed On| State|
+---++

[dspace-tech] Re: Index-Discovery with DSpace 5.8

2021-03-05 Thread LBOV

Dealing with the same problem, any clues? 


On Thursday, February 25, 2021 at 2:25:34 AM UTC-6 Kosmas Kaifel wrote:

> Hello
>
> with the command ../bin/dspace index-discovery I receive the following 
> error message
>
> Exception: Handle is null
> org.dspace.discovery.SearchServiceException: Handle is null
> at 
> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:507)
> at org.dspace.discovery.IndexClient.main(IndexClient.java:126)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
>
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at 
>
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at 
>
> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
> at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)
> Caused by: java.lang.IllegalArgumentException: Handle is null
> at 
> org.dspace.handle.HandleManager.findHandleInternal(HandleManager.java:532)
> at 
> org.dspace.handle.HandleManager.resolveToObject(HandleManager.java:322)
> at 
> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:488)
> ... 7 more
> SOLR Search Optimize -- Process Started:1614200413002
> SOLR Search Optimize -- Process Finished:1614200413017
> SOLR Search Optimize -- Total time taken:15 (ms).
>
> With two sql-statment I try to find items without handle but I can not 
> find any
>
> 1) select * from handle h where h.handle='' or h.handle is null
>
> 2) Select i.item_id FROM item i WHERE i.in_archive=True And Not EXISTS
> (Select resource_id FROM handle h WHERE h.resource_id = i.item_id 
> And h.resource_type_id = 2)
>
> Best Regards
> Kosmas
>
> -- 
> +---+
> Universität Ulm
> Kommunikations- und Informationszentrum (kiz)
> Abt. Informationsmedien
> Albert-Einstein-Allee 37
> 89081 Ulm
> Tel. 0731/50-15495
> EMail: kosmas...@uni-ulm.de
> ++
>
>

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
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/e0d7ce34-70f2-4f08-8ca8-3e8dcb67d944n%40googlegroups.com.

Re: [dspace-tech] Re: Index-Discovery with DSpace 5.8

2021-03-05 Thread José Geraldo

Using parameter -b, will return same error?

-b (re)build index, wiping out current one if it exists

Em sex., 5 de mar. de 2021 às 11:49, LBOV 
escreveu:

> Dealing with the same problem, any clues?
>
>
> On Thursday, February 25, 2021 at 2:25:34 AM UTC-6 Kosmas Kaifel wrote:
>
>> Hello
>>
>> with the command ../bin/dspace index-discovery I receive the following
>> error message
>>
>> Exception: Handle is null
>> org.dspace.discovery.SearchServiceException: Handle is null
>> at
>> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:507)
>> at org.dspace.discovery.IndexClient.main(IndexClient.java:126)
>> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>> at
>> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
>>
>> at
>> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>>
>> at java.lang.reflect.Method.invoke(Method.java:498)
>> at
>> org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:226)
>>
>> at
>> org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:78)
>> Caused by: java.lang.IllegalArgumentException: Handle is null
>> at
>> org.dspace.handle.HandleManager.findHandleInternal(HandleManager.java:532)
>>
>> at
>> org.dspace.handle.HandleManager.resolveToObject(HandleManager.java:322)
>> at
>> org.dspace.discovery.SolrServiceImpl.cleanIndex(SolrServiceImpl.java:488)
>> ... 7 more
>> SOLR Search Optimize -- Process Started:1614200413002
>> SOLR Search Optimize -- Process Finished:1614200413017
>> SOLR Search Optimize -- Total time taken:15 (ms).
>>
>> With two sql-statment I try to find items without handle but I can not
>> find any
>>
>> 1) select * from handle h where h.handle='' or h.handle is null
>>
>> 2) Select i.item_id FROM item i WHERE i.in_archive=True And Not EXISTS
>> (Select resource_id FROM handle h WHERE h.resource_id = i.item_id
>> And h.resource_type_id = 2)
>>
>> Best Regards
>> Kosmas
>>
>> --
>> +---+
>> Universität Ulm
>> Kommunikations- und Informationszentrum (kiz)
>> Abt. Informationsmedien
>> Albert-Einstein-Allee 37
>> 89081 Ulm
>> Tel. 0731/50-15495
>> EMail: kosmas...@uni-ulm.de
>> ++
>>
>> --
> All messages to this mailing list should adhere to the Code of Conduct:
> https://duraspace.org/about/policies/code-of-conduct/
> ---
> 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/e0d7ce34-70f2-4f08-8ca8-3e8dcb67d944n%40googlegroups.com
> 
> .
>


-- 
At.te,

José Geraldo

-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
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/CANP4ikTP2bXKFgU4dQh7nzaWny3a9BVPnV%2B0vQw197wZqtVoNg%40mail.gmail.com.

Re: [dspace-tech] Re: Index-Discovery with DSpace 5.8

2021-03-05 Thread LBOV

Hi, 
Using parameter -b don't return any error, returns nothing actually, but it 
seems to complete the index rebuild.
Nevertheless, if I run index-discovery (without de -b parameter) after run 
index-discovery -b, the same error is shown again...





-- 
All messages to this mailing list should adhere to the Code of Conduct: 
https://duraspace.org/about/policies/code-of-conduct/
--- 
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/e077e3d4-34d8-4e02-bc56-e16ff60dc3a6n%40googlegroups.com.

[dspace-tech] Re: index-discovery

[dspace-tech] Re: index-discovery

[dspace-tech] Re: index-discovery error

[dspace-tech] Re: index-discovery failed

Re: [dspace-tech] Re: index-discovery error

Re: [dspace-tech] Re: index-discovery error

[dspace-tech] Re: Index-Discovery with DSpace 5.8

Re: [dspace-tech] Re: Index-Discovery with DSpace 5.8

Re: [dspace-tech] Re: Index-Discovery with DSpace 5.8

9 matches

Site Navigation

Mail list logo

Footer information