from:"David Baker"

Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-03-06 Thread David Baker

Thanks, Tim. I've added

db.schema = public

to my local.cfg and that appears to have helped with the issue. Do I need 
to be concerned that my ./dspace database info shows these 2 lines as 
"Baselin" and "OutOrdr" instead of "Success" like all of the others?

 1  | << Flyway Init >>   | 2015
-06-09 12:16:21 | Baselin |
 4.9.2015.10.26 | DS-2818 registry update | 2019
-03-06 07:52:45 | OutOrdr |

If those lines are OK, it looks like the upgrade was fairly successful. 
Thanks again for the help.

David

On Monday, March 4, 2019 at 10:48:40 AM UTC-5, Tim Donohue wrote:
>
> Hi David,
>
> No, what I was referring to is an automatic update of the local (bitstream 
> format and metadata) registries that happens *AFTER* all the database 
> upgrade scripts run (this update is triggered by a callback script which 
> requires the database be updated first -- as the registry update is simply 
> adding data to your database, including default metadata schemas, fields, 
> and default recognized file formats).  So, it won't appear in the "./dspace 
> database info" output.  But, if the registry updates fail, they will log 
> errors in your dspace.log file during your upgrade process.
>
> In any case, manually rerunning the local registry updates won't harm your 
> database in any way. The scripts check to see if the registry information 
> already exists (and if so, it skips re-adding it).  So, again, I'd 
> recommend manually updating your registries as noted in Step 11 (part "d") 
> of the Upgrade Docs: 
> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>
> As noted in the previous email, you also should double check your settings 
> for "db.schema" in your dspace.cfg or local.cfg.  For PostgreSQL, this 
> should likely be set to "public". Having the schema improperly set could 
> result in the issues you are seeing.  Again, see this email thread: 
> http://dspace.2283337.n4.nabble.com/DSpace6-SQL-Error-td4684728.html 
>
> - Tim
>
>
> On Fri, Mar 1, 2019 at 3:23 PM David Baker > 
> wrote:
>
> Below is the result of ./dspace database info. Is the ignored DS-2818 
> registry update what you were referring to as updating the local DSpace 
> registries?
>
>
> Using DSpace installation in: C:\dspace
>
> Database Type: postgres
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Database Schema: public
> Database Username: dspace
> Database Software: PostgreSQL version 9.4.17
> Database Driver: PostgreSQL JDBC Driver version 42.2.1
> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)
>
>
> ++-+-+-+
> | Version| Description | 
> Installed on| State   |
>
> ++-+-+-+
> | 1  | << Flyway Init >>   | 
> 2015-06-09 12:16:21 | Baselin |
> | 1.1| Initial DSpace 1.1 database schema  | 
> 2015-06-09 12:16:22 | Success |
> | 1.2| Upgrade to DSpace 1.2 schema| 
> 2015-06-09 12:16:22 | Success |
> | 1.3| Upgrade to DSpace 1.3 schema| 
> 2015-06-09 12:16:22 | Success |
> | 1.3.9  | Drop constraint for DSpace 1 4 schema   | 
> 2015-06-09 12:16:23 | Success |
> | 1.4| Upgrade to DSpace 1.4 schema| 
> 2015-06-09 12:16:23 | Success |
> | 1.5| Upgrade to DSpace 1.5 schema| 
> 2015-06-09 12:16:23 | Success |
> | 1.5.9  | Drop constraint for DSpace 1 6 schema   | 
> 2015-06-09 12:16:24 | Success |
> | 1.6| Upgrade to DSpace 1.6 schema| 
> 2015-06-09 12:16:24 | Success |
> | 1.7| Upgrade to DSpace 1.7 schema| 
> 2015-06-09 12:16:24 | Success |
> | 1.8| Upgrade to DSpace 1.8 schema| 
> 2015-06-09 12:16:24 | Success |
> | 3.0| Upgrade to DSpace 3.x schema| 
> 2015-06-09 12:16:24 | Success |
> | 4.0| Upgrade to DSpace 4.x schema| 
> 2015-06-09 12:16:24 | Success |
> | 4.9.2015.10.26 | DS-2818 registry update 
> | | Ignored |
> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 
> 2015-06-09 12:16:24 | Success |
> | 5.0.2014.09.25 | DS 1582 Metadata For All Obj

Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-03-01 Thread David Baker

