[SR-Users] TOPOS module errors
Enrico Bandiera
enrico.bandiera at cloud.timenet.it
Thu May 3 15:42:42 CEST 2018
Hi Daniel, tell me if you need more portions of the log:
0(111) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking
if host==us: 10==11 && [172.22.3.7] == [31.193.99.4]
0(111) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking
if port 5060 (advertise 0) matches port 5060
0(111) DEBUG: <core> [core/socket_info.c:559]: grep_sock_info(): checking
if host==us: 10==10 && [172.22.3.7] == [172.22.3.7]
0(111) DEBUG: <core> [core/socket_info.c:566]: grep_sock_info(): checking
if port 5060 (advertise 0) matches port 5060
0(111) DEBUG: tm [uac.c:426]: t_uac_prepare(): next_hop=<
sip:notification_peer at 127.0.0.1:5060>
0(111) DEBUG: tm [uac.c:152]: dlg2hash(): hashid 25495
0(111) DEBUG: topos [topos_mod.c:468]: tps_execute_event_route():
executing event_route[topos:...] (3)
0(111) ERROR: <script>: HIDING TOPOLOGY: 1:5060:127.0.0.1
0(111) DEBUG: <core> [core/parser/msg_parser.c:604]: parse_msg(): SIP
Request:
0(111) DEBUG: <core> [core/parser/msg_parser.c:606]: parse_msg():
method: <KDMQ>
0(111) DEBUG: <core> [core/parser/msg_parser.c:608]: parse_msg(): uri:
<sip:notification_peer at 127.0.0.1:5060>
0(111) DEBUG: <core> [core/parser/msg_parser.c:610]: parse_msg():
version: <SIP/2.0>
0(111) DEBUG: <core> [core/parser/parse_via.c:1303]: parse_via_param():
Found param type 232, <branch> =
<z9hG4bK7936.bcc62347000000000000000000000000.0>; state=16
0(111) DEBUG: <core> [core/parser/parse_via.c:2639]: parse_via(): end of
header reached, state=5
0(111) DEBUG: <core> [core/parser/msg_parser.c:492]: parse_headers(): Via
found, flags=2
0(111) DEBUG: <core> [core/parser/msg_parser.c:494]: parse_headers(): this
is the first via
0(111) DEBUG: <core> [core/parser/parse_addr_spec.c:864]:
parse_addr_spec(): end of header reached, state=10
0(111) DEBUG: <core> [core/parser/msg_parser.c:171]: get_hdr_field(): <To>
[40]; uri=[sip:notification_peer at 127.0.0.1:5060]
0(111) DEBUG: <core> [core/parser/msg_parser.c:172]: get_hdr_field(): to
body [<sip:notification_peer at 127.0.0.1:5060>
0(111) DEBUG: <core> [core/parser/msg_parser.c:152]: get_hdr_field(): cseq
<CSeq>: <10> <KDMQ>
0(111) DEBUG: <core> [core/parser/msg_parser.c:183]: get_hdr_field():
content_length=69
0(111) DEBUG: <core> [core/parser/msg_parser.c:89]: get_hdr_field(): found
end of header
0(111) DEBUG: <core> [core/parser/parse_addr_spec.c:185]:
parse_to_param(): add param: tag=2a154ea4a528648fbfaaac82505be461-4e03
0(111) DEBUG: <core> [core/parser/parse_addr_spec.c:864]:
parse_addr_spec(): end of header reached, state=29
0(111) DEBUG: topos [tps_msg.c:934]: tps_request_sent(): handling outgoing
request (0, 1)
0(111) DEBUG: topos [tps_msg.c:376]: tps_pack_message(): compacted headers
- x_via1: [SIP/2.0/UDP
172.22.3.7;branch=z9hG4bK7936.bcc62347000000000000000000000000.0](76) -
x_via2: [](0) - x_vbranch1:
[z9hG4bK7936.bcc62347000000000000000000000000.0](46)
0(111) DEBUG: topos [tps_msg.c:485]: tps_pack_message(): compacted headers
- a_rr: [](0) - b_rr: [](0) - s_rr: [](0)
0(111) DEBUG: topos [tps_msg.c:490]: tps_pack_message(): compacted headers
- as_contact: [](0) - bs_contact: [](0)
0(111) DEBUG: topos [tps_storage.c:124]: tps_storage_lock_get(): tps lock
get: 120
0(111) DEBUG: <core> [sruid.c:182]: sruid_next(): new sruid is
[tpsh-5aeb10fb-6f-1] (1 / 18)
0(111) WARNING: topos [tps_storage.c:400]: tps_storage_record(): no local
address - do record routing for all initial requests
0(111) ERROR: topos [tps_storage.c:480]: tps_db_insert_dialog(): No
database handle - misconfiguration?
0(111) ERROR: topos [tps_storage.c:412]: tps_storage_record(): failed to
store
0(111) DEBUG: topos [tps_storage.c:136]: tps_storage_lock_release(): tps
lock release: 120
0(111) DEBUG: tm [uac.c:645]: send_prepared_request_impl(): uac:
0x7f88fdc0b468 branch: 0 to 127.0.0.1:5060
0(111) DEBUG: tm [../../core/onsend.h:69]: run_onsend(): required
parameters are not available - ignoring
0(111) DEBUG: dmq [dmq_funcs.c:165]: bcast_dmq_message(): skipping node
sip:172.22.3.7:5060
0(111) DEBUG: <core> [core/sr_module.c:941]: init_mod_child(): idx 0 rank
0: htable [main]
0(111) DEBUG: htable [htable.c:232]: child_init(): rank is (0)
0(111) DEBUG: <core> [core/sr_module.c:941]: init_mod_child(): idx 0 rank
0: app_python [main]
0(111) DEBUG: <core> [core/sr_module.c:941]: init_mod_child(): idx 0 rank
0: topos [main]
0(111) DEBUG: <core> [sruid.c:105]: sruid_init(): root for sruid is
[tpsh-5aeb10fb-6f-] (0 / 17)
0(111) DEBUG: <core> [main.c:1751]: main_loop(): Expect maximum 2266 open
fds
Thanks,
Enrico.
2018-05-03 15:33 GMT+02:00 Daniel-Constantin Mierla <miconda at gmail.com>:
> Can you run with higher debug level (e.g., add -ddd), then reproduce and
> send here all DEBUG and the rest of log messages printed by the same PID
> showing this error?
> The main attendant doesn't handle sip traffic in fork=yes, but -DD is
> telling not to daemonize the main attendant, so I need to see what that
> process does before throwing the error messages.
>
> Cheers,
> Daniel
>
>
> On 03.05.18 13:45, Enrico Bandiera wrote:
>
> kamailio -f $PATH_KAMAILIO_CFG -DD -E -e
>
> Thanks,
> Enrico.
>
> 2018-05-03 12:52 GMT+02:00 Daniel-Constantin Mierla <miconda at gmail.com>:
>
>> Hello,
>>
>> how do you start kamailio, or better, said what are the command line
>> parameters?
>> Cheers,
>> Daniel
>>
>>
>> On 03.05.18 12:26, Enrico Bandiera wrote:
>>
>> Hi Daniel, is kamcmd ps ok for this?
>>
>> 0(116) ERROR: topos [tps_storage.c:480]: tps_db_insert_dialog(): No
>> database handle - misconfiguration?
>> 0(116) ERROR: topos [tps_storage.c:412]: tps_storage_record(): failed to
>> store
>>
>> root at proxy-bbd996f48-mjzr4:/# kamcmd ps
>> 116 main process - attendant
>>
>> Thanks,
>> Enrico.
>>
>>
>> 2018-05-03 11:48 GMT+02:00 Daniel-Constantin Mierla <miconda at gmail.com>:
>>
>>> Hello,
>>>
>>> can you get the output for
>>>
>>> kamctl ps
>>>
>>> and see the description for process with pid 94?
>>>
>>> I assume you run it in docker, given low pid value shown in the log
>>> message...
>>>
>>> Cheers,
>>> Daniel
>>>
>>> On 03.05.18 10:42, Enrico Bandiera wrote:
>>>
>>> Hi, I'm trying to use the TOPOS module to solve some MTU issues we have
>>> (we have multiple kamailio servers in our architecture and route/via
>>> headers are becoming a problem)
>>>
>>> The module seems to work but I'm getting these errors on the log:
>>>
>>> 0(94) ERROR: topos [tps_storage.c:480]: tps_db_insert_dialog(): No
>>> database handle - misconfiguration?
>>> 0(94) ERROR: topos [tps_storage.c:412]: tps_storage_record(): failed to
>>> store
>>>
>>> I get these errors for some time after running kamailio and then they
>>> stop appearing.
>>>
>>> Data is inserted on topos_d and topos_t on the db, so I'm not sure what
>>> the error is referring to.
>>>
>>> Any idea?
>>>
>>> Thanks,
>>> Enrico.
>>>
>>>
>>> _______________________________________________
>>> Kamailio (SER) - Users Mailing Listsr-users at lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>>
>>> --
>>> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
>>> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
>>>
>>>
>>
>> --
>> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
>>
>>
>
> --
> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
> Kamailio World Conference - May 14-16, 2018 - www.kamailioworld.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20180503/565d4658/attachment.html>
More information about the sr-users
mailing list