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/
Related
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
A friend of mine who running e-commerce website using Magento 2 platform. She set price attribute on her products and now she wants to change the price. She is able to find the attribute input field and changed the price and then saved and cashed out, but it doesn't update frontend, and there is no any error show either.
I'm pretty new to Magento 2 and wondering any body has any idea what is going on?
You must flush storage cache then run this command (from the root of magento's directory) line to get the change applied :
$ php bin/magento indexer:reindex
Let me know if you still face the problem then.
If you cannot ssh to server, you can go to admin System->Tools->Index Management to Re
I upgraded my Multi-store magento from 1.7 to 1.9.2.2.
On frontend CMS , Categories etc are working fine. but product detail pages giving 404 error.
I reindexed all indexes.
refresh all caches but still same.
Can anyone help?
It sounds like the URL rewrite is to blame. You may want to run the indexes via command line.
SSH Into the server and cd into the directory that has your magento code then use this command to run the indexes
php shell/indexer.php --reindexall
You may also want to clear you caches, and check the server logs for some hints.
404 is most certainly the URL rewrite causing the problem, so running the indexes via command line should fix that for you.
I have a situation where I had to restore my magento site from an FTP backup which I made earlier of all the files and folders of the public_html directory. Note that I don't have a mySql backup.
Now when I try to visit my www.domainname.com site, it just displays an error number. Note that I can no longer go to www.domainname.com/admin. I do not know how to enable debug logging so I can see what the error number is trying to tell me. However, I can go to my hostgator.com control panel and click on the error logs, but there are no entries.
My question is: is there any way I can salvage the original site, minus the database? I'm okay with having to re-enter products, etc., that I once had into the database.
Thanks in advance.
The site is 85% the database. No database backup, no site.
You must backup both your public_html files and your Magento database to fully back up your Magento e-commerce installation.
Basically all you have is the application, code changes, skin and templates from the previous version.
Configuration, CMS pages, categories, product and all the rest live in the database.
The error number displayed is the file name of a stack trace that ends up in var/report. It's probably telling you that no database exists at this point.
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.