[Archivesspace_Users_Group] : HOUR_OF_DAY: 1 -> 2

Blake Carver blake.carver at lyrasis.org
Tue Mar 28 07:15:05 EDT 2023


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-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> on behalf of Philip Webster <philip.webster at sheffield.ac.uk>
Sent: Tuesday, March 28, 2023 7:07 AM
To: 'Archivesspace Users Group' <archivesspace_users_group at lyralists.lyrasis.org>
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-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Andrew Morrison
Sent: 27 March 2023 09:07
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
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();






-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20230328/00dd5058/attachment.html>


More information about the Archivesspace_Users_Group mailing list