Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI processEventQueue going straight to 'unprocessed' #406

Open
jasonlipo opened this issue Jun 20, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@jasonlipo
Copy link

commented Jun 20, 2019

I am trying to use the event queue processing and the running the following command on terminal:
php /var/app/current/web/owa/cli.php cmd=processEventQueue

On doing so I get the following result:

21:43:13 2019-06-20 7927 [console_log] About to process event queues: incoming_tracking_events,processing 
21:43:13 2019-06-20 7927 [console_log] receive event. 
21:43:13 2019-06-20 7927 [console_log] queue files to process: Array
(
    [1560961626] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-19-17-2708.txt
    [1560961683] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-19-17-2805.txt
    [1560961795] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-19-17-3006.txt
    [1560961938] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-19-17-3222.txt
    [1561060911] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-0153.txt
    [1561060995] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-0318.txt
    [1561061111] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-0528.txt
    [1561061202] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-0647.txt
    [1561061695] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-1457.txt
    [1561061714] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-1522.txt
    [1561061755] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-1600.txt
    [1561062087] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2318.txt
    [1561062144] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2233.txt
    [1561062170] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2253.txt
    [1561062183] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2307.txt
    [1561062364] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2618.txt
    [1561062429] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2711.txt
    [1561062540] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2905.txt
    [1561062596] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-2957.txt
    [1561062790] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-3314.txt
    [1561062872] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-3441.txt
    [1561063033] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-3721.txt
    [1561063073] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-3754.txt
    [1561063091] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-3815.txt
    [1561063274] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-4127.txt
    [1561063392] => /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-20-21-4313.txt
)
 
21:43:13 2019-06-20 7927 [console_log] Opening queue file /var/app/current/web/owa/owa-data/logs/unprocessed/incoming_tracking_events-eventfile-2019-06-19-17-2708.txt to process. 

After that last line, there's no error and it just stops. The events.txt file is no longer there but instead a file has been added to the 'unprocessed' folder and all the other unprocessed log files are still there. Crucially, nothing's been added to the database.

Can someone explain the problem?
There's no database connection error or permissions denied error so can't work out how to get rid of this backlog of events...

@warrenvail-micron

This comment has been minimized.

Copy link

commented Jun 25, 2019

Began experiencing errors attempting to post events to the owa site, error message suggest inability to reference the Tracker owa_cmds queue. Interestingly enough, I believe it may relate to a windows 10 update that occurred at that time. Your trace suggests a unix server, and our servers are unix as well, but the browsers (Firefox and Chrome) are operated from windows, which is where the JS prepares the GET to the OWA unix server to post things. Have not been able to track anything in OWA since Thursday late.

Seeing the following in Firefox;
Synchronous XMLHttpRequest on the main thread is deprecated because of its detrimental effects to the end user’s experience. For more help http://xhr.spec.whatwg.org/
Have no idea who whatwg.org is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.