Forums / Install & configuration / Notification cronjob timeouts

Notification cronjob timeouts

Previous topic

Install & configuration

Next topic

Author	Message
Piotrek Karaś	Saturday 08 August 2009 2:53:54 am Hello there, We have a site based on 4.1.3 that has around 30-40 thousand of objects published. So far the notifications haven't been used on that site (even though we have notification experiences from other sites, no special problems). Now, when I start to run notification.php cronjob, I get an error: self:/home/pd/www/pd# php runcronjobs.php notification Running cronjob part 'notification' Running cronjobs/notification.php Starting notification event processing Fatal error: Allowed memory size of 314572800 bytes exhausted (tried to allocate 491520 bytes) in /home/pd/www/pd/var/site/cache/template/compiled/plain-392b702a566fdd19849d50eb6bdecacb.php on line 335 Fatal error: eZ Publish did not finish its request The execution of eZ Publish was abruptly ended, the debug output is present belo w. self:/home/pd/www/pd# This is already 300MB of memory assigned to CLI, still no success. 1) How much memory should we except to be enough? 2) How do the notifications really work in terms of performance? Will that much memory be required each time the notification cronjob is run? OR do we have this problem only because of running it for the very first time on a larger amount of objects? Thanks, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu
André R.	Monday 10 August 2009 6:53:38 am 1) Depends on whats being done in the notification templates, like the one you have some issues with there (open the file mentioned to see witch template this is). 2) again, depends on whats being done in templates. But if this is first time you run it, there might be a lot of pending notifications waiting to be sent out. eZ Online Editor 5: http://projects.ez.no/ezoe \|\| eZJSCore (Ajax): http://projects.ez.no/ezjscore \|\| eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription @: http://twitter.com/andrerom
Piotrek Karaś	Monday 10 August 2009 1:56:20 pm Hello Andre, Thanks for your reply. Isn't there (or shouldn't there be) a way to buffer or limit the range of the cronjob per run? If not, what if someone had 500000 objects with notifications never on, and then decides otherwise? ;) Anyway, I will try with some more memory... Cheers, Piotrek -- Company: mediaSELF Sp. z o.o., http://www.mediaself.pl eZ references: http://ez.no/partners/worldwide_partners/mediaself eZ certified developer: http://ez.no/certification/verify/272585 eZ blog: http://ez.ryba.eu

Author

Message

Piotrek Karaś

Saturday 08 August 2009 2:53:54 am

Hello there,

We have a site based on 4.1.3 that has around 30-40 thousand of objects published. So far the notifications haven't been used on that site (even though we have notification experiences from other sites, no special problems). Now, when I start to run notification.php cronjob, I get an error:

self:/home/pd/www/pd# php runcronjobs.php notification
Running cronjob part 'notification'
Running cronjobs/notification.php
Starting notification event processing

Fatal error: Allowed memory size of 314572800 bytes exhausted 
(tried to allocate 491520 bytes) 
in /home/pd/www/pd/var/site/cache/template/compiled/plain-392b702a566fdd19849d50eb6bdecacb.php on line 335

Fatal error: eZ Publish did not finish its request
The execution of eZ Publish was abruptly ended, the debug output is present belo                                              w.
self:/home/pd/www/pd#

This is already 300MB of memory assigned to CLI, still no success.

1) How much memory should we except to be enough?
2) How do the notifications really work in terms of performance? Will that much memory be required each time the notification cronjob is run? OR do we have this problem only because of running it for the very first time on a larger amount of objects?

Thanks,
Piotrek

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

André R.

Monday 10 August 2009 6:53:38 am

1) Depends on whats being done in the notification templates, like the one you have some issues with there (open the file mentioned to see witch template this is).

2) again, depends on whats being done in templates. But if this is first time you run it, there might be a lot of pending notifications waiting to be sent out.

eZ Online Editor 5: http://projects.ez.no/ezoe || eZJSCore (Ajax): http://projects.ez.no/ezjscore || eZ Publish EE http://ez.no/eZPublish/eZ-Publish-Enterprise-Subscription
@: http://twitter.com/andrerom

Piotrek Karaś

Monday 10 August 2009 1:56:20 pm

Hello Andre,

Thanks for your reply.
Isn't there (or shouldn't there be) a way to buffer or limit the range of the cronjob per run?
If not, what if someone had 500000 objects with notifications never on, and then decides otherwise? ;)

Anyway, I will try with some more memory...

Cheers,
Piotrek