I am performing some reindexing manually in my store, and I have noticed that another reindexation is executed in another index without having placed it in the command.
I would like to know why this happens, or how to prevent magento from doing it.
enter image description here
As you can see in the image, I ran the reindex of the "cataloginventory_stock" index, but when the reindexing was finished, Magento ran another reindex on the "catalogsearch_fulltext" index without authorization
I consulted the magento guide, and the command that I am executing has the correct syntax
Related
Been having some problems reindexing in a new install of Magento 1.9.1.0. I have been re-indexing from admin and from shell. Both seem to reindex successfully but the admin screen immediatley returns to 'reindex required'. I have checked to see if var/locks exists, and it doesn't.
Our data was migrated from a Magento 1.8. All the attributes migrated with the prefix 'c2c_' which meant that some of the attribute names were too long. We manually edited these in the database to remove the 'c2c_' Could this be the problem?
Any pointers would be appreciated.
I am running Magento 1.8.1 with embeddedERP extension.
Not sure if extension is to blame for the behaviour, i don't think so as it seemed to work fine for a while after I installed the extension. The issue appears to relate to indexing.
I reindexed the site in response to a magento index aler. When I try to view products in the backend the page is blank but only from from the horizontal line below the Add New product button, there is no list of products but also no products table at all, rather than the products table with no rows one would expect.
I have tried deleting cache and session folders.
I've tried disabling cache.
I enabled logging and there isn't an exceptions.log file so presuming this means no exceptions happening.
I've logged in and out.
On one occasion when i tried creating a new product after saving it it displayed the products (new one and existing) but now that doesn't work either.
Previously, deleting session and cache and logging back in appeared to work but now doesn't.
Can anyone suggest how I can go about working out what is wrong. My magento debugging skills probably need some enhancing.
Thanks,
Came back to this and the site was then displaying an error:
Warning: Unknown: Unable to allocate memory for pool in [filepath]/Autoload.php
This thread:
http://www.magentocommerce.com/boards%20/viewthread/216180/#t462005
highlighted this is as an apc issue.
Altering the memory size to 256M as suggested solved this.
Hope this helps if anyone else gets this, still don't know why this issue showed a blank screen to start with, perhaps an APC caching issue?
My catalog URL has not run for over a month. I have tried running in both from Magento and the command line.
When running from Magento it times out on the front end but when I go back to it I can see that it is processing.
When running from the command line I can see in Magento it says processing and the command line also tells me that it has successfully rebuild the index.
However, after doing these several times Magento is still telling me that the Catalog URL Rewrites index was last run on 20/4/13.
Any ideas what the problem could be?
I would try the following 2 steps after taking a full file system & database backup of your site.
Repair your Magento database: http://www.magentocommerce.com/wiki/1_-_installation_and_configuration/db-repair-tool
Rebuild your Magento index from the command line: http://www.atwix.com/magento/process-magento-indexes-from-command-line/
This is really strange. Some of the products from the catalog gives 404 error, even if targeted directly.
The product can be seen in admin and is enabled with stock set. I checked the URL rewrite section but couldn't find anything. Also, tried reindexing everything, but couldn't resolve the issue. Even flushed the cache still nothing.
After searching the issue, I found a solution saying running an SQL command. I did that but it said the entry already exists.
Even when I search the product in catalog, nothing returns. The item is there but its just redundant and not showing.
You can check that the product is...
Assigned to a website
Inventory level is above 0 and status is in stock
Enabled
Visible in catalog/search
I have highlighted point 1 as it does tend to catch people out in a multi store environment.
Also, you may need to reindex/clear cache etc.
Finally, double check you are using the correct suffix if relevant i.e. you may have to add .html to the url.
Make sure that your product's status is 'Enabled'.
Re-indexing may help you to resolved the issue.
Go to admin panel System > Index Management. Here select all and do re-indexing. After doing re-indexing try to clear your magento cache and check.
I've imported 6K categories and 16K products to magento using a custom import profile.
When I'm trying to reindex everything works except for 'Catalog URL Rewrites' that keep showing PROCESSING but never completes.
log and exceptions files don't show anything.
Is there something I can do to make the index work?
Can I just ignore this index and not use it? (I don't know what it does).
Thanks
You can sort of ignore this index if you do not care about pretty, search engine "friendly" URL's. The products will still appear in the catalog but will have their default "Zend Framework" type URL (/catalog/product/view/id/123)
My store has 150,000+ SKUs in two store views. On my development environment it took almost two weeks to complete.
The best way to determine how fast it is running is to look at the core_url_rewrite database table. It appears that the process starts at product ID 1 in store ID 1 and looks to make sure all of its URLs exist and creates the ones that do not yet exist.
For me the reason it took so long was that it had to go through my entire catalog twice to make all the URLs. One thing I did notice was that this process creates a ton of URLs that are completely unnecessary. In our store easily 90% of our products belong to a configurable product so their visibility is set to "Not Visible Individually" so they never would need to have a URL. This index creates those URLs anyways.
Hopefully this will shed some light on to how this URL works. I would keep an eye on that database table so you sorta know how far the process has come. I would also seriously consider running the reindex process for the command line. I have included a link that explains how to do this (disclosure: it's from my blog)
http://overlycaffeinated.com/2011/02/when-reindexing-in-magento-fails-use-the-command-line/
My own attempt of reindexing URL rewrites was with 10,000 products and it took me like an Hour and Half to finish up.
this link will help you do it from Command Line , which is preferable than doing it from the same Magento admin panel.
http://www.yireo.com/tutorials/magento/magento-administration/340-magento-14-cronjobs
Make sure you read the part about skipping some basic configuration when facing memory limits , this is the one i usually use.
You need catalog URL rewrites to make your catalog work properly. How long are you letting it run for? There's a really substantial amount of data to be written to it...
If you cannot make it work programmatically, it may be possible to shove the data into the table manually and force the index to feel refreshed? Caveat emptor, I have not tried this.
I was encountering the same problem, the server that I am running this on is a FreeBSD server. With the help of the sample of the above code I was able to get the issue to resolve buy running the following command in the shell.
/usr/local/bin/php /usr/local/www/magento/shell/indexer.php --reindex catalog_url
It runs very quickly and resolved my issue. I then created a cron for this to run every 6 hours on my server.
You can reindex using command line it will reduce 75% of load and your magento admin panel working as normal while reindexing.