[prev in list] [next in list] [prev in thread] [next in thread]
List: freediameter-help
Subject: [Help] freeDiameter app_test
From: sdecugis () freediameter ! net (Sebastien Decugis)
Date: 2011-06-06 17:01:43
Message-ID: 4DED07F7.7070006 () freediameter ! net
[Download RAW message or body]
Hi,
Ok, it is good to know that it works now. Let's hope the problem does
disappear :)
Best regards,
Sebastien.
Le 2011/06/06 12:20, ayaaash a ?crit :
> Hi,
>
> I tried to report the log and the message exchange to solve the
> problem but it doesn't exist anymore. The servers are able to send and
> echo the messages now. I don't know what was causing the segfault but
> if it appeared again, I will let you know. Thank you for your help anyway.
>
> Regards,
>
> Ishfaq
>
> On Tue, May 31, 2011 at 10:32 AM, Sebastien Decugis
> <sdecugis at freediameter.net <mailto:sdecugis at freediameter.net>> wrote:
>
> Hi,
>
> Can you provide the log of the daemons? Also, it would be very
> useful to get more information on the segmentation fault, can you
> provide the stack at the time of segfault (from gdb)?
>
> If some watchdog messages are exchanged, I take it that the peers
> remain in OPEN state for a while at least. During this time, are
> you not able to send app_test messages ? Can you tell me what
> happens when you send the SIGUSR1 signal to the daemon?
>
> Regards,
> Sebastien.
>
> Le 2011/05/30 8:30, ayaaash a ?crit :
>> Hi,
>>
>> I have setup two computers and have configured freeDiameter on
>> each of them. I am now using the app_test to send messages from
>> one computer to the other, but somehow I am not able to send any
>> messages through. The daemon is loaded with no problem in both
>> the computers and the state also changes from CLOSE to OPEN, but
>> then immediately goes back to CLOSE. Now I know that the app_test
>> can't send messages unless the state is open but I want to figure
>> out what I am doing wrong.
>>
>> The monitor shows me that app_test hasn't sent any messages. 0
>> Echoed, 0 sent and 0 Received. The daemon does capability
>> exchange for a while after the state goes to close and afterwards
>> does watchdog exchange too. The daemon, then closes on one of the
>> peers because of a segmentation fault.
>>
>> Thank your very much for your time and help.
>>
>>
>> Regards,
>>
>> Ishfaq
>>
>>
>> _______________________________________________
>> Help mailing list
>> Help at freediameter.net <mailto:Help at freediameter.net>
>> http://lists.freediameter.net/cgi-bin/mailman/listinfo/help
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freediameter.net/pipermail/help/attachments/20110606/944469c8/attachment.html>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic