I'm having a problem with Examine Index constantly locking.
We are running 2 Domains from Umbraco.
Domain 1 - Home
Domain 2 - Home
They are slightly different versions of the website, so independently they are specific, use specific and shared templates.
Hosted on a dedicated server:
Server: Windows 2012 R2
Umbraco: v 7.15.3
App Pool: Both Domains running under the same IIS App Pool.
NO load balancing, NO Azure. NO CDN.
When a Member signs up, my code executes and it does sign them Ok, but I'm getting the InternalMemberIndexer continually locking up.
It's not just limited to this Indexer, sometimes the site crashed as the indexes are locked when just navigating around each one of the sites.
The stack trace is:
2020-06-09 14:29:46,773 [P4912/D3/T60] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:46,788 [P4912/D3/T60] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:46,898 [P4912/D3/T60] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:46,898 [P4912/D3/T60] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:46,960 [P4912/D3/T14] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:46,960 [P4912/D3/T14] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:47,070 [P4912/D3/T54] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:47,085 [P4912/D3/T54] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:47,179 [P4912/D3/T57] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:47,179 [P4912/D3/T57] INFO UmbracoExamine.DataServices.UmbracoLogService - Field "email" is listed multiple times in the index set "InternalMemberIndexSet". Please ensure all names are unique, Provider=InternalMemberIndexer, NodeId=24102
2020-06-09 14:29:47,210 [P4912/D3/T75] INFO Umbraco.Web.Mvc.UmbracoPageResult - Executing Umbraco RouteDefinition controller
2020-06-09 14:29:47,288 [P4912/D3/T75] INFO Umbraco.Web.Mvc.UmbracoPageResult - Finished (took 75ms)
2020-06-09 14:29:48,492 [P4912/D2/T47] ERROR UmbracoExamine.DataServices.UmbracoLogService - Provider=InternalMemberIndexer, NodeId=-1
But essentially this keeps cropping up, the Member emails don't get sent out for member verification as the error I'm seeing is that the Index is locked.
2020-06-09 14:29:48,492 [P4912/D2/T47] ERROR UmbracoExamine.DataServices.UmbracoLogService - Provider=InternalMemberIndexer, NodeId=-1
System.Exception: Cannot index queue items, the index is currently locked,, IndexSet: InternalMemberIndexSet
Any idea how I can get this to stop locking the index?
Setting up a multi-domain Umbraco instance do I need some special config settings?
Each Member is being created with a separate Member Type though.
Each with their own set of properties.
There was a separate Email field I did have in the Member Types as it was needed for Dialogue to work. I've removed it and tried to sign up as a member but still get the locking error.
There is another locking error if I restart the site in IIS
Have you had a look at the Member with ID of 24102?
Anything untoward? or Strange? - Might be worthwhile, taking a backup of the entire site. Removing all the Members, and seeing if/when the errors kick in.
I think it's more to do with 2 domains accessing the same Website in IIS. All be it they are the same site structure-wise, just different templates here and there and completely different CSS and imagery.
Even though they are on separate Domains and Nodes in Umbraco it seems setting 2 sites to point at the same folder/Umbraco install in IIS can't be done?
Yeh, I thought that as well, multilingual sites are done in a similar way, however, in my instance, they are two completely different domain names. Wonder if that makes a difference?
So the structure:
domain.com
domain.com/en/
domain.com/fr/
Should be Ok as they are the same domain?
would:
en.domain.com
fr.domain.com
be Ok as well?
In my instance I have:
domain1.com
domain2.com
I've upgraded from a lower version of Umb V7, think it was around 7.10, so not a major jump, to now upgraded 7.15.5. Maybe something amiss if it was upgraded from Umb 6 or 4, but we built it in the high 7s, so I can't think it would be that.
Profile data/properties differ slightly between Member Types. But that's just text strings and a few multinode tree pickers. Nothing out the ordinary.
I've used both scenarios for numerous multilingual sites, using completely different hostnames, or subfolders. And not hit this member indexing issue.
What I have seen happen is when a site gets upgraded from earlier versions the XML generation fails if a string contains a special (or hidden character). Typically when the text has been copied from a MAC device, or Word Document. (I could be barking up the wrong tree).
My first port of call would be to copy the site, remove all the member data, and see if you get the same errors. Then you'll know for sure, if its something to do with the profile data, against a particular member.
V7 - Examine Index Locking - Multi Domain
Hi
I'm having a problem with Examine Index constantly locking. We are running 2 Domains from Umbraco.
They are slightly different versions of the website, so independently they are specific, use specific and shared templates.
Hosted on a dedicated server: Server: Windows 2012 R2 Umbraco: v 7.15.3 App Pool: Both Domains running under the same IIS App Pool.
NO load balancing, NO Azure. NO CDN.
When a Member signs up, my code executes and it does sign them Ok, but I'm getting the InternalMemberIndexer continually locking up. It's not just limited to this Indexer, sometimes the site crashed as the indexes are locked when just navigating around each one of the sites.
The stack trace is:
But essentially this keeps cropping up, the Member emails don't get sent out for member verification as the error I'm seeing is that the Index is locked.
Any idea how I can get this to stop locking the index? Setting up a multi-domain Umbraco instance do I need some special config settings?
Hmmmm i can see why and how this would crop up.
As the "member" would think the sites are separate, but they actually share the same "member base".
Have you tried switching on "Use Unique Username", but switch off "Use Email As Username".
Each Member is being created with a separate Member Type though.
Each with their own set of properties.
There was a separate Email field I did have in the Member Types as it was needed for Dialogue to work. I've removed it and tried to sign up as a member but still get the locking error.
There is another locking error if I restart the site in IIS
So there is defo something wrong with 2 sites reading and writing to the same Examine Index.
Hi Neil,
Do you have 2 IIS sites point to the same website folder ? That is not supported.
dave
Yep
Both point to the same Website in IIS, Then within Umbraco,
I have Hostnames as :
Home - DomainName1 (Node)
Home - DomainName2 (Node)
Multiple IIS websites pointing to the same umbraco folder is not supported. This will lead to the locking issue you are describing.
It's better to have one IIS website and have multiple domain bindings on that one.
Dave
Ah-ha, I see.
So my setup of having 2 IIS websites is the problem.
Just setting up the bindings on the singular website to have
Then let Umbraco route to the correct (Home) node using 'Culture & Hostnames' should do the trick?
Yep
that should do the trick.
Dave
Have you had a look at the Member with ID of 24102?
Anything untoward? or Strange? - Might be worthwhile, taking a backup of the entire site. Removing all the Members, and seeing if/when the errors kick in.
Yeh, the ID pertains to the new Member created.
I think it's more to do with 2 domains accessing the same Website in IIS. All be it they are the same site structure-wise, just different templates here and there and completely different CSS and imagery.
Even though they are on separate Domains and Nodes in Umbraco it seems setting 2 sites to point at the same folder/Umbraco install in IIS can't be done?
Sounds peculiar - as this is typically how multilingual site are set up in Umbraco. (different domains pointing to the same umbraco solution)
Has the site been upgraded from a previous version? - and do you have any extra profile data you store against the member?
Yeh, I thought that as well, multilingual sites are done in a similar way, however, in my instance, they are two completely different domain names. Wonder if that makes a difference?
So the structure:
Should be Ok as they are the same domain?
would:
be Ok as well?
In my instance I have:
I've upgraded from a lower version of Umb V7, think it was around 7.10, so not a major jump, to now upgraded 7.15.5. Maybe something amiss if it was upgraded from Umb 6 or 4, but we built it in the high 7s, so I can't think it would be that.
Profile data/properties differ slightly between Member Types. But that's just text strings and a few multinode tree pickers. Nothing out the ordinary.
I've used both scenarios for numerous multilingual sites, using completely different hostnames, or subfolders. And not hit this member indexing issue.
What I have seen happen is when a site gets upgraded from earlier versions the XML generation fails if a string contains a special (or hidden character). Typically when the text has been copied from a MAC device, or Word Document. (I could be barking up the wrong tree).
My first port of call would be to copy the site, remove all the member data, and see if you get the same errors. Then you'll know for sure, if its something to do with the profile data, against a particular member.
Deffo : NeedleAndHaySack
Good luck!
Are you sure you didn't name this custom property "email" ?? - Just checking :)
is working on a reply...
This forum is in read-only mode while we transition to the new forum.
You can continue this topic on the new forum by tapping the "Continue discussion" link below.