Join the community today
Become a Member

Linode Critical Maintenance for CPU Vulnerabilities

Discussion in 'VPS Provider Network Status' started by eva2000, Jan 11, 2018.

  1. eva2000

    eva2000 Administrator Staff Member

    54,564
    12,224
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,793
    Local Time:
    9:45 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    Jan 10, 22:17 UTC
    Identified - A number of serious security vulnerabilities affecting multiple CPU architectures were recently disclosed by Google’s Project Zero team as outlined in our blog post[1]. In order to address these vulnerabilities, the host on which your Linode resides will need to undergo maintenance. This is the first of several separate maintenances that will be necessary to fully mitigate these vulnerabilities.

    Each Linode's maintenance window will be communicated to you via support ticket and will also be visible within the Linode Manager. During the maintenance window, your Linode will be cleanly shut down and will be unavailable while we perform the updates. A two-hour window is allocated, however the actual downtime should be much less. After the maintenance has concluded, each Linode will be returned to its last state (running or powered off).

    You can prepare your Linode for this maintenance by following our Reboot Survival Guide. By following this guide before your maintenance, you will be able to ensure that services running on your Linode are resumed properly. The Reboot Survival Guide is available here:

    https://www.linode.com/docs/uptime/reboot-survival-guide

    These updates affect the underlying infrastructure that your Linode resides on and will not affect the data stored within your Linode. In order to fully mitigate the Meltdown vulnerability, you must update your Linode’s kernel to version 4.14.12 or later. If your Linode’s Configuration Profile is set to utilize our latest kernel, your Linode will automatically use 4.14.12 or later upon rebooting.

    We regret the short notice and the downtime required for this maintenance. However, due to the severity of these vulnerabilities, we have no choice but to take swift and immediate action to ensure the safety and security of our customers. For these reasons, we must adhere to a strict timetable, and will not be able to reschedule or defer this maintenance.


    Stay tuned for more information.

    [1] /blog.linode.com/2018/01/03/cpu-vulnerabilities-meltdown-spectre>

    Continue reading...
     
  2. dooma

    dooma Active Member

    326
    34
    28
    Oct 15, 2016
    Cairo
    Ratings:
    +49
    Local Time:
    1:45 PM
    my server with Linode went down many times.
     
  3. eva2000

    eva2000 Administrator Staff Member

    54,564
    12,224
    113
    May 24, 2014
    Brisbane, Australia
    Ratings:
    +18,793
    Local Time:
    9:45 PM
    Nginx 1.27.x
    MariaDB 10.x/11.4+
    due to this maintenance reboot or previous issues ?

    I just got my first Linode's email notification of node reboot scheduled for tomorrow. A few more Linodes to get emails for though.
     
  4. dooma

    dooma Active Member

    326
    34
    28
    Oct 15, 2016
    Cairo
    Ratings:
    +49
    Local Time:
    1:45 PM
    maintenance reboot but Linode is my best :)
     
  5. Jon Snow

    Jon Snow Active Member

    835
    170
    43
    Jun 30, 2017
    Ratings:
    +256
    Local Time:
    7:45 AM
    Nginx 1.13.9
    MariaDB 10.1.31
    So it was rebooted multiple times or it started going down after the reboot?