|
|
 |
 |
Joined: 2/2/2012
Posts: 278
|
|
|
Hello -
I am currently running Smith Cart version 5.17 on my development site of temp.yandasmusic.com to make sure the upgrade is functioning properly before I go live with it.
I installed the upgraded module about a week ago, and since then, my hosting provided has had to take my temp site down several times for the following reasons:
"Essentially, something on the site was continually running which ran up records in the eventlog table. This made the database size balloon to over 26 G in a couple days. Also, it was using all the free memory of the processor and causing our server to crash."
Is anyone aware of a situation with Smith Cart that could cause this? I am running a live version of that same temp site, the only difference between them being the smith cart version and some page updates, and it runs smoothly.
Thanks - Alex
|
|
|
|
 | |
|
|
 |
Joined: 1/1/0001
Posts: 0
|
|
|
Hi Alex,
I haven't seen this reported before.
Which version of DNN are you currently running?
Could you also please specify the records which are being logged in the eventlog table?
Thanks
|
|
|
|
| |
|
|
|
|
Joined: 2/2/2012
Posts: 278
|
|
|
I am running DNN 06.02.02
I'll get you that info asap Kevin -
We're running some more tests to confirm if Smith Cart is really causing the issue. I'll keep you posted.
|
|
|
|
| |
|
|
|
|
Joined: 2/2/2012
Posts: 278
|
|
|
Ok Kevin,
We reloaded the site back to a stable version. The site was running perfectly normal on Smith Cart Version 5.17.
My store is running 42 unique buy now modules. I shared each product so they would all be available to the search module. I then purchased the Smith.Search module, and added the search module to each one of my pages.
I then tried to do a search on the site, and the site EXPLODED! I have attached screenshots provided to me by my hosting provider showing the search module literally taking up all the ram their servers and our database balooning after the search query.
We are restoring the site from a backup, and I am removing all search functionality from the site, so that we can still use it. Can you look into this issue? It's hard for us to test on our servers, because it's literally crippling them. I reallly REALLY want to have search functionality on this site. I hope we can find an alternative or a fix!
Thanks - Alex
EDIT:
For some reason I can not attach images to this post. If you give me an e-mail address, I can send you the screen shots.
|
|
|
|
| |
|
|
|
|
Joined: 2/2/2012
Posts: 278
|
|
|
Update:
Although it seemed like the search module was the culprit from our last test, we have found that the problem is arising from the scheduler. We disabled the scheduler, and now the site is acting normally, even with search.
Does Smith Cart, or any of it's associated module, use the scheduler in any way?
|
|
|
|
| |
|
|
 |
 |
Joined: 3/11/2010
Posts: 1979
|
|
|
By default, SmithCart does not use the DNN scheduler. SmithCart has the following scheduler programs that can be configured to run using the DNN scheduler:
- Variant Import Scheduler
- Order Export Scheduler
- Saved Cart/Wishlist Automated Email Reminder
Please see page 316 of the cart user's guide for more info on these scheduler programs and how to configure them.
http://www.smith-consulting.com/Porta...
Scott Kelly
Project Manager
|
|
|
|
| |
|
|
 |
 |
Joined: 12/18/2009
Posts: 174
|
|
|
BuyNow supports iSearchable which is called automatically by the Search Engine Scheduler.
You can verify this through Extensions, Smith.BuyNow, edit module settings.
If the business controller class is set to Smith.DNN.Modules.BuyNow.ProductsController, it will indicate iSearchable.
Disabling the seach engine scheduler as a temporary workaorund will cause other search problems in DNN.
Obviously something needs to be fixed.
|
|
|
|
| |
|
|
|
|
Joined: 2/2/2012
Posts: 278
|
|
|
Thanks for this heads up djbaldwin. I checked the module settings, and as you said, it was set to be iSearchable.
We disabled the scheduler entirely on the site as a temporary fix, until we have time to pin down the culprit of the error. If I am not using the DNN stock search provider, could I disable the iSearchable function in Smith.BuyNow?
This could possibly fix our issue so that I can enable the scheduler again.
|
|
|
|
| |
|
|
|
|
Joined: 3/11/2010
Posts: 1979
|
|
|
Yes, if you are not using the DNN stock search provider, you can disable the iSearchable function in Smith.BuyNow module.
Scott Kelly
Project Manager
|
|
|
|