[prev in list] [next in list] [prev in thread] [next in thread] 

List:       freediameter-dev
Subject:    [Dev] dbg_interactive question
From:       sdecugis () freediameter ! net (Sebastien Decugis)
Date:       2011-06-18 20:04:06
Message-ID: 4DFD04B6.5080206 () freediameter ! net
[Download RAW message or body]

Hello Roelf,

It seems to me the usage you are trying is correct, there is probably a 
bug in freeDiameter on this platform. The dbg_interactive extension is 
quite fragile, it probably enters some deadlock in the python thread 
(and this thread only, so the remaining of the daemon is still alive and 
well).

It would be interesting if possible to attach with  gdb to the process 
and check where in the code the stuck thread is located.

If I understand correctly, you built your package from source. I would 
be also interested to hear if the pre-built package for Lenny (from 
http://www.freediameter.net/trac/wiki/DebRepository ) has the same issue.

Sorry I cannot help much more on this issue at the moment!

Best regards,
Sebastien.




Le 2011/06/17 15:12, Roelf Diedericks a ?crit :
> I've built the mecurial "tip" of freediameter on Debian Lenny, against
> Python 2.5 and enabled the
> dbg_interactive application to do some testing and fooling around.
>
> However it looks like the interpreter simply locks up, or I'm
> completely misunderstanding things.
>
> In the following output, after entering
> "print cvar.fd_g_config.cnf_diamid" at the python prompt, nothing
> happens and no output
> occurs.
>
>
> -----------------------------------------------------------------------------
> libfdproto initialized.
> libgnutls '2.4.2', libgcrypt '1.4.1', initialized.
> Parsing configuration file: /etc/freeDiameter/freeDiameter.conf
> Extension /usr/lib/freeDiameter/dbg_interactive.fdx added to the list.
> Loading : /usr/lib/freeDiameter/dbg_interactive.fdx
> Checking dependencies for 'dbg_interactive'...
> Extension [/usr/lib/freeDiameter/dbg_interactive.fdx] fd_ext_fini has
> been resolved successfully.
> All extensions loaded.
> -- Configuration :
>    Debug trace level ...... : +2
>    Configuration file ..... : /etc/freeDiameter/freeDiameter.conf
>    Diameter Identity ...... : dev-radius.blah (l:24)
>    Diameter Realm ......... : blah (l:13)
>    Tc Timer ............... : 30
>    Tw Timer ............... : 30
>    Local port ............. : 3868
>    Local secure port ...... : 3869
>    Number of SCTP streams . : 30
>    Number of server threads : 4
>    Local endpoints ........ : Default (use all available)
>    Local applications ..... : (none)
>    Flags : - IP ........... : Enabled
>            - IPv6 ......... : DISABLED
>            - Relay app .... : Enabled
>            - TCP .......... : Enabled
>            - SCTP ......... : DISABLED
>            - Pref. proto .. : SCTP
>            - TLS method ... : Separate port
>    TLS :   - Certificate .. : /etc/freeDiameter/cert.pem
>            - Private key .. : /etc/freeDiameter/privkey.pem
>            - CA (trust) ... : /etc/freeDiameter/cert.pem (1 certs)
>            - CRL .......... : (none)
>            - Priority ..... : (default: 'NORMAL')
>            - DH file ...... : /etc/freeDiameter/dh.pem
>    Origin-State-Id ........ : 1308308816
>    Local server address(es) :
>       [4x.7x.4x.5]:0 {---L}
>
> Starting interactive python interpreter [experimental].
> Example syntax:
>     >>>  print cvar.fd_g_config.cnf_diamid
>     'dev-radius.blah'
> Python 2.5.2 (r252:60911, Jan 24 2010, 18:02:01)
> [GCC 4.3.2] on linux2
> Type "help", "copyright", "credits" or "license" for more information.
>>>> freeDiameterd daemon initialized.
>>>>
>>>> print cvar.fd_g_config.cnf_diamid
> ----- nothing happens, but freeDiameter is still live/listening: see below  ---
>
> TCP srv [0.0.0.0]:3869 (6) : accepted new client [127.0.0.1].
> New connection accepted
>
>
> --------------- SNIP  (some output/ip's sanitized) ---------------
>
> I've tried with a test.py script as well, and it seems like whilst
> freeDiameter carries on running
> (accepts connections etc) the Python interpreter never runs further
> than the first statement
> in the script that accesses freeDiameter internals.
>
> Any ideas ?
> _______________________________________________
> Dev mailing list
> Dev at freediameter.net
> http://lists.freediameter.net/cgi-bin/mailman/listinfo/dev


[prev in list] [next in list] [prev in thread] [next in thread]