Re: [Archivesspace_Users_Group] Odd permissions problem with resources

[Dyson-Smith, Bridger]

Hi Nancy,
Thanks for the response. I'll take a closer look at our logs and see if we're 
experiencing those errors. I don't know if an upgrade to v2.6 is in the 
immediate cards for us, but we'll have to consider it if we can't fix this 
problem.

Best wishes,
Bridger

Get Outlook for Android


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of Kennedy, 
Nancy 
Sent: Monday, July 27, 2020 12:53:40 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Odd permissions problem with resources


[External Email]

Hi Bridger -
Just wanted to say that when we were on 2.5, we had an issue like this pop up.  
For the same search, we would see different results for some users.  Admin and 
repo managers were able to search for the specific record, but not others. This 
was in the staff interface (we don't use the pui).

We were working on moving up to 2.6 at the time, and our problem did go away 
after moving into 2.6.  Here are details from my notes, in case it helps you --

That error message points to an issue that was resolved for v2.6.0. So, you may 
not be on v2.6.0 OR your plugin that overrides the listing view is not up to 
date with v2.6.0:

I, [2019-09-19T11:41:48.479388 
#921]
 INFO -- : Rendered 
/opt/archivesspace/plugins/local/frontend/views/search/_listing.html.erb 
(1844.8ms)

I'd recommend a) be on v2.6.0 (if not) and b) update 
plugins/local/frontend/views/search/_listing.html.erb to be up to date with 
v2.6.0 with your edits.



Nancy Kennedy
Smithsonian Institution
kenne...@si.edu


From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Dyson-Smith, Bridger 
Sent: Monday, July 27, 2020 12:25 PM
To: archivesspace_users_group@lyralists.lyrasis.org 

Subject: Re: [Archivesspace_Users_Group] Odd permissions problem with resources

External Email - Exercise Caution

Mark -

Thanks for the response! That was a good thought, but unfortunately I
checked and the resources are not suppressed. I really appreciate the
suggestion.

Best,
Bridger


On Mon, 2020-07-27 at 13:48 +, Custer, Mark wrote:
> Bridger,
>
> Regarding the first issue, are those two resources "suppressed" by
> any chance?  A suppressed record cannot be seen in the staff
> interface by most users unless they also have the ability to view
> suppressed records.  Since you mentioned that you could see it as an
> admin user, that's my first guess.
>
> Mark
>
>
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of
> Dyson-Smith, Bridger 
> Sent: Monday, July 27, 2020 9:30 AM
> To: Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> Subject: [Archivesspace_Users_Group] Odd permissions problem with
> resources
>
> Hi all -
>
> We're experiencing a strange issue with at least two of our
> resources: they are available in the staff UI for some admin-level
> users (me),  but not others. They're  unavailable in the public UI
> for everyone (except very briefly during a reindex - once the reindex
> is finished, they're not longer available in the public UI).
>
> Any suggestions for where to start trying to determine a solution?
> Both resources are published.
>
> Thanks in advance for your time. And apologies if you're seeing this
> twice - I had emailed the Google Group last week.
>
> Best,
> Bridger
> --
> University of Tennessee Libraries
> Digital Initiatives
>
>
>
> Get Outlook for Android
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_groupdata=02%7C01%7CKennedyN%40si.edu%7Cd1cd5b8bcba0455b5a6408d83249b87c%7C989b5e2a14e44efe93b78cdd5fc5d11c%7C0%7C0%7C637314639503226572sdata=M7m7klG4edzOwumsObFJCiol15IOc8FxkvuQA3%2Bk5EU%3Dreserved=0
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
https://nam02.safelinks.protection.outlook.com/?url=http%3A%2F%2Flyralists.lyrasis.org%2Fmailman%2Flistinfo%2Farchivesspace_users_groupdata=02%7C01%7CKennedyN%40si.edu%7Cd1cd5b8bcba0455b5a6408d83249b87c%7C989b5e2a14e44efe93b78cdd5fc5d11c%7C0%7C0%7C637314639503236569sdata=WZHRNz0OIga2D%2BggMKTklBUaC%2F4urwCOeY10tSxs1Fc%3Dreserved=0
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org

Re: [Archivesspace_Users_Group] Odd permissions problem with resources

[Dyson-Smith, Bridger]

Mark - 

Thanks for the response! That was a good thought, but unfortunately I
checked and the resources are not suppressed. I really appreciate the
suggestion.

Best,
Bridger


On Mon, 2020-07-27 at 13:48 +, Custer, Mark wrote:
> Bridger,
> 
> Regarding the first issue, are those two resources "suppressed" by
> any chance?  A suppressed record cannot be seen in the staff
> interface by most users unless they also have the ability to view
> suppressed records.  Since you mentioned that you could see it as an
> admin user, that's my first guess. 
> 
> Mark
> 
> 
> From: archivesspace_users_group-boun...@lyralists.lyrasis.org <
> archivesspace_users_group-boun...@lyralists.lyrasis.org> on behalf of
> Dyson-Smith, Bridger 
> Sent: Monday, July 27, 2020 9:30 AM
> To: Archivesspace Users Group <
> archivesspace_users_group@lyralists.lyrasis.org>
> Subject: [Archivesspace_Users_Group] Odd permissions problem with
> resources
>  
> Hi all - 
> 
> We're experiencing a strange issue with at least two of our
> resources: they are available in the staff UI for some admin-level
> users (me),  but not others. They're  unavailable in the public UI
> for everyone (except very briefly during a reindex - once the reindex
> is finished, they're not longer available in the public UI). 
> 
> Any suggestions for where to start trying to determine a solution?
> Both resources are published. 
> 
> Thanks in advance for your time. And apologies if you're seeing this
> twice - I had emailed the Google Group last week. 
> 
> Best, 
> Bridger 
> --
> University of Tennessee Libraries 
> Digital Initiatives
> 
> 
> 
> Get Outlook for Android
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Odd permissions problem with resources

[Dyson-Smith, Bridger]

Hi all -

We're experiencing a strange issue with at least two of our resources: they are 
available in the staff UI for some admin-level users (me),  but not others. 
They're  unavailable in the public UI for everyone (except very briefly during 
a reindex - once the reindex is finished, they're not longer available in the 
public UI).

Any suggestions for where to start trying to determine a solution? Both 
resources are published.

Thanks in advance for your time. And apologies if you're seeing this twice - I 
had emailed the Google Group last week.

Best,
Bridger
--
University of Tennessee Libraries
Digital Initiatives



Get Outlook for Android
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ArchivesSpace 6th Annual Member Forum is one week away!

[Jessica Crouch]

[A picture containing woman, holding, standing  Description automatically 
generated]



There is still time to 
register
 for next week’s 6th Annual ArchivesSpace Member Forum!



Just as in previous years, this will be a free opportunity for staff from 
ArchivesSpace member institutions to meet and share information with each other 
and the program team about all things ArchivesSpace.  Unlike previous years, 
ArchivesSpace will be holding its sixth Annual Member Forum virtually, on 
August 3-7, 2020, from 12pm-3pm ET each day via Zoom.

This free event is a chance for ArchivesSpace members to come together to 
highlight the work they are doing in ArchivesSpace, show off new plugins or 
tools they’ve developed, and attend workshops and trainings on a variety of 
topics. As with our previous Annual Member Forums, it is being held in 
conjunction with the Society of American Archivists annual meeting, but it is 
not part of SAA and does not require registration for the SAA Annual Meeting.



When:

Presentations and breakout discussions will be held on August 3-4, 2020 from 
12pm-3pm ET, and all individuals from ArchivesSpace member institutions are 
welcome to attend some or all of the sessions on these days.  Small workshops 
covering specific elements of the ArchivesSpace application will be offered 
August 5-7, 2020 from 12pm-3pm ET.  These workshops will be limited in 
capacity. Registrations for each day are separate and you must register for 
individually for all days you are interested in attending.


Where:



All online via Zoom, with opportunities to join via computer or phone.


Who Can Attend:
The ArchivesSpace Member Forum is open to individuals from ArchivesSpace member 
institutions only. To register, you must use an institutional email address 
associated with an ArchivesSpace member institution.  Registrations using 
personal email addresses and addresses associated with non-member institutions 
will not be accepted.  This means that events with limited capacity may fill 
before you are able to correct your registration.
Online registration:  
https://archivesspace.atlassian.net/wiki/spaces/ADC/pages/1422819333/ArchivesSpace+Member+Forum+2020

Registrations for each day of the Forum are separate. You will need to register 
for each day you are interested in attending to guarantee your spot. 
Registration for each activity is linked above the session in the agenda.  
Workshop attendance is limited.
Discussion sessions on Tuesday, August 4, will occur in two separate zoom 
rooms.  You must register for both Zoom Room A and B if you want to attend 
discussions in both rooms.
The number of registrations available for the workshops on August 5-7 is 
limited.  The total number of attendees is noted next to the registration. To 
give as many people as possible a chance to attend, you may register for only 
one workshop.

We will be recording the sessions on August 3, 2020 but will not be recording 
discussions or workshops. We encourage you to dip in and out of the live 
programs on August 3-4, 2020 as much as you can.


Please feel free to contact ArchivesSpace Community Engagement Coordinator 
Jessica Crouch (jessica.cro...@lyrasis.org) 
with questions. We look forward to seeing many of you there!

Jessica Dowd Crouch
Community Engagement Coordinator for ArchivesSpace
jessica.cro...@lyrasis.org
[page1image482511520]

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

Re: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed"

[Mark Cyzyk]

Hi Lora!

Sorry, I should have mentioned this, I'm running against MariaDB:

MariaDB from Ubuntu 20.04 repository, version 10.3

(We're running against MariaDB here in Prod and Dev on CentOS 7.)

Thanks!

Mark

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.

On 7/27/20 11:22 AM, Lora Woodford wrote:


Hiya Mark!

So, if the issue were a db schema mismatch, you’d likely get an error 
message explaining that.  Something like “Schema Info Mismatch. 
Expected #{expected schema version}, received #{your schema version} 
for ASPACE version #{version you’re trying to run}.”



What version of mysql (if mysql?) are you using?  I’ve seen similar 
issues with folks attempting to run against MySql 8. Can you try 5.7?


Lora

*From: * on 
behalf of Mark Cyzyk 
*Reply-To: *"mcy...@jhu.edu" , Archivesspace Users 
Group 

*Date: *Monday, July 27, 2020 at 10:55 AM
*To: *"archivesspace_users_group@lyralists.lyrasis.org" 

*Subject: *[Archivesspace_Users_Group] ASpace upgrade: "Connection to 
backend failed"



All,

I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant 
box before upgrading for real.


I was having problems running the /scripts/database-setup.sh migration 
script via my Vagrant file, and, as with Vagrant, Ansible, etc. found 
myself spending lots of time troubleshooting the script I've written 
to install the software, when I could have just installed the software!


So now I have my Vagrant box up and running, I SSH in and run 
/scripts/database-setup.sh without any problem.


BUT now that I've kicked this can down the road, the next issue is:

When I go to boot up ASpace, I end up with the following error:

INFO: DEBUG: resetting rack response due exception
E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004:
Connection to backend failed (http://www.w3.org/TR/html4/loose.dtd;
>


I read that if the schema in the DB does not match the schema in the 
ASpace codebase, the backend will not start.


And yet, the setup-database.sh migration script ran without error, so 
at this point the schemas should be in sync.


Any advice on how to get the backend up and running greatly appreciated,

Mark

--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu  
Verba volant, scripta manent.


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

Re: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed"

[Lora Woodford]

Hiya Mark!

So, if the issue were a db schema mismatch, you’d likely get an error message 
explaining that.  Something like “Schema Info Mismatch. Expected #{expected 
schema version}, received #{your schema version} for ASPACE version #{version 
you’re trying to run}.”

What version of mysql (if mysql?) are you using?  I’ve seen similar issues with 
folks attempting to run against MySql 8.  Can you try 5.7?

Lora

From:  on behalf of 
Mark Cyzyk 
Reply-To: "mcy...@jhu.edu" , Archivesspace Users Group 

Date: Monday, July 27, 2020 at 10:55 AM
To: "archivesspace_users_group@lyralists.lyrasis.org" 

Subject: [Archivesspace_Users_Group] ASpace upgrade: "Connection to backend 
failed"


All,

I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant box 
before upgrading for real.

I was having problems running the /scripts/database-setup.sh migration script 
via my Vagrant file, and, as with Vagrant, Ansible, etc. found myself spending 
lots of time troubleshooting the script I've written to install the software, 
when I could have just installed the software!

So now I have my Vagrant box up and running, I SSH in and run 
/scripts/database-setup.sh without any problem.

BUT now that I've kicked this can down the road, the next issue is:

When I go to boot up ASpace, I end up with the following error:
INFO: DEBUG: resetting rack response due exception
E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004: Connection to 
backend failed (http://www.w3.org/TR/html4/loose.dtd;>

I read that if the schema in the DB does not match the schema in the ASpace 
codebase, the backend will not start.

And yet, the setup-database.sh migration script ran without error, so at this 
point the schemas should be in sync.

Any advice on how to get the backend up and running greatly appreciated,

Mark


--

<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>

Mark Cyzyk, M.A., M.L.S.

Library Applications Group

The Sheridan Libraries

The Johns Hopkins University

mcy...@jhu.edu



Verba volant, scripta manent.
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] ASpace upgrade: "Connection to backend failed"

[Mark Cyzyk]

All,

I'm trying to practice upgrading ASpace (2.5.1 --> 2.8.0) in a Vagrant 
box before upgrading for real.


I was having problems running the /scripts/database-setup.sh migration 
script via my Vagrant file, and, as with Vagrant, Ansible, etc. found 
myself spending lots of time troubleshooting the script I've written to 
install the software, when I could have just installed the software!


So now I have my Vagrant box up and running, I SSH in and run 
/scripts/database-setup.sh without any problem.


BUT now that I've kicked this can down the road, the next issue is:

When I go to boot up ASpace, I end up with the following error:

   INFO: DEBUG: resetting rack response due exception
   E, [2020-07-25T15:57:06.898049 #38438] ERROR -- : Thread-2004:
   Connection to backend failed (http://www.w3.org/TR/html4/loose.dtd;>


I read that if the schema in the DB does not match the schema in the 
ASpace codebase, the backend will not start.


And yet, the setup-database.sh migration script ran without error, so at 
this point the schemas should be in sync.


Any advice on how to get the backend up and running greatly appreciated,

Mark

--
<><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><>
Mark Cyzyk, M.A., M.L.S.
Library Applications Group
The Sheridan Libraries
The Johns Hopkins University
mcy...@jhu.edu

Verba volant, scripta manent.

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

Re: [Archivesspace_Users_Group] Odd permissions problem with resources

[Custer, Mark]

Bridger,

Regarding the first issue, are those two resources "suppressed" by any chance?  
A suppressed record cannot be seen in the staff interface by most users unless 
they also have the ability to view suppressed records.  Since you mentioned 
that you could see it as an admin user, that's my first guess.

Mark



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
 on behalf of 
Dyson-Smith, Bridger 
Sent: Monday, July 27, 2020 9:30 AM
To: Archivesspace Users Group 
Subject: [Archivesspace_Users_Group] Odd permissions problem with resources

Hi all -

We're experiencing a strange issue with at least two of our resources: they are 
available in the staff UI for some admin-level users (me),  but not others. 
They're  unavailable in the public UI for everyone (except very briefly during 
a reindex - once the reindex is finished, they're not longer available in the 
public UI).

Any suggestions for where to start trying to determine a solution? Both 
resources are published.

Thanks in advance for your time. And apologies if you're seeing this twice - I 
had emailed the Google Group last week.

Best,
Bridger
--
University of Tennessee Libraries
Digital Initiatives



Get Outlook for 
Android
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group