Sitemaps: cronjobs disables itself

Hi,

After running a few times, the sitemap cronjob just deactivates itself.
It unticks the box in front of it in /acp/index.php/CronjobList/

I don't see any error messages or a clear reason why it deactivates itself.

Any idea what could cause it or where I could look for the cause of the issue?

Thank you

No, it just displays a line in the logs without "success", an empty line.

The cronjob stopped again last Thursday (unticked it's active state).

These are the database records of the cronjob log (wcf1_cronjob_log):

cronjobLogID cronjobID execTime success error
52427 15 1409841010 0 NULL
52428 15 1409841020 0 NULL
52429 15 1409841023 1 NULL
55576 15 1410184332 1 NULL
55577 15 1410184358 1 NULL
55578 15 1410184365 1 NULL

So the last execution seems to be a success, but still it disabled itself.

Is there a way in your package to enable advanced debugging?

Let me know if there is anything I can do to help you resolve this issue.
Re-enabling cronjobs every 3 days is quite a hassle.

Hi,

I started a thread here and there indeed seems to be an automatic disabling system:
http://www.woltlab.com/forum/i…cronjobs-disables-itself/

Can you try to assist in this topic as well in case new answers appear?

Thank you,
Koen

I tried that, but then on nginx it does not create multiple files, it only creates one.

Alexander from woltlab looked at it and this was his conclusion:
"I've checked the cronjob (which calls the worker itself) and the issue might be the way the entire file is being created: All data is stored into a temporary variable and then written in one step only. This saves a lot of time because the disks are not busy writing every single line, but this also causes the temporary variable to eventually grow really big. Filling the buffer variable up to a certain threshold and then flushing to disk might avoid this problem."