ror: 0, SQLState: 
> 42601
> 2019-03-01 13:09:16,849 ERROR 
> org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ Batch entry 0 delete 
> from .webapp where webapp_id=396 was aborted: ERROR: syntax error at or 
> near "."
>   Position: 13  Call getNextException to see other errors in the batch. 
>
> I'm hoping that the primary issue is that your registries didn't update 
> properly. But, you also may want to look back at the logs for the database 
> upgrade itself, to see if any other strange warnings or errors are noted 
> there.
>
> If it's a simple registry issue, you should be able to manually update 
> your registries as noted in Step 11 (part "d") of the Upgrade Docs: 
> https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace
>
> If that manual update of the registries doesn't work, then I highly 
> suspect some (other) part of the upgrade didn't complete successfully.  You 
> should look back at the logs (or try the upgrade again on a test server, 
> closely watching the logs).  You also could verify your database is 
> reporting successful upgrades by checking the output of "./dspace database 
> info".
>
> I also just found this old email thread that mentioned this same error. 
> The suggestion in that thread was to check your settings for "db.schema" 
> (which for PostgreSQL should be set to "public"): 
> http://dspace.2283337.n4.nabble.com/DSpace6-SQL-Error-td4684728.html
>
> Tim
>
>  
>
> On Fri, Mar 1, 2019 at 12:53 PM David Baker  > wrote:
>
> Thanks, Tim. I deleted the duplicate COLLECTION_29_DEFAULT_READ group and 
> the migration proceeded past. It now shows all of the migrations as 
> successful except DS-2818 registry update, which I'm assuming is normal. 
>
> I'm apparently having an issue somewhere else now, though. When I browse 
> to my repository, I only get a blank white screen. The end of my dspace.log 
> file is showing a few errors:
>
>
> 2019-03-01 12:57:19,683 INFO  
> org.dspace.importer.external.service.ImportService @ Loading 1 import 
> sources.
> 2019-03-01 12:57:30,980 INFO  org.dspace.core.LoggerServiceImpl @ Using 
> dspace provided log configuration (log.init.config)
> 2019-03-01 12:57:30,996 INFO  org.dspace.core.LoggerServiceImpl @ Loading: 
> C:\dspace/config/log4j.properties
> 2019-03-01 12:57:35,058 INFO  org.dspace.storage.rdbms.DatabaseUtils @ 
> Loading Flyway DB migrations from: filesystem:C:\dspace/etc/postgres, 
> classpath:org.dspace.storage.rdbms.sqlmigration.postgres, 
> classpath:org.dspace.storage.rdbms.migration
> 2019-03-01 12:57:35,449 INFO  
> org.flywaydb.core.internal.util.VersionPrinter @ Flyway 4.0.3 by Boxfuse
> 2019-03-01 12:57:35,621 INFO  
> org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database: 
> jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.4)
> 2019-03-01 12:57:49,574 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2015.08.31 - DS 2701 Hibernate 
> Workflow Migration
> 2019-03-01 12:57:49,887 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.01.03 - DS-3024
> 2019-03-01 12:57:50,699 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.01.26 - DS 2188 Remove DBMS 
> Browse Tables
> 2019-03-01 12:57:50,918 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.02.25 - 
> DS-3004-slow-searching-as-admin
> 2019-03-01 12:57:50,949 INFO  
> org.flywaydb.core.internal.dbsupport.JdbcTemplate @ DB: column "name" of 
> relation "epersongroup" does not exist, skipping
> 2019-03-01 12:57:51,012 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.04.01 - DS-1955 Increase 
> embargo reason
> 2019-03-01 12:57:51,090 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.04.04 - 
> DS-3086-OAI-Performance-fix
> 2019-03-01 12:57:52,090 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.04.14 - 
> DS-3125-fix-bundle-bitstream-delete-rights
> 2019-03-01 12:57:52,418 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.05.10 - 
> DS-3168-fix-requestitem item id column
> 2019-03-01 12:57:52,512 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to version 6.0.2016.07.21 - DS-2775
> 2019-03-01 12:57:52,605 INFO  org.flywaydb.core.internal.command.DbMigrate 
> @ Migrating schema "public" to

Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-03-01 Thread David Baker

