Is there a way to stop a magento indexer process?
I've searched similar topics but no solution seems to work. Is there a way to stop a specific magento indexer process?
When I try to reindex from shell I get this:
php -f indexer.php reindex all
Stock Status Index process is working now. Please try run this process later.
Product Prices Index process is working now. Please try run this process later.
Catalog URL Rewrites Index process is working now. Please try run this process later.
Product Flat Data Index process is working now. Please try run this process later.
Category Flat Data Index process is working now. Please try run this process later.
Category Products Index process is working now. Please try run this process later.
Catalog Search Index Index process is working now. Please try run this process later.
Stock Status index was rebuilt successfully
Tag Aggregation Data Index process is working now. Please try run this process later.
When I try to see indexer status I get this:
Product Attributes: Pending
Product Prices: Pending
Catalog URL Rewrites: Pending
Product Flat Data: Pending
Category Flat Data: Pending
Category Products: Pending
Catalog Search Index: Pending
Stock Status: Pending
Tag Aggregation Data: Pending
If I reindex from the admin, reindexing process throws no errors. Is there a link to some documentation on this matter?
Thanks,
Radu
magento
asked Mar 29 '12 at 11:50
RaduRadu
63321431
add a comment |
I've searched similar topics but no solution seems to work. Is there a way to stop a specific magento indexer process?
When I try to reindex from shell I get this:
php -f indexer.php reindex all
Stock Status Index process is working now. Please try run this process later.
Product Prices Index process is working now. Please try run this process later.
Catalog URL Rewrites Index process is working now. Please try run this process later.
Product Flat Data Index process is working now. Please try run this process later.
Category Flat Data Index process is working now. Please try run this process later.
Category Products Index process is working now. Please try run this process later.
Catalog Search Index Index process is working now. Please try run this process later.
Stock Status index was rebuilt successfully
Tag Aggregation Data Index process is working now. Please try run this process later.
When I try to see indexer status I get this:
Product Attributes: Pending
Product Prices: Pending
Catalog URL Rewrites: Pending
Product Flat Data: Pending
Category Flat Data: Pending
Category Products: Pending
Catalog Search Index: Pending
Stock Status: Pending
Tag Aggregation Data: Pending
If I reindex from the admin, reindexing process throws no errors. Is there a link to some documentation on this matter?
Thanks,
Radu
magento
asked Mar 29 '12 at 11:50
RaduRadu
63321431
add a comment |
I've searched similar topics but no solution seems to work. Is there a way to stop a specific magento indexer process?
When I try to reindex from shell I get this:
php -f indexer.php reindex all
Stock Status Index process is working now. Please try run this process later.
Product Prices Index process is working now. Please try run this process later.
Catalog URL Rewrites Index process is working now. Please try run this process later.
Product Flat Data Index process is working now. Please try run this process later.
Category Flat Data Index process is working now. Please try run this process later.
Category Products Index process is working now. Please try run this process later.
Catalog Search Index Index process is working now. Please try run this process later.
Stock Status index was rebuilt successfully
Tag Aggregation Data Index process is working now. Please try run this process later.
When I try to see indexer status I get this:
Product Attributes: Pending
Product Prices: Pending
Catalog URL Rewrites: Pending
Product Flat Data: Pending
Category Flat Data: Pending
Category Products: Pending
Catalog Search Index: Pending
Stock Status: Pending
Tag Aggregation Data: Pending
If I reindex from the admin, reindexing process throws no errors. Is there a link to some documentation on this matter?
Thanks,
Radu
magento
asked Mar 29 '12 at 11:50
RaduRadu
63321431
I've searched similar topics but no solution seems to work. Is there a way to stop a specific magento indexer process?
When I try to reindex from shell I get this:
php -f indexer.php reindex all
Stock Status Index process is working now. Please try run this process later.
Product Prices Index process is working now. Please try run this process later.
Catalog URL Rewrites Index process is working now. Please try run this process later.
Product Flat Data Index process is working now. Please try run this process later.
Category Flat Data Index process is working now. Please try run this process later.
Category Products Index process is working now. Please try run this process later.
Catalog Search Index Index process is working now. Please try run this process later.
Stock Status index was rebuilt successfully
Tag Aggregation Data Index process is working now. Please try run this process later.
When I try to see indexer status I get this:
Product Attributes: Pending
Product Prices: Pending
Catalog URL Rewrites: Pending
Product Flat Data: Pending
Category Flat Data: Pending
Category Products: Pending
Catalog Search Index: Pending
Stock Status: Pending
Tag Aggregation Data: Pending
If I reindex from the admin, reindexing process throws no errors. Is there a link to some documentation on this matter?
Thanks,
Radu
magento
magento
asked Mar 29 '12 at 11:50
RaduRadu
63321431
asked Mar 29 '12 at 11:50
RaduRadu
63321431
asked Mar 29 '12 at 11:50
RaduRadu
63321431
asked Mar 29 '12 at 11:50
RaduRadu
63321431
asked Mar 29 '12 at 11:50
RaduRadu
63321431
63321431
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
Indexing mostly (mostly meaning I'm pretty sure it's always) happens during a single HTTP request. If that request stop/timeouts/fails because of a PHP error, the indexer leaves lock files lying around even though there's no indexing going on. These files are located in
/path/to/mage/var/locks/index_process*.lock
The
Index process is working now. Please try run this process later
exception is Magento telling you it sees one of these lock files. If you know for sure no one else is trying to run an index, just delete the files and restart your indexing.
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
1
I consulttopand if it doesn't show an lsphp5 session (LiteSpeed WS) clocking out at a fairly high rate and quite continuously, then I know that no index process is actually running. The next step is to delete the lock files and run via command line separately each reindex to make sure that all run to completion by avoiding resource exhaustion and prematurely failed sessions. It pays totopduring various Magento operations so you know what's normal processor usage, then this becomes an easy diagnosis.
– Fiasco Labs
Mar 30 '12 at 1:08
1
Alan if you can please put some light on indexing process of magento.I started an indexing process (catalog search index) and it got stopped by closing browser. now ideally it should also terminate php process behind it but when i check mysql processlist ouptut it was suggesting that magento is still indexing in background the indexing was still running in background got confirmed when i saw that solr document were also updating. i didnt understand how magento manage to keep process running.the site is on staging so nobody else were initiating index either from shell or browser.
– anshuman
Oct 31 '12 at 10:26
There is NO locks folder in this path/path/to/mage/var/
– Pratik C Joshi
Oct 6 '15 at 6:03
add a comment |
First, try to set the index mode to manual:
php indexer.php --mode-manual catalog_product_attribute
php indexer.php --mode-manual catalog_product_price
php indexer.php --mode-manual catalog_url
php indexer.php --mode-manual catalog_product_flat
php indexer.php --mode-manual catalog_category_flat
php indexer.php --mode-manual catalog_category_product
php indexer.php --mode-manual catalogsearch_fulltext
php indexer.php --mode-manual cataloginventory_stock
php indexer.php --mode-manual tag_summary
Then, try to reindex all indexes:
php indexer.php reindexall
And set the mode to realtime again:
php indexer.php --mode-realtime catalog_product_attribute
php indexer.php --mode-realtime catalog_product_price
php indexer.php --mode-realtime catalog_url
php indexer.php --mode-realtime catalog_product_flat
php indexer.php --mode-realtime catalog_category_flat
php indexer.php --mode-realtime catalog_category_product
php indexer.php --mode-realtime catalogsearch_fulltext
php indexer.php --mode-realtime cataloginventory_stock
php indexer.php --mode-realtime tag_summary
If this does not work, try to restart apache with something like sudo /etc/init.d/apache2 restart. This should stop the indexing process and you can probably start it again afterwards. But mind that your site will not be available for a few seconds if you restart Apache.
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
Restarting Apache didn't help either.
– Mike
May 13 '15 at 17:41
add a comment |
In the latest versions the lock files has been changed and working from database(Magento 1.9).
Login to your phpMyAdmin, and run the below command.
UPDATE index_process SET status = 'pending' WHERE status = 'working'
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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');
});
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%2fstackoverflow.com%2fquestions%2f9924756%2fis-there-a-way-to-stop-a-magento-indexer-process%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Indexing mostly (mostly meaning I'm pretty sure it's always) happens during a single HTTP request. If that request stop/timeouts/fails because of a PHP error, the indexer leaves lock files lying around even though there's no indexing going on. These files are located in
/path/to/mage/var/locks/index_process*.lock
The
Index process is working now. Please try run this process later
exception is Magento telling you it sees one of these lock files. If you know for sure no one else is trying to run an index, just delete the files and restart your indexing.
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
1
I consulttopand if it doesn't show an lsphp5 session (LiteSpeed WS) clocking out at a fairly high rate and quite continuously, then I know that no index process is actually running. The next step is to delete the lock files and run via command line separately each reindex to make sure that all run to completion by avoiding resource exhaustion and prematurely failed sessions. It pays totopduring various Magento operations so you know what's normal processor usage, then this becomes an easy diagnosis.
– Fiasco Labs
Mar 30 '12 at 1:08
1
Alan if you can please put some light on indexing process of magento.I started an indexing process (catalog search index) and it got stopped by closing browser. now ideally it should also terminate php process behind it but when i check mysql processlist ouptut it was suggesting that magento is still indexing in background the indexing was still running in background got confirmed when i saw that solr document were also updating. i didnt understand how magento manage to keep process running.the site is on staging so nobody else were initiating index either from shell or browser.
– anshuman
Oct 31 '12 at 10:26
There is NO locks folder in this path/path/to/mage/var/
– Pratik C Joshi
Oct 6 '15 at 6:03
add a comment |
Indexing mostly (mostly meaning I'm pretty sure it's always) happens during a single HTTP request. If that request stop/timeouts/fails because of a PHP error, the indexer leaves lock files lying around even though there's no indexing going on. These files are located in
/path/to/mage/var/locks/index_process*.lock
The
Index process is working now. Please try run this process later
exception is Magento telling you it sees one of these lock files. If you know for sure no one else is trying to run an index, just delete the files and restart your indexing.
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
1
I consulttopand if it doesn't show an lsphp5 session (LiteSpeed WS) clocking out at a fairly high rate and quite continuously, then I know that no index process is actually running. The next step is to delete the lock files and run via command line separately each reindex to make sure that all run to completion by avoiding resource exhaustion and prematurely failed sessions. It pays totopduring various Magento operations so you know what's normal processor usage, then this becomes an easy diagnosis.
– Fiasco Labs
Mar 30 '12 at 1:08
1
Alan if you can please put some light on indexing process of magento.I started an indexing process (catalog search index) and it got stopped by closing browser. now ideally it should also terminate php process behind it but when i check mysql processlist ouptut it was suggesting that magento is still indexing in background the indexing was still running in background got confirmed when i saw that solr document were also updating. i didnt understand how magento manage to keep process running.the site is on staging so nobody else were initiating index either from shell or browser.
– anshuman
Oct 31 '12 at 10:26
There is NO locks folder in this path/path/to/mage/var/
– Pratik C Joshi
Oct 6 '15 at 6:03
add a comment |
Indexing mostly (mostly meaning I'm pretty sure it's always) happens during a single HTTP request. If that request stop/timeouts/fails because of a PHP error, the indexer leaves lock files lying around even though there's no indexing going on. These files are located in
/path/to/mage/var/locks/index_process*.lock
The
Index process is working now. Please try run this process later
exception is Magento telling you it sees one of these lock files. If you know for sure no one else is trying to run an index, just delete the files and restart your indexing.
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
Indexing mostly (mostly meaning I'm pretty sure it's always) happens during a single HTTP request. If that request stop/timeouts/fails because of a PHP error, the indexer leaves lock files lying around even though there's no indexing going on. These files are located in
/path/to/mage/var/locks/index_process*.lock
The
Index process is working now. Please try run this process later
exception is Magento telling you it sees one of these lock files. If you know for sure no one else is trying to run an index, just delete the files and restart your indexing.
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
edited May 13 '15 at 20:30
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
answered Mar 29 '12 at 19:55
Alan StormAlan Storm
129k70330506
129k70330506
1
I consulttopand if it doesn't show an lsphp5 session (LiteSpeed WS) clocking out at a fairly high rate and quite continuously, then I know that no index process is actually running. The next step is to delete the lock files and run via command line separately each reindex to make sure that all run to completion by avoiding resource exhaustion and prematurely failed sessions. It pays totopduring various Magento operations so you know what's normal processor usage, then this becomes an easy diagnosis.
– Fiasco Labs
Mar 30 '12 at 1:08
1
Alan if you can please put some light on indexing process of magento.I started an indexing process (catalog search index) and it got stopped by closing browser. now ideally it should also terminate php process behind it but when i check mysql processlist ouptut it was suggesting that magento is still indexing in background the indexing was still running in background got confirmed when i saw that solr document were also updating. i didnt understand how magento manage to keep process running.the site is on staging so nobody else were initiating index either from shell or browser.
– anshuman
Oct 31 '12 at 10:26
There is NO locks folder in this path/path/to/mage/var/
– Pratik C Joshi
Oct 6 '15 at 6:03
add a comment |
1
I consulttopand if it doesn't show an lsphp5 session (LiteSpeed WS) clocking out at a fairly high rate and quite continuously, then I know that no index process is actually running. The next step is to delete the lock files and run via command line separately each reindex to make sure that all run to completion by avoiding resource exhaustion and prematurely failed sessions. It pays totopduring various Magento operations so you know what's normal processor usage, then this becomes an easy diagnosis.
– Fiasco Labs
Mar 30 '12 at 1:08
1
Alan if you can please put some light on indexing process of magento.I started an indexing process (catalog search index) and it got stopped by closing browser. now ideally it should also terminate php process behind it but when i check mysql processlist ouptut it was suggesting that magento is still indexing in background the indexing was still running in background got confirmed when i saw that solr document were also updating. i didnt understand how magento manage to keep process running.the site is on staging so nobody else were initiating index either from shell or browser.
– anshuman
Oct 31 '12 at 10:26
There is NO locks folder in this path/path/to/mage/var/
– Pratik C Joshi
Oct 6 '15 at 6:03
1
1
I consult
top and if it doesn't show an lsphp5 session (LiteSpeed WS) clocking out at a fairly high rate and quite continuously, then I know that no index process is actually running. The next step is to delete the lock files and run via command line separately each reindex to make sure that all run to completion by avoiding resource exhaustion and prematurely failed sessions. It pays to top during various Magento operations so you know what's normal processor usage, then this becomes an easy diagnosis.– Fiasco Labs
Mar 30 '12 at 1:08
I consult
top and if it doesn't show an lsphp5 session (LiteSpeed WS) clocking out at a fairly high rate and quite continuously, then I know that no index process is actually running. The next step is to delete the lock files and run via command line separately each reindex to make sure that all run to completion by avoiding resource exhaustion and prematurely failed sessions. It pays to top during various Magento operations so you know what's normal processor usage, then this becomes an easy diagnosis.– Fiasco Labs
Mar 30 '12 at 1:08
1
1
Alan if you can please put some light on indexing process of magento.I started an indexing process (catalog search index) and it got stopped by closing browser. now ideally it should also terminate php process behind it but when i check mysql processlist ouptut it was suggesting that magento is still indexing in background the indexing was still running in background got confirmed when i saw that solr document were also updating. i didnt understand how magento manage to keep process running.the site is on staging so nobody else were initiating index either from shell or browser.
– anshuman
Oct 31 '12 at 10:26
Alan if you can please put some light on indexing process of magento.I started an indexing process (catalog search index) and it got stopped by closing browser. now ideally it should also terminate php process behind it but when i check mysql processlist ouptut it was suggesting that magento is still indexing in background the indexing was still running in background got confirmed when i saw that solr document were also updating. i didnt understand how magento manage to keep process running.the site is on staging so nobody else were initiating index either from shell or browser.
– anshuman
Oct 31 '12 at 10:26
There is NO locks folder in this path
/path/to/mage/var/– Pratik C Joshi
Oct 6 '15 at 6:03
There is NO locks folder in this path
/path/to/mage/var/– Pratik C Joshi
Oct 6 '15 at 6:03
add a comment |
First, try to set the index mode to manual:
php indexer.php --mode-manual catalog_product_attribute
php indexer.php --mode-manual catalog_product_price
php indexer.php --mode-manual catalog_url
php indexer.php --mode-manual catalog_product_flat
php indexer.php --mode-manual catalog_category_flat
php indexer.php --mode-manual catalog_category_product
php indexer.php --mode-manual catalogsearch_fulltext
php indexer.php --mode-manual cataloginventory_stock
php indexer.php --mode-manual tag_summary
Then, try to reindex all indexes:
php indexer.php reindexall
And set the mode to realtime again:
php indexer.php --mode-realtime catalog_product_attribute
php indexer.php --mode-realtime catalog_product_price
php indexer.php --mode-realtime catalog_url
php indexer.php --mode-realtime catalog_product_flat
php indexer.php --mode-realtime catalog_category_flat
php indexer.php --mode-realtime catalog_category_product
php indexer.php --mode-realtime catalogsearch_fulltext
php indexer.php --mode-realtime cataloginventory_stock
php indexer.php --mode-realtime tag_summary
If this does not work, try to restart apache with something like sudo /etc/init.d/apache2 restart. This should stop the indexing process and you can probably start it again afterwards. But mind that your site will not be available for a few seconds if you restart Apache.
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
Restarting Apache didn't help either.
– Mike
May 13 '15 at 17:41
add a comment |
First, try to set the index mode to manual:
php indexer.php --mode-manual catalog_product_attribute
php indexer.php --mode-manual catalog_product_price
php indexer.php --mode-manual catalog_url
php indexer.php --mode-manual catalog_product_flat
php indexer.php --mode-manual catalog_category_flat
php indexer.php --mode-manual catalog_category_product
php indexer.php --mode-manual catalogsearch_fulltext
php indexer.php --mode-manual cataloginventory_stock
php indexer.php --mode-manual tag_summary
Then, try to reindex all indexes:
php indexer.php reindexall
And set the mode to realtime again:
php indexer.php --mode-realtime catalog_product_attribute
php indexer.php --mode-realtime catalog_product_price
php indexer.php --mode-realtime catalog_url
php indexer.php --mode-realtime catalog_product_flat
php indexer.php --mode-realtime catalog_category_flat
php indexer.php --mode-realtime catalog_category_product
php indexer.php --mode-realtime catalogsearch_fulltext
php indexer.php --mode-realtime cataloginventory_stock
php indexer.php --mode-realtime tag_summary
If this does not work, try to restart apache with something like sudo /etc/init.d/apache2 restart. This should stop the indexing process and you can probably start it again afterwards. But mind that your site will not be available for a few seconds if you restart Apache.
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
Restarting Apache didn't help either.
– Mike
May 13 '15 at 17:41
add a comment |
First, try to set the index mode to manual:
php indexer.php --mode-manual catalog_product_attribute
php indexer.php --mode-manual catalog_product_price
php indexer.php --mode-manual catalog_url
php indexer.php --mode-manual catalog_product_flat
php indexer.php --mode-manual catalog_category_flat
php indexer.php --mode-manual catalog_category_product
php indexer.php --mode-manual catalogsearch_fulltext
php indexer.php --mode-manual cataloginventory_stock
php indexer.php --mode-manual tag_summary
Then, try to reindex all indexes:
php indexer.php reindexall
And set the mode to realtime again:
php indexer.php --mode-realtime catalog_product_attribute
php indexer.php --mode-realtime catalog_product_price
php indexer.php --mode-realtime catalog_url
php indexer.php --mode-realtime catalog_product_flat
php indexer.php --mode-realtime catalog_category_flat
php indexer.php --mode-realtime catalog_category_product
php indexer.php --mode-realtime catalogsearch_fulltext
php indexer.php --mode-realtime cataloginventory_stock
php indexer.php --mode-realtime tag_summary
If this does not work, try to restart apache with something like sudo /etc/init.d/apache2 restart. This should stop the indexing process and you can probably start it again afterwards. But mind that your site will not be available for a few seconds if you restart Apache.
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
First, try to set the index mode to manual:
php indexer.php --mode-manual catalog_product_attribute
php indexer.php --mode-manual catalog_product_price
php indexer.php --mode-manual catalog_url
php indexer.php --mode-manual catalog_product_flat
php indexer.php --mode-manual catalog_category_flat
php indexer.php --mode-manual catalog_category_product
php indexer.php --mode-manual catalogsearch_fulltext
php indexer.php --mode-manual cataloginventory_stock
php indexer.php --mode-manual tag_summary
Then, try to reindex all indexes:
php indexer.php reindexall
And set the mode to realtime again:
php indexer.php --mode-realtime catalog_product_attribute
php indexer.php --mode-realtime catalog_product_price
php indexer.php --mode-realtime catalog_url
php indexer.php --mode-realtime catalog_product_flat
php indexer.php --mode-realtime catalog_category_flat
php indexer.php --mode-realtime catalog_category_product
php indexer.php --mode-realtime catalogsearch_fulltext
php indexer.php --mode-realtime cataloginventory_stock
php indexer.php --mode-realtime tag_summary
If this does not work, try to restart apache with something like sudo /etc/init.d/apache2 restart. This should stop the indexing process and you can probably start it again afterwards. But mind that your site will not be available for a few seconds if you restart Apache.
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
edited Mar 29 '12 at 14:35
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
answered Mar 29 '12 at 13:11
SimonSimon
2,79661947
2,79661947
Restarting Apache didn't help either.
– Mike
May 13 '15 at 17:41
add a comment |
Restarting Apache didn't help either.
– Mike
May 13 '15 at 17:41
Restarting Apache didn't help either.
– Mike
May 13 '15 at 17:41
Restarting Apache didn't help either.
– Mike
May 13 '15 at 17:41
add a comment |
In the latest versions the lock files has been changed and working from database(Magento 1.9).
Login to your phpMyAdmin, and run the below command.
UPDATE index_process SET status = 'pending' WHERE status = 'working'
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
add a comment |
In the latest versions the lock files has been changed and working from database(Magento 1.9).
Login to your phpMyAdmin, and run the below command.
UPDATE index_process SET status = 'pending' WHERE status = 'working'
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
add a comment |
In the latest versions the lock files has been changed and working from database(Magento 1.9).
Login to your phpMyAdmin, and run the below command.
UPDATE index_process SET status = 'pending' WHERE status = 'working'
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
In the latest versions the lock files has been changed and working from database(Magento 1.9).
Login to your phpMyAdmin, and run the below command.
UPDATE index_process SET status = 'pending' WHERE status = 'working'
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
edited Oct 9 '18 at 11:58
Alex
15.2k1172114
15.2k1172114
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
answered Sep 28 '16 at 4:15
Rinto GeorgeRinto George
18.9k83861
18.9k83861
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- 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');
});
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%2fstackoverflow.com%2fquestions%2f9924756%2fis-there-a-way-to-stop-a-magento-indexer-process%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');
});
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');
});
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');
});
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
