[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: KDC connections
You were on the right track. My process wasn't running out of file descriptors, but the send_and_recv_udp function uses select, and has FD_SETSIZE set to 1024. So if you're using more than that many file descriptors, you're in trouble.
We have come up with a version of this that uses poll instead of select for our purposes, but I'm wondering if this is something other people would want. It could be something that is decided at configure time.
From: Nicolas Williams [mailto:Nicolas.Williams@ubsw.com]
Sent: Tuesday, April 23, 2002 5:14 PM
Cc: firstname.lastname@example.org; email@example.com
Subject: Re: KDC connections
Chances are that your process is running out of file descriptors.
Try strace'ing your process(es).
On Tue, Apr 23, 2002 at 04:47:20PM -0400, firstname.lastname@example.org wrote:
> I am running into an issue where after a stream of many KDC ticket requests, I get a "Cannot contact any KDC for requested realm" error. However, the KDC is still running, and appears to be able to service requests, even from that same host. Is there some way I could be trying to make too many simultaneous connections to the KDC, or two many identitcal requests in a row, and the KDC is refusing to talk to me intentionally? I've tried this test on the same machine as the KDC, so it's not a transient network outage or anything. I just wanted to make sure there's not a security feature I'm not aware of that's tripping me up here.
> I'm using the krb5_get_init_creds_keytab() function for my ticket requests.
Visit our website at http://www.ubswarburg.com
This message contains confidential information and is intended only
for the individual named. If you are not the named addressee you
should not disseminate, distribute or copy this e-mail. Please
notify the sender immediately by e-mail if you have received this
e-mail by mistake and delete this e-mail from your system.
E-mail transmission cannot be guaranteed to be secure or error-free
as information could be intercepted, corrupted, lost, destroyed,
arrive late or incomplete, or contain viruses. The sender therefore
does not accept liability for any errors or omissions in the contents
of this message which arise as a result of e-mail transmission. If
verification is required please request a hard-copy version. This
message is provided for informational purposes and should not be
construed as a solicitation or offer to buy or sell any securities or
related financial instruments.