uniqueness is now guaranteed at the database level).  This is a very rare 
> scenario, as DSpace should have never allowed two groups of the same name 
> to be created. But, somehow this seems to have occurred at least a few 
> times (on your site, and on the site that reported bug DS-2824).
>
> In any case, the fix should be to look for two groups named 
> COLLECTION_29_DEFAULT_READ (this group is named oddly because it is the 
> group that is providing DEFAULT_READ permissions to your Collection with 
> ID=29). Figure out which one is the correct one, and delete the other one.  
> If you rerun the migration it should now succeed (again assuming there are 
> no other duplicative groups -- but there hopefully should not be).
>
> Good luck,
>
> Tim
>
>
>
> On Thu, Feb 28, 2019 at 2:29 PM David Baker  > wrote:
>
>> Anybody have any ideas why I'm running into this?
>> I found this bug report https://jira.duraspace.org/browse/DS-2824 but 
>> don't understand how the issue was resolved in that case.
>> Thanks.
>>
>>
>> On Thursday, February 28, 2019 at 3:27:27 PM UTC-5, David Baker wrote:
>>>
>>> I'm upgrading DSpace on Windows Server 2012 from version 5.3 to 6.3
>>>
>>> Here's the output of bin\dspace database info:
>>>
>>> Using DSpace installation in: c:\dspace
>>>
>>> Database Type: postgres
>>> Database URL: jdbc:postgresql://localhost:5432/dspace
>>> Database Schema: public
>>> Database Username: dspace
>>> Database Software: PostgreSQL version 9.4.17
>>> Database Driver: PostgreSQL JDBC Driver version 42.2.1
>>> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)
>>>
>>>
>>> ++-+-+-+
>>> | Version| Description | 
>>> Installed on| State   |
>>>
>>> ++-+-+-+
>>> | 1  | << Flyway Init >>   | 
>>> 2015-06-09 12:16:21 | Baselin |
>>> | 1.1| Initial DSpace 1.1 database schema  | 
>>> 2015-06-09 12:16:22 | Success |
>>> | 1.2| Upgrade to DSpace 1.2 schema| 
>>> 2015-06-09 12:16:22 | Success |
>>> | 1.3| Upgrade to DSpace 1.3 schema| 
>>> 2015-06-09 12:16:22 | Success |
>>> | 1.3.9  | Drop constraint for DSpace 1 4 schema   | 
>>> 2015-06-09 12:16:23 | Success |
>>> | 1.4| Upgrade to DSpace 1.4 schema| 
>>> 2015-06-09 12:16:23 | Success |
>>> | 1.5| Upgrade to DSpace 1.5 schema| 
>>> 2015-06-09 12:16:23 | Success |
>>> | 1.5.9  | Drop constraint for DSpace 1 6 schema   | 
>>> 2015-06-09 12:16:24 | Success |
>>> | 1.6| Upgrade to DSpace 1.6 schema| 
>>> 2015-06-09 12:16:24 | Success |
>>> | 1.7| Upgrade to DSpace 1.7 schema| 
>>> 2015-06-09 12:16:24 | Success |
>>> | 1.8| Upgrade to DSpace 1.8 schema| 
>>> 2015-06-09 12:16:24 | Success |
>>> | 3.0| Upgrade to DSpace 3.x schema| 
>>> 2015-06-09 12:16:24 | Success |
>>> | 4.0| Upgrade to DSpace 4.x schema| 
>>> 2015-06-09 12:16:24 | Success |
>>> | 4.9.2015.10.26 | DS-2818 registry update 
>>> | | Ignored |
>>> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 
>>> 2015-06-09 12:16:24 | Success |
>>> | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint| 
>>> 2015-06-09 12:16:24 | Success |
>>> | 5.0.2014.09.26 | DS-1582 Metadata For All Objects| 
>>> 2015-06-09 12:16:24 | Success |
>>> | 5.6.2016.08.23 | DS-3097 | 
>>> 2019-02-28 14:52:18 | Success |
>>> | 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id column | 
>>> 2019-02-28 14:52:20 | Success |
>>> | 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow  | 
>>> 2019-02-28 14:52:21 | Success |
>>> | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration  | 
>>&

[dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-02-28 Thread David Baker

Anybody have any ideas why I'm running into this?
I found this bug report https://jira.duraspace.org/browse/DS-2824 but don't 
understand how the issue was resolved in that case.
Thanks.


On Thursday, February 28, 2019 at 3:27:27 PM UTC-5, David Baker wrote:
>
> I'm upgrading DSpace on Windows Server 2012 from version 5.3 to 6.3
>
> Here's the output of bin\dspace database info:
>
> Using DSpace installation in: c:\dspace
>
> Database Type: postgres
> Database URL: jdbc:postgresql://localhost:5432/dspace
> Database Schema: public
> Database Username: dspace
> Database Software: PostgreSQL version 9.4.17
> Database Driver: PostgreSQL JDBC Driver version 42.2.1
> PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)
>
>
> ++-+-+-+
> | Version| Description | 
> Installed on| State   |
>
> ++-+-+-+
> | 1  | << Flyway Init >>   | 
> 2015-06-09 12:16:21 | Baselin |
> | 1.1| Initial DSpace 1.1 database schema  | 
> 2015-06-09 12:16:22 | Success |
> | 1.2| Upgrade to DSpace 1.2 schema| 
> 2015-06-09 12:16:22 | Success |
> | 1.3| Upgrade to DSpace 1.3 schema| 
> 2015-06-09 12:16:22 | Success |
> | 1.3.9  | Drop constraint for DSpace 1 4 schema   | 
> 2015-06-09 12:16:23 | Success |
> | 1.4| Upgrade to DSpace 1.4 schema| 
> 2015-06-09 12:16:23 | Success |
> | 1.5| Upgrade to DSpace 1.5 schema| 
> 2015-06-09 12:16:23 | Success |
> | 1.5.9  | Drop constraint for DSpace 1 6 schema   | 
> 2015-06-09 12:16:24 | Success |
> | 1.6| Upgrade to DSpace 1.6 schema| 
> 2015-06-09 12:16:24 | Success |
> | 1.7| Upgrade to DSpace 1.7 schema| 
> 2015-06-09 12:16:24 | Success |
> | 1.8| Upgrade to DSpace 1.8 schema| 
> 2015-06-09 12:16:24 | Success |
> | 3.0| Upgrade to DSpace 3.x schema| 
> 2015-06-09 12:16:24 | Success |
> | 4.0| Upgrade to DSpace 4.x schema| 
> 2015-06-09 12:16:24 | Success |
> | 4.9.2015.10.26 | DS-2818 registry update 
> | | Ignored |
> | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 
> 2015-06-09 12:16:24 | Success |
> | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint| 
> 2015-06-09 12:16:24 | Success |
> | 5.0.2014.09.26 | DS-1582 Metadata For All Objects| 
> 2015-06-09 12:16:24 | Success |
> | 5.6.2016.08.23 | DS-3097 | 
> 2019-02-28 14:52:18 | Success |
> | 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id column | 
> 2019-02-28 14:52:20 | Success |
> | 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow  | 
> 2019-02-28 14:52:21 | Success |
> | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration  | 
> 2019-02-28 14:52:22 | Success |
> | 6.0.2015.03.07 | DS-2701 Hibernate migration | 
> 2019-02-28 14:52:23 | Success |
> | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration| 
> 2019-02-28 14:54:57 | Success |
> | 6.0.2016.01.03 | DS-3024 | 
> 2019-02-28 14:54:57 | Success |
> | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables   | 
> 2019-02-28 14:54:58 | Success |
> | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin 
> | | Pending |
> | 6.0.2016.04.01 | DS-1955 Increase embargo reason 
> | | Pending |
> | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix 
> | | Pending |
> | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights  
> | | Pending |
> | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column  
> | | Pending |
> | 6.0.2016.07.21 | DS-2775 
> | | Pending |
> | 6.0.2016.07.26 | DS-3277 fix handle assignment   
> | | Pending |
> | 6.0.2016.08.23 | DS-3097 
> | | Pending |
> | 6.1.2017

[dspace-tech] Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

2019-02-28 Thread David Baker

I'm upgrading DSpace on Windows Server 2012 from version 5.3 to 6.3

Here's the output of bin\dspace database info:

Using DSpace installation in: c:\dspace

Database Type: postgres
Database URL: jdbc:postgresql://localhost:5432/dspace
Database Schema: public
Database Username: dspace
Database Software: PostgreSQL version 9.4.17
Database Driver: PostgreSQL JDBC Driver version 42.2.1
PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1)

