Well, I am guessing that the “Quick Search” that is using “Searchanise” has a bug or something. Any of our community edition websites that are using this function stopped working tonight. If you disable “Quick Search” your site will work again. Literally, no one will be able to get to your site if you have “Searchanise” turned on! If you have the “Quick Search” turned on it will stop your site from responding while it is waiting for “Searchanise” to wake up or respond. This is ONLY in the community edition (free edition) and not in the pro as “Searchanise” appears to have only been used in the CE edition from 2.2.1 and on.
Sorry about the double post, for some reason the forum is giving me a 500 error and I didn’t realize the first one posted.
Well, I've gone through all of the sites that use the CE or free edition of CS 2.2.2 and everyone of them were shut down or did not open because of this problem with searchanise. Once I disabled the Quick Search everyone of the sites started working right away.
BTW, I have not been able to get to their website at searchanise.com either. So I am guessing that if your site is running the “Quick Search” for the Community Edition it is unable to contact their server and then it shuts down your site. This should be work out as no site should just freeze and not be able to open because someone's server is down.
One thing I learned real fast is after you disable it, what ever you do you do NOT want to make it active again or you will have a problem.
I've just noticed this issue myself, I'll be turning off that plugin right now
I can confirm this as well. Luckily I don't run any CE versions, but I do have some for testing purposes and Jim is correct.
Maybe you guys can put some type of time limit on this or something? Kind of like what you did for the license check?
Thanks,
Brandon
Hello!
Please let me apologize for any inconvenience caused by this problem.
Due to the inrush of users, we faced the problem of availability of our server.
We have taken measures to prevent recurrence of similar errors in the future.
[quote name='KleriK' timestamp='1317291158' post='122563']
Hello!
Please let me apologize for any inconvenience caused by this problem.
Due to the inrush of users, we faced the problem of availability of our server.
We have taken measures to prevent recurrence of similar errors in the future.
[/quote]
So is “Searchanise” a CS-Cart project too?
Also, does this mean that something is going to be changed on our end? I'm not so sure it is a good idea that any shopping cart has to rely on a different server in order for it to start. This sounds like trouble waiting to happen.
Looked up whois.
Registrant:
Simbirsk Technologies
Domain Name: SEARCHANISE.COM
So CS-Cart does own it. My next question would be, why are you making the front end of the CE rely on contact with searchnise before the page will even start?
[quote name='clips' timestamp='1317303609' post='122593']
Looked up whois.
Registrant:
Simbirsk Technologies
Domain Name: SEARCHANISE.COM
So CS-Cart does own it. My next question would be, why are you making the front end of the CE rely on contact with searchnise before the page will even start?
[/quote]
My 2 cents, I think it had more to do with the nature of outage, the searchanise servers completely stopped responding, I should have checked if the DNS servers were responding but forgot.
Unfortunately the inline javascript at the top of the page caused all js rendering to block (javascript always runs as a single thread). A more robust way to do this would be reference the searchanise js at the top of the page but add a jquery document.ready to actually use it. I think that would have prevented the problems we saw.
I wouldn't be to hard on Simbirsk for this I've seen both omniture tracking and doubleclick adds bring down sites in exactly the same way.
Jerome
I'm not really being hard on them…but it is a bug or issue that just shouldn't have been set up like that in the first place. Nobody wants a load from another site to kill the loading of their own site. Even it is the CE.
[quote name='nome30' timestamp='1317353116' post='122636']
Unfortunately the inline javascript at the top of the page caused all js rendering to block (javascript always runs as a single thread). A more robust way to do this would be reference the searchanise js at the top of the page but add a jquery document.ready to actually use it. I think that would have prevented the problems we saw.
[/quote]
We can assure you that in the nearest update, we will change the code of the “Quick Search” add-on so that
unavailability of our servers could not affect operability of your store in any way.
We apologize for the caused inconveniences once again.
same here for pro edition…when searchanize wont respond your site will neither…
dispatch=searchanise.async&no_session=Y HTTP/1.1
takes 15 seconds, to laod my site… i disabled but its still there
acutally its down…
so to make site load faster (else you get your site loading layer for ever !!!)
make this…
replace in /addons/searchanise/func.php line 19
fn_define('SE_REQUEST_TIMEOUT', 10);
BY
fn_define('SE_REQUEST_TIMEOUT', 0.1);
then all is fast !
Which version are you using? I thought CS-Cart fixed this one. I sure hope it doesn't affect the site when it isn't even installed.
sure does, mine was disabled lol
What does searchandise do anyway?