<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/topics-files/atom2xhtml.xsl" type="text/xsl"?>
<!-- This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers.
This is a 512 byte XML comment that one must put into XML Atom feeds
such that browsers like Firefox 2.0 and IE7 will obey the XSL stylesheet.
Everybody hates overbearing browsers. -->
<feed xmlns="http://www.w3.org/2005/Atom"
><title
>Blog@Case Topics: problem report</title
><link rel="self" href="http://blog.case.edu/topics/problem%20report"
 /><id
>http://blog.case.edu/topics/problem%20report</id
><category term="problem report" label="problem report"
 /><link rel="related" href="http://blog.case.edu/topics/frontpaged" title="frontpaged"
 /><contributor
><name
>David Kovacic</name
><email
>david.kovacic@case.edu</email
><uri
>http://blog.case.edu/test/dave</uri
></contributor
><updated
>2010-05-26T21:09:51Z</updated
><entry
><title
>Problem Report: Network Outage - Buildings on Bellflower Road and E.117th.</title
><link href="http://blog.case.edu/its-status/2010/05/26/problem_report_network_outage_buildings_on_bellflower_road_and_e117th"
 /><id
>http://blog.case.edu/its-status/2010/05/26/problem_report_network_outage_buildings_on_bellflower_road_and_e117th</id
><published
>2010-05-26T21:09:45Z</published
><updated
>2010-05-26T21:09:51Z</updated
><category term="Problem Report" label="Problem Report"
 /><category term="frontpaged" label="frontpaged"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Network Outage - Buildings on Bellflower Road and E.117th.
Cause:     Power Outage
Affects:   see notes
Started:   05/26/2010 04:04 PM
Resolved:  
</pre>
<h4>Notes:</h4>
<p>Power outage along Bellflower Raod and E.117th. Affected buildings include AXO ZBT PGD, Bellflower House, Wolstein Hall, all rental apartments on East 117 street.
<br />
<br />Security and Plant Services have been notified. No ETA at this point.</p>
<hr />
<p>
<strong>Created:</strong> 05/26/2010 16:09:44 by wxc16</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: MyCase is down due to a DNS issue</title
><link href="http://blog.case.edu/its-status/2010/05/10/problem_report_mycase_is_down_due_to_a_dns_issue"
 /><id
>http://blog.case.edu/its-status/2010/05/10/problem_report_mycase_is_down_due_to_a_dns_issue</id
><published
>2010-05-10T13:33:34Z</published
><updated
>2010-05-10T13:50:02Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   MyCase is down due to a DNS issue
Cause:     DNS issues
Affects:   all users of MyCase
Started:   05/10/2010 08:27 AM
Resolved:  05/10/2010 08:47 AM
</pre>
<h4>Notes:</h4>
<p>The issue has been resolved.
<br />
<br /></p>
<p>MyCase is being directed to www.case.edu
<br />We are investigating and working with the DNS administrators to resolve this issue</p>
<hr />
<p>
<strong>Created:</strong> 05/10/2010 08:33:33 by gsr9</p>
<p>
<strong>Updates:</strong> 05/10/2010 08:49:33 by gsr9</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Tippit House, a complete network outage</title
><link href="http://blog.case.edu/its-status/2010/04/25/problem_report_tippit_house_a_complete_network_outage"
 /><id
>http://blog.case.edu/its-status/2010/04/25/problem_report_tippit_house_a_complete_network_outage</id
><published
>2010-04-25T21:50:43Z</published
><updated
>2010-04-25T21:50:49Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Tippit House, a complete network outage
Cause:     unknown
Affects:   everybody in the Tippit House, data and voice, wired and wireless
Started:   04/25/2010 03:29 PM
Resolved:  04/25/2010 04:39 PM
</pre>
<h4>Notes:</h4>
<p>Luckily, its Emerson/Liebert UPS might have protected
<br />its Cisco Catalyst Switch, a C-6513, from any electrical
<br />damage during the Lightning/Thunder Storm this afternoon.
<br />
<br />Luckily, we were able to reboot its Supervisor Two module,
<br />from the Rom-Mon-One console prompt this afternoon, and
<br />everything came back fine including its three analog VGs.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 04/25/2010 16:50:41 by euw</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: In the Sigma Nu House, over the past weekend, there was a flood in their laundry room in the their basement.</title
><link href="http://blog.case.edu/its-status/2010/04/19/problem_report_in_the_sigma_nu_house_over_the_past_weekend_there_was_a_flood_in_their_laundry_room_in_the_their_basement"
 /><id
