i noticed these kind of errors in syslog when running master version
from around may 22:
Jun 10 13:03:03 box /usr/sbin/sip-proxy[32740]: ERROR: <core> [db_id.c:244]: new_db_id(): no private memory left
Jun 10 13:03:03 box /usr/sbin/sip-proxy[32740]: ERROR: <core> [db.c:311]: db_do_init2(): cannot parse URL 'mysql://foo:bar@127.0.0.1/sip_proxy_usage'
Jun 10 13:03:03 box /usr/sbin/sip-proxy[32740]: ERROR: db_mysql [km_dbase.c:141]: db_mysql_async_exec_task(): failed to open connection for [mysql://foo:bar@127.0.0.1/sip_proxy_usage]
ps shows that two RPC processes have run out of memory:
32733 RPC 11534336 0
32740 RPC 11534336 0
32741 RPC 9939320 1595016
in the config, i run on timer two routes that execute sql_query_async
insert and delete queries, which do not have "result" param.
looks like some memory does not get freed. any ideas? have i missed an
already committed fix?
-- juha
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#440 - CRASH: segmentation fault if there is no dispatcher available
User who did this - Daniel-Constantin Mierla (miconda)
----------
Should not crash and should be fixed. Just that I was investigating in the wrong direction based on your description.
Can you get the log messages with debug=3 in this case? I expect to be a lot of them as the PUBLISH is looping.
Also, what is the value for the retransmission timeout you set in the config file?
----------
More information can be found at the following URL:
http://sip-router.org/tracker/index.php?do=details&task_id=440#comment1524
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task is now closed:
FS#441 - route name in action struct
User who did this - Víctor Seva (linuxmaniac)
Reason for closing: Implemented
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=441
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#441 - route name in action struct
User who did this - Daniel-Constantin Mierla (miconda)
----------
Just use "unknown_route" instead of "unknown_type_route" (suggestive enough and shorter). Then it can be committed.
----------
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=441#comment1523
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.
THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.
The following task has a new comment added:
FS#441 - route name in action struct
User who did this - Víctor Seva (linuxmaniac)
----------
Something like this, doesn't it?
----------
One or more files have been attached.
More information can be found at the following URL:
https://sip-router.org/tracker/index.php?do=details&task_id=441#comment1522
You are receiving this message because you have requested it from the Flyspray bugtracking system. If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.