Brittany, Thanks for getting in touch. I am forwarding your query on to the CollectionSpace talk list, where a member of our development team should be able to offer some assistance. Thanks, Megan Megan Forbes CollectionSpace Community Outreach and Support Manager megan.forbes@lyrasis.org 800.999.8558 x 2917 Main 917.267.9676 Cell meganbforbes Skype ________________________________________ From: collectionspace@lyrasis.org <collectionspace@lyrasis.org> on behalf of www.collectionspace.org <collectionspace@lyrasis.org> Sent: Thursday, June 5, 2014 1:44 PM To: Megan Forbes Subject: Form submission from: Contact Us Name: Brittany Holliss E-mail: bholliss@miamuseum.ca Subject: Cleared Cache Question or comment: I had previously had an issue where while saving a Media record, I was kicked out of the account an unable to log back in due to an error message reading, "PageBuilder was not able to retrieve login information and user permissions: error". I thought that if I cleared my browser cache this might help, but then I would get a message through Google Chrome saying, "Google Chrome could not connect to ec2-23-20-211-6.compute-1.amazonaws.com:8180" If anyone has advice on how to get back access to my admin account that would be fantastic. Thanks! Best, Brittany

Hi Brittany, Thanks for writing with this problem report. We've encountered that "PageBuilder was not able to retrieve login information and user permissions: error" message before. This usually means that the part of CollectionSpace that runs in your web browser can't communicate with the CollectionSpace server. That can be due to: - Some network connectivity issue (on your wireless or wired network, or between your network and the one on which your serveris running), in cases where the CollectionSpace server is running on a different machine than yours. - Some problem that's making the CollectionSpace server unresponsive. The latter can, in turn, can be due to: - One or more long-running database queries, often resulting from complex searches, that are tying up the server and making it unresponsive. If this is the case, typically the server will again become responsive after one or more of those queries are completed (or when the application code that is waiting for results from these queries gives up and times out). (There are also some fixes for these types of situations in the upcoming CollectionSpace Release 4.1: http://wiki.collectionspace.org/display/collectionspace/Release+4.1) - A serious error condition, such as the server running out of memory, for instance. In both instances, the quickest way to attempt to restore your ability to work with CollectionSpace is to restart the server, by shutting it down and starting it back up again. Unsaved work on your part or others, if any, will be lost; typically this involves unsaved changes on a single record. To restart CollectionSpace, you - or anyone else in a system administration role with the privileges to do so - can follow the "Server Shutdown" and "Server Startup" instructions linked from: http://wiki.collectionspace.org/display/DOC/Reference+Information Regarding the issue when attempting to clear caches in Chrome, that may be separate and generic to Chrome. One possible explanation and fix - that may or may not apply to your situation, but can easily be tried - is discussed here: http://www.ghacks.net/2010/06/26/fix-oops-google-chrome-could-not-connect-to-errors/ (Scroll down to the very bottom of this document, which starts with "Update 2: Google has redesigned the Chrome browser. Here are the updated instructions to turn off the feature:", to see the currently suggested fix.) Aron Roberts UC Berkeley On Thu, Jun 5, 2014 at 10:47 AM, Megan Forbes <megan.forbes@lyrasis.org> wrote: > Brittany, > > Thanks for getting in touch. I am forwarding your query on to the CollectionSpace talk list, where a member of our development team should be able to offer some assistance. > > Thanks, > Megan > > > Megan Forbes > CollectionSpace Community Outreach and Support Manager > megan.forbes@lyrasis.org > 800.999.8558 x 2917 Main > 917.267.9676 Cell > meganbforbes Skype > > ________________________________________ > From: collectionspace@lyrasis.org <collectionspace@lyrasis.org> on behalf of www.collectionspace.org <collectionspace@lyrasis.org> > Sent: Thursday, June 5, 2014 1:44 PM > To: Megan Forbes > Subject: Form submission from: Contact Us > > > Name: Brittany Holliss > E-mail: bholliss@miamuseum.ca > Subject: Cleared Cache > Question or comment: > I had previously had an issue where while saving a Media record, I was kicked > out of the account an unable to log back in due to an error message reading, > "PageBuilder was not able to retrieve login information and user permissions: > error". > > I thought that if I cleared my browser cache this might help, but then I > would get a message through Google Chrome saying, "Google Chrome could not > connect to ec2-23-20-211-6.compute-1.amazonaws.com:8180" > > If anyone has advice on how to get back access to my admin account that would > be fantastic. Thanks! > Best, > Brittany > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Following up on Aron's remarks: Yes, the most obvious interpretation of these error messages is that the Amazon instance went down (crashed) or otherwise got hung up. Another is that the IP address (probably an Elastic IP) has been reassigned or otherwise no longer points to the instance (this would be a DNS problem or AWS admin mistake). If someone can log in to the AWS admin console they could check both of these. John On Thu, Jun 5, 2014 at 10:47 AM, Megan Forbes <megan.forbes@lyrasis.org> wrote: > Brittany, > > Thanks for getting in touch. I am forwarding your query on to the CollectionSpace talk list, where a member of our development team should be able to offer some assistance. > > Thanks, > Megan > > > Megan Forbes > CollectionSpace Community Outreach and Support Manager > megan.forbes@lyrasis.org > 800.999.8558 x 2917 Main > 917.267.9676 Cell > meganbforbes Skype > > ________________________________________ > From: collectionspace@lyrasis.org <collectionspace@lyrasis.org> on behalf of www.collectionspace.org <collectionspace@lyrasis.org> > Sent: Thursday, June 5, 2014 1:44 PM > To: Megan Forbes > Subject: Form submission from: Contact Us > > > Name: Brittany Holliss > E-mail: bholliss@miamuseum.ca > Subject: Cleared Cache > Question or comment: > I had previously had an issue where while saving a Media record, I was kicked > out of the account an unable to log back in due to an error message reading, > "PageBuilder was not able to retrieve login information and user permissions: > error". > > I thought that if I cleared my browser cache this might help, but then I > would get a message through Google Chrome saying, "Google Chrome could not > connect to ec2-23-20-211-6.compute-1.amazonaws.com:8180" > > If anyone has advice on how to get back access to my admin account that would > be fantastic. Thanks! > Best, > Brittany > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

