Please find the updates for the Lent term at the Summer LUVLE Update page
Friday, 25 March 2011
Questionmark Perception (QMP) experienced a problem this morning at around 5am. You may recall that QMP is the data engine behind both LUMES and Computer Based Assessment. The back end database took about 4.5 hours to run a routine maintenance process which normally takes half an hour, making it unavailable for use. This process finished at about 9:30am and the service is back to normal without a re-start. During the period, although the server did not go down, there were approximately 25 unsuccessful visitors to the site. Investigations into the reasons for the prolonged process are still ongoing.
Wednesday, 23 March 2011
At 04:28 of 22 Mar one LUVLE server (domino.lancs) had an outage which lasted 131 minutes. Because it was shortly after the 04:10 re-start, fewer than 29 were likely affected. Crash data were sent to IBM for analysis. Although our analysis is still not complete, we suspect it was caused by a logon to an old template LUVLE Space. We have denied anonymous access to that and other sites.
Wednesday, 16 March 2011 - 18:00 PM
Announcement: LTG and Learning Zone Extra LUVLE Cover for 16-27 March 2011
We have entered a critical time in the academic calendar as we approach the end of term. Thus ISS are providing a special set of services from 16 through 27 March. Often we see an increased use of Coursework Submission during this period right before the end of term. Below is a listing of proactive changes we are making to assure that this period of increased demand on LUVLE 10 will be met:
Learning Zone (LZ) hours (staffed)
Wednesday, 16 March 2011
Because of the work we did to stabilise the one LUVLE server yesterday (see below), we were unable to complete full testing of the IBM-provided hotfix before the scheduled installation time of 15:00 today. We felt it was best to not take the chance of disturbing service at this critical time of the academic year, so we are now planning to fully test the hotfix this week and, if the results are favorable, we will consider installing the hotfix next Wednesday. Thanks for your understanding.
For those of you who plan ahead, we are planning another upgrade of the LUVLE servers during the Easter break time. Here's the scheduled dates:
Later we will more fully describe what we are doing and who these server changes will affect.
Tuesday, 15 March 2011 (18:45)
Full LUVLE service from all of our servers has been restored. The recap is as follows:
Tuesday, 15 March 2011
The ISS server monitoring tools indicated a slow responsiveness in one server of LUVLE starting about 12:30. This was intermittently decreasing the responsiveness to as slow as 15 seconds. To remedy this problem, we are adding another CPU. This requires that the server be shut down and restarted.
We apologise for any inconvenience but feel this will improve responsiveness for the foreseeable future.
Monday, 14 March 2011
On Saturday 12th March, ltg-domino suffered an unplanned re-start and was unavailable for 13 minutes. The cause was the same as all the recent re-starts on this server. We expect the hot fix (a software patch) that we received on Friday 11th March will prevent further recurrence of this problem after it is applied on Wednesday 16th March afternoon. LUVLE is scheduled to be unavailable for application of the hotfix at 3 pm, it should not take more than 30 minutes.
The MyPlace server suffered a unplanned re-start later on Saturday for 5 minutes, this is also a known but rarely occurring issue and one that should disappear when MyPlace is moved to a 64 bit platform at the end of term. MyPlace is scheduled to be unavailable to allow this move on the 4th and 5th of April.
Friday, 11 March 2011
Just before noon we received the latest Hotfix from IBM. It is intended to clear up the problem we have been having as demonstrated by 11 of the last 14 outages in six weeks. We have started our testing routine today and, if all goes well, plan to apply it to our LUVLE servers on Wednesday, 16 March starting at 15:00. Unfortunately we will have to shut down the servers before we can apply this fix, so you should plan to be off LUVLE at 15:00!
We have announced this plan in MOTD today, and will remove that notice as soon as the full service is restored. Thanks for your patience.
Thursday, 10 March 2011
One of the LUVLE servers, ltg-domino, had an unexpected outage this morning between 08:13 and 08:17 (5 minutes). Anyone trying to logon to LUVLE through MyModules would have found it unavailable for those five minutes. We estimate that about 73 users who were online at that time may have lost their connection. We are working closely with IBM to determine the cause of this intermittent problem, and have escallated it to the vice-president level.
Wednesday, 9 March 2011
One of the LUVLE servers (ltg-domino) had a short problem this morning at 09:10 for three minutes. It appears to be the same problem as listed for 4 March. IBM are being contacted.
Friday, 4 March 2011 (PM)
The two instances of one of the LUVLE servers (ltg-domino) being re-started were both caused by calls for information to LUSI. This is the same very intermittent problem that caused six other server problems last month. We have sent the server log files to IBM and expect them to send us another Hotfix soon. Our request is at the highest priority in the IBM queue.
Friday, 4 March 2011 (AM)
We have had two instances of one of the LUVLE servers (ltg-domino) being re-started at 08:42 and 08:59 this morning. They lasted 8 and 6 minutes respectively. Both re-starts were triggered by slow response times. We are investigating the cause, and will update this site with the results.
Thursday 24th February 2011
There have been occasional, unscheduled breaks of service since the previous update in December but over the last few days the server hosting MyModules and a large proportion of module spaces has suffered a short break in service each day. We know the problem is in IBM software and they have been on the case since this sequence began, we expect to receive a system hotfix from them soon. At the same time we are working on other ways to avoid the problem recurring.