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

Timestamp:

Jun 30, 2018, 11:03:19 PM (7 years ago)

Author:

Jamie McClelland

Comment:

--

jessie-stretch-upgrade

@@ -3 +3 @@
 = Jessie Stretch Upgrade Page =
 
-== MOSH's ==
-
-Upgrading a mosh? Great. It's simple now.
-
-First, push the latest puppet changes to the mosh.
-
-Then, run: `mf-dist-upgrade-mosh`
-
-It will warn you about problems and try to run the entire upgrade with minimal intervention.
-
-See below for more details about what is happening.
-== Change to puppet .pp file ==
-
-Each .pp file has the following lines:
-
-{{{
-  class { "mayfirst::m_unattended_upgrades":
-    uu_origin_patterns => [ "a=stable", "n=jessie-backports" ],
-    uu_upgrade_email => $parent
-  }
-}}}
-
-Please remove the n=jessie-backports part so it simply reads:
-
-{{{
-  class { "mayfirst::m_unattended_upgrades":
-    uu_origin_patterns => [ "a=stable" ],
-    uu_upgrade_email => $parent
-  }
-}}}
-
-== Purge ntp on virtual servers ==
-
-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.
-
-Don't purge ntp on physical servers.
-
 == Upgrade ==
+
+These are the general steps if you are NOT upgrading a MOSH (see below for MOSH's), but please read this full page before starting!
 
 {{{
@@ -54 +19 @@
 }}}
 
+
+== Change to puppet .pp file ==
+
+Each .pp file has the following lines:
+
+{{{
+  class { "mayfirst::m_unattended_upgrades":
+    uu_origin_patterns => [ "a=stable", "n=jessie-backports" ],
+    uu_upgrade_email => $parent
+  }
+}}}
+
+Please remove the n=jessie-backports part so it simply reads:
+
+{{{
+  class { "mayfirst::m_unattended_upgrades":
+    uu_origin_patterns => [ "a=stable" ],
+    uu_upgrade_email => $parent
+  }
+}}}
+
+== MOSH's ==
+
+Upgrading a mosh? Great. It's simple now.
+
+First, remove "jessie-backports" as described above, commit and push the latest puppet changes to the mosh.
+
+Then, run: `mf-dist-upgrade-mosh`
+
+It will warn you about problems and try to run the entire upgrade with minimal intervention.
+
+See below for more details about what is happening.
+
+== Purge ntp on virtual servers ==
+
+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.
+
+Don't purge ntp on physical servers.
+
 == mysql/mariadb ==
 
@@ -61 +65 @@
 
 Check with: `grep -r log_slow_queries /etc/mysql` and remove that setting if you find it.
+
+Also, 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.
+
+You can look for them with:
+
+{{{
+mysql -e "select * from user where char_length(Password) = 16;"  mysql
+}}}
+
+Reset passwords with (replace $USER and $NEWPASS):
+
+{{{
+SET PASSWORD FOR '$USER'@'localhost' = password('$NEWPASS');
+}}}
 
 == MOSH only ==
@@ -123 +141 @@
  * /etc/apt/apt.conf.d/50unattended-upgrades
  * /etc/apache2/envvars
+ * /etc/ImageMagick-6/policy.xml
+ * /etc/cron.daily/spamassassin
+ * /etc/spamassassin/local.cf