Changes between Version 39 and Version 40 of jessie-stretch-upgrade


Ignore:
Timestamp:
Jun 30, 2018, 11:03:19 PM (7 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • jessie-stretch-upgrade

    v39 v40  
    33= Jessie Stretch Upgrade Page =
    44
    5 == MOSH's ==
    6 
    7 Upgrading a mosh? Great. It's simple now.
    8 
    9 First, push the latest puppet changes to the mosh.
    10 
    11 Then, run: `mf-dist-upgrade-mosh`
    12 
    13 It will warn you about problems and try to run the entire upgrade with minimal intervention.
    14 
    15 See below for more details about what is happening.
    16 == Change to puppet .pp file ==
    17 
    18 Each .pp file has the following lines:
    19 
    20 {{{
    21   class { "mayfirst::m_unattended_upgrades":
    22     uu_origin_patterns => [ "a=stable", "n=jessie-backports" ],
    23     uu_upgrade_email => $parent
    24   }
    25 }}}
    26 
    27 Please remove the n=jessie-backports part so it simply reads:
    28 
    29 {{{
    30   class { "mayfirst::m_unattended_upgrades":
    31     uu_origin_patterns => [ "a=stable" ],
    32     uu_upgrade_email => $parent
    33   }
    34 }}}
    35 
    36 == Purge ntp on virtual servers ==
    37 
    38 This is not stricly a stretch upgrade task, but while upgrading''virtual guests'', please take the time to purge `ntp` (and ensure that /etc/ntp.conf). With ntp gone, freepuppet will configure systemd-timesyncd.
    39 
    40 Don't purge ntp on physical servers.
    41 
    425== Upgrade ==
     6
     7These are the general steps if you are NOT upgrading a MOSH (see below for MOSH's), but please read this full page before starting!
    438
    449{{{
     
    5419}}}
    5520
     21
     22== Change to puppet .pp file ==
     23
     24Each .pp file has the following lines:
     25
     26{{{
     27  class { "mayfirst::m_unattended_upgrades":
     28    uu_origin_patterns => [ "a=stable", "n=jessie-backports" ],
     29    uu_upgrade_email => $parent
     30  }
     31}}}
     32
     33Please remove the n=jessie-backports part so it simply reads:
     34
     35{{{
     36  class { "mayfirst::m_unattended_upgrades":
     37    uu_origin_patterns => [ "a=stable" ],
     38    uu_upgrade_email => $parent
     39  }
     40}}}
     41
     42== MOSH's ==
     43
     44Upgrading a mosh? Great. It's simple now.
     45
     46First, remove "jessie-backports" as described above, commit and push the latest puppet changes to the mosh.
     47
     48Then, run: `mf-dist-upgrade-mosh`
     49
     50It will warn you about problems and try to run the entire upgrade with minimal intervention.
     51
     52See below for more details about what is happening.
     53
     54== Purge ntp on virtual servers ==
     55
     56This is not stricly a stretch upgrade task, but while upgrading''virtual guests'', please take the time to purge `ntp` (and ensure that /etc/ntp.conf). With ntp gone, freepuppet will configure systemd-timesyncd.
     57
     58Don't purge ntp on physical servers.
     59
    5660== mysql/mariadb ==
    5761
     
    6165
    6266Check with: `grep -r log_slow_queries /etc/mysql` and remove that setting if you find it.
     67
     68Also, if you have any mysql users that created a password using the old format you are really screwed. You should fix those first or those usernames will stop working.
     69
     70You can look for them with:
     71
     72{{{
     73mysql -e "select * from user where char_length(Password) = 16;"  mysql
     74}}}
     75
     76Reset passwords with (replace $USER and $NEWPASS):
     77
     78{{{
     79SET PASSWORD FOR '$USER'@'localhost' = password('$NEWPASS');
     80}}}
    6381
    6482== MOSH only ==
     
    123141 * /etc/apt/apt.conf.d/50unattended-upgrades
    124142 * /etc/apache2/envvars
     143 * /etc/ImageMagick-6/policy.xml
     144 * /etc/cron.daily/spamassassin
     145 * /etc/spamassassin/local.cf
    125146
    126147