>http://blog.case.edu/its-status/2010/04/19/problem_report_in_the_sigma_nu_house_over_the_past_weekend_there_was_a_flood_in_their_laundry_room_in_the_their_basement</id
><published
>2010-04-19T16:06:28Z</published
><updated
>2010-04-19T16:06:35Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   In the Sigma Nu House, over the past weekend, there was a flood in their laundry room in the their basement.  
Cause:     unknown
Affects:   In the Zeta Psi House, no one.  
Started:   04/19/2010 08:00 AM
Resolved:  04/19/2010 11:00 AM
</pre>
<h4>Notes:</h4>
<p>This morning, we found out that, there was a minor flood,
<br />in their basement, which luckily didn't directly affected
<br />their SER One, or wiring closet in their basement;
<br />so therefore, their computer network may continue running
<br />without being interrupted while they clear away the water.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 04/19/2010 11:06:27 by euw</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: In the Zeta Psi House, over the past weekend, there was a flood in their laundry room in the their basement.</title
><link href="http://blog.case.edu/its-status/2010/04/19/problem_report_in_the_zeta_psi_house_over_the_past_weekend_there_was_a_flood_in_their_laundry_room_in_the_their_basement"
 /><id
>http://blog.case.edu/its-status/2010/04/19/problem_report_in_the_zeta_psi_house_over_the_past_weekend_there_was_a_flood_in_their_laundry_room_in_the_their_basement</id
><published
>2010-04-19T15:58:23Z</published
><updated
>2010-04-19T20:34:02Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   In the Zeta Psi House, over the past weekend, there was a flood in their laundry room in the their basement.  
Cause:     Rupture in water pipe.
Affects:   In the Zeta Psi House, everyone, data and voice, wired and wireless.  
Started:   04/19/2010 08:00 AM
Resolved:  04/19/2010 03:32 PM
</pre>
<h4>Notes:</h4>
<p>This morning, we found out that, there was a major flood,
<br />in their basement, which directly affected their SER One, or wiring closet in their basement;
<br />so therefore, an electrician, he shut off the 60-Amps 220-Volts input electrical power to their SER One, because
<br />for their wiring closet in their basement,
<br />the Plant Services,
<br />they would like to try to drain-out and to dry-up,
<br />these flooded rooms in their basement today.
<br />
<br />Power has been restored. Switch is back up.</p>
<hr />
<p>
<strong>Created:</strong> 04/19/2010 10:58:21 by euw</p>
<p>
<strong>Updates:</strong> 04/19/2010 15:32:17 by deh8</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Budgeting System is down</title
><link href="http://blog.case.edu/its-status/2010/04/09/problem_report_budgeting_system_is_down"
 /><id
>http://blog.case.edu/its-status/2010/04/09/problem_report_budgeting_system_is_down</id
><published
>2010-04-09T21:02:53Z</published
><updated
>2010-04-09T21:10:17Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Budgeting System is down
Cause:     Unknown
Affects:   Budgeting Applicatuon
Started:   04/09/2010 02:00 PM
Resolved:  04/09/2010 04:05 PM
</pre>
<h4>Notes:</h4>
<p>The budgeting system is unresponsive and for all intents and purposes is down. The Windows application server is being rebooted to clear up the problem. ETA for the system back up is 4:30 pm.
<br />
<br />UPDATE: The Windows server was rebooted at 4:05 pm and everything is now working OK.</p>
<hr />
<p>
<strong>Created:</strong> 04/09/2010 16:02:52 by rxg263</p>
<p>
<strong>Updates:</strong> 04/09/2010 16:07:47 by rxg263</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: The following four Cisco Catalyst Switches; searslib-m1-E1-C3548, olin-rm404-eecs, greenhouse-m1-e1, uwest-p3-e1; they went off-line this morning at around seven o'clock.</title
><link href="http://blog.case.edu/its-status/2010/04/07/problem_report_the_following_four_cisco_catalyst_switches_searslibm1e1c3548_olinrm404eecs_greenhousem1e1_uwestp3e1_they_went_offline_this_morning_at_around_seven_oclock"
 /><id
