On Dec 9, 2005, at 00:00, Doug Hardie wrote:
Well, it finally happened again. This is the packet with the same
timestamp as the signal 10 message. There is no response to it. I
haven't decoded it completely yet, but it appears that the user id
is corrupt. I wonder if something
On Dec 5, 2005, at 14:31, Alan DeKok wrote:
Doug Hardie [EMAIL PROTECTED] wrote:
I have a primary and backup freeradius server running on different
machines. For the last couple days they have both been receiving a
signal 10 at almost the same time.
Signal 10 is SIGBUS: Bus error. It's
Hi,
shows there either. I suspect its a request from somewhere. I am
going to enable tcpdump on the secondary server but am at a loss to
figure out how to get a core dump. I don't see any place in the code
where signal 10 is redirected. Any other ideas on how to diagnose
I have a primary and backup freeradius server running on different
machines. For the last couple days they have both been receiving a
signal 10 at almost the same time. The secondary server gets the
signal exactly 10 seconds after the primary. The time between the
signals varies from
Doug Hardie [EMAIL PROTECTED] wrote:
I have a primary and backup freeradius server running on different
machines. For the last couple days they have both been receiving a
signal 10 at almost the same time.
Signal 10 is SIGBUS: Bus error. It's usually indicative of bad memory.
I
5 matches
Mail list logo
