We've been having some problems with what may be an overload on
Radiator's ability to process authentication requests. I'm NOT asking
for ideas in this regard (this time); I'm familiar with the suggestions
under High Availability and Performance.
My question is this:
Is it possible to get a "no such user" reply from Radiator because of
some type of TCP/IP or traffic overload?
Another way of phrasing the question is, what ARE the symptoms of TCP/IP
or traffic overloads?
The reason I ask is this. I was working with a customer this week, and
confirmed from the logs that she was logging in as "jane", and that
Radiator was returning "no such user". (The log showed no extraneous
space or control characters). When I went to test the CDB itself:
$ cdbget <users.cdb "jane"
her entry was, indeed, there. When we tried to reproduce it ourselves,
the authentication also failed, but there were no log entries at all,
suggesting that Radiator may have just had to discard that request
completely.
What is the explanation of this phenomona, and is "no such user"
sometimes an indication of overload?
Thanks in advance!
Dave
===
Archive at http://www.starport.net/~radiator/
Announcements on [EMAIL PROTECTED]
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
