From blevine at fhcrc.org Wed Mar 12 18:30:47 2014 From: blevine at fhcrc.org (Levine, Beth D) Date: Wed, 12 Mar 2014 22:30:47 +0000 Subject: [Eagle-i-admins] FHCRC eagle-i node down Message-ID: According to the node registry service page at https://search.eagle-i.net/central/status, our eagle-i node is not responding. When I try to access our SWEET tool, I get the following error message: Service Temporarily Unavailable The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. Apache/2.2.22 (Ubuntu) Server at eagle-i.fhcrc.org Port 443 I was able to reboot the server yesterday, which appeared to resolve the problem, but only for a few hours, at which point the server became unresponsive again. I note that our repository ontology and software versions are out of date. I am not sure if this is relevant, but we do have drupal integration through a custom module which provides some basic configuration tools, but I'd have to review the module documentation in order to make any sense of it. We are currently between sys admins so I am not sure how to proceed, and would appreciate any pointers to get us back up and running. Thanks! Beth Levine Systems Librarian Arnold Library | Fred Hutchinson Cancer Research Center | Seattle, WA blevine at fhcrc.org? |? tel 206.667.5537 |? fax 206.667.4737 From David_Neiman at hms.harvard.edu Mon Mar 17 13:33:28 2014 From: David_Neiman at hms.harvard.edu (Neiman, David) Date: Mon, 17 Mar 2014 13:33:28 -0400 Subject: [Eagle-i-admins] FHCRC eagle-i node down In-Reply-To: References: Message-ID: <5EC4FBDF-9EE3-4D8B-A4EA-337331A20F6D@hms.harvard.edu> Hello Beth, I heard that a second restart solved your problem for now. Perhaps someone else on the list has come across a problem like this, where a restart gets the node working again for a period of time. It would be great if they could reply to the list with their knowledge. Thank you, Dave Neiman The eagle-i team On Mar 12, 2014, at 6:30 PM, "Levine, Beth D" wrote: > According to the node registry service page at https://search.eagle-i.net/central/status, our eagle-i node is not responding. > > When I try to access our SWEET tool, I get the following error message: > > Service Temporarily Unavailable > > The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. > Apache/2.2.22 (Ubuntu) Server at eagle-i.fhcrc.org Port 443 > > I was able to reboot the server yesterday, which appeared to resolve the problem, but only for a few hours, at which point the server became unresponsive again. > > I note that our repository ontology and software versions are out of date. I am not sure if this is relevant, but we do have drupal integration through a custom module which provides some basic configuration tools, but I'd have to review the module documentation in order to make any sense of it. > > We are currently between sys admins so I am not sure how to proceed, and would appreciate any pointers to get us back up and running. > > Thanks! > > > Beth Levine > Systems Librarian > Arnold Library | Fred Hutchinson Cancer Research Center | Seattle, WA > blevine at fhcrc.org | tel 206.667.5537 | fax 206.667.4737 > > > _______________________________________________ > Eagle-i-admins mailing list > Eagle-i-admins at open.med.harvard.edu > https://open.med.harvard.edu/mailman/listinfo/eagle-i-admins From blevine at fhcrc.org Mon Mar 17 13:52:40 2014 From: blevine at fhcrc.org (Levine, Beth D) Date: Mon, 17 Mar 2014 17:52:40 +0000 Subject: [Eagle-i-admins] FHCRC eagle-i node down In-Reply-To: <5EC4FBDF-9EE3-4D8B-A4EA-337331A20F6D@hms.harvard.edu> References: <5EC4FBDF-9EE3-4D8B-A4EA-337331A20F6D@hms.harvard.edu> Message-ID: Yes, just to add more details, we first tried a server reboot from the command line, which brought the node back online for a few hours before it went back down. Then, on Friday, we tried a hard reboot from our vSphere client, which seems to have produced a more stable response. The server stayed online through the weekend. Beth -----Original Message----- From: Neiman, David [mailto:David_Neiman at hms.harvard.edu] Sent: Monday, March 17, 2014 10:33 AM To: Levine, Beth D Cc: eagle-i-admins at open.med.harvard.edu Subject: Re: [Eagle-i-admins] FHCRC eagle-i node down Hello Beth, I heard that a second restart solved your problem for now. Perhaps someone else on the list has come across a problem like this, where a restart gets the node working again for a period of time. It would be great if they could reply to the list with their knowledge. Thank you, Dave Neiman The eagle-i team On Mar 12, 2014, at 6:30 PM, "Levine, Beth D" wrote: > According to the node registry service page at https://search.eagle-i.net/central/status, our eagle-i node is not responding. > > When I try to access our SWEET tool, I get the following error message: > > Service Temporarily Unavailable > > The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later. > Apache/2.2.22 (Ubuntu) Server at eagle-i.fhcrc.org Port 443 > > I was able to reboot the server yesterday, which appeared to resolve the problem, but only for a few hours, at which point the server became unresponsive again. > > I note that our repository ontology and software versions are out of date. I am not sure if this is relevant, but we do have drupal integration through a custom module which provides some basic configuration tools, but I'd have to review the module documentation in order to make any sense of it. > > We are currently between sys admins so I am not sure how to proceed, and would appreciate any pointers to get us back up and running. > > Thanks! > > > Beth Levine > Systems Librarian > Arnold Library | Fred Hutchinson Cancer Research Center | Seattle, WA > blevine at fhcrc.org | tel 206.667.5537 | fax 206.667.4737 > > > _______________________________________________ > Eagle-i-admins mailing list > Eagle-i-admins at open.med.harvard.edu > https://open.med.harvard.edu/mailman/listinfo/eagle-i-admins From fcoldren at mail.med.upenn.edu Thu Mar 27 12:54:51 2014 From: fcoldren at mail.med.upenn.edu (Faith Coldren) Date: Thu, 27 Mar 2014 12:54:51 -0400 Subject: [Eagle-i-admins] Error with Resource Provider Summary Lists Message-ID: Hi, The links to Resource Provider Summary Lists from Penn's search page return an error: HTTP Status 500 - org.eaglei.services.repository.RepositoryProviderException: Could not authenticate user. Re-enter username and/or password. *type* Exception report *message* *org.eaglei.services.repository.RepositoryProviderException: Could not authenticate user. Re-enter username and/or password.* *description* *The server encountered an internal error that prevented it from fulfilling this request.* We recently modified configuration properties in two conf files to try and fix another issue. I'm not sure to which username and/or password the HTTP Status 500 message refers. Is it the eaglei.catalyst.user? Thanks in advance, Faith -------------- next part -------------- An HTML attachment was scrubbed... URL: https://open.med.harvard.edu/pipermail/eagle-i-admins/attachments/20140327/df70ba73/attachment.html