Is there by any chance any errors when indexing media? I've had weird issues with examine when I had a custom property with the same name as a built in one. For example 'id'.

You could try and download the examine index and open it with Luke, and see what kind of data is in there. Then you can determine if it's the read or the write that fails.

Are there any answers to this? This is happening on a live site and causes the log to become several hundred megabytes.

I see a similar issue on a recently upgraded site (from 7.2.1 -> 7.3.5). Not hosted on Azure. It reports:

Umbraco.Web.PublishedCache.XmlPublishedCache.PublishedMediaCache - Could not retrieve media 0 from Examine index, reverting to looking up media via legacy library.GetMedia method

And it gets logged about 40 times per minute - resulting in really long log files.

Is there an option to stop "WARN" items getting logged?

This all could be related to a timeout issue identified with PetaPoco.

http://issues.umbraco.org/issue/U4-7887

Fingers crossed the solution will be added soon.

Hmmm... I think we were too quick to close this. I'm still getting the very same error on a v7.4.1 build.

Hi All

Has anyone found a solution to this problem? I have recently deployed a 7.4.1 instance and am getting this error in the logs multiple times per second. I'm also not seeing any images on the site as the called to Umbraco.Media(id); in my razor is what's triggering these errors.

The site is on a 2 server web farm, with a shared file storage (IIS accessing via UNC paths) - permissions are all correct and the External Examine and Member logs are all working as expected.

Any help greatly appreciated.

Thanks, Dave

Same here , logs filling up quickly.

Umbraco version 7.3.8 assembly: 1.0.5891.22674

That happens because somewhere the code is accessing media nodes that don't exist in the Examine index.

The code below will fix this problem by indexing all media nodes that don't exist in the Examine index.

@inherits UmbracoTemplatePage
@{
    // Retrieve all media nodes 
    var xmlMediaNodes = new List<IMedia>();
    foreach (var mediaNode in ApplicationContext.Current.Services.MediaService.GetRootMedia())
    {
        xmlMediaNodes.AddRange(ApplicationContext.Current.Services.MediaService.GetDescendants(mediaNode.Id));
    }

    //Retrieve all media nodes from lucene index (InternalSearcher)
    var searcher = ExamineManager.Instance.SearchProviderCollection["InternalSearcher"];
    var searchCriteria = searcher.CreateSearchCriteria(Examine.SearchCriteria.BooleanOperation.And);
    var query = searchCriteria.RawQuery("+__IndexType:media");
    var luceneMediaNodes = searcher.Search(query).ToList();

    // Index media nodes that exist in the xml cache but not in the lucene index
    var nodesReindexed = 0;
    foreach (var mediaNode in xmlMediaNodes)
    {
        if (!luceneMediaNodes.Any(x => x.Id == mediaNode.Id))
        {
            ExamineManager.Instance.ReIndexNode(ApplicationContext.Current.Services.PackagingService.Export(ApplicationContext.Current.Services.MediaService.GetById(mediaNode.Id), false), UmbracoExamine.IndexTypes.Media);
            nodesReindexed++;
            // As more nodes are indexed, more time is given to lucene to re-index
            System.Threading.Thread.Sleep((int)Math.Truncate(Math.Log(nodesReindexed) * 50));
        }
    }
}

You will still get a warning when you try to access a media with Id 0. This has been fixed in Umbraco 7.4.2 (http://issues.umbraco.org/issue/U4-7823)

If someone is wondering where this warning is coming from, take a look at: https://github.com/umbraco/Umbraco-CMS/blob/dev-v7/src/Umbraco.Web/PublishedCache/XmlPublishedCache/PublishedMediaCache.cs [line 224]

Hope that helps.

Hi All,

We are still getting this error message on a 7.4.3 installation.

It's becoming a major issue for our client, it can easily be replicated by them deleting a node that is referenced in a multi-node picker.

As soon as the Examine index tried to re-build we get a flood of these errors and it seems to slow the index building significantly which is not good when they have 25k nodes.

Did anyone create an Umbraco Issue for this?

Cheers,

Chris

See new issue http://issues.umbraco.org/issue/U4-8856

Can flood the log if eg a site contains many media pickers and the picked medias have been deleted => will write 1 line per media = bad.

Stephan

Hi Stephan,

I see the issue with the logging has been fixed but we have a problem when it falls back to the db lookup instead of examine if you are fetching a folder they have no children but if you get it from the examine index it does have children.

So the fallback method isn't a replacement for the examine version. We allow users to pick a folder rather than individual images and it's become quite an issue for us.

This happens on our sites a lot our logs are full of these message and makes me concerned that the examine index becomes corrupted/invalid very frequently

Steve

is working on a reply...