Magento 目录价格规则

发布于 2024-10-08 01:20:33 字数 595 浏览 1 评论 0原文

我的目录价格规则始终失败。

自 1.4.1 以来,它们就失败了。我已经升级到 1.4.2,因为有些人说它已修复,但不幸的是对我来说并没有。

克朗运行。 Cron 作业监视器报告正在计划并成功运行的各种任务。除了目录价格规则之外的一切。这东西是怎么回事?

我设置了我的系统 -> Cron 设置为:

Generate schedules every: 60
Schedule ahead for: 1
Missed if not run within: 60
History cleanup every: 120
Success history lifetime: 120
Failure history lifetime: 120

Update#1。我正在查看 cronmonitor.php 文件,发现 Catalogrule_apply_all 截至凌晨 1 点处于待处理状态。我还看到很多工作被错过了。

更新#2。凌晨 2 点,catalogrule_apply_all 从 cronmonitor 中消失,我认为历史记录已被清除,所以我没有看到任何遗漏的内容。我很确定它被错过了。

那么,现在我该如何防止错过呢?

My catalog price rules consistently fail..

They've failed ever since 1.4.1. I've upgraded to 1.4.2 because some people said that it was fixed, unfortunately for me it wasn't.

Cron runs. Cron job monitor reports various tasks being scheduled and successfully running. Everything except catalog price rules. What is the matter with this thing?

I set my System -> Cron settings to:

Generate schedules every: 60
Schedule ahead for: 1
Missed if not run within: 60
History cleanup every: 120
Success history lifetime: 120
Failure history lifetime: 120

Update#1. I'm looking at my cronmonitor.php file and I see catalogrule_apply_all was pending as of 1AM. I also see a lot of jobs that were missed.

Update#2. At 2am catalogrule_apply_all disappeared from cronmonitor and I think the history was cleared, so I don't see anything under missed. I'm pretty sure that it was missed.

So, now, how do I prevent it from being missed?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(2

や莫失莫忘 2024-10-15 01:20:33

我建议您使用您最喜欢的 IDE 设置进行调试,然后从 Web 浏览器调用 cron.php 并逐步执行代码。您可以手动将条目插入数据库的 cron_schedule 表中,以强制 cron 执行特定的 cronjob,例如 catalogrule_apply_all。在 Mage_CatalogRule_Model_Observer::dailyCatalogUpdate($observe) 中设置断点并跟踪它。

这应该可以让您隔离问题并(希望)解决。

I would recommend that you get your favourite IDE setup to debug, and then call cron.php from your web browser and step through the code. You can manually insert entries into the cron_schedule table in the database to force cron to execute a particular cronjob such as catalogrule_apply_all. Set a breakpoint inside Mage_CatalogRule_Model_Observer::dailyCatalogUpdate($observe) and trace it through.

That should allow you to isolate the problem and (hopefully) resolve.

眸中客 2024-10-15 01:20:33

好吧,经过更多的挖掘和调查,我的问题终于解决了!

事实证明,更新到 1.4.2 后,我的本地法师文件夹中仍然有一些修改过的 1.4.1 目录价格规则文件,这些文件导致规则无法正常运行。我删除了那些。

之后,我还必须在“配置”>“设置”中设置我的 Cron 计划。系统:

Generate Schedules Every: 1
Schedule Ahead for: 15
Missed if Not Run Within: 120
History Cleanup Every: 1440
Success History Lifetime: 1440
Failure History Lifetime: 1440

最后三个设置为 1440 分钟,这样我就可以在我的 cron 监视器中看到完整的 24 小时。

现在讨论 Google Base 问题。

Well, after more digging and investigation, my problem is finally RESOLVED!

Turns out that after updating to 1.4.2, I still had some modified 1.4.1 catalog price rule files in my local mage folder that were preventing the rules from running properly. I deleted those.

After that, I also had to set my Cron schedules in Configuration > System to:

Generate Schedules Every: 1
Schedule Ahead for: 15
Missed if Not Run Within: 120
History Cleanup Every: 1440
Success History Lifetime: 1440
Failure History Lifetime: 1440

The last three are set to 1440 minutes so that I can see a full 24 hours in my cron monitor.

Now onto the Google Base issue.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文