++-+-+-+
| Version| Description | 
Installed on| State   |
++-+-+-+
| 1  | << Flyway Init >>   | 
2015-06-09 12:16:21 | Baselin |
| 1.1| Initial DSpace 1.1 database schema  | 
2015-06-09 12:16:22 | Success |
| 1.2| Upgrade to DSpace 1.2 schema| 
2015-06-09 12:16:22 | Success |
| 1.3| Upgrade to DSpace 1.3 schema| 
2015-06-09 12:16:22 | Success |
| 1.3.9  | Drop constraint for DSpace 1 4 schema   | 
2015-06-09 12:16:23 | Success |
| 1.4| Upgrade to DSpace 1.4 schema| 
2015-06-09 12:16:23 | Success |
| 1.5| Upgrade to DSpace 1.5 schema| 
2015-06-09 12:16:23 | Success |
| 1.5.9  | Drop constraint for DSpace 1 6 schema   | 
2015-06-09 12:16:24 | Success |
| 1.6| Upgrade to DSpace 1.6 schema| 
2015-06-09 12:16:24 | Success |
| 1.7| Upgrade to DSpace 1.7 schema| 
2015-06-09 12:16:24 | Success |
| 1.8| Upgrade to DSpace 1.8 schema| 
2015-06-09 12:16:24 | Success |
| 3.0| Upgrade to DSpace 3.x schema| 
2015-06-09 12:16:24 | Success |
| 4.0| Upgrade to DSpace 4.x schema| 
2015-06-09 12:16:24 | Success |
| 4.9.2015.10.26 | DS-2818 registry update 
| | Ignored |
| 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 
2015-06-09 12:16:24 | Success |
| 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint| 
2015-06-09 12:16:24 | Success |
| 5.0.2014.09.26 | DS-1582 Metadata For All Objects| 
2015-06-09 12:16:24 | Success |
| 5.6.2016.08.23 | DS-3097 | 
2019-02-28 14:52:18 | Success |
| 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id column | 
2019-02-28 14:52:20 | Success |
| 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow  | 
2019-02-28 14:52:21 | Success |
| 6.0.2015.03.06 | DS 2701 Dso Uuid Migration  | 
2019-02-28 14:52:22 | Success |
| 6.0.2015.03.07 | DS-2701 Hibernate migration | 
2019-02-28 14:52:23 | Success |
| 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration| 
2019-02-28 14:54:57 | Success |
| 6.0.2016.01.03 | DS-3024 | 
2019-02-28 14:54:57 | Success |
| 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables   | 
2019-02-28 14:54:58 | Success |
| 6.0.2016.02.25 | DS-3004-slow-searching-as-admin 
| | Pending |
| 6.0.2016.04.01 | DS-1955 Increase embargo reason 
| | Pending |
| 6.0.2016.04.04 | DS-3086-OAI-Performance-fix 
| | Pending |
| 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights  
| | Pending |
| 6.0.2016.05.10 | DS-3168-fix-requestitem item id column  
| | Pending |
| 6.0.2016.07.21 | DS-2775 
| | Pending |
| 6.0.2016.07.26 | DS-3277 fix handle assignment   
| | Pending |
| 6.0.2016.08.23 | DS-3097 
| | Pending |
| 6.1.2017.01.03 | DS 3431 Add Policies for BasicWorkflow  
| | Pending |
++-+-+-+


Then there's this in my dspace.log file:


2019-02-28 14:54:58,834 INFO  org.flywaydb.core.internal.command.DbMigrate 
@ Migrating schema "public" to version 6.0.2016.02.25 - 
DS-3004-slow-searching-as-admin
2019-02-28 14:54:58,928 INFO  
org.flywaydb.core.internal.dbsupport.JdbcTemplate @ DB: column "name" of 
relation "epersongroup" does not exist, skipping
2019-02-28 14:54:59,537 ERROR org.flywaydb.core.internal.command.DbMigrate 
@ Migration of schema "public" to version 6.0.2016.02.25 -

Re: [dspace-tech] Statistics showing are not current

2017-02-08 Thread David Baker

Terry, I've created issue DS-3481 
<https://jira.duraspace.org/browse/DS-3481>

Thanks.
David

On Tuesday, January 31, 2017 at 3:31:40 PM UTC-5, Terry Brady wrote:
>
> David,
>
> I am working through a number of shard-related issues within DSpace 5 and 
> DSpace 6.
>
>
> https://wiki.duraspace.org/display/~terrywbrady/Statistics+Import+Export+Issues
>
> Once these issues are resolved, it will be interesting to see if your 
> issues persist.
>
> Could you create a DSpace Jira ticket describing the issues you are 
> encountering?
>
> Terry
>
> On Tue, Jan 31, 2017 at 10:58 AM, David Baker <daba...@gmail.com 
> > wrote:
>
>> The Statistics page (Administrative > Statistics) in our DSpace 5.3 
>> instance is only showing 4 months since our site went live (6/9/15 - 
>> 10/19/15):
>>
>>
>>
>> <https://lh3.googleusercontent.com/-kAVwsiVK6vo/WJDZRSxr4mI/ADA/7ECB8W2_c8oJLSVQLsPacc8AzOS6i5csgCLcB/s1600/2017-01-31%2B13_35_01-Statistical%2BSummary.png>
>>
>>
>>
>> I run a nightly spider deletion and optimization on the stats:
>>
>> dspace stats-util -i
>> dspace stats-util -o
>>
>> These commands have both been logging an error for a while.
>>
>> The spider cleaning command runs at 1:00 AM and generates this error:
>>
>> 2017-01-30 01:00:13,872 INFO  org.apache.solr.core.SolrCore @ [statistics
>> ] webapp=/solr path=/select params={q=type:2+AND+id:1=javabin=
>> 2} hits=0 status=0 QTime=14 
>> 2017-01-30 01:00:13,945 INFO  org.apache.solr.handler.admin.
>> CoreAdminHandler @ core create command dataDir=c:
>> /dspace\solr\statistics-2014\data=statistics-2014=CREATE=statistics=javabin=2
>> 2017-01-30 01:00:13,952 WARN 
>>  org.apache.solr.handler.admin.CoreAdminHandler @ Creating a core with 
>> existing name is not allowed
>> 2017-01-30 01:00:13,953 ERROR org.apache.solr.core.SolrCore @ 
>> org.apache.solr.common.SolrException: Core with name 'statistics-2014' 
>> already exists.
>>  at 
>> org.apache.solr.handler.admin.CoreAdminHandler.handleCreateAction(CoreAdminHandler.java:555)
>>  at 
>> org.apache.solr.handler.admin.CoreAdminHandler.handleRequestInternal(CoreAdminHandler.java:199)
>>  at 
>> org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(CoreAdminHandler.java:188)
>>  at 
>> org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
>>  at 
>> org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:729)
>>  at 
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:258)
>>  at 
>> org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>  at 
>> org.dspace.solr.filters.LocalHostRestrictionFilter.doFilter(LocalHostRestrictionFilter.java:50)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
>>  at 
>> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
>>  at 
>> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
>>  at 
>> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
>>  at 
>> org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
>>  at 
>> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
>>  at 
>> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
>>  at 
>> org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:617)
>>  at 
>> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
>>  at 
>> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
>>  at 
>> org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
>>  at 
>> org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
>>  at org.apache.tomcat.util.net
>> .AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2463)
>>  at org.apache.tomcat.util.net
>> .AprEndpoint$SocketProcessor.run(AprEndpoint.java:2452)
>>  at 
>> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
>>  at 
>> java.util.concurrent.ThreadPoolExec

