Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2023-03-28 Thread Blake Carver
It looks like there's a bad date hiding somewhere else. It's ALMOST always in 
the user table, but not always always.

Try something like:

https://gist.github.com/Blake-/d493da28be5554a49a3a3835bbd98f05

https://gist.github.com/Blake-/3c133ec7e42d039d85afbad5b3089eb4

You can update that year-month-day on those and see if you can find something.

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Philip 
Webster 
Sent: Tuesday, March 28, 2023 7:07 AM
To: 'Archivesspace Users Group' 

Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2


Hi,

Ran into this yesterday, and I ran the SQL UPDATE query – I got a report of 4 
rows affected, but now our AS instance won’t start up due to initialisation 
errors. We are getting the same error as before.



Here is the console interaction for SQL:

mysql> UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Query OK, 4 rows affected (0.01 sec)

Rows matched: 4  Changed: 4  Warnings: 0



Here is the stack trace (first few lines):

Mar 28, 2023 12:00:08 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log

WARNING: ERROR: initialization failed

org.jruby.rack.RackInitializationException: Java::JavaSql::SQLException: 
HOUR_OF_DAY: 1 -> 2

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:129)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:97)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:89)

   from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:63)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:73)

from 
com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(com/mysql/cj/jdbc/exceptions/SQLExceptionsMapping.java:85)

from 
com.mysql.cj.jdbc.result.ResultSetImpl.getTimestamp(com/mysql/cj/jdbc/result/ResultSetImpl.java:947)

from java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)

from 
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456)

from 
org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther0:getTimestamp(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.timestamp_convert(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from org.jruby.RubyMethod.call(org/jruby/RubyMethod.java:123)

from 
org.jruby.RubyMethod$INVOKER$i$call.call(org/jruby/RubyMethod$INVOKER$i$call.gen)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther9:call(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.process_result_set(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from org.jruby.RubyArray.each(org/jruby/RubyArray.java:1809)



This is affecting a production service, so I may have to raise a technical 
support request if there isn’t a community solution.



Regards,



Philip Webster

The University of Sheffield





From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: 27 March 2023 09:07
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2



A reminder to anyone in Europe, whose clocks changed this weekend, to check 
your ArchivesSpace system. If everything but the home page isn't working, try 
the fix below...



Andrew.





On 12/03/2023 19:57, Blake Carver wrote:



It's that time of year again! If ArchivesSpace isn't working for you today, 
check the logs... If you see

DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2



Try this and restart, that'll probably do the trick.



UPDATE user set user_mtime = NOW(), system_mtime=NOW();






___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2023-03-28 Thread Philip Webster
Hi,

Ran into this yesterday, and I ran the SQL UPDATE query – I got a report of 4 
rows affected, but now our AS instance won’t start up due to initialisation 
errors. We are getting the same error as before.

 

Here is the console interaction for SQL:

mysql> UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Query OK, 4 rows affected (0.01 sec)

Rows matched: 4  Changed: 4  Warnings: 0

 

Here is the stack trace (first few lines):

Mar 28, 2023 12:00:08 PM 
org.eclipse.jetty.server.handler.ContextHandler$Context log

WARNING: ERROR: initialization failed

org.jruby.rack.RackInitializationException: Java::JavaSql::SQLException: 
HOUR_OF_DAY: 1 -> 2

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:129)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:97)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:89)

   from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:63)

from 
com.mysql.cj.jdbc.exceptions.SQLError.createSQLException(com/mysql/cj/jdbc/exceptions/SQLError.java:73)

from 
com.mysql.cj.jdbc.exceptions.SQLExceptionsMapping.translateException(com/mysql/cj/jdbc/exceptions/SQLExceptionsMapping.java:85)

from 
com.mysql.cj.jdbc.result.ResultSetImpl.getTimestamp(com/mysql/cj/jdbc/result/ResultSetImpl.java:947)

from java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)

