I have 3 DB servers running 1.6.22.1. I'm planning to update hardware (with
identical IP addresses) and SW to 1.8.7. Do you see a problem in updating
machine for machine with some time in between, so that I have several steps
in time:
now : 3x 1.6.22.1
intermediate: 2x 1.6.22.1 + 1x 1.8
Hi Bruce,
Off the top of my head, the "vos release" workflows I deal with all involve
adding new data, not removing any. [0] So, in some cases it is prudent to send
a best-effort notification to potential consumers that they may experience
a pause in access, there's not a real need to specificall
The one other offlist response I got was that behavior can depend on the
client.
I guess what I'd really be most interested in is users' perspectives: is
a "vos release" something you do you routinely with no special
precautions? Or do you have to, say, schedule them for times when
client applica
> now : 3x 1.6.22.1
> intermediate: 2x 1.6.22.1 + 1x 1.8.7
> intermediate: 1x 1.6.22.1 + 2x 1.8.7
> final : 3x 1.8.7
I have for many years upgraded db severs in this manner. So I expect
that it works this time as well. Actually we are currently runnig a
mix of 1.8 and 1.6 without
Dear Jeffrey and others,
please allow a more general upgrade question:
Jeffrey E Altman wrote on 18.01.21 17:56:
...
All clients and servers running OpenAFS 1.8.[0123456] and OpenAFS 1.9.0
will fail to communicate with OpenAFS peers (clients or servers) and
MUST be updated.
OpenAFS 1.2.x, 1.4.
On 1/18/2021 11:46 AM, Richard Brittain (richard.britt...@dartmouth.edu)
wrote:
> I'm a bit confused about what versions are affected by this bug. I've got
> mostly 1.8.[56] clients, which I'm upgrading now. My servers are still
> running 1.6.22 and appear to be fine for vos operations between
I'm a bit confused about what versions are affected by this bug. I've got
mostly 1.8.[56] clients, which I'm upgrading now. My servers are still running
1.6.22 and appear to be fine for vos operations between themselves, and the DB
servers have been restarted since this happened (but not the
Dear David,
from https://launchpad.net/~openafs/+archive/ubuntu/stable :
"Note: to use this PPA on Ubuntu 18.04 bionic, you will need to ‘apt
install init-system-helpers/bionic-backports’ "
This worked for me.
Best regards
Christoph
On 18.01.21 17:21, David Eck wrote:
I have tried to upgr
I have tried to upgrade from openafs 1.8.0 to 1.8.6-5 on Ubuntu 18.04 to
fix the recently discovered bug, using the PPA openafs/stable
However, there is an unmet dependency on init-system-helpers (>= 1.54).
The installed version is 1.51. So the upgrade fails.
Can anyone help with instructions
