|
|
| Line 1: |
Line 1: |
| | <!-- *************** BEGIN ACTIVE NOTICES **************************** --> | | <!-- *************** BEGIN ACTIVE NOTICES **************************** --> |
| | | | |
| − | == <span style="color:#ff0000">SERVICE OUTAGES <span>== | + | == {{red|CS IT STAFF AVAILABILITY}} == |
| − | <br>
| |
| − | <!-- === UNPLANNED ''JHU'' SERVICE OUTAGES ===
| |
| | | | |
| − | :'''WHEN:''' 4/23/18 3:45pm | + | * The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus. |
| | + | * We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only. |
| | + | * Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance. |
| | + | * Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication. |
| | + | * For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details. |
| | | | |
| − | :'''WHAT:''' Unexpected JHU Network Outage
| + | <br><p> |
| | | | |
| − | :'''DESCRIPTION:''' At this time, the university is experiencing some kind of network outage. Also, access to the Hopkins wifi may not available. Accessing to outside of JHU (and to inside of JHU) seems to down. JHU is aware of the issue and is currently working on it.
| |
| | | | |
| − | :Because our CS websites (including this support wiki) use elements from outside, connections to our websites might be slow or non-existent.
| + | <!-- |
| − | | + | == {{red|JHU IT SERVICE OUTAGES AFFECTING CS IT SERVICES}} == |
| − | :'''UPDATE:''' 4pm - Good news! Some or most network connectivity has returned. Many systems look to be reachable; there might still be some services that are delayed. We're thinking that JHU has fixed the issue and systems might be slowing coming back online. JHU wifi looks to have returned.
| + | === PLANNED ''JHU'' SERVICE OUTAGES === |
| − | | |
| − | <br> -->
| |
| − | | |
| − | === UNPLANNED CS SERVICE OUTAGES === | |
| − | | |
| − | ==== Slow Access To Various CS IT Services====
| |
| − | | |
| − | :'''4/30/18 6:30am:'''
| |
| − | | |
| − | ::We are experiencing very slow access to various CS IT services, including web, DNS, and mail, perhaps some others. We are investigating now.
| |
| − | | |
| − | <!--:'''UPDATE 6:50am'''
| |
| − | | |
| − | ::''Problem '''resolved'''.'' All operations should be back to normal.-->
| |
| − | <!--:None at this time.-->
| |
| − | <br>
| |
| − | | |
| − | === PLANNED CS SERVICE OUTAGES === | |
| − | | |
| − | :None at this time.
| |
| − | <!-- -->
| |
| − | <!--******************TEMPLATES BEGIN HERE*****************-->
| |
| − | <!-- -->
| |
| − | <!-- ******TEMPLATE GRAD NET OUTAGE*****
| |
| − | ====Major CS Grad/Research Net service outage (mail, web, home directories, login, etc.) ====
| |
| − | | |
| − | '''WHAT:''' Major CS Grad/Research Net (and some Ugrad) IT services outage, as we apply security updates to our systems. | |
| − | | |
| − | '''WHEN:''' '''''Rescheduled for''''' Thursday, January 18, from 5am to approx 7am.
| |
| − | | |
| − | '''DETAILS:''' Many CS Grad/Research Net servers will be shut down to apply security updates. We will apply these updates on Thursday, January 18, from 5am to approximately 7am.
| |
| − | | |
| − | During the process of applying updates, several of our CS services will be unavailable. If there are any unexpected complications during the update process that will delay the restoration of services, we will update the CS IT Support Wiki's Notices page at https://support.cs.jhu.edu/wiki/Notices
| |
| − | | |
| − | Suspended (Unavailable) Grad/Research Net services while the servers are updated:
| |
| − | | |
| − | * CS Mail service, both incoming and outgoing, will be suspended for CS Grad/Research Net users.
| |
| − | | |
| − | * Incoming mail should be queued by the sender until our mail service is back up again. Outgoing mail will not be available.
| |
| − | | |
| − | * IMAP, POP, and Webmail from our CS (Grad/Research Net) Mail server will be unavailable.
| |
| − | | |
| − | * Some CS webpages, including user (and possibly lab and other CS pages), will be unavailable.
| |
| − | | |
| − | * Grad/Research Net user accounts/home directories will be inaccessible during the downtime.
| |
| − | | |
| − | * SMB File Shares (CS Office Staff uses these) will be unavailable.
| |
| − | | |
| − | * ssh service to our CS Grad/Research Net Linux boxes (masters1 through masters16, gradx, and gradz) will be unavailable.
| |
| − | | |
| − | * Console (desktop) access to masters1 through masters16 will be unavailable.
| |
| − | | |
| − | * MySQL service via the mysql.cs.jhu.edu server will be unavailable.
| |
| − | | |
| − | Note to Ugrad Net users: During the Grad Net servers' security updates process, email directed to your ugrad acct @cs.jhu.edu will not be immediately delivered. Other Ugrad Net services should remain available. Also, we will be applying security patches on the CS Ugrad net the next day, so you'll see an email for that at some point soon.
| |
| − | | |
| − | Updates, if necessary, will be posted here.
| |
| − | ******TEMPLATE END*****-->
| |
| − | <!-- -->
| |
| − | <!--******TEMPLATE BEGIN - UGRAD NET OUTAGE
| |
| − | | |
| − | ::::'''''NOTE: DATE CHANGE BELOW for OUTAGE #1!!!!!!!!'''''
| |
| − | | |
| − | ====OUTAGE #1 - Major CS ''UGrad Net'' service outage (mail, web, home directories, login, etc.) ==== | |
| − | | |
| − | '''Update 2''': As of 7:45 am, all services are available.
| |
| − | | |
| − | '''Update''': As of 7:00 am, all services are available ''except for ugradx''. It will need some additional time to finish its updates.
| |
| − | | |
| − | '''WHAT:''' Major CS Ugrad Net IT services outage, as we apply security updates to our systems.
| |
| − | | |
| − | '''WHEN:''' '''''Rescheduled for''''' Tuesday, January, 23, from 5am to approx 7am.
| |
| − | | |
| − | '''DETAILS:''' Many of our CS Ugrad Net servers will be shut down to apply security updates. We will apply these updates on Tuesday, January 23, from 5am to approximately 7am.
| |
| − | | |
| − | During the process of applying updates, several of our CS services will be unavailable. If there are any unexpected complications during the update process that will delay the restoration of services, we will update the CS IT Support Wiki's Notices page at https://support.cs.jhu.edu/wiki/Notices
| |
| − | | |
| − | Suspended (Unavailable) Ugrad Net services while the servers are updated:
| |
| − | | |
| − | * CS Ugrad Mail service, both incoming and outgoing, will be suspended for CS Ugrad Net users.
| |
| − | | |
| − | * Incoming mail should be queued by the sender until our mail service is back up again. Outgoing mail will not be available.
| |
| − | | |
| − | * IMAP, POP, and Webmail from our CS (Ugrad Net) Mail server will be unavailable.
| |
| − | | |
| − | * CS Ugrad Net webpages will be unavailable.
| |
| − | | |
| − | * CS Ugrad Net user accounts/home directories will be inaccessible during the downtime.
| |
| − | | |
| − | * ssh service to our CS Ugrad Net Linux boxes (ugrad1 through ugrad24, ugradx, and ugradz) will be unavailable.
| |
| − | | |
| − | * Console (desktop) access to ugrad1 through ugrad24 will be unavailable.
| |
| − | | |
| − | * MySQL service via the dbase.cs.jhu.edu server (Dr. Yarowsky's class) will be unavailable.
| |
| − | | |
| − | Updates, if necessary, will be posted here.
| |
| | --> | | --> |
| − | <!--:'''WHAT:''' Emergency reboot of ''blaze'', the dept's main Grad/Research net mail server. | + | <!-- |
| − | | + | === UNPLANNED ''JHU'' SERVICE OUTAGES === |
| − | :'''WHEN:''' ''(TODAY!)'' Tuesday, Dec. 12 @ noon and lasting approx 1/2 hour if all goes well.
| |
| − | | |
| − | :'''DETAILS:'''
| |
| − | | |
| − | ::We have discovered an issue with our mail spool disk on ''blaze'' our Grad/Research net mail server which must be corrected right away. As such, we expect that a configuration change and reboot should fix the problem.
| |
| − | | |
| − | ::We plan to do this shortly, at ''noon today (lunchtime.)'' The reboot should take approx. 1/2 hour if all goes well. If there are issues, it might take some additional time to complete the repair.
| |
| − |
| |
| − | ::During the reboot time, there will be ''no CS email service in or out of the CS Grad/Research network.'' You will not be able to send or receive mail (IMAP/POP/etc.) through blaze (smtp.cs.jhu.edu/pop.cs.jhu.edu) or via webmail during that time. Also, DNS might be slow or non-existent, depending upon your client's own configuration.
| |
| − | | |
| − | ::You also might experience slow connection times to www.cs.jhu.edu.
| |
| − | | |
| − | ::Grad Net Lab Linux systems (masters1 through masters16, gradx, and gradz) may experience a short delay as their NIS service connects to a different server.
| |
| − | | |
| − | ::Any updates and notice of completion will be presented through this NOTICES page today.
| |
| − | | |
| − | :'''''UPDATE:''''' 12/12/17 at 12:15pm
| |
| − | | |
| − | ::Reboot successful! Blaze is back in operation and services have been returned to normal operation.
| |
| | --> | | --> |
| | | | |
| − | <!-- :'''WHAT:''' Brief CS network outage
| + | == {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} == |
| | | | |
| − | :'''WHEN:''' ''Rescheduled for'' Thursday, July 20, from 9am to 9:30am.
| |
| | | | |
| − | :'''DETAILS:''' JHU Networking (in conjunction with JHU Network Security) will be moving the various CS Networks in Malone Hall from one firewall platform to another. This will ''now'' take place on Thursday, July 20 at 9am and should only last approximately 5 minutes or so. But, we're providing a 30 minute window in case JHU Networking needs to troubleshoot any issues.
| + | === UNPLANNED CS IT SERVICE OUTAGES === |
| | | | |
| − | :During the network outage, CS systems might not be seen by each other, and network traffic between CS and outside-of-CS may be halted. Many CS services will be unavailable when the network is unavailable. Again, JHU Networking expects this to be a brief network outage, so you might only experience a short system hang. | + | :None at this time. |
| | | | |
| − | We will update this Notices page in case there are delays with restoring any of our services.
| + | === PLANNED CS IT SERVICE OUTAGES === |
| | | | |
| | + | <!--:None at this time.--> |
| | | | |
| | + | ==== Malone '''MH 122''' ''and'' '''G61''' Ugrad and Masters Labs {{red|'''''Closure'''''}}==== |
| | | | |
| | + | :'''WHAT:''' Malone Hall MH 122 '''and''' Malone Hall G61, both the Masters and Ugrad sides of the lab, '''and ''all'' the lab Linux computers, will be closed to CS students due to an ACM Programming Contest. |
| | | | |
| − | -->
| + | :'''WHEN:''' Starting Friday evening, November 15, 5pm '''through''' Saturday, November 16, 9pm. |
| | | | |
| − | <!-- ****** FILE SERVER OUTAGE TEMPLATE ******
| + | :'''DETAILS:''' |
| | | | |
| − | ===Planned Outage 1: CS Ugrad Net File Server Upgrade (barley.cs.jhu.edu)===
| + | : Both the MH 122 '''and''' G61 Masters and Ugrad Labs will be used for an ACM Programming Contest and will therefore be '''''closed''''' to those not participating in the contest. |
| | | | |
| | + | : Additionally, all of the labs' Linux computers (grad1 through grad16 and ugrad1 through ugrad24) will be unavailable during the time period referenced above. |
| | | | |
| − | :'''WHAT:''' Major <span style="color:#ff0000">CS *Undergrad* Net computing services outage</span>, as we upgrade our CS Undergrad Net home directory file server,''' barley.cs.jhu.edu'''
| + | * During the lab closure times, compute servers, gradx.cs.jhu.edu, gradz.cs.jhu.edu, ugradx.cs.jhu.ed, and ugradz.cs.jhu.edu '''''will continue to be available remotely''''', via SSH. |
| | | | |
| − | :'''WHEN:''' Wednesday, January 18, from ''8am to approx 11am''.
| + | * We have to take down the lab systems late that Friday afternoon. At the end of the ACM contest that Saturday night, the coordinators of that contest will be turning our lab computer systems back on. Most should boot normally. But, if some do not, just trying using an alternate one in the lab. We'll be back in the Monday afterwards and can check on any systems that didn't boot normally. (And don't forget, as mentioned above our compute servers -- gradx, gradz, ugradx, ugradz -- will continue to be remotely available, even if the lab systems are not.) |
| | | | |
| − | :'''DETAILS:''' Our CS Undergrad Net home directory file server, barley.cs.jhu.edu, will be shut down to perform an major upgrade to its operating system.
| + | * The printers in MH 122 and MH G61 will remain online, but, please pick up your printouts outside of the contest hours. |
| | | | |
| − | :Due to this shutdown for an upgrade, several of our CS '''''Ugrad''''' Net services will be unavailable during this time. If there are any unexpected complications during the upgrade process that will delay the restoration of services, we will update the CS IT Support Wiki's Notices page at [https://support.cs.jhu.edu/wiki/Notices https://support.cs.jhu.edu/wiki/Notices]
| + | <br> |
| | | | |
| − | ====Suspended (Unavailable) Ugrad Net services while ''barley.cs.jhu.edu'' is down==== | + | == {{red|CS COMPUTING LAB AVAILABILITY}} == |
| | | | |
| − | :::*'''CS Ugrad Mail service,''' both incoming and outgoing, will be suspended for CS Ugrad Net users (as this fileserver works in tandem with our CS Ugrad mail server.) Incoming mail should be queued until our Ugrad mail service is back up again. Outgoing mail from CS Ugrad Net users will not be available.
| |
| | | | |
| − | :::*'''IMAP, POP, and Webmail''' from our CS Ugrad Mail server will be unavailable.
| |
| | | | |
| − | :::*'''Webpages''' served from our CS Ugrad webserver will be unavailable.
| + | <!-- ***** NORMAL POSTING MH 122****** --> |
| − | | + | :'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access. |
| − | :::*'''Ugrad Net user accounts/home directories''' will be inaccessible during the downtime.
| + | :{{red|However, please see the info above regarding the mid-November lab closure and systems unavailability.}} |
| − | | |
| − | :::*'''ssh service to our CS Ugrad Net Linux boxes''' (ugrad1 through ugrad24,and ugradx) will be unavailable.
| |
| − | | |
| − | :::*'''Console (desktop) access to ugrad1 through ugrad24''' will be unavailable. However, although the CS Ugrad computers will be unavailable during the fileserver downtime, the CS Ugrad Labs will remain open.
| |
| − | | |
| − | :::*'''MySQL service via the dbase.cs.jhu.edu server''' (used by a databases class) will be unavailable.
| |
| − | | |
| − | :Future updates will be posted on the [https://support.cs.jhu.edu/wiki/Notices Notices] page of the CS IT Support Wiki
| |
| − | | |
| − | ===Planned Outage 2: Databases Class MySQL Database Server ('''dbase.cs.jhu.edu''') Unavailability===
| |
| − | | |
| − | :'''WHAT:''' The Databases class's MySQL database server, dbase.cs.jhu.edu, will be unavailable when the CS Ugrad Net's fileserver, barley.cs.jhu.edu, is being upgraded (see above.)
| |
| − | | |
| − | :'''WHEN:''' Wednesday, January 18, from ''8am to approx 11am''.
| |
| − | | |
| − | :'''DETAILS:''' dbase.cs.jhu.edu uses the CS Ugrad Net file server and will therefore be unavailable during the barley.cs.jhu.edu upgrade time.
| |
| − | | |
| − | :Future updates will be posted on the [https://support.cs.jhu.edu/wiki/Notices Notices] page of the CS IT Support Wiki
| |
| − | | |
| − | | |
| − | ****** END FILE SERVER OUTAGE TEMPLATE ******-----> | |
| − | <!-- ------------------------------------------------------------- -->
| |
| − | <!-- **VM Server Shutdown TEMPLATE **
| |
| − | | |
| − | '''WHAT:''' The dept's Virtual Machine will be shutdown.
| |
| − | | |
| − | '''WHEN:''' Wednesday, January 11 from 6am to 3pm (or earlier) | |
| − | | |
| − | We need to do some work on the VM server and will be taking it down during the above date and time.
| |
| − | | |
| − | As part of the shutdown process, we will suspend most or all of the VMs; some
| |
| − | VMs might have to be shutdown all the way instead. And when the VM server is back up and running again, we will restart or unsuspend all VMs. In all cases, VM owner intervention should not be needed; we can handle this remotely.
| |
| − | | |
| − | After the VM server is up and running again, VM owners will receive an announcement (and updates will be posted here), and, we do ask that VM owners check to make sure their VMs are running as expected. Please email [mailto:support@cs.jhu.edu support@cs.jhu.edu] if there are issues.
| |
| − | | |
| − | ** END VM Server Shutdown TEMPLATE** -->
| |
| − | <!-- **Begin Specific Client shutdown TEMPLATE**
| |
| − | | |
| − | '''WHAT:''' ugradz.cs.jhu.edu (one of our CS Dept Linux Ugrad Net compute servers) will go down for a memory upgrade.
| |
| − | | |
| − | '''WHEN:''' Thursday, April 6, from 9am to 11am.
| |
| − | | |
| − | '''DETAILS:''' ugradz will be taken offline so that its memory can be upgraded. While ugradz is down for its memory upgrade, you can still access our other Ugrad Net Fedora 25
| |
| − | systems (ugrad1 through ugrad24 and ugradx.) Info about our Fedora systems can be found at: https://support.cs.jhu.edu/wiki/Category:Linux_Clients
| |
| − | | |
| − | Please make sure you are logged off of ugradz before the upgrade time.
| |
| − | | |
| − | Any updates will be posted here.
| |
| − | | |
| − | **End Specific Client shutdown TEMPLTE** -->
| |
| − | | |
| − | == <span style="color:#ff0000">CS COMPUTING LAB AVAILABILITY </span> ==
| |
| − | | |
| − | === MH 122 (Ugrad Lab) ===
| |
| − | | |
| − | ====Projector in the main MH 122 Ugrad lab is down.====
| |
| − | | |
| − | : 11/2/17 - Kit-cats (JHU's A/V group) has been called. They have been out and are evaluating their options for repair. ETA for repair is unknown at this time.
| |
| − | | |
| − | | |
| − | <!--:None at this time.-->
| |
| − | | |
| − | === MH G-61 (Masters/Ugrad Lab)===
| |
| − | | |
| − | :None at this time.
| |
| − | | |
| − | <!-- *************** END ACTIVE NOTICES ********************-->
| |
| | <!-- | | <!-- |
| − | *
| + | :'''MH 122 ''UNAVAILABILITY''''' |
| − | *
| |
| − | * ********************* BEGIN TEMPLATES ********************
| |
| − | *
| |
| − | *
| |
| − | *
| |
| | --> | | --> |
| − | <!-- ************ LAB CLOSURE TEMPLATE - START ***************
| |
| − |
| |
| − | ==== '''PLANNED CLOSURE''''' ====
| |
| − |
| |
| − |
| |
| − | '''''WHERE:''''' Malone Hall G-61, both the Masters and Ugrad sides of the lab.
| |
| − |
| |
| − | '''''WHEN:''''' Monday, March 14 & Tuesday, March 15, from 6am to 12 Noon.
| |
| − |
| |
| − | '''''WHY:''''' Network cable installation. The lab will be closed those two
| |
| − | mornings as workers install additional network cable.
| |
| − |
| |
| − | =====NOTES:=====
| |
| − |
| |
| − | * During the lab closure times, the masters and ugrad Linux computers in G-61 will continue to be available remotely, via SSH.
| |
| − |
| |
| − | * Ugrad Lab, MH 122 will not be affected and will remain open during those times.
| |
| − |
| |
| − | ************* LAB CLOSURE TEMPLATE- END *************-->
| |
| − | <!-- ********** BARLEY SHUTDOWN TEMPLATE - START *************
| |
| − |
| |
| − |
| |
| − | ===Planned Outage 1: CS Ugrad Net File Server Repair (barley.cs.jhu.edu)===
| |
| − |
| |
| − | UPDATE: 10/4/16 7:15am All systems back in operation!
| |
| − |
| |
| − |
| |
| − | :'''WHAT:''' Major CS *Undergrad* Net IT services outage, as we make repairs to the CS Undergrad Net file server, '''barley.cs.jhu.edu'''
| |
| − |
| |
| − | :'''WHEN:''' Tuesday, October 4, from ''6am to approx 8am''.
| |
| − |
| |
| − | :'''DETAILS:''' Our CS Undergrad Net home directory file server, barley.cs.jhu.edu, will be shut down to swap out a motherboard, since its own motherboard is reporting errors.
| |
| − |
| |
| − | :Due to this shutdown for repair, several of our CS Ugrad Net services will be unavailable during this time. If there are any unexpected complications during the repair process that will delay the restoration of services, we will update the CS IT Support Wiki's Notices page at [https://support.cs.jhu.edu/wiki/Notices https://support.cs.jhu.edu/wiki/Notices]
| |
| − |
| |
| − | <span style="color:#ff0000">UPDATE: 10/4/16 7:15am All systems back in operation! </span>
| |
| − |
| |
| − | ====Suspended (Unavailable) Ugrad Net services while ''barley.cs.jhu.edu'' is down====
| |
| − |
| |
| − | :::*'''CS Ugrad Mail service,''' both incoming and outgoing, will be suspended for CS Ugrad Net users (as this fileserver works in tandem with our CS Ugrad mail server.) Incoming mail should be queued until our mail service is back up again. Outgoing mail from CS Ugrad Net users will not be available.
| |
| − |
| |
| − | :::*'''IMAP, POP, and Webmail''' from our CS Ugrad Mail server will be unavailable.
| |
| − |
| |
| − | :::*'''Webpages''' served from our CS Ugrad webserver will be unavailable.
| |
| − |
| |
| − | :::*'''Ugrad Net user accounts/home directories''' will be inaccessible during the downtime.
| |
| − |
| |
| − | :::*'''ssh service to our CS Ugrad Net Linux boxes''' (ugrad1 through ugrad24,and ugradx) will be unavailable.
| |
| − |
| |
| − | :::*'''Console (desktop) access to ugrad1 through ugrad24''' will be unavailable. However, although the CS Ugrad computers will be unavailable during the repair time, the CS Ugrad Labs will remain open.
| |
| − |
| |
| − | :::*'''MySQL service via the dbase.cs.jhu.edu server''' (used by a databases class) will be unavailable.
| |
| − |
| |
| − | :Future updates will be posted on the [https://support.cs.jhu.edu/wiki/Notices Notices] page of the CS IT Support Wiki
| |
| − |
| |
| − | <span style="color:#ff0000">UPDATE: 10/4/16 7:15am All systems back in operation! </span>
| |
| | | | |
| | | | |
| | + | <!-- ****** NORMAL POSTING G61 ********** --> |
| | + | :'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access. |
| | + | :{{red|However, please see the info above regarding the mid-November lab closure and systems unavailability.}} |
| | <br> | | <br> |
| | | | |
| − | ===Planned Outage 2: Databases Class MySQL Database Server ('''dbase.cs.jhu.edu''') Unavailability=== | + | == {{red|AUDIO/VISUAL (A/V) OUTAGES}} == |
| − | | + | :None at this time. |
| − | :'''WHAT:''' The Databases class's MySQL database server, dbase.cs.jhu.edu, will be unavailable when the CS Ugrad Net's fileserver, barley.cs.jhu.edu, is being repaired (see above.)
| |
| − | | |
| − | :'''WHEN:''' Tuesday, October 4, from ''6am to approx 8am''.
| |
| − | | |
| − | :'''DETAILS:''' dbase.cs.jhu.edu uses the CS Ugrad Net file server and will therefore be unavailable during the barley.cs.jhu.edu repair time.
| |
| − | | |
| − | :Future updates will be posted on the [https://support.cs.jhu.edu/wiki/Notices Notices] page of the CS IT Support Wiki
| |
| − | | |
| − | <span style="color:#ff0000">UPDATE: 10/4/16 7:15am All systems back in operation! </span>
| |
| − | | |
| − | | |
| − | <br>
| |
| − | | |
| − | ********** BARLEY SHUTDOWN TEMPLATE - END ************* -->
| |
| − | <!-- ******************* MINOR OUTAGE TEMPLATE BEGIN ***********************
| |
| − | | |
| − | '''Wed, July 30, 9am through noon:''' ''Entire Undergrad Net'' (clients and servers) will be down as we complete system maintenance and move some equipment to a different rack.
| |
| − | | |
| − | Additionally, the Ugrad Net web and mail service will be unavailable during that time. (Incoming ugrad net mail should queue up on another of our mail servers during that time, until the ugrad mail server is back up and running and transfers the mail.)
| |
| − | | |
| − | ************** MINOR OUTAGE TEMPLATE END ********************* -->
| |
| − | <!-- ************** MAJOR OUTAGE TEMPLATE BEGIN *********************
| |
| − | | |
| − | '''MAJOR''' motherboard repair of ''rtfm.cs.jhu.edu'', one of our main CS ''Grad/Research'' Net file system servers, will create up to (but hopefully, much shorter than) 6-hour planned downtime for the Grad/Research Network. Our hardware service/repair company will be on-site completing repairs.
| |
| − | | |
| − | '''Outage will begin at 12am (midnight), Thursday, 8/22, and will last until 6am (or earlier) Thursday.'''
| |
| − | | |
| − | During that time, the following services will be ''unavailable'':
| |
| − | | |
| − | * ''Email in or out on the Grad/Research Net will be disabled.'' (Connections to smtp.cs.jhu.edu and pop.cs.jhu.edu will fail during that time. However, incoming mail to CS should queue at an alternative server.)
| |
| − | | |
| − | * ''Email on the Undergrad Net will be disabled during this time'' (as CS Ugrad e-mail addresses are registered via a server on the CS Grad Net.)
| |
| − | | |
| − | * ''DNS will only be available if you've configured your computer with a secondary DNS server.'' If you don't have a secondary server in your computer's DNS defined, please add 128.220.2.7 You may notice a delay in DNS name resolution when falling back to the secondary server.
| |
| − | | |
| − | * ''Grad/Research Net user accounts/home directories will be inaccessible'' during the downtime.
| |
| − | | |
| − | * ''Access to any of our Grad/Research Net linux clients (including gradx and masters1 through masters16, as well as Dr. Smith's pllab machines that we maintain) will be unavailable''
| |
| − | | |
| − | * ''peregrine.cs.jhu.edu (our Solaris login server) will be unavailable''
| |
| − | | |
| − | * ''Our mysql server, mysql.cs.jhu.edu, will be unavailable.''
| |
| − | | |
| − | * ''Samba shares will be unavailable.''
| |
| − | | |
| − | * ''Your Grad/Research Net web pages will be unavailable.'' (The webserver is expected to be serving minimal pages, mostly notices, during that time.)
| |
| − | | |
| − | ******************** MAJOR OUTAGE TEMPLATE END ************************* -->
| |
| − | <!-- ********* JHU-WIDE OUTAGES TEMPLATE - START *******************
| |
| − | | |
| − | ==JHU-WIDE IT SERVICE OUTAGES== | |
| − | | |
| − | <br>
| |
| − | | |
| − | '''8/24/16 3:30pm''' UPDATE: We are told that JHU has fixed their mail servers and that JHU mail is back in operation again.
| |
| − | | |
| − | | |
| − | '''8/24/16 1:30pm''' JHU's central mail servers are experiencing an issue that is causing mail bouncebacks for people not on JHU Exchange sending to people on JHU Exchange. An error might look like:
| |
| − |
| |
| − | :'''The reason for the problem: 5.1.2 - Bad destination host 'Multiple DNS'''
| |
| − | :'''queries were attempted and failed: DNS Hard Error looking up'''
| |
| − | :'''feint.johnshopkins.edu<http://feint.johnshopkins.edu/> (A): NXDomain'''
| |
| − | | |
| − | JHU is looking into the problem at their end. Note that although the CS email servers are working fine, those on CS sending to JHU Exchange users may experience the same issue as others outside of JHU Exchange sending to JHU Exchange.
| |
| − | | |
| − | <br>
| |
| − | *********** JHU-WIDE OUTAGES TEMPLATE - END*********** -->
| |
| − | <!-- **************** MAIL BOUNCES TEMPLATE - START ****************
| |
| − | | |
| − | | |
| − | | |
| − | ===Possible Email Bounces From Normally-Working Sites===
| |
| − | | |
| − | '''8/8/16''' We have been receiving reports of ''email bounces from people/organizations that normally work without problems.'' We think we know what is happening. We recently discovered that one of our CS student accounts had been compromised and was being used to send spam. Even though we disabled the account as soon as the compromise was discovered, several mail server reputation services had already classified us as a possible source of spam. As a result of that classification, some organizations have decided to temporarily reject email from our mail server. We can't predict ahead of time which organizations those are, since there are a variety of reputation services, and individual organizations differ in the ways they make use of reputation information.
| |
| − | | |
| − | This problem will fix itself automatically over the next few days, as the reputation services take note of the fact that we have stopped sending spam. There's no way to speed up this process, unfortunately.
| |
| − | | |
| − | This sort of problem doesn't often happen to us. But when it does, it causes headaches like the unexpected bounce messages some people have received. We will be implementing some new processes that we expect will allow us to react more quickly to situations like this, before they reach the point where other organizations stop accepting our mail.
| |
| − | | |
| − | We will update this page once the reputation scores have returned to normal.
| |
| − | <br>
| |
| − | | |
| − | | |
| − | **************** MAIL BOUNCES TEMPLATE - END -->
| |
| − | | |
| | | | |
| | [[Category:All]] | | [[Category:All]] |