from 
org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:456)

from 
org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:317)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther0:getTimestamp(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.timestamp_convert(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:685)

from org.jruby.RubyMethod.call(org/jruby/RubyMethod.java:123)

from 
org.jruby.RubyMethod$INVOKER$i$call.call(org/jruby/RubyMethod$INVOKER$i$call.gen)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.invokeOther9:call(home/archivesspace/archivesspace/gems/gems/sequel_minus_5_dot_9_dot_0/lib/sequel/adapters//home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from 
home.archivesspace.archivesspace.gems.gems.sequel_minus_5_dot_9_dot_0.lib.sequel.adapters.jdbc.process_result_set(/home/archivesspace/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:793)

from org.jruby.RubyArray.each(org/jruby/RubyArray.java:1809)

 

This is affecting a production service, so I may have to raise a technical 
support request if there isn’t a community solution.

 

Regards,

 

Philip Webster

The University of Sheffield

 

 

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 On Behalf Of Andrew 
Morrison
Sent: 27 March 2023 09:07
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

 

A reminder to anyone in Europe, whose clocks changed this weekend, to check 
your ArchivesSpace system. If everything but the home page isn't working, try 
the fix below...

 

Andrew.

 

 

On 12/03/2023 19:57, Blake Carver wrote:

 

It's that time of year again! If ArchivesSpace isn't working for you today, 
check the logs... If you see

DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

 

Try this and restart, that'll probably do the trick. 

 

UPDATE user set user_mtime = NOW(), system_mtime=NOW();

 

 

 

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2023-03-27 Thread Andrew Morrison
A reminder to anyone in Europe, whose clocks changed this weekend, to 
check your ArchivesSpace system. If everything but the home page isn't 
working, try the fix below...



Andrew.



On 12/03/2023 19:57, Blake Carver wrote:


It's that time of year again! If ArchivesSpace isn't working for you 
today, check the logs... If you see

DatabaseError: Java::JavaSql::SQLException:HOUR_OF_DAY: 1 -> 2

Try this and restart, that'll probably do the trick.

UPDATE user set user_mtime = NOW(), system_mtime=NOW();

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2023-03-12 Thread Blake Carver

It's that time of year again! If ArchivesSpace isn't working for you today, 
check the logs... If you see
DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

Try this and restart, that'll probably do the trick.

UPDATE user set user_mtime = NOW(), system_mtime=NOW();




From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, March 28, 2022 11:05 AM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Thanks Blake. It looks like the one-liner (UPDATE user set user_mtime = NOW(), 
system_mtime=NOW();) did the trick. I'll remember that for future seasonal 
changes.

Cheers
Scott



==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: 28 March 2022 16:00
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email 
is genuine and the content is safe.
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2022-March/009092.html

You can probably just:
UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Though might need to:

-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- DATE
update `date` set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- USER
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='SOME_OTHER_USER';



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, March 28, 2022 10:55 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Little bit more information- running v.2.8.1 and MariaDB 5.5.68.

Time complained about is eg

Time: 2022-03-28 15:46:28 +0100



So basically any startup time + 0100 (I'm not sure which table it would be 
writing to there), which puts it into the future- no longer blaming users! I am 
guessing that a reindex won't solve this; my time_zone settings are unchanged.


MariaDB [(none)]> SELECT @@global.time_zone, @@session.time_zone;

++-+

| @@global.time_zone | @@session.time_zone |

++-+

| SYSTEM | SYSTEM  |

++-+

1 row in set (0.00 sec)


Cheers

Scott


Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

--- System

jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.322-b06 on 1.8.0_322-b06 +jit [linux-x86_64]

Time: 2022-03-28 15:46:28 +0100

Server: jetty/8.1.5.v20120716

jruby.home: uri:classloader://META-INF/jruby.home


--- Context Init Parameters:

jruby.max.runtimes = 1

jruby.min.runtimes = 1

public.root = /

rack.env = production


--- Backtrace

Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

   raise_error at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/misc.rb:419

 statement at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:677

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:239

  hold at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/connection_pool/threaded.rb:87

   synchronize at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/connecting.rb:270

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:238

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:1082

fetch_rows at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:726

 with_sql_each at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:934

with_sql_first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:944

single_record! at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:700

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:243

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/plugins.rb:33

[] at 
/apps/archivesspace/gems/gems/sequ

Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2022-03-28 Thread RENTON Scott
Thanks Blake. It looks like the one-liner (UPDATE user set user_mtime = NOW(), 
system_mtime=NOW();) did the trick. I'll remember that for future seasonal 
changes.

Cheers
Scott



==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Blake 
Carver 
Sent: 28 March 2022 16:00
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email 
is genuine and the content is safe.
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2022-March/009092.html

You can probably just:
UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Though might need to:

-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- DATE
update `date` set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- USER
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='SOME_OTHER_USER';



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, March 28, 2022 10:55 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Little bit more information- running v.2.8.1 and MariaDB 5.5.68.

Time complained about is eg

Time: 2022-03-28 15:46:28 +0100



So basically any startup time + 0100 (I'm not sure which table it would be 
writing to there), which puts it into the future- no longer blaming users! I am 
guessing that a reindex won't solve this; my time_zone settings are unchanged.


MariaDB [(none)]> SELECT @@global.time_zone, @@session.time_zone;

++-+

| @@global.time_zone | @@session.time_zone |

++-+

| SYSTEM | SYSTEM  |

++-+

1 row in set (0.00 sec)


Cheers

Scott


Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

--- System

jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.322-b06 on 1.8.0_322-b06 +jit [linux-x86_64]

Time: 2022-03-28 15:46:28 +0100

Server: jetty/8.1.5.v20120716

jruby.home: uri:classloader://META-INF/jruby.home


--- Context Init Parameters:

jruby.max.runtimes = 1

jruby.min.runtimes = 1

public.root = /

rack.env = production


--- Backtrace

Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

   raise_error at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/misc.rb:419

 statement at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:677

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:239

  hold at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/connection_pool/threaded.rb:87

   synchronize at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/connecting.rb:270

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:238

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:1082

fetch_rows at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:726

 with_sql_each at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:934

with_sql_first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:944

single_record! at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:700

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:243

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/plugins.rb:33

[] at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/base.rb:214

create_system_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:

 create_hidden_system_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:21

create_search_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:306

   at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.wa

Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2022-03-28 Thread Blake Carver
http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/2022-March/009092.html

You can probably just:
UPDATE user set user_mtime = NOW(), system_mtime=NOW();

Though might need to:

-- AO
update archival_object set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- DATE
update `date` set create_time = '2022-03-13 06:00:00', system_mtime = 
'2022-03-13 06:00:00'
where create_time >= '2022-03-13 02:00:00' and create_time <= '2022-03-13 
03:00:00';
-- USER
UPDATE user set user_mtime = NOW(), system_mtime=NOW() where 
username='SOME_OTHER_USER';



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: Monday, March 28, 2022 10:55 AM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Little bit more information- running v.2.8.1 and MariaDB 5.5.68.

Time complained about is eg

Time: 2022-03-28 15:46:28 +0100



So basically any startup time + 0100 (I'm not sure which table it would be 
writing to there), which puts it into the future- no longer blaming users! I am 
guessing that a reindex won't solve this; my time_zone settings are unchanged.


MariaDB [(none)]> SELECT @@global.time_zone, @@session.time_zone;

++-+

| @@global.time_zone | @@session.time_zone |

++-+

| SYSTEM | SYSTEM  |

++-+

1 row in set (0.00 sec)


Cheers

Scott


Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

--- System

jruby 9.2.12.0 (2.5.7) 2020-07-01 db01a49ba6 OpenJDK 64-Bit Server VM 
25.322-b06 on 1.8.0_322-b06 +jit [linux-x86_64]

Time: 2022-03-28 15:46:28 +0100

Server: jetty/8.1.5.v20120716

jruby.home: uri:classloader://META-INF/jruby.home


--- Context Init Parameters:

jruby.max.runtimes = 1

jruby.min.runtimes = 1

public.root = /

rack.env = production


--- Backtrace

Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 1 -> 2

   raise_error at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/misc.rb:419

 statement at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:677

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:239

  hold at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/connection_pool/threaded.rb:87

   synchronize at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/database/connecting.rb:270

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:238

   execute at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:1082

fetch_rows at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/adapters/jdbc.rb:726

 with_sql_each at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:934

with_sql_first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:944

single_record! at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:700

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/dataset/actions.rb:243

 first at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/plugins.rb:33

[] at 
/apps/archivesspace/gems/gems/sequel-5.9.0/lib/sequel/model/base.rb:214

create_system_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:

 create_hidden_system_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:21

create_search_user at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:306

   at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:330

 at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/lib/bootstrap_access_control.rb:1

   require at org/jruby/RubyKernel.java:974

  require_relative at org/jruby/RubyKernel.java:1002

  ArchivesSpaceService at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:195

  open at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:105

   transaction at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:69


Re: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2022-03-28 Thread RENTON Scott
db.rb:101

  open at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/model/db.rb:426

  ArchivesSpaceService at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:194

 configure at 
/apps/archivesspace/gems/gems/sinatra-2.0.5/lib/sinatra/base.rb:1426

   at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:79

 at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/app/main.rb:39

   require at org/jruby/RubyKernel.java:974

   require at 
uri:classloader:/META-INF/jruby.home/lib/ruby/stdlib/rubygems/core_ext/kernel_require.rb:54

 at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:4

 instance_eval at org/jruby/RubyBasicObject.java:2622

initialize at 
uri:classloader:/vendor/rack-2.2.3/rack/builder.rb:125

 at 
/apps/solr/data/tmp/jetty-0.0.0.0-8089-backend.war-_-any-/webapp/WEB-INF/config.ru:1

  start_server at launcher/launcher.rb:92

  main at launcher/launcher.rb:157

 at launcher/launcher.rb:261



==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of RENTON 
Scott 
Sent: 28 March 2022 15:13
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: [Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Hi folks

I've got the

--- Backtrace Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 
1 -> 2 (https://archivesspace.atlassian.net/browse/ANW-1229)

issue which I see from threads can happen after Daylight Saving. I've never 
seen it before, but it looks like our users have put some data in today that's 
thrown it out.

I've found a few fixes talked about, but I wanted to check with yourselves to 
see if there was an official fix that I could safely run.

I've taken the system down temporarily.

Cheers
Scott


==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

The University of Edinburgh is a charitable body, registered in Scotland, with 
registration number SC005336. Is e buidheann carthannais a th’ ann an Oilthigh 
Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group


[Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

2022-03-28 Thread RENTON Scott
Hi folks

I've got the

--- Backtrace Sequel::DatabaseError: Java::JavaSql::SQLException: HOUR_OF_DAY: 
1 -> 2 (https://archivesspace.atlassian.net/browse/ANW-1229)

issue which I see from threads can happen after Daylight Saving. I've never 
seen it before, but it looks like our users have put some data in today that's 
thrown it out.

I've found a few fixes talked about, but I wanted to check with yourselves to 
see if there was an official fix that I could safely run.

I've taken the system down temporarily.

Cheers
Scott


==

Scott Renton

Digital Library Development & Systems

Floor F East

Argyle House

515219

The University of Edinburgh is a charitable body, registered in Scotland, with 
registration number SC005336. Is e buidheann carthannais a th' ann an Oilthigh 
Dhùn Èideann, clàraichte an Alba, àireamh clàraidh SC005336.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group