Skip to Local Navigation
Skip to Content
California State University, Long BeachCalifornia State University, Long Beach
Skip to Content

ITS Incident Alerts

This page contains a list of service impacting IT incident alerts, which remain listed here for fourteen (14) calendar days.

Incidents within Past 14 Days

Open Incidents (Gold box): 0

MySQL Database Hosting Outage

Websites using MySQL01 are experiencing service outage

  • STATUS: Closed
  • REPORTED: 2012-05-21 9:56 AM
  • ACTUAL START: 2012-05-20 6:30 AM
  • RESOLVED: 2012-05-21 3:00 PM

Issue is resolved.  Production and Development services are restored.  Root cause is currently attributed to insufficient disk space caused by logs taking up too much space.  Root cause will be investigated further and addressed with configuration changes if necessary.

Web Hosting Degradation

The DAFTEST domain is having connection time-outs

  • STATUS: Closed
  • REPORTED: 2012-05-16 10:20 AM
  • ACTUAL START: 2012-05-16 10:20 AM
  • RESOLVED: 2012-05-16 10:25 AM

The DAFTEST domain http://daftest.csulb.edu/ is having connection time-outs.

Database Hosting Outage

SQL Server Outage

  • STATUS: Closed
  • REPORTED: 2012-05-16 2:16 AM
  • ACTUAL START: 2012-05-16 2:16 AM
  • RESOLVED: 2012-05-16 8:27 AM

The SQL server shutdown unexpectedly.  The following list of applications that connect to the Campus-SQL server may have experienced service outages:
-App-V (SoftGrid)
-Blackberry Enterprise Services
-CLA custom app
-EMS
-FMIS Franklin app
-Footprints
-Institutional Research Cognos app
-SARSGrid
-Sharepoint
-Student Services custom app

Root cause is under investigation.

Web Hosting Outage

Sites utilizing PHP may not load for some sites

  • STATUS: Closed
  • REPORTED: 2012-05-09 5:00 PM
  • ACTUAL START: 2012-05-09 5:17 PM
  • RESOLVED: 2012-05-09 5:30 PM

Some sites utilizing PHP were not loading.
Root Cause:  Web server three had a runaway PHP process yesterday evening at 5:17 PM.  This process consumed all Apache resources and would not allow the instance to respond to other requests.  Because our load balancer utilizes IP persistence to determine which system receives requests, some requests kept getting sent to the hung server.  Other requests received were routed to the other web servers which were fine.  A monitoring script eventually caught the hung process and killed it off.  The server fixed itself and was back on-line at 5:30 PM.

Communication Channels for incident Alerts

We anticipate using several different channels in order to gain a robust and redundant communication network. Choose one or more channels from which to be  informed of our incidents.

Email

If you are interested in receiving Incident Alerts via Email, please contact Sean Hernandez at 5-5651 or shernan7@csulb.edu. We are waiting for expressed interest before developing this channel.

RSS

If you are interested in receiving Incident Alerts via RSS, please contact Sean Hernandez at 5-5651 or shernan7@csulb.edu. We are waiting for expressed interest before developing this channel.

Twitter

If you are interested in receiving Incident Alerts via Twitter, please contact Sean Hernandez at 5-5651 or shernan7@csulb.edu. We are waiting for expressed interest before developing this channel.