<?xml version="1.0" encoding="UTF-8"?>
<!--Generated by Squarespace Site Server v5.0.0 (http://www.squarespace.com/) on Thu, 20 Nov 2008 09:53:02 GMT--><rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><title>eClips Support Notifications</title><link>http://blog.nla-eclips.com/support/</link><description>NLA eClips Support Notifications</description><copyright></copyright><language>en-GB</language><generator>Squarespace Site Server v5.0.0 (http://www.squarespace.com/)</generator><item><title>NLA eClips Service Incident - Report</title><dc:creator>Incident Management Team</dc:creator><pubDate>Tue, 04 Nov 2008 17:55:40 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/11/4/nla-eclips-service-incident-report.html</link><guid isPermaLink="false">110277:1019045:2518050</guid><description><![CDATA[<p style="FONT-WEIGHT: bold; FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Problem:</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Loading of The Daily Mail into the NLA database failed on Tuesday 4th November 2008. This meant that the distribution of feeds to NLA clients did not contain 1st edition Daily Mail content by the target time of 01:00. Loading and distribution of other titles were unaffected.</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</p>
<p style="FONT-WEIGHT: bold; FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Cause:</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">A momentary connectivity failure between the server running the loading module and the storage device to which loading takes place, caused a single thread of the loading module to loop erroneously.</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</p>
<p style="FONT-WEIGHT: bold; FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Solution:</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">NLA engineers restarted the loading module which resulted in the loading and distribution of all the 1st edition Daily Mail content by 01:15.</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</p>
<p style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Analysis of the loading module's source code has identified areas where modifications can be made to prevent a similar incident in future. These modifications will be scheduled soon.</p>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-2518050.xml</wfw:commentRss></item><item><title>NLA eClips Service Incident - Report</title><dc:creator>Incident Management Team</dc:creator><pubDate>Sat, 18 Oct 2008 21:01:14 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/10/18/nla-eclips-service-incident-report.html</link><guid isPermaLink="false">110277:1019045:2442704</guid><description><![CDATA[&nbsp;
<P style="FONT-WEIGHT: bold; FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Problem:</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Certain eClips customers had intermittent access to NLA web and FTP services from 7:35am to 9:00am and from 9:19am to 9:33am on Saturday 18th October 2008.</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</P>
<P style="FONT-WEIGHT: bold; FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Cause:</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">The owners of NLA's London hosting facility were carrying out the first phase of a planned, annual, power-down exercise on Saturday 18th October. This involved disabling one of the two power feeds which supply the NLA infrastructure. The NLA's infrastructure can usually tolerate removal of one power feed as it has a dual-fed, clustered architecture. In this instance, the automated failover of one clustered network component did not complete successfully.</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</P>
<P style="FONT-WEIGHT: bold; FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">Solution:</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">&nbsp;</P>
<P style="FONT-SIZE: 8.5pt; MARGIN: 0in; FONT-FAMILY: Verdana">The failover process for the affected network component required manual intervention by engineers, who ensured that it completed successfully. The engineers also made some configuration changes to the cluster which should reduce the risk of a similar event occurring in future.</P>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-2442704.xml</wfw:commentRss></item><item><title>NLA eClips Service Incident Report</title><dc:creator>Incident Management Team</dc:creator><pubDate>Mon, 06 Oct 2008 12:19:22 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/10/6/nla-eclips-service-incident-report.html</link><guid isPermaLink="false">110277:1019045:2392575</guid><description><![CDATA[<P><strong> <A href="http://blog.nla-eclips.com/support/2008/9/23/nla-eclips-service-incident-report.html"> NLA eClips Service Incident - Report </A> </strong></P> <P><strong> Problem: </strong></P> <P> At approximately 9:30 this morning an incident occurred which impacted eClips service delivery. The incident was resolved at 10:00. During this incident, clients ability to view eClips content was impacted as the service was intermittently unavailable. </P> <P><strong> Cause: </strong></P> <P> The root cause of the incident is still under investigation by NLA engineers, however indications show that when attempting to serve a higher than normal number of requests, the eClips database license checking process became less responsive and is being investigated as a potential area requiring optimization. </P> <P><strong> Solution: </strong> </P> <P> NLA engineers are now reviewing the eClips core code related to this aspect of the service with the aim of discovering the root cause and optimizing it to prevent reoccurrence. </P> <P> The NLA engineering team is also preparing to deploy a new database architecture which will be more resilient and scalable. This should also have the benefit of preventing such an incident from occurring. </P> <P> NLA Service Operations Management </P>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-2392575.xml</wfw:commentRss></item><item><title>CANCELLED: NLA maintenance - Saturday 4th October 2008 at 13:00</title><dc:creator>Incident Management Team</dc:creator><pubDate>Thu, 02 Oct 2008 10:36:19 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/10/2/cancelled-nla-maintenance-saturday-4th-october-2008-at-1300.html</link><guid isPermaLink="false">110277:1019045:2377780</guid><description><![CDATA[<P>NLA engineers will be carrying out configuration changes to the NLA eClips environment on Saturday 4th October at 13:00. Web and FTP services will be intermittently unavailable for up to three hours while the work takes place.</P>
<P>Notifications will be sent before the work begins and as soon as it is complete.</P>
<P>We apologise for any inconvenience this may cause.</P>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-2377780.xml</wfw:commentRss></item><item><title>NLA eClips Email Issues</title><dc:creator>Incident Management Team</dc:creator><pubDate>Tue, 23 Sep 2008 12:02:21 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/9/23/nla-eclips-email-issues.html</link><guid isPermaLink="false">110277:1019045:2320814</guid><description><![CDATA[<P>Yesterday the NLA implemented changes to our email system which creates further resilience and fault tolerance. Unfortunately, during the implementation, new rules and restrictions within the system blocked some emails from being passed to third party recipients. In particular, this issue impacted client requests sent to the <A href="mailto:reprocessing@nla.co.uk">reprocessing@nla.co.uk</A> alias. All requests sent yesterday to this alias were not routed appropriately to Ninestars and therefore any requests for reprocessing were not performed. </P> <P fontFamily>The NLA apologises for any impact this may have had on PCA eClips production workflow. The issue has now been resolved and all emails are being routed appropriately.</P>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-2320814.xml</wfw:commentRss></item><item><title>NLA eClips Service Incident - Report</title><dc:creator>Incident Management Team</dc:creator><pubDate>Tue, 23 Sep 2008 09:57:42 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/9/23/nla-eclips-service-incident-report.html</link><guid isPermaLink="false">110277:1019045:2320676</guid><description><![CDATA[<P><strong>Problem: </strong></P>
<P>At approximately 9:20 yesterday an incident occurred which impacted eClips service delivery. The incident was resolved at 10:15. During this incident, clients ability to view eClips content was impacted as the service was intermittently unavailable. </P>
<P><strong>Cause: </strong></P>
<P>The root cause of the incident is still under investigation by NLA engineers, however indications show that when attempting to serve a high number of multi-object requests containing more than the permitted 100 objects, the eClips web application spawned unnecessary additional connections to the eClips database which in turn impacted performance. Yesterday, we experienced a higher than normal number of large multi-object requests. </P>
<P><strong>Solution: </strong></P>
<P>Once the cause of the incident was understood by NLA engineers the service was restarted and returned to normal operation immediately. NLA engineers are now putting in place further monitoring which will provide an earlier warning of the potential reoccurrence of this type of incident. The NLA is also investigating the eClips core code related to this aspect of the service with the aim of discovering the root cause and redeveloping it to prevent reoccurrence. </P>
<P>Separately, the NLA engineering team is preparing to deploy a new database architecture which will be more resilient and scalable. This should also have the benefit of preventing such an incident from occurring. </P>
<P><br><br></P>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-2320676.xml</wfw:commentRss></item><item><title>NLA eClips: Emergency Maintenance</title><dc:creator>Matt Groshong</dc:creator><pubDate>Tue, 02 Sep 2008 09:29:38 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/9/2/nla-eclips-emergency-maintenance.html</link><guid isPermaLink="false">110277:1019045:2211249</guid><description><![CDATA[<P> NLA engineers will be carrying out emergency maintenance on the eClips database storage device today at 19:00. This will require stopping all eClips web and FTP services for up to 60 minutes. </P> <P> Further notification will be sent when the work is complete. </P> <P> We apologise for any inconvenience this may cause. </P> <br/>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-2211249.xml</wfw:commentRss></item><item><title>NLA eClips - Content Delivery Issues</title><dc:creator>Incident Management Team</dc:creator><pubDate>Thu, 03 Jul 2008 08:49:37 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/7/3/nla-eclips-content-delivery-issues.html</link><guid isPermaLink="false">110277:1019045:1964243</guid><description><![CDATA[<p>The NLA has&nbsp;experienced an increase, recently, in&nbsp;content not being made available through the eClips Service&nbsp;to service delivery targets. This has effected regional titles, and City AM in particular. There is no common thread to the issues, which have been caused by various internal problems with publisher production systems. </p><p>These failures follow a lengthy period of successful delivery and we are working hard with the publishers in question to ensure normal service is resumed.</p><p>The NLA Service Operations team&nbsp;would like to apologise&nbsp;for the inconvenience caused and hopes that the established communication processes&nbsp;have ensured clients are notified appropriately.</p><p>If you have any questions or concerns please send a mail to the <a href="mailto:srvopsmgmt@nla.co.uk">NLA Service Operations Management Team</a>.</p>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-1964243.xml</wfw:commentRss></item><item><title>NLA eClips Service Incident - Report</title><dc:creator>Incident Management Team</dc:creator><pubDate>Tue, 27 May 2008 17:14:28 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/5/27/nla-eclips-service-incident-report.html</link><guid isPermaLink="false">110277:1019045:1866434</guid><description><![CDATA[<p><strong>Problem:</strong></p><p>Some content was loaded into the eClips database and distributed to clients later than usual on Tuesday 27<sup>th</sup> May 2008. </p><p><strong>Cause:</strong></p><p>A fault with one of the external Internet links, from an eClips production site in India, resulted in corrupt files being transmitted to London. These corrupt files were not loaded into the eClips database at the first attempt. </p><p><strong>Solution:</strong></p><p>The problematic link was shut down and traffic from the affected production site was distributed over the remaining external links. The corrupt files were then retransmitted and any outstanding content was loaded and distributed by 5:30am. </p><p>Further investigation into the exact nature of the fault is ongoing. The implementation of additional monitoring processes will minimise the time required to react if a similar event should occur in future. </p>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-1866434.xml</wfw:commentRss></item><item><title>NLA eClips Service Incident: REPORT</title><dc:creator>Incident Management Team</dc:creator><pubDate>Tue, 20 May 2008 16:07:53 +0000</pubDate><link>http://blog.nla-eclips.com/support/2008/5/20/nla-eclips-service-incident-report.html</link><guid isPermaLink="false">110277:1019045:1851383</guid><description><![CDATA[<p class="title">&nbsp;</p><p class="title"><strong>Problem:</strong></p><p class="title">The eClips Service has recently experienced two service incidents which have impacted the performance of the service.&nbsp; The first incident happened Friday 16th and the second occurred Monday 19th.&nbsp; Both incidents occurred during the early morning which is the peak time for usage of the eClips service.&nbsp; </p><p class="title"><strong>Cause:</strong></p><div class="body"><p>After further investigation and testing, NLA engineers have discovered that these incidents were caused by a recent service release which was deployed at 19:00 Thursday 15th as part of a service enhancement.&nbsp; </p><p>Service testing before the release of this enhancement unfortunately did not uncover a performance issue.&nbsp; This performance issue was only found when the eClips service experienced peak traffic load on Friday 16th.&nbsp; </p><p>Following the first incident on the 16th, NLA engineers were unable to determine that the service enhancement had caused the incident.&nbsp; However, when on 19th a similiar incident occurred at a similiar time of day, additional information was obtained that pointed to the service release as the most likely root cause of both incidents.</p><p><strong>Solution:</strong></p><p>As soon the service release was determined to be the cause of the incidents, NLA engineers 'rolled back' the changes (Monday 19th at aproximately 9:30).&nbsp; Once the change was removed from the service, normal operation returned and this issue has not occurred again.</p><p>NLA service release testing processes have been reviewed following these incidents and new procedures are now in place to ensure that testing more accurrately reflects the level of performance releases must cope with in the live environment.&nbsp; </p><p>The release of this most recent service enhancement has now been delayed until further testing and redevelopment can occur.&nbsp; </p></div>]]></description><wfw:commentRss>http://blog.nla-eclips.com/support/rss-comments-entry-1851383.xml</wfw:commentRss></item></channel></rss>