site cron status does not update after external elysia-cron run. [#1675970]

I've installed elysia_cron

I'm setting up the cmd string for use in my crontab. I use wget as follows:

	wget -U firefox --ca-certificate="/srv/sec/my_CA/my_CA.crt" --no-check-certificate -O - -t 1 https://test.loc/cron.php?cron_key=kPB...abc
		--2012-07-08 10:35:03--  https://test.loc/cron.php?cron_key=kPB...abc
		Resolving test.loc (test.loc)... 2001:xxx:xxxx:xxx::33, 192.168.1.33
		Connecting to test.loc (test.loc)|2001:xxx:xxxx:xxx::33|:443... connected.
		HTTP request sent, awaiting response... 200 OK
		Length: 0 [text/html]
		Saving to: `STDOUT'

		    [ <=>                                                                        ] 0           --.-K/s   in 0s

		2012-07-08 10:35:03 (0.00 B/s) - written to stdout [0/0]

In my apache access log:

	==> /var/log/apache2/test.loc.8084.2012-07-08-00.access_log <==
	test.loc 2001:xxx:xxxx:xxx::33, 127.0.0.1, 127.0.0.1 - - [08/Jul/2012:10:41:34 -0700] "GET /cron.php?cron_key=kPBkPB...abc HTTP/1.1" 200 - "-" "firefox"

It looks like it's working.

Immediately after running that job, I check @ site status, (admin/reports/status),

	Cron maintenance tasks	Last run 43 min 1 sec ago
	You can run cron manually.
	To run cron from outside the site, go to https://test.loc/cron.php?cron_key=kPB...abc

Cron execution status never updates after an external cron-job run.

Otoh, If I exec the "run cron manually" link from within the browser,

	https://test.loc/admin/reports/status/run-cron

the status page immediately reflects:

Cron maintenance tasks Last run 0 sec ago

Iiuc, the status page should (?) get updated after an external-init'd cron run.

Comments

Comment #1

gotheric commented 11 July 2012 at 01:05

Priority:	Normal	» Minor
Status:	Active	» Postponed

Hmmm, it sounds weird but this is the right thing to do.

Updating the "Last run" in status page results in a loss of permance in sites with frequent cron calls.
One of the performance optimizations of elysia cron is right that.

The correct "Last run" time is shown in "admin/config/system/cron".

However i can understand that from a user point of view this is not smart.
I'll try to see if i can replace entirely that block in status table, with correct data.
But not right now, i must complete the development of next major release first.

Comment #2

Renee S commented 1 April 2014 at 20:20

Hmm, ok, I'm not seeing "last run" time updated in either place. Using cronkey, tried with and without Allowed Hosts, and the only way cron runs is by poorman's cron (logged in as an administrator only), or hitting the big button.

Comment #3

Renee S commented 1 April 2014 at 20:20

Status:

Postponed

» Active

Comment #4

techypaul commented 6 June 2014 at 13:55

Hi,

I am getting the same issue as reported (and re-opened by Renee). I can't run cron at all unless I do so logged in and using the run cron button. If i do it from the URL internally, or via the browser, and I am not logged in it doesn't work. I do not get 403, but 200, yet it still doesn't trigger.

Any suggestions?

Thanks,
Paul.

Comment #5

techypaul commented 6 June 2014 at 13:55

Priority:

Minor

» Normal

Comment #6

spidersilk commented 11 August 2014 at 20:10

I'm having this on one site as well - Elysia Cron will run when I click the "Run cron" button, but not on its own as a scheduled job, or by manually entering the URL that the scheduled job uses in my browser. Despite the fact that it used to (up until about three months ago), and other sites that also use the module, on the same server, with an identical setup, do have it running properly. I've been through all the settings over and over again and I can't see why it's stopped running on this one particular site....

Comment #7

mooru commented 25 August 2014 at 22:12

Same issue here as #6. What's the fix?

Comment #8

rob3000 commented 27 November 2014 at 04:11

I'm having the same issue.

I changed my cron tab to use the cron.php file found in the elysia module e.g
http://example.com/sites/all/contrib/modules/elysia_cron/cron.php?key_id?key

its seems to run but every now and then the watchdog shows a 'page not found' for the cron.php file but i can see that the Cron channel default run completed.

Any one have any ideas?