>http://blog.case.edu/its-status/2010/04/07/problem_report_the_following_four_cisco_catalyst_switches_searslibm1e1c3548_olinrm404eecs_greenhousem1e1_uwestp3e1_they_went_offline_this_morning_at_around_seven_oclock</id
><published
>2010-04-07T13:55:57Z</published
><updated
>2010-04-07T13:56:02Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   The following four Cisco Catalyst Switches; searslib-m1-E1-C3548, olin-rm404-eecs, greenhouse-m1-e1, uwest-p3-e1; they went off-line this morning at around seven o'clock.  
Cause:     unknown
Affects:   some of the end-users in the Sear Library Building, Bio-Enterprise Building, Olin Hall, Green-House Building
Started:   04/07/2010 07:00 AM
Resolved:  04/07/2010 09:00 AM
</pre>
<h4>Notes:</h4>
<p>They are all back up and running now.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 04/07/2010 08:55:55 by euw</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Server backup service temporarily unavailable</title
><link href="http://blog.case.edu/its-status/2010/03/31/problem_report_server_backup_service_temporarily_unavailable"
 /><id
>http://blog.case.edu/its-status/2010/03/31/problem_report_server_backup_service_temporarily_unavailable</id
><published
>2010-04-01T02:48:15Z</published
><updated
>2010-04-01T02:48:21Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Server backup service temporarily unavailable
Cause:     Tape stuck in physical tape library drive
Affects:   Users of server backup service
Started:   03/31/2010 09:46 PM
Resolved:  03/31/2010 10:46 PM
</pre>
<h4>Notes:</h4>
<p>Must restart Networker servers in order to regain use of tape and tape drive. Only systems currently running backups or restores will be affected and there are none at this time. There are no backups scheduled to start during this time.</p>
<hr />
<p>
<strong>Created:</strong> 03/31/2010 21:48:14 by dxi16</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: server PULITZER emergency reboot</title
><link href="http://blog.case.edu/its-status/2010/03/31/problem_report_server_pulitzer_emergency_reboot"
 /><id
>http://blog.case.edu/its-status/2010/03/31/problem_report_server_pulitzer_emergency_reboot</id
><published
>2010-03-31T21:01:02Z</published
><updated
>2010-03-31T21:01:10Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   server PULITZER emergency reboot
Cause:     reboot needed to correct software hallucinations
Affects:   all users of PULITZER
Started:   03/31/2010 06:00 PM
Resolved:  03/31/2010 06:30 PM
</pre>
<h4>Notes:</h4>
<p>Symptoms include clients PCs getting bogus time settings when logging in to Pulitzer.</p>
<hr />
<p>
<strong>Created:</strong> 03/31/2010 16:01:01 by jan3</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Tippit House</title
><link href="http://blog.case.edu/its-status/2010/03/26/problem_report_tippit_house"
 /><id
>http://blog.case.edu/its-status/2010/03/26/problem_report_tippit_house</id
><published
>2010-03-27T03:12:28Z</published
><updated
>2010-03-27T03:12:34Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Tippit House
Cause:     unknown
Affects:   all of the End Users, in the Tippit House; for the Voice and the Data, for the Wireless and the Wired
Started:   03/26/2010 08:00 PM
Resolved:  03/26/2010 10:00 PM
</pre>
<h4>Notes:</h4>
<p>The Cisco Catalyst Switch, Tippit-M1-E1, a C-6513,
<br />its Supervisor Module lost its management; so therefore,
<br />we were able to restore its full capability luckily tonight.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 03/26/2010 22:12:27 by euw</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: IM server to be restarted</title
><link href="http://blog.case.edu/its-status/2010/03/26/problem_report_im_server_to_be_restarted"
 /><id
>http://blog.case.edu/its-status/2010/03/26/problem_report_im_server_to_be_restarted</id
><published
>2010-03-26T20:20:32Z</published
><updated
>2010-03-26T20:20:38Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   IM server to be restarted
Cause:     reported issues with gateways and performance
Affects:   access to the IM server
Started:   03/26/2010 06:00 PM
Resolved:  03/26/2010 06:15 PM
</pre>
<h4>Notes:</h4>
<p>Due to some reported issues with IM gateway connections and some performance problems, we will be restarting the IM server at 6:00pm. The interruption should be brief.</p>
<hr />
<p>
<strong>Created:</strong> 03/26/2010 15:20:31 by sdh7</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Brief Internet disruption</title
><link href="http://blog.case.edu/its-status/2010/03/17/problem_report_brief_internet_disruption"
 /><id
