This list has been dormant for quite some time. Many of us have met. But in case we haven’t, I’m Eric Lopatin, the services manager for Merritt. It’s good to meet you, virtually!
As many folks are probably aware, today is World Digital Preservation Day<https://www.dpconline.org/events/world-digital-preservation-day>. There are many good posts<https://twitter.com/hashtag/WorldDigitalPreservationDay> bubbling up in the larger digital preservation community. On that note, the Merritt team would like to bring your attention to one in particular, which reviews recent development efforts to make Merritt a more streamlined and resilient preservation system<https://uc3.cdlib.org/2020/11/05/streamlining-merritt-microservice-configuration/>.
Some recent Merritt news to announce. Merritt and Dash have been certified by CoreTrustSeal as a trustworthy repository. You can read more about what this means here: http://uc3.cdlib.org/2018/08/22/merritt-and-dash-certified-as-trustworthy-repositories/
Thanks to the Merritt team, particularly Stephen Abrams, for all their work on the certification process.
We wanted to add information about the certification to the Merritt home page, and decided to update the UI. We updated some content, and now have a responsive design that will work on your phone and other devices. We also improved the accessibility. Have a look: https://merritt.cdlib.org
From: Merritt users list <[log in to unmask]> On Behalf Of Perry Willett Sent: Wednesday, August 22, 2018 2:14 PM To: MERRITT-L <[log in to unmask]> Subject: Merritt news
Some recent Merritt news to announce. Merritt and Dash have been certified by CoreTrustSeal as a trustworthy repository. You can read more about what this means here: http://uc3.cdlib.org/2018/08/22/merritt-and-dash-certified-as-trustworthy-repositories/
Thanks to the Merritt team, particularly Stephen Abrams, for all their work on the certification process.
I'm going on vacation starting Friday July 20, through Monday Aug 21. Please send any support requests to [log in to unmask]<mailto:[log in to unmask]>, which will be monitored by CDL staff. We will respond to your requests, but please be a little patient if we don't respond right away. Let us know if you have any questions or concerns. Thanks, and have a great summer,
I'll generate the Merritt billing information for FY 2016/2017 and send to you next week. Once you've had a chance to look at it, I'll pass it along to the CDL business office to begin the recharge process. Let me know if you have any questions. Best wishes,
We're seeing normal download speeds from SDSC this morning. We haven't determined what caused the problem yesterday; SDSC reported no problems. We'll continue to monitor it, and please contact us if you experience slow downloads (or any other problem). Sorry for the inconvenience. Best wishes,
Perry Willett California Digital Library
From: Perry Willett Sent: Tuesday, March 07, 2017 4:12 PM To: [log in to unmask] Subject: some slow downloads from Merritt
We're seeing very slow download speeds from our SDSC storage node-like 1 MB *per hour*. Some download requests just time out. We're not sure what's causing it, but we've contacted SDSC to try to determine the cause.
This problem affects content in restricted collections. Content in public collections use AWS as the primary storage node, and should not experience any slow transfer rates.
As I mentioned last week, we replicated publicly available Merritt collections to Amazon S3. This means, for instance, that datasets from the Dash collections are stored in S3. Any download request for files in these public collections is now served from S3.
We are starting to work with the eScholarship team on providing access to its publications directly from the Merritt S3 storage node, looking to exploit some of the services available from Amazon such as Cloudfront for distribution and file streaming. If you have thoughts or ideas about using other Amazon services in conjunction with content stored in Merritt,
The maintenance is complete, and ingest is now back in production. Thanks for your patience. We're now providing public access to our collections from Amazon S3!
Perry
From: Perry Willett Sent: Thursday, November 10, 2016 1:01 PM To: [log in to unmask] Subject: Merritt maintenance now estimated to end at 2:30pm
Well, it looks like even our interim estimate was wrong. We're now estimating that the work will be complete at 2:30pm PT. We're very sorry for the inconvenience and thanks for your patience.
Well, it looks like even our interim estimate was wrong. We're now estimating that the work will be complete at 2:30pm PT. We're very sorry for the inconvenience and thanks for your patience.
Perry
From: Perry Willett Sent: Thursday, November 10, 2016 11:13 AM To: [log in to unmask] Subject: Merritt maintenance now estimated to end at 12:30
The maintenance is taking longer than expected. We currently estimate that it will finish at 12:30 PT today. We'll unpause ingest at that point. We apologize for the inconvenience-please send any questions or concerns to [log in to unmask]<mailto:[log in to unmask]>. Thanks,
Perry
From: Perry Willett Sent: Wednesday, November 09, 2016 11:28 AM To: [log in to unmask] Subject: Merritt ingest paused from 9-11am on Thurs 11/10/2016
We're in the process of migrating data to the new storage node at Amazon S3. Once this migration is complete, content in publicly available collections will use the new Amazon S3 storage node as the primary source.
We'd like to do this tomorrow (Thurs Nov 10) from 9-11am PT. We've actually replicated all the data, but will need to pause ingest in order to update some of the database tables. If possible, please do not submit any ingests during this time, although nothing bad will happen if you do-it will simply sit in the ingest queue until after the maintenance
Good luck! We, ourselves, are looking at the S3 way and like the off Campus, off CA choices.
Giulia
On Wed, Nov 9, 2016 at 11:28 AM, Perry Willett <[log in to unmask]> wrote:
> We’re in the process of migrating data to the new storage node at Amazon > S3. Once this migration is complete, content in publicly available > collections will use the new Amazon S3 storage node as the primary source. > > > > We’d like to do this tomorrow (Thurs Nov 10) from 9-11am PT. We’ve > actually replicated all the data, but will need to pause ingest
We determined the problem was with one of our 2 storage servers. These are the servers that interact with our storage nodes. We've taken the problem server out of the load-balancing rotation, and everything seems to be working smoothly. Let us know if you experienced problems that we can help diagnose.
We're experiencing some problems with our storage node at SDSC. Ingests and retrievals can take a while, and may even fail. The problems seem to be intermittent. We're still investigating, and I'll send out more information as we figure this out. Please let me know any questions or concerns, and my apologies for the inconvenience.
There will be a very brief Merritt outage this afternoon around 2pm (PT), less than one minute.
Most of the Merritt infrastructure already uses load balancing, and we're adding it to the remaining servers this afternoon. This requires changing the DNS records and restarting servers. We'll pause ingest a little before 2. The only other potential effect is if someone is trying to download a file around 2pm-it will likely be interrupted and fail. Otherwise, there should only be a momentary outage (less than a minute). Please contact us if you experience any problems. Thanks,
We're experiencing problems retrieving content from storage. We think it's a problem at SDSC. We can still retrieve content from our DataONE storage node at UNM. We're looking into it. Sorry again.
Looks like we're back and able to retrieve content again. Let us know if you experience any problems. Sorry for the inconvenience.
Perry
From: Perry Willett Sent: Tuesday, March 29, 2016 4:20 PM To: MERRITT-L Subject: problems with retrieving content from storage
We're experiencing problems retrieving content from storage. We think it's a problem at SDSC. We can still retrieve content from our DataONE storage node at UNM. We're looking into it. Sorry again.
Merritt is now back online, with all of the servers now on AWS. We ran into some problems with the Apache configuration and SSL certificate. Sorry for the delay and inconvenience. Please let us know if you experience any problems, and thanks for your patience.
The maintenance is taking longer than expected-we hope to have the system working soon. I'll send out a message either when everything is in production or with more information if it takes significantly longer. I apologize for the inconvenience.
We're migrating the rest of the Merritt infrastructure to AWS tomorrow. Merritt will be unavailable from 10:45am until 11:15am (PT) tomorrow (Tues March 29) while this occurs. We will have a maintenance page in place. Please do not submit any ingest jobs during this period-they will likely fail.
The new servers are actually already running-we just need to do a little maintenance and then a DNS change at 11:00am to point to the new servers. You shouldn't need to do anything after the maintenance, but there might be a brief period while the DNS change is propagating through the network
There will be a brief outage this afternoon at 2pm (PT) as we move the Merritt database to a larger AWS server. We've been hitting 100% of CPU usage so we want to move it to a server with more capacity. The outage should only be a few minutes. Please let us know if you have any concerns or questions. Thanks,
We were able to get Merritt back in operation about 9:30 last night. Everything seems to be working properly now. Please let us know if you experience any problems. Apologies for all the inconvenience. Thanks,
Apparently some network cables in the UCOP data center were disconnected causing multiple web service outages. UCOP ITS is working to verify that things are back up and running, but for the moment we can't log into several of our servers. Until we can access our servers, we can't fix the problem we were having with SDSC storage. We can't win for losing today.
It looks like the SDSC unavailability is related to the Drown Attack that was uncovered today: https://drownattack.com/
SDSC made some changes to their server configuration without telling us. Now that we understand it, we think we will be able to reconnect soon. I'll keep everyone updated. Sorry again for the inconvenience.
The Merritt storage node is currently unavailable due to a problem with SDSC Cloud Storage. This means we can't access any Merritt content. We're looking into what's happening. Apologies for the inconvenience.
Merritt will be unavailable on Saturday Jan 9, from 1pm to 6pm (PT) while we migrate our database to AWS. We will pause ingest during this time, and content will not be available for viewing or download. We will have a maintenance page in place of the regular Merritt home page. If you have automated submissions, it will be better to pause them during this time, but any submissions will be queued and processed after the maintenance period is over.
The Merritt maintenance that we announced earlier for Sunday Dec 6 has been cancelled. Merritt will be available, and you can plan on submitting content during the time originally announced. Let me know if you have any questions. Thanks,
Perry
From: Perry Willett Sent: Monday, November 23, 2015 2:09 PM To: MERRITT-L Subject: Merritt: maintenance outage, Sunday Dec 6, 1pm-10pm (PT)
Merritt will be unavailable on Sunday Dec 6 from 1pm-10pm (PT) while we migrate our database from the UCOP Data Center to Amazon RDS.
In addition to testing for the accuracy of the data migration, we will also test failover, and also change the configuration to utfmb4 to accommodate a larger character set. We're going to put up a maintenance page and pause ingest. It would be better to suspend any automated submission scripts during this time. Anything submitted to Merritt during the maintenance will go to the ingest queue and ingested after the maintenance is completed-but we don't want
SDSC installed new SSL certificates and we can now reach our storage nodes. Sorry for any inconvenience. Please let me know if you have any questions or concerns.
We've discovered that the SSL certificate for the server at cloud.sdsc.edu expired today at 4pm PT. We've notified SDSC. Until they fix this, we can't access Merritt content stored at SDSC. We apologize for the inconvenience.
We're having some problems with our connection to the storage at SDSC. Ingest and retrieval requests are all failing. We're looking into it, but for now, please hold off any new ingests. Sorry for the inconvenience.
Due to maintenance, Merritt will have limited availability on Wednesday July 1 from 06:00 PDT - 15:00 PDT.
Merritt will be completely unavailable for 10 minutes, and then available in "read-only" mode. Here's the schedule with more info: 06:00 - 06:10: Merritt will be completely unavailable and have a maintenance page. 06:10 - 15:00: Merritt will be available in "read-only" mode. This means that you can log in, see your collections, and retrieve existing content during the maintenance period. You can even submit content during this period, but the database will not be updated until after the maintenance is completed.
The maintenance is taking a little longer than expected. We're extending the period until 16:00 (4pm) PDT. Merritt content is still available for browsing and retrieval. Sorry for the inconvenience, and thanks for your continuing patience.
Perry
From: Perry Willett Sent: Thursday, June 25, 2015 3:58 PM To: MERRITT-L Subject: Merritt: limited availability July 1 6am-3pm PDT
At the moment, users are unable to log into Merritt. We're having a problem with our LDAP server. We are investigating and will keep everyone updated. We apologize for the inconvenience.
Perry
Perry Willett Digital Preservation Services Manager California Digital Library 415 20th St., 4th Floor Oakland CA 94612-2901 Ph: 510-987-0078 Fax: 510-893-5212 Email: [log in to unmask]<mailto:[log in to unmask]>
We're back online. Let us know if you experience any problems or have any questions. Apologies for the inconvenience.
Perry
From: Perry Willett Sent: Thursday, June 04, 2015 8:09 AM To: MERRITT-L Subject: problem logging into Merritt
At the moment, users are unable to log into Merritt. We're having a problem with our LDAP server. We are investigating and will keep everyone updated. We apologize for the inconvenience.
We fixed a significant problem with ingest last week. Connections between the ingest server and the storage server were being dropped randomly, and the submissions would fail as a result. The problem occurred regularly with large files (and we're seeing a lot more large files lately). It may have been happening with smaller files as well, but it was more likely to occur with large files. The current process will now resume the transfer if the connection is dropped, and at the point at which it was interrupted (similar to wget's "continue" command). We tested it with large files over
We're currently experiencing a very high load on Merritt. We're very close to finishing replicating content from SDSC to UCLA-just the largest objects are left. But one outcome of replication is that the size of our audit process has doubled-we're now running the audit process in both SDSC and UCLA. This doubles the load on the database. We're looking into how to optimize our database use for this increased load, but in the meantime the response is sluggish.
Just a reminder that Merritt will be unavailable this Sunday March 15 from 8am-10am (PT). Let us know if you have any questions or concerns. Thanks,
Perry
From: Perry Willett Sent: Thursday, March 05, 2015 4:17 PM To: MERRITT-L Subject: Merritt unavailable, Sunday March 15 8am-10am (PT)
On Sunday March 15, 2015 from 8:00am until 10:00am (PDT), Merritt will be unavailable due to system maintenance. During this time, the entire website will be unavailable, so users will not be able to log in to Merritt, or view or retrieve content. We will have a maintenance page instead of the regular
On Sunday March 15, 2015 from 8:00am until 10:00am (PDT), Merritt will be unavailable due to system maintenance. During this time, the entire website will be unavailable, so users will not be able to log in to Merritt, or view or retrieve content. We will have a maintenance page instead of the regular home page. We apologize for the inconvenience. Please let us know any questions or concerns by emailing them to [log in to unmask]<mailto:[log in to unmask]>. Thanks,
We successfully implemented the new SLES VM for the Merritt storage service this morning, and normal submission can resume again. We're confident that we've fixed the problems with ingesting large objects that we experienced in the past two weeks. We'll continue to monitor submissions as they come through to be sure. Let me know if you have any questions. Thanks for your patience while we fixed this problem.
-----Original Message----- From: Merritt users list [mailto:[log in to unmask]] On Behalf Of Perry Willett Sent: Thursday, February 05, 2015 4:04 PM To: MERRITT-L Subject: new Merritt server
We successfully implemented the new SLES VM for the Merritt storage service this morning, and normal submission can resume again. We're confident that we've fixed the problems with ingesting large objects that we experienced in the past two weeks. We'll continue to monitor submissions as they come through to be sure. Let me know if you have any questions. Thanks for your patience while we fixed this problem.
We're experiencing problems with ingesting objects larger than 100 MB. Many of the submissions are failing due to slow processing and time-outs. We've isolated the problem to the Solaris VM that runs the storage service. We recently migrated the storage service from a physical Solaris server to the Solaris VM[1], and the problem has gotten worse. We think the problem is related to the Solaris operating system.
In response to the "Poodle" attack, we disabled SSLv3 on all of the UC3 secure websites for Merritt, Dash and DMPTool. We made this change on Wednesday, as soon as the vulnerability was identified. More on this latest vulnerability is here: http://en.wikipedia.org/wiki/POODLE
Let us know if you have any questions or concerns. Best wishes,
Due to maintenance on almost all CDL servers, Merritt will be unavailable on Saturday Oct 18 from 8:00pm (20:00) until 11:59pm (23:59) PT. We will suspend ingest during this time, and put up a maintenance page informing users of the status. We apologize for the inconvenience. Please let us know any questions or concerns. Thanks,
There will be maintenance in the UCOP data center on the Internet router on Sunday Oct 12 from 6:30-6:45am. No traffic in or out of the data center will be possible during this outage. As a result, almost all CDL services will be unavailable during this time, including Merritt. As a precaution, we will suspend Merritt ingest at 6:00am on Oct 12, and resume at 7:00am. Let us know if you have any questions or concerns.
We have patched servers on the virtual machines that run most of the Merritt service (UI, Ingest and Inventory). There are some servers for parts of Merritt that haven't been patched yet-primarily for the Merritt storage service. However, these are behind the CDL firewall and don't receive any direct external input; everything is mediated through the API or UI, which are both implemented in Ruby/Rails, so we believe we're well protected against someone trying to exploit the vulnerability. We are continuing to analyze the situation. Please let us know if you have any questions.
You may have heard about the vulnerability to online services involving Bash scripts that's being called "Shellshock." More info on this bug is here: http://krebsonsecurity.com/2014/09/shellshock-bug-spells-trouble-for-web-security/
We're aware of the vulnerabilities surrounding this issue and are analyzing our systems to see if we're affected. We'll keep you informed as we learn more. Let us know any questions or concerns. Best,
We've resolved the problem with Merritt storage, and ingests should start being processed again. If you've made any submissions this afternoon, they have been likely sitting in a queue. They should start getting processed now. Let me know if you have questions or concerns. Sorry for the inconvenience.
Perry
From: Perry Willett Sent: Monday, September 22, 2014 3:24 PM To: [log in to unmask] Subject: problem with merritt
Perry, Five or six objects that I added yesterday are not showing up yet. Another six or seven did appear. Rita
On Mon, Sep 22, 2014 at 4:14 PM, Perry Willett <[log in to unmask]> wrote:
> We’ve resolved the problem with Merritt storage, and ingests should > start being processed again. If you’ve made any submissions this afternoon, > they have been likely sitting in a queue. They should start getting > processed now. Let me know if you have questions or concerns. Sorry for the > inconvenience. > > > > Perry > > > > > > *From:* Perry Willett
There were a number of objects that were successfully ingested yesterday but weren’t fully processed in inventory so that they don’t show up in the UI. We’re reprocessing them now, and you should see them later this morning. Let me know if you notice any problems.
Perry
From: Merritt users list [mailto:[log in to unmask]] On Behalf Of Rita M EVANS Sent: Tuesday, September 23, 2014 8:35 AM To: MERRITT-L Subject: Re: problem with merritt now resolved
We did a quick restart of Merritt earlier this afternoon, but it didn't recover. Some items cannot be retrieved from storage, and ingests will queue up until we resolve the issue. We do restarts periodically when updating the software, and they typically take just a minute, so we don't generally notify you. I'll let you know when we've resolved the problem. Sorry for the inconvenience.
Merritt is now available. The maintenance took longer than anticipated. We apologize for the inconvenience. Please let us know at [log in to unmask] if you experience any problems.
The maintenance that started at 9:00am was supposed to only take 30 seconds, but there seem to have been complications and Merritt is still unavailable. We're working on it, and will keep you updated. I apologize for the inconvenience.
Please share this information with your colleagues.
A scheduled maintenance for CDL's services will occur on Sunday, September 14th from 9:00 AM until 9:30 AM PDT. This work will affect all CDL services hosted in our Oakland data center, including Merritt. Only 30 seconds of downtime is expected for any given application. Please contact us at [log in to unmask]<mailto:[log in to unmask]> with any questions or concerns.
UCSD reports that they're still working on the issue with their primary border router. http://status.ucsd.edu
We're not experiencing any problems, so we've resumed ingest and believe that things are back to normal. Please let us know if you experience any problems. Best wishes,
Perry
Perry Willett Digital Preservation Services Manager California Digital Library 415 20th St., 4th Floor Oakland CA 94612-2901 Ph: 510-987-0078 Fax: 510-893-5212 Email: [log in to unmask]<mailto:[log in to unmask]>
UCSD reports intermittent internet connectivity, starting around 3:00pm this afternoon. They continue to investigate. http://status.ucsd.edu/ This affects content stored in Merritt storage nodes in the SDSC Cloud Service. We have just begun to move Merritt collections to SDSC; so far this will mostly affect content in a few restricted collections: Open Context, Online Archive of California, and the content from the DPR. Otherwise, the only other content is from CDL collections. Let us know if you experience any problems or have questions. Best wishes,
Due to maintenance, Merritt will be unavailable on Saturday July 26 at 5:00pm until Sunday July 27 at 12:01am. During this time, Merritt will be unavailable for submission and also download. We will pause ingest, so that any submissions during this period will be queued and ingested after the maintenance is complete. The user interface will be unavailable, and a "maintenance page" announcing its unavailability. Please let us know if you have any questions or concerns. Thanks,
Due to maintenance, Merritt will be unavailable on Saturday July 12 at 18:00 (6pm) until Sunday July 13 at 09:00. During this time, Merritt will be unavailable for submission and also download. The user interface will be unavailable, and a "maintenance page" announcing its unavailability. Please let us know at [log in to unmask] if you have any questions or concerns. Thanks,
You may have been reading about the Heartbleed vulnerability. You'll be happy to hear that while Merritt uses OpenSSL, we use a version (0.9.8) that is not vulnerable. You can read more about the Heartbleed bug here:
http://heartbleed.com/
Let us know if you have any questions. Thanks,
Perry
Perry Willett Digital Preservation Services Manager California Digital Library 415 20th St., 4th Floor Oakland CA 94612-2901 Ph: 510-987-0078 Fax: 510-893-5212 Email: [log in to unmask]<mailto:[log in to unmask]>
We've successfully implemented the new Merritt Inventory--this is the metadata catalog within Merritt that keeps track of all descriptive and system information.[1] This new Inventory should be more responsive (ie faster) and also more robust (ie run better). Objects submitted to Merritt should show up very quickly after submission. Landing pages for collections and objects should come up more quickly also.
I need to poke around with this but my initial reaction is a big THANK YOU to you and your development team for addressing the messy issue of the URL and its persistent form.
Rita
On Thu, Nov 21, 2013 at 4:08 PM, Perry Willett <[log in to unmask]>wrote:
> Dear Merritt users, > > > > A few exciting changes in Merritt to report. > > > > We've successfully implemented the new Merritt Inventory--this is the > metadata catalog within Merritt that keeps track of all descriptive and > system information.[1] This new Inventory should be more responsive (ie >
The underlying DB problem has been corrected and Merritt service is back in operation.
Please let us know if you see any unexpected behavior.
--sla
Stephen Abrams Associate Director, UC Curation Center California Digital Library University of California, Office of the President [log in to unmask] www.cdlib.org/uc3 +1 (510) 987-0370
From: Stephen Abrams Sent: Thursday, October 24, 2013 9:51 AM To: MERRITT-L Subject: Merritt service outage
Merritt is currently experiencing a service outage due to an as-yet unknown problem with a number of CDL production service databases. UCOP IT, CDL, and UC3 staff are investigating the problem and hope to have it resolved quickly.
We will provide more information as it becomes available.
--sla
Stephen Abrams Associate Director, UC Curation Center California Digital Library University of California, Office of the President [log in to unmask] www.cdlib.org/uc3 +1 (510) 987-0370
Maintenance periods: Tuesday, Oct 8: 9:00pm - 9:15pm PT Thursday, Oct 10: 6:00am - 6:30am PT
We are upgrading our version of Rails for Merritt. There will be a brief outage tomorrow (Tuesday) evening at 9pm PT to update one of the Merritt servers. We will upgrade the other two Merritt servers at 6am PT on Thursday morning.
The maintenance on Merritt was completed as scheduled, and it's now back in operation. Please let us know if you notice any problems. Thanks,
Perry
Perry Willett Digital Preservation Services Manager California Digital Library 415 20th St., 4th Floor Oakland CA 94612-2901 Ph: 510-987-0078 Fax: 510-893-5212 Email: [log in to unmask]<mailto:[log in to unmask]>
Just a reminder about the maintenance tomorrow morning. Please let me know if you have any questions or concerns. Best,
Perry
From: Perry Willett Sent: Tuesday, September 17, 2013 10:11 AM To: [log in to unmask] Subject: Merritt maintenance, Thursday Sept 26, 6:00am-7:00am
Merritt will be unavailable on Thursday, Sept 26 from 6:00am-7:00am (PT), to perform routine maintenance. During this time, both the user interface and API will be unavailable, and users will not be able to submit or retrieve content from Merritt.
Merritt will be unavailable on Thursday, Sept 26 from 6:00am-7:00am (PT), to perform routine maintenance. During this time, both the user interface and API will be unavailable, and users will not be able to submit or retrieve content from Merritt.
We'll pause Ingest on Wednesday evening (Sept 25) in preparation for this maintenance, and restart it Thursday morning (Sept 26) after the maintenance. Any content submitted to Merritt after this pause will go into a queue, and be processed after the restart. Any content submitted Wednesday evening won't be fully processed until Thursday. We apologize for the inconvenience. Please send
We're upgrading the version of Ruby/Rails on our stage server, and have run into some configuration issues with the Merritt software on https://merritt-stage.cdlib.org.
Production Merritt (https://merritt.cdlib.org) is not affected, and is working as expected. We're working to correct the problems. Until then, Merritt is not available on merritt-stage through the UI. Merritt-stage is still available through the API. We'll keep you updated on progress toward solving these problems, and we apologize for the inconvenience. Please let me know if you have any questions. Best,
We've completed work on migrating the Merritt infrastructure to virtual machines. As a last step, we have made some DNS changes that may take 24 hours to fully propagate. You might see an error when you go to https://merritt.cdlib.org if your local DNS data hasn't refreshed. You can force a refresh by following these commands:
As the final step in migrating the Merritt infrastructure to virtual machines, we will need to suspend access to Merritt while the DNS name changes are performed. Moving Merritt to a virtual environment will provide a higher level of stability and efficiency.
We are coordinating with UCOP ITS (who will actually perform the work), so we are scheduling a generous maintenance period on:
We experienced a temporary database outage on Sunday 5/19, and a temporary network outage at UCOP and the CDL this afternoon 5/21 at approximately 3:00pm, which prevented access to Merritt. The content stored in Merritt is not affected by the outages.
The service is available and back online. We apologize for any inconvenience from the temporary outages.
Merritt is now available again. The problem started last night with CDL's high availability management software (VCS, causing most CDL services to be unavailable. The content stored in Merritt was never affected, but access was not possible during this time. The issue has been resolved and Merritt is now operating normally. Please contact us with any questions or concerns. We apologize for the inconvenience.
Merritt is down. We're looking into the problem; no estimate of when it might be back in operation. We'll send out a notice when we know more. We apologize for the inconvenience.
Perry Willett Digital Preservation Services Manager California Digital Library 415 20th St., 4th Floor Oakland CA 94612-2901 Ph: 510-987-0078 Fax: 510-893-5212 Email: [log in to unmask]<mailto:[log in to unmask]>
We've established a new listserv for Merritt users and account holders -- and have just subscribed you to the list. We'll use the list to primarily send notifications, updates, and announcements pertaining to the service.
The list is also open for subscription by any of your colleagues who utilize Merritt.
Below are instructions for posting to or unsubscribing.
The maintenance is still underway. We're extending the period once again, this time until 21:00 (9pm) PDT. Again, my apologies for the inconvenience. Please contact me with any questions or concerns. Thanks,
The UCOP network outage seems to be resolved. Here's the message we received:
At 1:29PM this afternoon, a UCOP network outage occurred which impacted connectivity for CDL operations including CDL production, CDL dev, stage, email service, Internet connectivity and other vital CDL services.
I received a call from Steve Cavalli at 2:33PM informing me that the UCOP network was coming back on-line, although a second interrupt occurred around 3PM.
