Indexer stuck in processing
Magento ver. 2.0.7
Hello, I'm trying to reindex my store so that products I added from the backend will show up on the frontend.
As shown below, after running bin/magento indexer:reindex, every index has been rebuilt successfully but bin/magento indexer:status shows some of the indices still processing as confirmed in the Admin Panel > System > Index Management
What can I do to resolve this? My website no longer shows any products.
[user@server root]$ bin/magento indexer:reindex
Customer Grid index has been rebuilt successfully in 00:00:00
Category Products index has been rebuilt successfully in 00:00:00
Product Categories index has been rebuilt successfully in 00:00:00
Product Price index has been rebuilt successfully in 00:00:04
Product EAV index has been rebuilt successfully in 00:00:06
Stock index has been rebuilt successfully in 00:00:00
Catalog Rule Product index has been rebuilt successfully in 00:00:00
Catalog Product Rule index has been rebuilt successfully in 00:00:00
Catalog Search index has been rebuilt successfully in 00:00:00
[user@server root]$ bin/magento indexer:status
Customer Grid: Processing
Category Products: Processing
Product Categories: Processing
Product Price: Ready
Product EAV: Ready
Stock: Ready
Catalog Rule Product: Ready
Catalog Product Rule: Ready
Catalog Search: Processing
magento2 indexing reindex
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
add a comment |
Magento ver. 2.0.7
Hello, I'm trying to reindex my store so that products I added from the backend will show up on the frontend.
As shown below, after running bin/magento indexer:reindex, every index has been rebuilt successfully but bin/magento indexer:status shows some of the indices still processing as confirmed in the Admin Panel > System > Index Management
What can I do to resolve this? My website no longer shows any products.
[user@server root]$ bin/magento indexer:reindex
Customer Grid index has been rebuilt successfully in 00:00:00
Category Products index has been rebuilt successfully in 00:00:00
Product Categories index has been rebuilt successfully in 00:00:00
Product Price index has been rebuilt successfully in 00:00:04
Product EAV index has been rebuilt successfully in 00:00:06
Stock index has been rebuilt successfully in 00:00:00
Catalog Rule Product index has been rebuilt successfully in 00:00:00
Catalog Product Rule index has been rebuilt successfully in 00:00:00
Catalog Search index has been rebuilt successfully in 00:00:00
[user@server root]$ bin/magento indexer:status
Customer Grid: Processing
Category Products: Processing
Product Categories: Processing
Product Price: Ready
Product EAV: Ready
Stock: Ready
Catalog Rule Product: Ready
Catalog Product Rule: Ready
Catalog Search: Processing
magento2 indexing reindex
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
You can runphp bin/magento indexer:resetto reset the ones stuck on 'processing', then reindex them all (again). That probably won't solve your real problem though.
– Ryan Hoerr
Aug 12 '16 at 3:37
Try reindexing only one of the problematic ones and see if errors display.
– Steve Johnson
Aug 14 '16 at 14:17
@RyanH. I'm getting an err msg 'Command "indexer:reset" is not defined'
– Nikkawat
Aug 15 '16 at 17:10
@SteveJohnson They're still stuck in processing, let's see what Magento forums say
– Nikkawat
Aug 15 '16 at 17:11
add a comment |
Magento ver. 2.0.7
Hello, I'm trying to reindex my store so that products I added from the backend will show up on the frontend.
As shown below, after running bin/magento indexer:reindex, every index has been rebuilt successfully but bin/magento indexer:status shows some of the indices still processing as confirmed in the Admin Panel > System > Index Management
What can I do to resolve this? My website no longer shows any products.
[user@server root]$ bin/magento indexer:reindex
Customer Grid index has been rebuilt successfully in 00:00:00
Category Products index has been rebuilt successfully in 00:00:00
Product Categories index has been rebuilt successfully in 00:00:00
Product Price index has been rebuilt successfully in 00:00:04
Product EAV index has been rebuilt successfully in 00:00:06
Stock index has been rebuilt successfully in 00:00:00
Catalog Rule Product index has been rebuilt successfully in 00:00:00
Catalog Product Rule index has been rebuilt successfully in 00:00:00
Catalog Search index has been rebuilt successfully in 00:00:00
[user@server root]$ bin/magento indexer:status
Customer Grid: Processing
Category Products: Processing
Product Categories: Processing
Product Price: Ready
Product EAV: Ready
Stock: Ready
Catalog Rule Product: Ready
Catalog Product Rule: Ready
Catalog Search: Processing
magento2 indexing reindex
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
Magento ver. 2.0.7
Hello, I'm trying to reindex my store so that products I added from the backend will show up on the frontend.
As shown below, after running bin/magento indexer:reindex, every index has been rebuilt successfully but bin/magento indexer:status shows some of the indices still processing as confirmed in the Admin Panel > System > Index Management
What can I do to resolve this? My website no longer shows any products.
[user@server root]$ bin/magento indexer:reindex
Customer Grid index has been rebuilt successfully in 00:00:00
Category Products index has been rebuilt successfully in 00:00:00
Product Categories index has been rebuilt successfully in 00:00:00
Product Price index has been rebuilt successfully in 00:00:04
Product EAV index has been rebuilt successfully in 00:00:06
Stock index has been rebuilt successfully in 00:00:00
Catalog Rule Product index has been rebuilt successfully in 00:00:00
Catalog Product Rule index has been rebuilt successfully in 00:00:00
Catalog Search index has been rebuilt successfully in 00:00:00
[user@server root]$ bin/magento indexer:status
Customer Grid: Processing
Category Products: Processing
Product Categories: Processing
Product Price: Ready
Product EAV: Ready
Stock: Ready
Catalog Rule Product: Ready
Catalog Product Rule: Ready
Catalog Search: Processing
magento2 indexing reindex
magento2 indexing reindex
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
asked Aug 11 '16 at 20:18
NikkawatNikkawat
56312
56312
You can runphp bin/magento indexer:resetto reset the ones stuck on 'processing', then reindex them all (again). That probably won't solve your real problem though.
– Ryan Hoerr
Aug 12 '16 at 3:37
Try reindexing only one of the problematic ones and see if errors display.
– Steve Johnson
Aug 14 '16 at 14:17
@RyanH. I'm getting an err msg 'Command "indexer:reset" is not defined'
– Nikkawat
Aug 15 '16 at 17:10
@SteveJohnson They're still stuck in processing, let's see what Magento forums say
– Nikkawat
Aug 15 '16 at 17:11
add a comment |
You can runphp bin/magento indexer:resetto reset the ones stuck on 'processing', then reindex them all (again). That probably won't solve your real problem though.
– Ryan Hoerr
Aug 12 '16 at 3:37
Try reindexing only one of the problematic ones and see if errors display.
– Steve Johnson
Aug 14 '16 at 14:17
@RyanH. I'm getting an err msg 'Command "indexer:reset" is not defined'
– Nikkawat
Aug 15 '16 at 17:10
@SteveJohnson They're still stuck in processing, let's see what Magento forums say
– Nikkawat
Aug 15 '16 at 17:11
You can run
php bin/magento indexer:reset to reset the ones stuck on 'processing', then reindex them all (again). That probably won't solve your real problem though.– Ryan Hoerr
Aug 12 '16 at 3:37
You can run
php bin/magento indexer:reset to reset the ones stuck on 'processing', then reindex them all (again). That probably won't solve your real problem though.– Ryan Hoerr
Aug 12 '16 at 3:37
Try reindexing only one of the problematic ones and see if errors display.
– Steve Johnson
Aug 14 '16 at 14:17
Try reindexing only one of the problematic ones and see if errors display.
– Steve Johnson
Aug 14 '16 at 14:17
@RyanH. I'm getting an err msg 'Command "indexer:reset" is not defined'
– Nikkawat
Aug 15 '16 at 17:10
@RyanH. I'm getting an err msg 'Command "indexer:reset" is not defined'
– Nikkawat
Aug 15 '16 at 17:10
@SteveJohnson They're still stuck in processing, let's see what Magento forums say
– Nikkawat
Aug 15 '16 at 17:11
@SteveJohnson They're still stuck in processing, let's see what Magento forums say
– Nikkawat
Aug 15 '16 at 17:11
add a comment |
4 Answers
4
active
oldest
votes
You can fix this from the command line by reseting the index which will invalidate the state of the index and remove the processing flag from the index.
php bin/magento indexer:reset
Optionally you may also append the index name to the command to just just reset that index.
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
This command doesn't exist in 2.0.4
– jtate
Feb 20 '17 at 14:26
but answer is absolutly right its work for me thanks in 2.1.6
– Sagar Dobariya
Jun 5 '17 at 4:57
add a comment |
unfortunately your only option is to change in the database the state of the processing indexes because till there are processing indexes no other index gets updated and neither the command line works.
update indexer_state set status = 'invalid' where indexer_id = 'catalogsearch_fulltext';
also keep in mind this bug https://github.com/magento/magento2/issues/5146 that might be the cause for your problem
answered Jan 11 '17 at 14:51
springerinspringerin
480511
This is not the only option, index state can be reset from the m2 cli which is more satisfactory than tinkering with tables.
– Christopher Hackett
Jan 25 '17 at 10:41
no, it can't. try and you'll see. but i agree with you, would be best if it worked from cli
– springerin
Jan 25 '17 at 12:56
With indexer:reset (not indexer:reindex)? Works fine for me. I can cause the error situation that causes the reindex to fail and am able to recover to the state of invalidated. I can then re-run the reindex (which without the command would have just been skipped as it was marked as processing) in a situation it will not error and all is fine.
– Christopher Hackett
Jan 25 '17 at 16:02
my bad, i didn't know about indexer:reset. i'll check that out, thanks in case it works :)
– springerin
Jan 25 '17 at 16:28
add a comment |
In Magento 2 indexer states are stored in indexer_state table.
In case in the CLI reset does not work, change the state directly from the table.
If Product Price is stuck for long time, use following. And so on.
update indexer_state set status = 'invalid' where indexer_id = 'catalog_product_price';
answered Apr 26 '18 at 10:48
NahidNahid
490612
add a comment |
Just execute this command "php bin/magento indexer:reset" and it will be all good.
answered 25 mins ago
zuber bandizuber bandi
11914
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "479"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f131133%2findexer-stuck-in-processing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
You can fix this from the command line by reseting the index which will invalidate the state of the index and remove the processing flag from the index.
php bin/magento indexer:reset
Optionally you may also append the index name to the command to just just reset that index.
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
This command doesn't exist in 2.0.4
– jtate
Feb 20 '17 at 14:26
but answer is absolutly right its work for me thanks in 2.1.6
– Sagar Dobariya
Jun 5 '17 at 4:57
add a comment |
You can fix this from the command line by reseting the index which will invalidate the state of the index and remove the processing flag from the index.
php bin/magento indexer:reset
Optionally you may also append the index name to the command to just just reset that index.
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
This command doesn't exist in 2.0.4
– jtate
Feb 20 '17 at 14:26
but answer is absolutly right its work for me thanks in 2.1.6
– Sagar Dobariya
Jun 5 '17 at 4:57
add a comment |
You can fix this from the command line by reseting the index which will invalidate the state of the index and remove the processing flag from the index.
php bin/magento indexer:reset
Optionally you may also append the index name to the command to just just reset that index.
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
You can fix this from the command line by reseting the index which will invalidate the state of the index and remove the processing flag from the index.
php bin/magento indexer:reset
Optionally you may also append the index name to the command to just just reset that index.
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
answered Jan 25 '17 at 10:39
Christopher HackettChristopher Hackett
19313
19313
This command doesn't exist in 2.0.4
– jtate
Feb 20 '17 at 14:26
but answer is absolutly right its work for me thanks in 2.1.6
– Sagar Dobariya
Jun 5 '17 at 4:57
add a comment |
This command doesn't exist in 2.0.4
– jtate
Feb 20 '17 at 14:26
but answer is absolutly right its work for me thanks in 2.1.6
– Sagar Dobariya
Jun 5 '17 at 4:57
This command doesn't exist in 2.0.4
– jtate
Feb 20 '17 at 14:26
This command doesn't exist in 2.0.4
– jtate
Feb 20 '17 at 14:26
but answer is absolutly right its work for me thanks in 2.1.6
– Sagar Dobariya
Jun 5 '17 at 4:57
but answer is absolutly right its work for me thanks in 2.1.6
– Sagar Dobariya
Jun 5 '17 at 4:57
add a comment |
unfortunately your only option is to change in the database the state of the processing indexes because till there are processing indexes no other index gets updated and neither the command line works.
update indexer_state set status = 'invalid' where indexer_id = 'catalogsearch_fulltext';
also keep in mind this bug https://github.com/magento/magento2/issues/5146 that might be the cause for your problem
answered Jan 11 '17 at 14:51
springerinspringerin
480511
This is not the only option, index state can be reset from the m2 cli which is more satisfactory than tinkering with tables.
– Christopher Hackett
Jan 25 '17 at 10:41
no, it can't. try and you'll see. but i agree with you, would be best if it worked from cli
– springerin
Jan 25 '17 at 12:56
With indexer:reset (not indexer:reindex)? Works fine for me. I can cause the error situation that causes the reindex to fail and am able to recover to the state of invalidated. I can then re-run the reindex (which without the command would have just been skipped as it was marked as processing) in a situation it will not error and all is fine.
– Christopher Hackett
Jan 25 '17 at 16:02
my bad, i didn't know about indexer:reset. i'll check that out, thanks in case it works :)
– springerin
Jan 25 '17 at 16:28
add a comment |
unfortunately your only option is to change in the database the state of the processing indexes because till there are processing indexes no other index gets updated and neither the command line works.
update indexer_state set status = 'invalid' where indexer_id = 'catalogsearch_fulltext';
also keep in mind this bug https://github.com/magento/magento2/issues/5146 that might be the cause for your problem
answered Jan 11 '17 at 14:51
springerinspringerin
480511
This is not the only option, index state can be reset from the m2 cli which is more satisfactory than tinkering with tables.
– Christopher Hackett
Jan 25 '17 at 10:41
no, it can't. try and you'll see. but i agree with you, would be best if it worked from cli
– springerin
Jan 25 '17 at 12:56
With indexer:reset (not indexer:reindex)? Works fine for me. I can cause the error situation that causes the reindex to fail and am able to recover to the state of invalidated. I can then re-run the reindex (which without the command would have just been skipped as it was marked as processing) in a situation it will not error and all is fine.
– Christopher Hackett
Jan 25 '17 at 16:02
my bad, i didn't know about indexer:reset. i'll check that out, thanks in case it works :)
– springerin
Jan 25 '17 at 16:28
add a comment |
unfortunately your only option is to change in the database the state of the processing indexes because till there are processing indexes no other index gets updated and neither the command line works.
update indexer_state set status = 'invalid' where indexer_id = 'catalogsearch_fulltext';
also keep in mind this bug https://github.com/magento/magento2/issues/5146 that might be the cause for your problem
answered Jan 11 '17 at 14:51
springerinspringerin
480511
unfortunately your only option is to change in the database the state of the processing indexes because till there are processing indexes no other index gets updated and neither the command line works.
update indexer_state set status = 'invalid' where indexer_id = 'catalogsearch_fulltext';
also keep in mind this bug https://github.com/magento/magento2/issues/5146 that might be the cause for your problem
answered Jan 11 '17 at 14:51
springerinspringerin
480511
answered Jan 11 '17 at 14:51
springerinspringerin
480511
answered Jan 11 '17 at 14:51
springerinspringerin
480511
answered Jan 11 '17 at 14:51
springerinspringerin
480511
480511
This is not the only option, index state can be reset from the m2 cli which is more satisfactory than tinkering with tables.
– Christopher Hackett
Jan 25 '17 at 10:41
no, it can't. try and you'll see. but i agree with you, would be best if it worked from cli
– springerin
Jan 25 '17 at 12:56
With indexer:reset (not indexer:reindex)? Works fine for me. I can cause the error situation that causes the reindex to fail and am able to recover to the state of invalidated. I can then re-run the reindex (which without the command would have just been skipped as it was marked as processing) in a situation it will not error and all is fine.
– Christopher Hackett
Jan 25 '17 at 16:02
my bad, i didn't know about indexer:reset. i'll check that out, thanks in case it works :)
– springerin
Jan 25 '17 at 16:28
add a comment |
This is not the only option, index state can be reset from the m2 cli which is more satisfactory than tinkering with tables.
– Christopher Hackett
Jan 25 '17 at 10:41
no, it can't. try and you'll see. but i agree with you, would be best if it worked from cli
– springerin
Jan 25 '17 at 12:56
With indexer:reset (not indexer:reindex)? Works fine for me. I can cause the error situation that causes the reindex to fail and am able to recover to the state of invalidated. I can then re-run the reindex (which without the command would have just been skipped as it was marked as processing) in a situation it will not error and all is fine.
– Christopher Hackett
Jan 25 '17 at 16:02
my bad, i didn't know about indexer:reset. i'll check that out, thanks in case it works :)
– springerin
Jan 25 '17 at 16:28
This is not the only option, index state can be reset from the m2 cli which is more satisfactory than tinkering with tables.
– Christopher Hackett
Jan 25 '17 at 10:41
This is not the only option, index state can be reset from the m2 cli which is more satisfactory than tinkering with tables.
– Christopher Hackett
Jan 25 '17 at 10:41
no, it can't. try and you'll see. but i agree with you, would be best if it worked from cli
– springerin
Jan 25 '17 at 12:56
no, it can't. try and you'll see. but i agree with you, would be best if it worked from cli
– springerin
Jan 25 '17 at 12:56
With indexer:reset (not indexer:reindex)? Works fine for me. I can cause the error situation that causes the reindex to fail and am able to recover to the state of invalidated. I can then re-run the reindex (which without the command would have just been skipped as it was marked as processing) in a situation it will not error and all is fine.
– Christopher Hackett
Jan 25 '17 at 16:02
With indexer:reset (not indexer:reindex)? Works fine for me. I can cause the error situation that causes the reindex to fail and am able to recover to the state of invalidated. I can then re-run the reindex (which without the command would have just been skipped as it was marked as processing) in a situation it will not error and all is fine.
– Christopher Hackett
Jan 25 '17 at 16:02
my bad, i didn't know about indexer:reset. i'll check that out, thanks in case it works :)
– springerin
Jan 25 '17 at 16:28
my bad, i didn't know about indexer:reset. i'll check that out, thanks in case it works :)
– springerin
Jan 25 '17 at 16:28
add a comment |
In Magento 2 indexer states are stored in indexer_state table.
In case in the CLI reset does not work, change the state directly from the table.
If Product Price is stuck for long time, use following. And so on.
update indexer_state set status = 'invalid' where indexer_id = 'catalog_product_price';
answered Apr 26 '18 at 10:48
NahidNahid
490612
add a comment |
In Magento 2 indexer states are stored in indexer_state table.
In case in the CLI reset does not work, change the state directly from the table.
If Product Price is stuck for long time, use following. And so on.
update indexer_state set status = 'invalid' where indexer_id = 'catalog_product_price';
answered Apr 26 '18 at 10:48
NahidNahid
490612
add a comment |
In Magento 2 indexer states are stored in indexer_state table.
In case in the CLI reset does not work, change the state directly from the table.
If Product Price is stuck for long time, use following. And so on.
update indexer_state set status = 'invalid' where indexer_id = 'catalog_product_price';
answered Apr 26 '18 at 10:48
NahidNahid
490612
In Magento 2 indexer states are stored in indexer_state table.
In case in the CLI reset does not work, change the state directly from the table.
If Product Price is stuck for long time, use following. And so on.
update indexer_state set status = 'invalid' where indexer_id = 'catalog_product_price';
answered Apr 26 '18 at 10:48
NahidNahid
490612
answered Apr 26 '18 at 10:48
NahidNahid
490612
answered Apr 26 '18 at 10:48
NahidNahid
490612
answered Apr 26 '18 at 10:48
NahidNahid
490612
490612
add a comment |
add a comment |
Just execute this command "php bin/magento indexer:reset" and it will be all good.
answered 25 mins ago
zuber bandizuber bandi
11914
add a comment |
Just execute this command "php bin/magento indexer:reset" and it will be all good.
answered 25 mins ago
zuber bandizuber bandi
11914
add a comment |
Just execute this command "php bin/magento indexer:reset" and it will be all good.
answered 25 mins ago
zuber bandizuber bandi
11914
Just execute this command "php bin/magento indexer:reset" and it will be all good.
answered 25 mins ago
zuber bandizuber bandi
11914
edited 9 mins ago
answered 25 mins ago
zuber bandizuber bandi
11914
answered 25 mins ago
zuber bandizuber bandi
11914
answered 25 mins ago
zuber bandizuber bandi
11914
11914
add a comment |
add a comment |
Thanks for contributing an answer to Magento Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fmagento.stackexchange.com%2fquestions%2f131133%2findexer-stuck-in-processing%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
var $window = $(window),
onScroll = function(e) {
var $elem = $('.new-login-left'),
docViewTop = $window.scrollTop(),
docViewBottom = docViewTop + $window.height(),
elemTop = $elem.offset().top,
elemBottom = elemTop + $elem.height();
if ((docViewTop elemBottom)) {
StackExchange.using('gps', function() { StackExchange.gps.track('embedded_signup_form.view', { location: 'question_page' }); });
$window.unbind('scroll', onScroll);
}
};
$window.on('scroll', onScroll);
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You can run
php bin/magento indexer:resetto reset the ones stuck on 'processing', then reindex them all (again). That probably won't solve your real problem though.– Ryan Hoerr
Aug 12 '16 at 3:37
Try reindexing only one of the problematic ones and see if errors display.
– Steve Johnson
Aug 14 '16 at 14:17
@RyanH. I'm getting an err msg 'Command "indexer:reset" is not defined'
– Nikkawat
Aug 15 '16 at 17:10
@SteveJohnson They're still stuck in processing, let's see what Magento forums say
– Nikkawat
Aug 15 '16 at 17:11