>http://blog.case.edu/its-status/2010/03/17/problem_report_brief_internet_disruption</id
><published
>2010-03-17T20:29:54Z</published
><updated
>2010-03-18T14:49:30Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Brief Internet disruption
Cause:     Ongoing NetEnforcer Maintenance
Affects:   All Case Internet users
Started:   03/18/2010 03:00 AM
Resolved:  03/18/2010 04:00 AM
</pre>
<h4>Notes:</h4>
<p>This procedure is complete and was successful.
<br />
<br /></p>
<p>Network Engineering is continuing ongoing NetEnforcer (traffic shaper) maintenance. There may be brief interruptions to Internet connectivity for the duration of the maintenance window.</p>
<hr />
<p>
<strong>Created:</strong> 03/17/2010 15:29:53 by cpr</p>
<p>
<strong>Updates:</strong> 03/18/2010 09:48:47 by cpr</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: In the Tomlinson Hall, an Emerson/Liebert UPS failed overnight.</title
><link href="http://blog.case.edu/its-status/2010/03/11/problem_report_in_the_tomlinson_hall_an_emersonliebert_ups_failed_overnight"
 /><id
>http://blog.case.edu/its-status/2010/03/11/problem_report_in_the_tomlinson_hall_an_emersonliebert_ups_failed_overnight</id
><published
>2010-03-11T12:33:37Z</published
><updated
>2010-03-11T12:33:43Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   In the Tomlinson Hall, an Emerson/Liebert UPS failed overnight.  
Cause:     unknown
Affects:   no one
Started:   03/11/2010 02:11 AM
Resolved:  03/11/2010 07:28 AM
</pre>
<h4>Notes:</h4>
<p>This morning, we were able to recover it successfully now.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 03/11/2010 07:33:36 by euw</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: NetEnforcer Traffic Shaper crashed</title
><link href="http://blog.case.edu/its-status/2010/03/10/problem_report_netenforcer_traffic_shaper_crashed"
 /><id
>http://blog.case.edu/its-status/2010/03/10/problem_report_netenforcer_traffic_shaper_crashed</id
><published
>2010-03-10T15:20:03Z</published
><updated
>2010-03-10T22:53:08Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   NetEnforcer Traffic Shaper crashed
Cause:     Unknown
Affects:   All Case Internet users
Started:   03/10/2010 09:53 AM
Resolved:  03/10/2010 10:10 AM
</pre>
<h4>Notes:</h4>
<p>The NetEnforcer crashed when we attempted to make a connection to it via its management station. We have not determined the cause of the failure.
<br />
<br />The NetEnforcer is currently in bypass mode, passing traffic without inspection, while Engineers investigate.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 03/10/2010 10:20:02 by cpr</p>
<p>
<strong>Updates:</strong> 03/10/2010 17:44:39 by cpr</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Enrollment Management server hang - rebooted server</title
><link href="http://blog.case.edu/its-status/2010/03/09/problem_report_enrollment_management_server_hang_rebooted_server"
 /><id
>http://blog.case.edu/its-status/2010/03/09/problem_report_enrollment_management_server_hang_rebooted_server</id
><published
>2010-03-09T16:11:52Z</published
><updated
>2010-03-09T21:06:17Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Enrollment Management server hang - rebooted server
Cause:     Investigating possible harware issue
Affects:   Enrollment Management web users
Started:   03/09/2010 11:07 AM
Resolved:  03/09/2010 04:01 PM
</pre>
<h4>Notes:</h4>
<p>Received report that one of the enrollment management application was not responding. Identified server that was not responsive. Rebotted the server to investigate the issue.
<br />
<br />Replaced server chassis with spare server and moved disks to new chassis. Rand chkdsk, replaced Perc drivers, and rebooted. System is operational from Server and Storage Engineering perspective and has been turned over to the ITEM group for application verification.</p>
<hr />
<p>
<strong>Created:</strong> 03/09/2010 11:11:51 by rak7</p>
<p>
<strong>Updates:</strong> 03/09/2010 16:01:41 by rak7</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Name Server (ns3) has crashed</title
><link href="http://blog.case.edu/its-status/2010/03/09/problem_report_name_server_ns3_has_crashed"
 /><id
>http://blog.case.edu/its-status/2010/03/09/problem_report_name_server_ns3_has_crashed</id
><published
>2010-03-09T13:06:08Z</published
><updated
>2010-03-09T14:41:54Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Name Server (ns3) has crashed
Cause:     Resource shortage
Affects:   Multiple services
Started:   03/09/2010 07:55 AM
Resolved:  03/09/2010 08:50 AM
</pre>
<h4>Notes:</h4>
<p>The server had not crashed, and was still answering name queries (just not all of them). It experienced a resource shortage caused by running out of file handles, which resulted in it not being able to accept every new connection. The root cause of the shortage is unknown. Restarting the name server fixed the problem.
<br />
<br />Since there are four name servers at Case, and client name resolution has failover built in, the loss of one name server should have minimal impact.
<br />
<br /></p>
<p>Network Engineering has been called and is looking into the problem.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 03/09/2010 08:06:07 by dak</p>
<p>
<strong>Updates:</strong> 03/09/2010 09:36:26 by cpr</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Brief Internet Disruption</title
><link href="http://blog.case.edu/its-status/2010/03/08/problem_report_brief_internet_disruption"
 /><id
