[LON-CAPA-admin] Login problems

[Guy Albertelli II]

Hi Mark,

> 
> A student was saying that she was having problems logging in. The 
> following seems to be the case:
> 
> She has a ID file on capa7 from May 7 15:34
> 
> The following errors are in lonnet.log:
> 
> lonnet.log:Wed May  7 15:10:13 2003 (32075): User jl111902 at ohiou 
> authorized by oucapa2
> lonnet.log:Wed May  7 15:17:04 2003 (28846): User jl111902 at ohiou 
> rejected by oucapa2
> lonnet.log:Wed May  7 15:17:12 2003 (27073): User jl111902 at ohiou 
> authorized by oucapa2
> lonnet.log:Wed May  7 15:17:54 2003 (2230): <font color=blue>WARNING: 
> Connection buffer 
> /home/httpd/sockets/delayed/1052335072.0.2230.logohioujl1119.oucapa2: 
> log:ohiou:jl111902:Logout 64.247.112.198</font>

A child exited but was unable to contact oucapa2 the message was
delayed until the connection comes back up. You will see messages in
lonc/d.log around this time about connections going down and coming
back up.

> lonnet.log:Wed May  7 15:18:02 2003 (2229): User jl111902 at ohiou could 
> not be authenticated
> lonnet.log:Wed May  7 15:18:34 2003 (2232): User jl111902 at ohiou could 
> not be authenticated
> lonnet.log:Wed May  7 15:18:56 2003 (28893): User jl111902 at ohiou could 
> not be authenticated
> lonnet.log:Wed May  7 15:19:18 2003 (27073): User jl111902 at ohiou could 
> not be authenticated
> lonnet.log:Wed May  7 15:19:25 2003 (27032): User jl111902 at ohiou could 
> not be authenticated
> lonnet.log:Wed May  7 15:19:31 2003 (28846): User jl111902 at ohiou could 
> not be authenticated
> lonnet.log:Wed May  7 15:20:15 2003 (28893): User jl111902 at ohiou could 
> not be authenticated

'not be authenticated' means we couldn't find a server to try
authenticating the user, not that the password was wrong, this was
occuring because the connection was down.

 1.0 is better about telling the student whether the password was
   wrong or if the connection is down.

> lonnet.log:Wed May  7 15:25:29 2003 (28893): User jl111902 at ohiou 
> authorized by oucapa2

Connection is back up.

> I'm most confused by the sending delayed and how that might have factored 
> in.

It didn't. It was a side result of the connection going down between
the library server and access server. It looks like everything
recovered well, after ~ 2-3 minute downtime.


-- 
guy at albertelli.com  LON-CAPA Developer  0-7-6-9-