marcinzp

@tsteur thank you for your answer and explanations. In the night, the growing queue was "magically" processed, but I think I still need to prepare for the return of the...

Thank you @tsteur In advance - is there a way to remove permanently first request from the specific queue, just to see if this one was blocking the processing? By...

Thank you. I've checked, that we are using userId both in JS and SDK clients. So if my problem returns, I need to check what is different in requests in...

I didn't need to wait long @tsteur :-) I got WARNING of "Invalid argument" /usr/share/piwik/console queuedtracking:monitor Queue is enabled The command ./console queuedtracking:process has to be executed to process request...

After two hours: /usr/share/piwik/console queuedtracking:monitor Queue is enabled The command ./console queuedtracking:process has to be executed to process request sets within queue Up to 8 workers will be used Processor...

Thank you @tsteur - EDITED ~2 hours after patching, I see that queue is indeed decreasing its size AND I don't see requests from that user id: 179829 (50+179622+13+53+26+13+47+5) request...

So far so good :-) Thank you for helping me, I'll keep you informed.

@tsteur The problem is back :-( /usr/share/piwik/console queuedtracking:monitor Queue is enabled The command ./console queuedtracking:process has to be executed to process request sets within queue Up to 16 workers will...

@tsteur could you possible reopen this issue? Thank you, Marcin

@tsteur 1. I didn't see any error messages on "/console queuedtracking:print-queued-requests --queue-id=0" 2. Now I've checked historical logs of nginx and stderr from "console queuedtracking:process" but there's nothing interesting. 3....