[dspace-tech] Statistics showing are not current

2017-01-31 Thread David Baker



The Statistics page (Administrative > Statistics) in our DSpace 5.3 
instance is only showing 4 months since our site went live (6/9/15 - 
10/19/15):






I run a nightly spider deletion and optimization on the stats:

dspace stats-util -i
dspace stats-util -o

These commands have both been logging an error for a while.

The spider cleaning command runs at 1:00 AM and generates this error:

2017-01-30 01:00:13,872 INFO  org.apache.solr.core.SolrCore @ [statistics] 
webapp=/solr path=/select params={q=type:2+AND+id:1=javabin=2} 
hits=0 status=0 QTime=14 
2017-01-30 01:00:13,945 INFO  org.apache.solr.handler.admin.CoreAdminHandler 
@ core create command dataDir=c:
/dspace\solr\statistics-2014\data=statistics-2014=CREATE=statistics=javabin=2
2017-01-30 01:00:13,952 WARN 
 org.apache.solr.handler.admin.CoreAdminHandler @ Creating a core with 
existing name is not allowed
2017-01-30 01:00:13,953 ERROR org.apache.solr.core.SolrCore @ 
org.apache.solr.common.SolrException: Core with name 'statistics-2014' 
already exists.
 at 
org.apache.solr.handler.admin.CoreAdminHandler.handleCreateAction(CoreAdminHandler.java:555)
 at 
org.apache.solr.handler.admin.CoreAdminHandler.handleRequestInternal(CoreAdminHandler.java:199)
 at 
org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(CoreAdminHandler.java:188)
 at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
 at 
org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:729)
 at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:258)
 at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
 at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
 at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
org.dspace.solr.filters.LocalHostRestrictionFilter.doFilter(LocalHostRestrictionFilter.java:50)
 at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
 at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at 
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:219)
 at 
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106)
 at 
org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502)
 at 
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:142)
 at 
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79)
 at 
org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:617)
 at 
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88)
 at 
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:518)
 at 
org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1091)
 at 
org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:668)
 at 
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2463)
 at 
org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.run(AprEndpoint.java:2452)
 at 
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
 at 
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
 at 
org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
 at java.lang.Thread.run(Thread.java:745)


2017-01-30 01:00:13,955 INFO  org.apache.solr.servlet.SolrDispatchFilter @ 
[admin] webapp=null path=/admin/cores 
params={dataDir=c:/dspace\solr\statistics-2014\data=statistics-2014=CREATE=statistics=javabin=2}
 
status=500 QTime=10 
2017-01-30 01:00:13,955 ERROR org.apache.solr.servlet.SolrDispatchFilter @ 
null:org.apache.solr.common.SolrException: Core with name 'statistics-2014' 
already exists.
 at 
org.apache.solr.handler.admin.CoreAdminHandler.handleCreateAction(CoreAdminHandler.java:555)
 at 
org.apache.solr.handler.admin.CoreAdminHandler.handleRequestInternal(CoreAdminHandler.java:199)
 at 
org.apache.solr.handler.admin.CoreAdminHandler.handleRequestBody(CoreAdminHandler.java:188)
 at 
org.apache.solr.handler.RequestHandlerBase.handleRequest(RequestHandlerBase.java:135)
 at 
org.apache.solr.servlet.SolrDispatchFilter.handleAdminRequest(SolrDispatchFilter.java:729)
 at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:258)
 at 
org.apache.solr.servlet.SolrDispatchFilter.doFilter(SolrDispatchFilter.java:207)
 at 
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:239)
 at 
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)
 at

[dspace-tech] Tomcat crashes/stops when editing/deleting metadata

2015-12-08 Thread David Baker

When we edit metadata on items in a particular collection, the Tomcat 
service crashes/stops. We can replicate the issue by editing an item, 
clicking the Item Metadata tab, and then selecting a dc.subject for 
removal. The crash occurs after clicking the Update button.

DSpace 5.3 on Windows Server 2012

The following is a generated error report from Tomcat 8:

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  Internal Error (sharedRuntime.cpp:834), pid=3476, tid=5676
#  fatal error: exception happened outside interpreter, nmethods and vtable 
stubs at pc 0x01104a10
#
# JRE version: Java(TM) SE Runtime Environment (8.0_45-b15) (build 
1.8.0_45-b15)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.45-b02 mixed mode 
windows-amd64 compressed oops)
# Core dump written. Default location: C:\Program 
Files\apache-tomcat-8.0.23\hs_err_pid3476.mdmp
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---  T H R E A D  ---

Current thread (0x2c81a800):  JavaThread "http-nio-443-exec-8" 
daemon [_thread_in_Java, id=5676, 
stack(0x3381,0x3391)]

Stack: [0x3381,0x3391]
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native 
code)
V  [jvm.dll+0x32b57a]
V  [jvm.dll+0x279873]
V  [jvm.dll+0x27a509]
V  [jvm.dll+0x2717a6]
V  [jvm.dll+0x228bfe]
V  [jvm.dll+0x297d60]
V  [jvm.dll+0x32b408]
C  [ntdll.dll+0x93f1d]
C  [ntdll.dll+0x54897]
C  [ntdll.dll+0x930aa]
C  0x01104a10


---  P R O C E S S  ---

Java Threads: ( => current thread )
  0x2b5bd800 JavaThread "commitScheduler-10-thread-1" 
[_thread_blocked, id=7336, stack(0x3122,0x3132)]
  0x2c823800 JavaThread "commitScheduler-13-thread-1" 
[_thread_blocked, id=7952, stack(0x3437,0x3447)]
  0x2c823000 JavaThread "http-apr-80-exec-11" daemon 
[_thread_blocked, id=8708, stack(0x3427,0x3437)]
  0x2c822000 JavaThread "commitScheduler-16-thread-1" 
[_thread_blocked, id=4964, stack(0x33e1,0x33f1)]
  0x2c81b800 JavaThread "Thread-12" daemon [_thread_in_native, 
id=508, stack(0x3341,0x3351)]
  0x2c81d800 JavaThread "http-nio-443-exec-10" daemon 
[_thread_blocked, id=9504, stack(0x3331,0x3341)]
  0x2c81c000 JavaThread "http-apr-80-exec-10" daemon 
[_thread_blocked, id=5772, stack(0x33b1,0x33c1)]
  0x2c81e800 JavaThread "http-apr-80-exec-9" daemon 
[_thread_blocked, id=3536, stack(0x33a1,0x33b1)]
  0x2c81d000 JavaThread "http-nio-443-exec-9" daemon 
[_thread_blocked, id=5412, stack(0x3391,0x33a1)]
=>0x2c81a800 JavaThread "http-nio-443-exec-8" daemon 
[_thread_in_Java, id=5676, stack(0x3381,0x3391)]
  0x24b05800 JavaThread "http-nio-443-exec-7" daemon 
[_thread_blocked, id=5888, stack(0x3371,0x3381)]
  0x24b07000 JavaThread "http-nio-443-exec-6" daemon 
[_thread_blocked, id=4060, stack(0x3361,0x3371)]
  0x24b02800 JavaThread "http-nio-443-exec-5" daemon 
[_thread_blocked, id=6568, stack(0x3351,0x3361)]
  0x24b03800 JavaThread "http-apr-80-exec-8" daemon 
[_thread_blocked, id=8876, stack(0x3321,0x3331)]
  0x24b05000 JavaThread "http-apr-80-exec-7" daemon 
[_thread_blocked, id=8628, stack(0x142a,0x143a)]
  0x24b01000 JavaThread "http-apr-80-exec-6" daemon 
[_thread_blocked, id=8976, stack(0x141a,0x142a)]
  0x193ad000 JavaThread "http-apr-80-exec-5" daemon 
[_thread_blocked, id=8036, stack(0x32d1,0x32e1)]
  0x193ae800 JavaThread "http-apr-80-exec-4" daemon 
[_thread_blocked, id=7876, stack(0x32c1,0x32d1)]
  0x193ae000 JavaThread "http-apr-80-exec-3" daemon 
[_thread_blocked, id=7080, stack(0x32b1,0x32c1)]
  0x193a9800 JavaThread "http-apr-80-exec-2" daemon 
[_thread_blocked, id=7856, stack(0x32a1,0x32b1)]
  0x193a8800 JavaThread "http-nio-443-exec-4" daemon 
[_thread_blocked, id=6356, stack(0x325f,0x326f)]
  0x193ab800 JavaThread "http-nio-443-exec-3" daemon 
[_thread_blocked, id=7936, stack(0x324f,0x325f)]
  0x193aa000 JavaThread "http-nio-443-exec-2" daemon 
[_thread_blocked, id=6640, stack(0x321f,0x322f)]
  0x193a8000 JavaThread "http-nio-443-exec-1" daemon 
[_thread_blocked, id=7776, stack(0x320f,0x321f)]
  0x193ab000 JavaThread "ajp-apr-8009-AsyncTimeout" daemon 
[_thread_blocked, id=9208,

Re: [dspace-tech] Collection name stays same in breadcrumbs after renaming collection

2015-10-02 Thread David Baker

Thanks, Andrea -- I had already stopped Tomcat for a minute and cleared 
it's cache (C:\Program Files\apache-tomcat-8.0.23\work\Catalina). This took 
care of the problem. Next time I'll try the "Clear cache immediately" 
option within DSpace.

David


On Wednesday, September 30, 2015 at 4:17:19 PM UTC-4, Andrea Schweer wrote:
>
> Hi David, 
>
> On 01/10/15 07:57, David Baker wrote: 
> > We changed the name of one of our collections from "Sophomore Research 
> > Conference Papers" but was changed to just "Sophomore Research 
> > Conference". We're having an issue that items submitted prior to 
> > changing the name of the collection still show the old collection name 
> > in the breadcrumbs -- but only on the HTTP version of the site. In the 
> > following link, you can see that it still shows the old name in the 
> > breadcrumbs: 
> > 
> > http://mcstor.library.milligan.edu/handle/11558/41 
> > 
> > However, for the same item, if you view it on the HTTPS version of the 
> > site, it shows the correct, new name: 
> > 
> > https://mcstor.library.milligan.edu/handle/11558/41 
> > 
> > Has anybody seen this issue? 
>
> Yes, I believe I've seen it too. I'll do another test locally and will 
> report it as a bug (https://jira.duraspace.org/browse/DS) if I can 
> reproduce it. I believe it's due to the caching built into DSpace XMLUI. 
>
> > Site info: 
> > DSpace 5.3 
> > XMLUI Mirage 2 
> > Windows Server 2012 R2 
>
> You should be able to fix the problem without any tomcat outages: 
> * log in to DSpace an administrator 
> * go to the Control Panel (in the Administrative section of the sidebar) 
> * go to the Java Information tab 
> * click on the "Clear cache immediately" link. 
>
> Then your breadcrumbs should sync up. 
>
> cheers, 
> Andrea 
>
> -- 
> Dr Andrea Schweer 
> IRR Technical Specialist, ITS Information Systems 
> The University of Waikato, Hamilton, New Zealand 
> +64-7-837 9120 
>
>

-- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Collection name stays same in breadcrumbs after renaming collection

2015-09-30 Thread David Baker

We changed the name of one of our collections from "Sophomore Research 
Conference Papers" but was changed to just "Sophomore Research Conference". 
We're having an issue that items submitted prior to changing the name of 
the collection still show the old collection name in the breadcrumbs -- but 
only on the HTTP version of the site. In the following link, you can see 
that it still shows the old name in the breadcrumbs:

http://mcstor.library.milligan.edu/handle/11558/41

However, for the same item, if you view it on the HTTPS version of the 
site, it shows the correct, new name:

https://mcstor.library.milligan.edu/handle/11558/41

Has anybody seen this issue? 

Site info:
DSpace 5.3
XMLUI Mirage 2
Windows Server 2012 R2

Thanks,
David Baker
Milligan College Libraries

-- 
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 post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at http://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

[dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

[dspace-tech] Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin

Re: [dspace-tech] Statistics showing are not current

[dspace-tech] Statistics showing are not current

[dspace-tech] Tomcat crashes/stops when editing/deleting metadata

Re: [dspace-tech] Collection name stays same in breadcrumbs after renaming collection

[dspace-tech] Collection name stays same in breadcrumbs after renaming collection

10 matches

Site Navigation

Mail list logo

Footer information