A.L.M.Buxey@lboro.ac.uk wrote:
okay - updated to latest CVS after I saw the CVS log messages regarding this proxying issue. things look a little better but at the end the server is dead - unable to respond to any legitimate requests - (ie even simple local non proxy ones)
Please use 'gdb' to attach to the process and find out what it's doing (see doc/bugs). I don't know what OS you're running, and I can't reproduce the issue myself. So I'm *completely* stuck at this point. ...
WARNING: Marking home server 10.1.2.3 port 1812 as zombie (it looks like it is dead). Waking up in 1.9 seconds.
then nothing out of the server.
It's doing *something*. Is it using all of the available CPU? Can you run it in debugging mode under valgrind? $ valgrind --tool=memcheck radiusd -X and see what it prints out.
PS a little note. there are 2 other home servers configured in the proxy realm that this request could go to - the server at no point seems to want to talk to the other 2 home servers either.
That's fine. The request is reaching "max_request_time" at this point, too. It can't be proxied anywhere else, because it's used all of it's available time. Alan DeKok.