-
Notifications
You must be signed in to change notification settings - Fork 9.4k
Cron not Reindexing Index #5836
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
We also see this using CE 2.1.0 - PHP 7.0.8 - Mysql 5.7.13 When adding products, they don't appear on the frontend, until we manually run a Cronjobs are setup correctly and indexers are set to 'Update by Schedule'. Sounds like a pretty important bug. |
We are experiencing the same problem on lower Mage2 versions (2.0.4 and 2.0.6). So far we haven't found a solution for that. |
Yes, it is a important bug. I am experiencing the same issue as well, Magento 2.1 v, The cron is setup properly, but does not show products until it is re indexed. |
Works for me if I set 'Use Separate Process' to 'No' for the index CRON group. |
@boldhedgehog: tnx, but unfortunately it doesn't seem to fix our issue :( |
Setting 'Use Separate Process' to 'No' for the index CRON group does not work for me either. |
@hostep I had to wait a little and after 5-10 runs of cron:run Magento had added indexer tasks to cron_schedule:
|
@boldhedgehog: yes, I see them too, even with 'Use separate process' on 'Yes'. So this means the indexers are correctly executed through the cron, but something in the execution itself goes wrong I guess... If I find some time in the coming days, I'll debug and try figure out what exactly goes wrong. Tnx for the hints! |
This is the same behaviour for me as well. The cron_schedule table says success for the status but the frontend does not update. |
It has rebuilt my Elasticsearch index. This can be an index/caching issue, not a CRON/index issue you have now, in addition. |
I have the same problem in 2.1.0. I have setup the cron job nicely. I even tried to run |
This seems a critical issue. Is there any workaround for fixing this until an official fix is done? |
@ojhaujjwal I setup an additional cron job to run the indexer:reindex command for now. It fills up the debug.log file quite quickly when it's run though. |
@crtsl I noticed that if I add magento indexer:reindex to cron, the cache is invalidated everytime the command is run and I have to flush the page cache. This creates even more problems. |
I have noticed this behavior as well. I have to run indexer:reindex and it makes my debug.log incredibly large. It's a pain but I clear out information that is more than a month old. Magento 1 had an automated function to clear the logs. Wish they would bring that back. |
Can anybody tell me the status of this issue? Is there any internal-ticket for the issue? Is there any commits that may fix the issue? |
Has anyone found a solution to this problem yet? |
@gman-1986 running I don't see an internal ticket reference for this issue though which is concerning considering it is an important bug. |
Does anyone know if this issue is fixed in 2.1.1. |
The issue still appears to be there after upgrading to 2.1.1. |
+1 this, so annoying having to manually reindex via ssh every time I make a change to the site! |
@oserediuk is there any update to this issue? Is there an internet ticket? |
+1 This issue is critical for us |
I use temporary solution.
Run http://example.com/pub/reindex.php to reindex. Still waiting for solving of this issue. |
I have the same issue with Magento 2.1.1 on cPanel. But new products won't show if I do not manually reindex - |
Does anyone know if the latest version 2.1.2 has fixed the problem? |
@gman-1986 I just upgraded from 2.1.1 to 2.1.2 and this issue is not fixed. |
hi there! cheers! |
Can anyone confirm whether or not this is only affecting the indexers? Do any other scheduled tasks work normally? Edit: From further research it seems to just be affecting indexers |
How is it possible that this issue have existed since summer 2016 and not have been fixed by Magento? Following... |
If the indexers work from CLI, but not from cron. Check the default system ulimits. I've found that to be an issue on some systems. |
I have problem on M2.2.0 with cron job "indexer_update_all_views" i have some configurable products with many simple products assined. ~5k simple products. I don't see any errors in log files |
@crtsl, thank you for your report. |
Will the fix be backported to 2.1.x? |
Not sure if this is related or not... I'm having trouble running cron (2.2.1) I can reindex myself but when I try to run cron it just hangs. I checked php/magento logs and there was nothing in them, however... when I looked into mysql logs im getting (Got an error writing communication packets) timestamped at the exact time I'm trying to run cron. Thanks, |
Hi everybody! I had the same problem with indexes (my case product indexes) not being reindexed with cron:run. This caused new products to not being shown on frontend without a manual index:reindex. The problem was that version_id in mview_state table had a value much higher than the autoincrement value in catalog_product_category_cl table. Everytime magento 2 cron runs it checks whether the changelogs tables have higher values than mview_state indexes (version_id). In my case I was able to resolve my issue by setting version_id in mview_state to 0 for the faulty indexes. This command solved my problem: I hope this can help someone else out there, I hade to spend several frustrating hours on this issue. /Chris |
I still have the issue on 2.2.1 does anyone else? |
In my case column 'status' was stuck in 'suspended' for 'catalog_product_category' view in mview_state. Resetting the value to 'idle' fixed the issue. Additionally i set version_id to 0 and allowed the cron to reindex. |
Yes - this can happen sometimes when the cron process either crashes or is terminated by oom-killer. For that scenario, you can also use Note that before doing this, it's best to validate that no cron process is currently running. |
@magento-engcom-team , is it possible to see some references to commit or task number to understand what can cause this? |
@unicoder88 I've actually just opened #13577 to fix exactly that issue. You can see an explanation of why it happens there. |
You can check if the status of mview_state is not working after a script crash. |
We wrote an extension to fix these bugs, speed up performance, and control the execution of tasks: https://github.com/magemojo/m2-ce-cron |
No need to run re indexing. to get instant help please contact here [email protected] |
@crtsl Please see my bug report and the solution here: #19417 |
I still have this issue on Magento 2.3.0 Crons are setup correctly and my custom indexer is set to update on schedule. I have to run It only works fine calling it through the command line. |
I have same issue and found that magento cannot run separated process to execute index job. I had to switch settings to Use Separate Process = No and then scheduled indexes executes fine. I also noticed that indexer_update_all_views has status run. Magento 2.3.1 |
Hello, i need your Help: Results: I can't reindex following Position: Please tell my what i can to reindex this 2 Position. Thanks |
We are facing similar issue where after a customer purchases items on our store, items gets disappeared on our store front from category pages. Only solution is to manually reindex which is not a solution but strangely it is only happening to one of our stores. Magneto support yet to come up with a positive answer. We are on Magneto cloud 2.3.1 and yet facing such issue. I was hopeful after Adobe acquisition but no luck. |
[TSG] MC-35316: Pagination products not work in admin create order page
The indexes are not being reindexed with the standard cron:run cron job. This is particularly noticeable when making a change to a category and it not being updated on the front end. I can add a static block or description to a category and save it in the backend and the updates will not appear on the frontend until the indexers have been manually reindexed. This could possibly be related to #2855.
Preconditions
Steps to reproduce
Expected result
Actual result
I have noticed that the debug.log has been filling up quite fast with lines like the following:
I have setup a cron job just for reindexing as a work around for now and it seems to be working. My cron jobs are setup as follows:
The text was updated successfully, but these errors were encountered: