Apache OpenOffice (AOO) Bugzilla – Issue 61916
CVS rejects access occasionally
Last modified: 2010-10-23 06:48:06 UTC
CVS occasionally rejects access. Date: Mon Feb 6 12:32:02 2006 (CET) Error message: rt: no such user authorization failed: server so-cvs-tunnel.xxx.xxx.sun.com rejected access
Looking into this.
We checked the tunnel keys on the site but could not find any for the user "rt" ("=rt@" was not present in the tunnel keys files). However I do see the user present in the site. #1. Can the user confirm if they have submitted the keys and they are using the same keys to access the CVS? #2. Can the user provide the exact command used and paste the error out put that they get?
Assigning to the user who reported this issue.
user rt is usung the shared tunnel via the root@so-cvs-tunnel key.
Aniruddha Sarkar wrote: > We checked the tunnel keys on the site but could not find any for the > user "rt" ("=rt@" was not present in the tunnel keys files). > > However I do see the user present in the site. > > #1. Can the user confirm if they have submitted the keys and they are using > the same keys to access the CVS? > #2. Can the user provide the exact command used and paste the error out put > that they get? ad #1: already answered by mh. ad #2: It has nothing to do with the command I use. Usaual cvs commands as 'cvs status' or 'cvs log' sometimes occasionally fail from one minute to the other. Error output already is quoted in this issue: rt: no such user authorization failed: server so-cvs-tunnel.xxx.xxx.sun.com rejected access Re-assingning back support.
We did verify from the log files that there were slow responses from CEE's authorization servers during a heavy-load condition; hence causing this CVS error. As indicated in other performance related cases, CN engineering is looking into ways to address this (and other performance issues).
Revisiting this issue since CN has made some performance improvements on the site. Is it still occuring?
I assume you consider the issue fixed with the performance improvements. Despite the fact that we don't know what changes have been made and which functional areas are affected I would recommend to close the issue. We'll reopen if necessary.
Hi St Closing the issue for now and we shall reopen if necessarry. Regards, Karthik Support Operations
Closing
Created attachment 72349