Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hi all,
Having a problem upgrading a live system. I'm trying to upgrade the
secondary and then upgrade the primary from 8.3.0 to 8.3.1 without
disrupting the NFS cluster they feed. I assumed that I should upgrade
the secondary, and after the system resynchronizes I would upgrade the
primary. When I upgrade the secondary I get: 'Different verify-alg
settings. me="" peer="sha1"'. I'm guessing that I want to remove the
verify-alg settings before the upgrade and then re-add them after both
sides are upgraded and back up...
Is this correct?
Is this all I need to do before the upgrade to successfully upgrade
without bringing down the entire cluster?
Do I need to bring down the entire cluster and then upgrade the systems
independently?
Any insight would be greatly appreciated,
Stu
- --
And you run and you run to catch up with the sun, but its sinking
And racing around to come up behind you again
The sun is the same in the relative way, but youre older
Shorter of breath and one day closer to death
-- Pink Floyd - "Time Lyrics"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
iQIcBAEBCAAGBQJKDFJfAAoJEFKVLITDJSGS+a8QAMCMTeladIenBqp+PRPGZubW
Ax2GBXUbgSRU7Y0EbxChuFUlXJXHWZwa4QFCBI+/qd4uJt62b/2sNyMtYYmAvZYP
tiIwMhntWp14INIXriZ0eXFAb8J8SHboU1MGuWne/ay1VvFHAtJkbDiuHrNMmDLb
KxmZ0yD+laGN1ZCujksbmch5y3vv7XVYz+XrVTtMeld17B7K/qPQ0o1tOP3B3LFL
nzaOtpG8sk8juhlOSt+fKy0+rNxF7cNk05rN0ek3oKoTTEDpBTqlYFNdulR+peRE
sIALqEGvd8RyKXQarDth2ZRjBHt0vJXdYVjD9BcBLP9Adv70Nxa1EJDoDSfcYKwx
qtPdd9WfWdXO7G6F+YXCMgSDzIC9wXKsuE6r6irxQhq5I7sWOSqpE4x7oAeqJnEn
j2sxZeCI43i1Jta+KfMOknsfOca0zRLiORnS+nH3yulFVlt6pt5rtda7Bp9shHvM
0Hk+c7Hh4yyNWMgW2vItBvbbLFF4BlGVbnH9CIFjqDdBknICSeq0UC+a7a/trhJB
hB0NGX9x1aduvT1MH6MQVL+pJy8xIIuju7Ud28qYNrAZJsc/+KTfRsrOHngCffYj
UUGu+QnabY6vCibkAEpphC6V+nP3pfVLI37WdkUneyHcEvAHh4UDd8PjVZ7qmXgE
68JhP6lcGnqAiplh0CJC
=bzcM
-----END PGP SIGNATURE-----