>http://blog.case.edu/its-status/2010/03/08/problem_report_brief_internet_disruption</id
><published
>2010-03-08T19:53:17Z</published
><updated
>2010-03-08T19:53:23Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Brief Internet Disruption
Cause:     Diagnostic Tool execution caused Packet Shaper to stop passing traffic
Affects:   All Case Internet users
Started:   03/08/2010 02:40 PM
Resolved:  03/08/2010 02:42 PM
</pre>
<h4>Notes:</h4>
<p>Running one of the diagnostic tools recommended by the vendor to verify the health of the traffic shaping appliance resulted in the device not passing traffic for a period of about 65 seconds.
<br />
<br />Network Engineers aborted the execution of the tool when we realized its effect.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 03/08/2010 14:53:16 by wxc16</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Tomlinson Hall, Room 223-A, SER 1</title
><link href="http://blog.case.edu/its-status/2010/03/05/problem_report_tomlinson_hall_room_223a_ser_1"
 /><id
>http://blog.case.edu/its-status/2010/03/05/problem_report_tomlinson_hall_room_223a_ser_1</id
><published
>2010-03-05T18:16:52Z</published
><updated
>2010-03-05T18:17:01Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Tomlinson Hall, Room 223-A, SER 1
Cause:     unknown
Affects:   for the data and voice, the wired and wireless, all of the End-Users, in the Tomlinson Hall
Started:   03/05/2010 11:49 AM
Resolved:  03/05/2010 12:50 PM
</pre>
<h4>Notes:</h4>
<p>This morning, the input power to the Emerson/Liebert UPS,
<br />it tripped by itself; so therefore, I restored its power.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 03/05/2010 13:16:50 by euw</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: Case Wiki Down</title
><link href="http://blog.case.edu/its-status/2010/03/01/problem_report_case_wiki_down"
 /><id
>http://blog.case.edu/its-status/2010/03/01/problem_report_case_wiki_down</id
><published
>2010-03-01T12:20:06Z</published
><updated
>2010-03-01T12:20:12Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   Case Wiki Down
Cause:     Log rotation program silently failing
Affects:   Wiki users
Started:   03/01/2010 03:15 AM
Resolved:  03/01/2010 07:08 AM
</pre>
<h4>Notes:</h4>
<p>A log rotation was silently failing which caused the web server logs to grow beyond acceptable limits, causing the web server to that serves the wiki to crash.
<br />
<br />We have manually rotated the logs and restarted the wiki. We will look into why the log rotation was failing and will better instrument the wiki itself so that if it should crash again we will receive more timely notification.
<br /></p>
<hr />
<p>
<strong>Created:</strong> 03/01/2010 07:20:05 by dak</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
><entry
><title
>Problem Report: MyCase Portal Unvailable</title
><link href="http://blog.case.edu/its-status/2010/02/25/problem_report_mycase_portal_unvailable"
 /><id
>http://blog.case.edu/its-status/2010/02/25/problem_report_mycase_portal_unvailable</id
><published
>2010-02-25T12:16:39Z</published
><updated
>2010-02-25T12:16:47Z</updated
><category term="Problem Report" label="Problem Report"
 /><content type="xhtml"
><div xmlns="http://www.w3.org/1999/xhtml"
>
<pre>
Problem:   MyCase Portal Unvailable
Cause:     Unhappy following the db maintenance this morning
Affects:   All users of the MyCase portal
Started:   02/25/2010 06:50 AM
Resolved:  02/25/2010 07:10 AM
</pre>
<h4>Notes:</h4>
<p>The MyCase portal services were restarted and tested successfully following this morning's database maintenance but then began having trouble about an hour later. Most likely cause is a process that did not stop correctly on restart. A full shutdown and restart of all portal services corrected the problem.</p>
<hr />
<p>
<strong>Created:</strong> 02/25/2010 07:16:38 by jms20</p>
<p>
<strong>Updates:</strong>
</p>
<hr size="3" noshade="noshade" />
</div
></content
><author
><name
></name
><email
>blog-admin@case.edu</email
><uri
>http://blog.case.edu/its-status</uri
></author
></entry
></feed
>
