In our sitecore project (6.6.0 rev. 130404), we are facing an issue when trying to rebuild large indexes using sitecore control panel. There is an index which contains more than 650,000 items. Half-way through the index rebuilding operation, the process stops with the error "job ended unexpectedly" being displayed on the index-rebuild dialog box. When analyzing sitecore logs, we can't find any recorded exceptions related to this. Because we didn't know when the index rebuild really stopped, I searched all sitecore logs for the word "Exception" but couldn't find anything related to this.
We face the same issue with QuickSearch index (even larger index than our own) as well.
In logs, we see "Index rebuild job started" message but nothing related to that being ended or interrupted.
What can be the possible causes of this? and how can I find evidence using sitecore logs?
(ps. I have previously sought help for good indexing practices on this post, but haven't implemented the suggestions): Sitecore index rebuilding practices)
If you have permission to do so: Try to look into the EventLogs on the server you are hosting your solution on. Also, do you see logs like "Hosting Environment Initiated a Shutdown" or anything like this? There might be alot of reasons for Sitecore to be shutdown and showing this error. From my own experiences this can be:
Application pool with memory restriction exceeding limits and causing a shutdown;
Application pool rapid fail protection that shuts down the pool;
Changes in the Website/Data folder; (data folder can best be placed outside the website folder);
Application pool recycle times -> can be scheduled and cause application pool to recycle;
Those were just a few of the things I found to be the cause of recycles sometimes. You might best now check your eventlogs and from there try to shutdown the above stated causes.
EDIT: Ensure the data and indexes folders are outside of the web root and update the web.config to point to the data folder.
Hope this helps you a bit.
Related
I am using Sitecore 8.1 and whenever I build the solution. Sitecore starts rebuilding all the indexes when I load the website in browser. I am using IIS (localhost) on the development machine. Even if I change a some thing in web.config and reload the website (in browser), sitecore starts rebuilding indexes again.
Is it normal behavior with Sitcore 8.1? I have recently started working with it. I never had this kind of problem with Sitecore 7.2.
When you update web.config, Sitecore initiated a shutdown and restart again, once Sitecore gets restarted, it will start updating the indexes (I can see this in the crawling log).
IntervalAsynchronous strategy will be triggered and responsible for this behaviour.
The strategy forces a full index rebuild when the number of entries in
the history table exceeds the number you specify in the
Indexing.FullRebuildItemCountThreshold setting. This normally means
that a substantial publishing or deployment has taken place, and this
should always trigger a full index rebuild.
Refer to this link for more information: https://doc.sitecore.net/sitecore_experience_platform/setting_up__maintaining/search_and_indexing/indexing/index_update_strategies
We have a problem whereby the content editor is crashing the browser (any browser - Chrome, Firefox & IE) and then seems to lock out the session.
This issue seems to happen in waves - for most of the day it works fine, then for a period of time it consistently happens. An example trigger point is selecting an item in the content tree, then clicking the edit button. The page then freezes. Sometimes it says 'Not Responding' in the title bar, but sometimes you can still click into the address bar, yet the page itself is completely non responsive, almost like there is an overlay over the page, preventing anything being clicked. If the address bar is still available to click, going back to root URL just causes the site to hang and just continuously loads.
What's interesting is that when this occurs, users can load up a different browser and login fine (with the same credentials). So the issue seems to be connected to the browser session. But if the user tries to perform same action (clicking the 'edit' button for an item) in the new browser then it crashes too.
I have checked the JavaScript console in the browsers development tools and there doesn't appear to be any JavaScript errors & there is nothing in the logs to suggest a problem so we are a bit confused.
We have around 6+ content editors working concurrently.
After sending a dotTrace sample to Sitecore support, they have confirmed there was a bug in version 8.1 that was causing this. The reference number for the bug is 92994.
As a work around, they suggested the following:
As a workaround for the issue, please set value of the
Indexing.UpdateInterval setting to 00:00:00. It will disable automatic
updates of Quick Search (aka system) search index. This search index
is not used for searchin by Sitecore as Search.UseLegacySearchEngine
setting is set to false. Thus, indexing can be safely disabled
Since applying this workaround, our users haven't reported the issue.
Check to make sure you don't have a dependency hard-coded into your "Main Content" field that has been moved somewhere else in the content tree or deleted outright.
I've encountered this exact experience (freezing and then session lockout) when I moved a content item I had been linking to within an iframe. I had been using a hard-coded relative link and not a SiteCore link (otherwise, there would not have been an issue, since SiteCore auto updates internal links when content is moved).
The only solution I found with my particular issue was moving the updated content item back where it was, and then editing the "Main Content" field in the content item that referenced it (or restoring it to its original location, if it was deleted).
I realize your issue is not consistent, but it's worth checking out if you haven't already. If the changes that caused the freezing aren't yet posted to your staging or production environments, that could be why your users aren't seeing this happen constantly.
This happens on literally every Sitecore instance I've seen.
Sitecore uses synchronous requests in the admin interface - if you're looking in the browser console while in the admin interface you may notice that there's a stack of warnings about synchronous requests being deprecated because they may have a negative effect on user experience.
This negative effect is what you're experiencing, where the entire browser tab (or entire browser depending on which browser you're using) is locked and won't accept any input until the server responds.
Most of the time if you wait long enough (several minutes) the tab will become responsive again, but sometimes the server seems to just never respond and you just have to refresh the tab and find your place again.
To confirm that's what's happening when the browser is locked up, instead of looking for errors in the JavaScript console look in the Network tab of the developer tools for what request is taking a long time for the server to respond.
I guess the title says it all.
I noticed some ads were popping up on a client's site we are currently developing. It only shows on this particular site. Not any other site. It is very annoying to put it mildly.
I thought removing it would be as easy as setting up a new environment on ElasticBeanstalk for it. I was wrong!
I have started a fresh instance for the application, scanned the project folder for malware before deploying, emptied the content of s3 bucket for static files. All these made no difference. The adware/malware is still there.
It has been driving me nuts for the past few days. Does anyone know how to resolve this kind of problem?
Mark B pointed me in the right direction.
I used inspect element to check the network processes of pages showing the Malware/Adware. It was after this i noticed a few asynchronous posts going to http://api.adsrun.net/post. Of course, i'm not making any post calls to this link. So i decided to inspect my JavaScript files as seen in View Page Source. Fortunately, it was in the last few lines of the second file i inspected. Immediately i deleted this file, normalcy returned to my web application.
It has been a very frustrating several hours. Thanks once again, Mark B for your suggestion.
For last two updates of Glass (XE19.* and XE20*), whenever I load my Glass app onto a device it seems to get auto-deleted after a few hours. Has anyone else noticed this behavior and have a workaround to prevent it?
This question seems to indicate that if your apk has the same package name as one that is going through the review process, that it may be removed. Use a package name that is different or go through the review and whitelist process.
Update: The whitelist process allows you to permit a select group of people to be able to access the apks as you update them while they are being reviewed. You should be able to ask the review team about this once the process is underway.
I am creating a few nodes in neo4j using spring data, and then I am also accessing them via findByPropertyValue(prop, val).
Everything works correctly when I am reading/writing to the embedded DB using spring data.
Now, as per the Michael Hunger's book : Good Relationship, I opened up Neoclipse in read-only mode connection to my currently active Neo4j connection in Java..
But, it somehow still says that Neo4j's kernel is actively used by some other program or something.
Question 1 :What am I doing wrong here?
Also, I have created a few nodes and persisted them. Whenever I restart the embedded neo4j db, I can view all my nodes when I do findAll().
Question 2 :When I try to visualize all my nodes in Neoclipse(considering the db is accessible), I can only see one single node(which is empty), has no properties associated to it, whereas I have a name property defined.
I started my java app, persisted few nodes, traversed and got the output from in the java console. Now, I shutdown the application and started the Neoclipse IDE, connected to my DB and found that no nodes are present(Problem of Question 2).
After trying again(heads down), I go back to my Java app and ran my app, and surprisingly I found that I am getting a Lucene-file-corrupted error(unrecognized file format) error. I had no code changes, I did not delete anything, but still got this error.
Question 3 :Not sure what I am doing wrong. But since I found this discussion on my bug(lucene/concurrent db access), I am willing to know if this is a bug or if this is due to any programatic error.(Does it have to do something with Eclipse Juno)
Any reply would be highly appreciated.
Make sure you are properly committing the transactions.
Data is not immediately flushed to the disk by Neo4j and hence you might not be viewing the nodes immediately in Neoclipse. I always restart the application that is using Neo4j in
embedded mode so that data is flushed to the disk and then open neoclipse.
Posting your code would help us to check for any issues.