|
|
| Line 1: |
Line 1: |
| | <!-- *************** BEGIN ACTIVE NOTICES **************************** --> | | <!-- *************** BEGIN ACTIVE NOTICES **************************** --> |
| | | | |
| | + | == {{red|CS IT STAFF AVAILABILITY}} == |
| | | | |
| − | == UNPLANNED CS SERVICE OUTAGES ==
| + | * 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. |
| | | | |
| − | === CS Dept Home Dir File Server Is Functioning Again===
| + | <br><p> |
| − | | |
| − | :None at this time.
| |
| − | | |
| − | <br> | |
| − | | |
| − | == PLANNED CS SERVICE OUTAGES ==
| |
| − | | |
| − | '''WHAT:''' CS Dept user Virtual Machine (VM) server will be shutdown for a memory install.
| |
| − | | |
| − | '''WHEN:''' Wednesday, December 28, from 9am to 11am.
| |
| − | | |
| − | '''DETAILS:''' ''(The following '''only''' affects CS users that run a Virtual Machine on our VM server. We've emailed those VM owners separately.)'' We will be performing a RAM (memory) installation on vmserver. This requires us shutting down the VM server, installing the memory, and bringing it back up again. We have scheduled this for Wednesday morning, December 28, from 9am to 11am.
| |
| − | | |
| − | 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 vmserver is back up and running again, we will restart or unsuspend all VMs. In all cases, VM owners' intervention will not be needed; we can handle this remotely.
| |
| − | | |
| − | After vmserver is up and running again, we will send out an announcement to VM owners and ask that they check to make sure their VM is running as expected and to email support@cs.jhu.edu if there are issues.
| |
| − | | |
| − | <!-- :None at this time. --> | |
| − | | |
| − | <br>
| |
| − | | |
| − | == CS COMPUTING LAB AVAILABILITY ==
| |
| − | | |
| − | | |
| − | === MH 122 (Ugrad Lab) ===
| |
| − | | |
| − | :Open as usual. <br>
| |
| − | | |
| − | | |
| − | === MH G-61 (Masters/Ugrad Lab)===
| |
| − | | |
| − | :Open as usual. <br>
| |
| − | | |
| − | | |
| − | | |
| − | | |
| − | <!-- *************** END ACTIVE NOTICES ********************-->
| |
| | | | |
| | | | |
| | <!-- | | <!-- |
| − | *
| + | == {{red|JHU IT SERVICE OUTAGES AFFECTING CS IT SERVICES}} == |
| − | *
| + | === PLANNED ''JHU'' SERVICE OUTAGES === |
| − | * ********************* BEGIN TEMPLATES ********************
| + | --> |
| − | *
| + | <!-- |
| − | *
| + | === UNPLANNED ''JHU'' SERVICE OUTAGES === |
| − | *
| |
| | --> | | --> |
| | | | |
| | + | == {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} == |
| | | | |
| | | | |
| − | <!-- ************ LAB CLOSURE TEMPLATE - START ***************
| + | === UNPLANNED CS IT SERVICE OUTAGES === |
| | | | |
| − | ==== '''PLANNED CLOSURE''''' ====
| + | :None at this time. |
| | | | |
| | + | === PLANNED CS IT SERVICE OUTAGES === |
| | | | |
| − | '''''WHERE:''''' Malone Hall G-61, both the Masters and Ugrad sides of the lab. | + | <!--:None at this time.--> |
| | + | === Malone '''MH 122''' ''and'' '''G61''' Ugrad and Masters Labs {{red|'''''Closure'''''}}=== |
| | | | |
| − | '''''WHEN:''''' Monday, March 14 & Tuesday, March 15, from 6am to 12 Noon. | + | :'''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. |
| | | | |
| − | '''''WHY:''''' Network cable installation. The lab will be closed those two | + | :'''WHEN:''' Starting Friday evening, November 15, 5pm '''through''' Saturday, November 16, 9pm. |
| − | mornings as workers install additional network cable.
| |
| | | | |
| − | =====NOTES:=====
| + | :'''DETAILS:''' |
| | | | |
| − | * During the lab closure times, the masters and ugrad Linux computers in G-61 will continue to be available remotely, via SSH.
| + | : 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. |
| | | | |
| − | * Ugrad Lab, MH 122 will not be affected and will remain open during those times.
| + | : Additionally, all of the labs' Linux computers (grad1 through grad16 and ugrad1 through ugrad24) will be unavailable during the time period referenced above. |
| | | | |
| − | ************* LAB CLOSURE TEMPLATE- END *************-->
| + | * 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. |
| | | | |
| | + | * 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.) |
| | | | |
| − | | + | * The printers in MH 122 and MH G61 will remain online, but, please pick up your printouts outside of the contest hours. |
| − | | |
| − | | |
| − | <!-- ********** 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>
| |
| − | | |
| | | | |
| | <br> | | <br> |
| | | | |
| − | ===Planned Outage 2: Databases Class MySQL Database Server ('''dbase.cs.jhu.edu''') Unavailability=== | + | == {{red|CS COMPUTING LAB AVAILABILITY}} == |
| | | | |
| − | :'''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. | + | <!-- ***** NORMAL POSTING MH 122****** --> |
| − | | + | :'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access. |
| − | :Future updates will be posted on the [https://support.cs.jhu.edu/wiki/Notices Notices] page of the CS IT Support Wiki | + | :{{red|However, please see the info above regarding the mid-November lab closure and systems unavailability.}} |
| − | | + | <!-- |
| − | <span style="color:#ff0000">UPDATE: 10/4/16 7:15am All systems back in operation! </span>
| + | :'''MH 122 ''UNAVAILABILITY''''' |
| | + | --> |
| | | | |
| | | | |
| | + | <!-- ****** 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> |
| | | | |
| − | ********** BARLEY SHUTDOWN TEMPLATE - END ************* -->
| + | == {{red|AUDIO/VISUAL (A/V) OUTAGES}} == |
| − | | + | :None at this time. |
| − | | |
| − | | |
| − | | |
| − | | |
| − | <!-- ******************* 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]] |
