Systemd was Rate Limiting the console logs so that's the reason the capture
above was incomplete. Piping it to disk revealed the full debug log, thanks for
the tip.
The problem is that mongo does not have the AUTO INCREMENT id field such as
MySQL . The equivalent key is " _id" and is
If you monitor traffic at network level, do you seen opensips sending the
delete query to the DB server ?
---
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
Bogdan, the debug did not really print anything from the MSILO module as posted
below, Opensips 2.1.2. There is only a comment in the script during
registration when the m_dump() is executed. The mongdb query you see is just
housekeeping.
Mar 18 10:20:15 : route[initial_requests] :
@jalung , you printed/posted the debug for mdump() call, but the delete from DB
is done on the reply of the sent MESSAGE...If the signaling is ok, opensips
should receive a 200 OK reply for the MESSAGE request - the debugs for handling
that 200 OK are important.
---
You are receiving this
I highlighted the comments on the reply from the UA in the reply-route. M_dump
is not printing any de bug messages. Tell me what to change in the code for
m_dump to print messages.
Two points:
It works ok when silo is in mariaDB .
If there is a problem with signaling it should not continue to
BTW, what opensips version are you using ?
---
Reply to this email directly or view it on GitHub:
https://github.com/OpenSIPS/opensips/issues/798#issuecomment-193743689___
Devel mailing list
Devel@lists.opensips.org
@jalung , do you see any errors (in opensips log) on handling the 200 OK from
the end point ? Also, do you see any attempt to actually run the delete query?
using debug level 4 will help in providing more output from opensips.
---
Reply to this email directly or view it on GitHub:
If the messages are stored in a Mongo Replicaset using the CACHEDB module,
messages are stored, but being sent out repeatedly on each re-registration of
the client. It seems not able to update mongo on the 2xx.
---
Reply to this email directly or view it on GitHub:
