Upgrading the Lecture WWW Server (scheduled in February, 2019) [Completed}
Updated: February 06, 2019
November 16, 2018
Service of the “Lecture WWW server” has now resumed on the new server. Make sure to access the host name of old-lecuture.ecc.u-tokyo.ac.jp if you need to log in to the previous server. (Updated on February 5, 2019)
The Information Technology Center (the Center) operates a “Lecture WWW Server” (the server) for academic staff who has an Educational Campus-wide Computing System (ECCS) account and wish to store materials for lectures, such as HTML programs, on the web server.
The Center will migrate the server to a newly prepared server hosted on a public cloud (Microsoft Azure) as the operational period for the hardware of the existing server will end in February, 2019. We have decided to upgrade the OS version concurrently and make partial changes to the operating procedures.
We kindly ask academic staff who are using the server to perform the necessary tasks after reading the following instructions.
Main Changes after the Upgrade
- The OS for the server will be upgraded from CentOS 6.10 to CentOS 7.6. Following this, various software packages supplied with the OS and library versions will be changed.
- Public key authentication will be required when logging in remotely using SSH.
- Exclusive accounts, which are independent from the ECCS accounts, will be used for the server.
- Exclusive accounts using the same username will be issued for the existing users of the server.
- If an ECCS account expires, the accounts for the server will be suspended as before.
- The host name for the existing server, lecturev2.ecc.u-tokyo.ac.jp will be changed to lecturev3.ecc.u-tokyo.ac.jp for the new server.
- The web address of the web server will not be changed.
Request for Setting up Public Key Authentication on the Existing Server
To use public key authentication with SSH, users are required to save a public key generated on their personal computer (home PC etc.) as a specified file in each user’s home directory /.ssh/authorized_keys on the Lecture WWW server.
The Center will migrate all user’s files in the existing server to the new server to conduct the upgrade. If you set up the pubic key authentication on the existing server, you will be able to use the new server promptly after upgrade. We ask academic staff who use the server to set up public key authentication before we stop operation of the existing server in February, 2019.
Work Schedule (estimated schedule)
- 10 AM on Tuesday, February 5, 2019: Operation of the existing server will be stopped
- Server will be inaccessible even if logging in with SSH or through the web.
- The Center will migrate files from the existing server to the new server
- 1 PM on Tuesday, February 5, 2019: Operation of the new server will be started
- Logging in with an SSH public key authentication will be possible
- Contents on the new server will be useable by accessing the server’s address “https://lecture.ecc.u-tokyo.ac.jp”
- 1 PM on Tuesday, February 5, 2019: Operation of the existing server will be restarted
- 10 AM on Tuesday, February 19,2018 : Operation of the existing server will be terminated
- All files on the existing server will be deleted
Frequent Asked Questions
- Q: I do not know how to generate a public key.
- A: Please refer to the following ECCS announcement for details on how to generate a public authentication key using PuTTYGen software for Windows.
Uploading SSH Public Keys using PuTTYGen
After creating a public key in openssh format by following the steps in the above announcement, please place it on the Lecture WWW server.
For use of other software, please conduct your own search.
- Q: Where should I upload public key on the Lecture WWW server?
- A: Create a directory named “.ssh” (set to “only the owner can read/write” ) under the home directory in the Lecture WWW server (NOT in the ECCS) and save a file named “authorized_keys”
- Q: I would like to know the corresponding public keys.
- A: The public keys are RSA2 (greater than 2048 bit), DSA, and ECDSA
- Q: What is the ssh host key fingerprint for the server?
- Q: I cannot login to the new server
- A: If you did not set up public key authentication on the existing server, you are required to send the public key to the Center. The Center will upload the public keys to the new server accordingly, however it may take time depending on our workload.
- Q: Some applications that previously worked on the existing server are no longer working on the new server.
- A: The Center will investigate as much as possible, however please note that we will take supportive measures only if the problem is caused by problems with the upgrade procedure.