You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are subscribing multiple events to the same flatstore file. When you perform a evi_flat_rotate on the shared file only one event is "rotated" the other events continue to write to the old file.
To Reproduce
Steps to reproduce the behavior:
subscribe two or more events to the same flatstore file in route startup
create a timer route to print events and confirm events are written to file
…ame file
Use the same internal shm struct corresponding to a file for each evi
subscription for that file. This fixes an issue with the 'evi_flat_rotate' MI
command not properly "rotating" multiple subscriptions to the new file. Besides,
a file is now opened only once regardless of how many subscribtions there are
for the same file.
Also, do not reuse an old 'evi_reply_sock' structure for a new subscription for
the same file (if the file corresponding to an old subscription was not yet
closed by all processes). This led to incorrect expire times for new
subscriptions.
Fixes#1933
(cherry picked from commit a2f4f80)
…ame file
Use the same internal shm struct corresponding to a file for each evi
subscription for that file. This fixes an issue with the 'evi_flat_rotate' MI
command not properly "rotating" multiple subscriptions to the new file. Besides,
a file is now opened only once regardless of how many subscribtions there are
for the same file.
Also, do not reuse an old 'evi_reply_sock' structure for a new subscription for
the same file (if the file corresponding to an old subscription was not yet
closed by all processes). This led to incorrect expire times for new
subscriptions.
Fixes#1933
(cherry picked from commit a2f4f80)
OpenSIPS version you are running
Describe the bug
We are subscribing multiple events to the same flatstore file. When you perform a evi_flat_rotate on the shared file only one event is "rotated" the other events continue to write to the old file.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
We expect all subscribed events to rotate.
Relevant System Logs
Printed right after the rotate command
OS/environment information
Additional context
Attaching min config script.
opensips.cfg.txt
The text was updated successfully, but these errors were encountered: