[OpenSIPS-Users] lcr_dump/lcr_reload

Bogdan-Andrei Iancu bogdan at voice-system.ro
Wed Sep 30 21:45:18 CEST 2009


Hi Airton,

You have to have in mind that when using the mi_datagram, the 
communicate is via UDP and an UDP
package has maximum 65K, so printing 600o rules may be not enough (10 
bytes per rule :P).....

Maybe you should use something else than DATAGRAM, like XMLRPC where 
there are no limitations regarding the size of the output.

Regards,
Bogdan


Airton Kuada wrote:
> Hi.
>
> I am using the command lcr_dump with MI_Datagram (1.4.5).
> The table lcr (postgres) have about 8000 lines and gw table about 60 
> lines.
> I am modify config.h to
>
> #define PKG_MEM_POOL_SIZE 6*1024*1024
> #define SHM_MEM_SIZE 1024               
>
> I have no problems with opensipsctl fifo lcr_dump/lcr_reload.
>
> When I using MI_DATAGRAM my program send the buffer  - char buffer_cmd 
> []=":lcr_reload:\n "  - works correctly, however the buffer - char 
> buffer_cmd []=":lcr_dump:\n " not work. Produces the following output 
> in syslog.
>
>
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_server: received :lcr_dump:#012
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_server: mi_buf is :lcr_dump:#012 and we 
> have received 11 bytes
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:identify_command: the command starts here: lcr_dump:#012
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:identify_command: the command is lcr_dump
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:identify_command: dtgram->len is 11
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:identify_command: dtgram->len is 0
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_server: we have a valid command
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_server: after identifing the command, the 
> received datagram is
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_server: the command has no params
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_server: done parsing the mi tree
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_server: command process (lcr_dump)succeded
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <GW> and value <>
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <GW> and value <>
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <GW> and value <>
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <GW> and value <>
> ...
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> .....
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: writing the name <RULE> and 
> value <> 
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> DBG:mi_datagram:mi_datagram_write_node: a too long line
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> ERROR:mi_datagram:datagram_recur_write_tree: failed to write -line too 
> long!!!
> Sep 30 09:53:53 scelepar00188 /usr/local/sbin/opensips[11992]: 
> ERROR:mi_datagram:mi_datagram_server: failed to build the response
>
> Whats happen ?
>
> Airton.
> --------------------
>
> 26/09/09
>
> Airton Kuada
>
> (41)3200-6080
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>   




More information about the Users mailing list