(Thanks, John!!) Brittney, I believe John picked up on the error message you saw when clearing your browser cache, and sagely inferred that the CollectionSpace server might be running in Amazon.com's 'cloud' - that is, on a server machine provided by Amazon in one of its data centers. For you - or whoever administers that server - John's advice about logging into the AWS administrative console - typically a web page used to manage one or more services in that 'cloud' - is entirely apt. (If you administer that server, you might check the two possibilities that John raised: that Amazon's server might have crashed or hung, or that its Internet (IP) address might recently have been changed. Or, if someone else administers that server, you might share these possibilities with your system administrator or other appropriate IT/computing support person.) Aron On Thu, Jun 5, 2014 at 2:17 PM, John B. LOWE <jblowe@berkeley.edu> wrote: > Following up on Aron's remarks: > > Yes, the most obvious interpretation of these error messages is that > the Amazon instance went down (crashed) or otherwise got hung up. > > Another is that the IP address (probably an Elastic IP) has been > reassigned or otherwise no longer points to the instance (this would > be a DNS problem or AWS admin mistake). > > If someone can log in to the AWS admin console they could check both of these. > > John > > On Thu, Jun 5, 2014 at 10:47 AM, Megan Forbes <megan.forbes@lyrasis.org> wrote: >> Brittany, >> >> Thanks for getting in touch. I am forwarding your query on to the CollectionSpace talk list, where a member of our development team should be able to offer some assistance. >> >> Thanks, >> Megan >> >> >> Megan Forbes >> CollectionSpace Community Outreach and Support Manager >> megan.forbes@lyrasis.org >> 800.999.8558 x 2917 Main >> 917.267.9676 Cell >> meganbforbes Skype >> >> ________________________________________ >> From: collectionspace@lyrasis.org <collectionspace@lyrasis.org> on behalf of www.collectionspace.org <collectionspace@lyrasis.org> >> Sent: Thursday, June 5, 2014 1:44 PM >> To: Megan Forbes >> Subject: Form submission from: Contact Us >> >> >> Name: Brittany Holliss >> E-mail: bholliss@miamuseum.ca >> Subject: Cleared Cache >> Question or comment: >> I had previously had an issue where while saving a Media record, I was kicked >> out of the account an unable to log back in due to an error message reading, >> "PageBuilder was not able to retrieve login information and user permissions: >> error". >> >> I thought that if I cleared my browser cache this might help, but then I >> would get a message through Google Chrome saying, "Google Chrome could not >> connect to ec2-23-20-211-6.compute-1.amazonaws.com:8180" >> >> If anyone has advice on how to get back access to my admin account that would >> be fantastic. Thanks! >> Best, >> Brittany >> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org