Christine, Changing the time entries for search_indexer appears to have fixed the issue. Thank you for the help!
-Alan Huebschen Brookens Library Information Systems (217) 206-7115 From: [email protected] <[email protected]> On Behalf Of Christine Di Bella Sent: Wednesday, March 13, 2019 3:22 PM To: Archivesspace Users Group <[email protected]> Subject: Re: [Archivesspace_Users_Group] Possible issue with daylight savings time Hi Alan, (Since it sounds like a few people may be helped by this answer, I'm answering here instead of on the message you sent to [email protected]<mailto:[email protected]>. If the explanation below doesn't resolve your issue, I'll put that tech support ticket through for you. Several users have reported this problem to us in various ways. This error isn't unique to ArchivesSpace, but ArchivesSpace can be affected by it if you have timestamps in the hour that never happened (between 2 and 3am) in the search_indexer row in the user table. We're not sure how this would happen, but maybe if your server got restarted around that time? If you get rid of those errant times that problem should go away. We have also heard of people having an issue with their MySQL connector when they upgrade. You'll want to be sure the MySQL connector you are using is for 7 and not 8. It doesn't sounds like that's your issue, but one more thing to check just in case. Christine Christine Di Bella ArchivesSpace Program Manager [email protected]<mailto:[email protected]> 800.999.8558 x2905 678-235-2905 cdibella13 (Skype) [ASpaceOrgHomeMedium] From: [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> On Behalf Of Huebschen, Alan M Sent: Wednesday, March 13, 2019 9:59 AM To: Archivesspace Users Group <[email protected]<mailto:[email protected]>> Subject: [Archivesspace_Users_Group] Possible issue with daylight savings time Good morning, I'm not entirely sure, but it appears that our ArchivesSpace instance has stopped working due to the recent DST change. I'm still getting the same error after updating all packages on the system as well. "NoMethodError: undefined method `getSQLState' for java.lang.IllegalArgumentException: HOUR_OF_DAY: 2 -> 3:Java::JavaLang::IllegalArgumentException Did you mean? getClass" Has anyone encountered this error before? How did you fix it? -Alan Huebschen Brookens Library Information Systems (217) 206-7115
_______________________________________________ Archivesspace_Users_Group mailing list [email protected] http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
