Scheduled Tasks/Cron stopped working

[hpvd]

Since everything seems to be fixed with the (beta/RC)-Version in the mid of February now all the viewable
Scheduled Tasks/Cron-Jobs (for Geoip update etc ) have stopped working again (and are in the past)
please see attachment

[hpvd]

Attachment:
2014-02-28_11h00_50.png

[hpvd]

current version: 2.1RC9 (no update shown)

details of last fix:

#4263

finally fixed by fixing:
#4612

see also:
#4652

now everything works fine!

=> hopefully we can say this again soon :-)

[hpvd]

still not working in 2.1 final

Please see new attachment.

[hpvd]

Attachment:
2014-03-04_23h23_44.png

[tsteur]

Hi there,

I cannot really reproduce it at the moment and need your help...

Can you check the local (might be not present there) and global config value of

[Tracker]
scheduled_tasks_min_interval

and can you check the value of the option "lastTrackerCronRun" in the database "option" table?

There have been tracking visits since mid february right?

[hpvd]

urgghhh
you are ask-ing (its identified as spam..) the right thing:
"There have been tracking visits since mid february right?"

I would say: "Yes of course!"

Thinking a little longer:
We have got a multisite testing setup.
On 2 of 3 sites there were many many visits.

On the first site (the one with the lowest site ID) there were no visits
(because in the moment the development happens on the other sites..)

After visiting this site, there were immediately new tasks with a future date in the tasktime table plugin :-)

=> Maybe one should look on all sites for triggering the task/cron start.
Or find any other suitable way for starting.
-because we have really spent plenty of time on this topic and no one else should have to do this again...

Many thanks!!

[tsteur]

Sorry for having to spent so much time on this. You're right, it should be triggered on all sites. Without testing but having a look at the code it should work for all sites as long as the tracking request is not authenticated.

Is there the possibility you are setting the token_auth parameter when tracking the other sites?

I also just noticed there is a setting named "tracking_requests_require_authentication" and if disabled it would not start the ScheduledTasks via Tracker. But this should be irrelevant for your case as it would not work for any site then.

[hpvd]

thanks for your answer.

the is token_auth parameter is not set.
The only think we are doing is forwarding the piwik subdomain:
but tracking is working fine so everything should be ok on this place...

[hpvd]

the problem is reproduceable. See new screenshots.

[hpvd]

Attachment:
before-2014-03-14_13h23_45.png

[hpvd]

Attachment:
after-2014-03-14_13h25_45.png

[tsteur]

I do not think it is directly related to the "lowest idsite" but to a difference in how the tracking is done.

Do you think it is possible for you to change the following line: https://github.com/piwik/piwik/blob/master/piwik.php#L15 from

$GLOBALS['PIWIK_TRACKER_DEBUG'] = false;

to

$GLOBALS['PIWIK_TRACKER_DEBUG'] = true;

and then perform a regular tracking request and capture the response of that tracking request? Preferably first with the site that does not trigger the scheduled tasks and afterwards with the site that triggers the scheduled tasks (the site with the lowest id).

For instance in my case the output of a tracking request looks like this: http://pastebin.com/VZwDaAzx . You could post the responses either on pastebin and post a link here or if the responses contain sensitive data like IP or anything else you can send us an email to hello @ piwik.org .

It would help me as I cannot reproduce it so far.

[hpvd]

Hi many thanks for your advise - sure I can do that and have already done this.
=> Where can I find debug messages?
are they written to a special file?
or do I have to activate something else to see them directly?
sorry I'm no programmer...

[hpvd]

following the link in the doc
https://piwik.org/docs/tracking-api/#toc-debugging-the-tracking-calls
I could find no solution...

[tsteur]

In dbe8a79: refs #4780 added possibility to enable tracker debug via config, use logger for printing debug messages which allows users to log to screen, file or db