[OpenAFS] Occasional "VLDB: no permission access for call"
Jeffrey E Altman
jaltman@auristor.com
Mon, 29 Mar 2021 11:29:27 -0400
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--Ohs5DN0AHUT6Lg2lZLSIfrxMP1R3pCwK3
Content-Type: multipart/mixed; boundary="stiTzuLDuIXdDagOzfQiapGMBsbvopDx8";
protected-headers="v1"
From: Jeffrey E Altman <jaltman@auristor.com>
To: Ian Wienand <iwienand@redhat.com>
Cc: openafs-info@openafs.org
Message-ID: <1b86bff8-2980-4500-7ca1-cbc9f56c89d5@auristor.com>
Subject: Re: [OpenAFS] Occasional "VLDB: no permission access for call"
References: <YGFWTmmV4BsjmY9P@fedora19.localdomain>
In-Reply-To: <YGFWTmmV4BsjmY9P@fedora19.localdomain>
--stiTzuLDuIXdDagOzfQiapGMBsbvopDx8
Content-Type: multipart/mixed;
boundary="------------3FA84F811DC40885B55B2E2D"
Content-Language: en-US
This is a multi-part message in MIME format.
--------------3FA84F811DC40885B55B2E2D
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: quoted-printable
On 3/29/2021 12:23 AM, Ian Wienand (iwienand@redhat.com) wrote:
> A new thing I've noticed after we have upgraded everything to 1.8.6
openstack.org also deployed a new database server and this problem is=20
most likely due to a failure to synchronize the super-user list onto the =
new vlserver. If the vos command randomly chooses to speak with the new =
vlserver instance first, it receives a permission denied error and does=20
not contact any other servers.
Jeffrey Altman
--------------3FA84F811DC40885B55B2E2D
Content-Type: text/x-vcard; charset=utf-8;
name="jaltman.vcf"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: attachment;
filename="jaltman.vcf"
begin:vcard
fn:Jeffrey Altman
n:Altman;Jeffrey
org:AuriStor, Inc.
adr:;;255 W 94TH ST STE 6B;New York;NY;10025-6985;United States
email;internet:jaltman@auristor.com
title:CEO
tel;work:+1-212-769-9018
url:https://www.linkedin.com/in/jeffreyaltman/
version:2.1
end:vcard
--------------3FA84F811DC40885B55B2E2D--
--stiTzuLDuIXdDagOzfQiapGMBsbvopDx8--
--Ohs5DN0AHUT6Lg2lZLSIfrxMP1R3pCwK3
Content-Type: application/pgp-signature; name="OpenPGP_signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="OpenPGP_signature"
-----BEGIN PGP SIGNATURE-----
wsF5BAABCAAjFiEE+kRK8Zf0SbJM8+aZ93pzVZK2mgQFAmBh8lcFAwAAAAAACgkQ93pzVZK2mgSU
ZQ//c/5b3dpSyPPzWxJJ8v4Kv6GZGqyu2qnFX1E9vSl6EEij1yNOBR3xAPn6BHJkgaFyrSGe7YKj
MmW+CJyfbk0Vpb3nx8Ca3+T24CNWXH9qOGRJi3Ut/d6cIjub4WJK1LnJWHsV+8wL4amNzVdf3WIT
SwqK0XlZ9Lwu1VawxHtTqVN6WcEkDwFxJOlEus1uRO9Cmst6H0FxPkw1iSzUToRQCEBmkoD2X9I4
v171O7DV4k81O70sfjOePC2aE8I7xEXe7Wo+lpJVihsYpe9gOtA2a5ZT4ZbQo+ZiyYKotr3HX7RV
csQBtK0KFBGm/Zp3aYgAbxN+CzJ9d1QsastSzFWPKjEllPS0c9HZBCzAi98mVoo6r/Qeb08HZDQ/
ItD3bVpJUpcAOPTuw0KxsGafp1PyqL8DuxBSU5aCTt6sjfst39tgFp8hW46MAC0XepBSrnvsrSUa
5kjJi2JDei9NO7Zm9CdDCUHF/yjute8mvhVEI9KKPc0gwMEM9yxiv0QWag1wGPabbXibDuWJspJi
sC4gDC6U6GyGSTyOLpwSJfmUTw89Pj3mR9Qi+12ApGFwY0UM6ecrpnwdRNpR1gRSNM6xETV8HHGB
poXEy9KDjKWkpWxuq4So2waJjKAYUQe+M8s3G53CN1+9Ck/Lf3L2q2Oe8Ry5/v5F40RCucI7qN6m
59Q=
=19WW
-----END PGP SIGNATURE-----
--Ohs5DN0AHUT6Lg2lZLSIfrxMP1R3pCwK3--