This has been discussed a lot and I see similar bugs on the github, but it hasn't yet been fixed. Someone from the core development team, please address this issue.
I'm running a website with multiple domain names and I have a LOT of issues with locks like this one:
Cannot index queue items, the index is currently locked
Right now I tried copying a page with descendants and it failed with this error:
This particular site isn't on Azure, though I've definitely had lock-issues on Azure before. This website is hosted on Simply.com. Where are those lock files located?
My thought was permissions - it sounds like it's creating the write.lock file and then not able to delete it.
I'm sure you've probably checked it but just make sure the iis server's permissions include delete in the app_data folder - I've seen people have problems when they have modify but not full access?
Nope. Umbraco 8 is still not good for running multiple sites with different domain names. To be honest - it's such a huge let down that I'm looking into using another CMS going forward. The core developer team has failed to fix this problem for more than a year.
Got a fix for this!
Worth saying is that i also Use Simply.com as host and two domains (one domain alias).
So in my case it was the both External and the Internal Index which got the exception.
I noticed that my CustomProduct Index, was doing fine.
Therefore my first thought was to create another custom index for the documents.
Then i rebuild the index on the "onpublish" event in Umbraco.
Which worked out fine, the fix had been up and running for 12h without a problem.
In Short: Use CustomIndexes, Use this in appSettings
Database/index locks
This has been discussed a lot and I see similar bugs on the github, but it hasn't yet been fixed. Someone from the core development team, please address this issue.
I'm running a website with multiple domain names and I have a LOT of issues with locks like this one:
Cannot index queue items, the index is currently locked
Right now I tried copying a page with descendants and it failed with this error:
Lucene.Net.Store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@d:\web\localuser\byens-hotel.dk\public_html\App_Data\TEMP\ExamineIndexes\External\write.lock
I really hope someone can address these issues soon.
I also have problems deleting pages which will sometimes cause problems like this error:
System.AggregateException: Exceptions were thrown by listed actions. ---> Lucene.Net.Store.LockObtainFailedException: Lock obtain timed out: SimpleFSLock@d:\web\localuser\domain.dk\publichtml\AppData\TEMP\ExamineIndexes\External\write.lock
It's driving me crazy. Someone help please.
Running 8.3
Are you on azure? Also latest umbraco upgrade has some locking fixes. We have an instance on azure and every now and then we get index lock.
We have 3 indexes and its always the custom one that locks. We have to manually delete the lock file and then search starts working again.
We are planning upgrade soon hopefully that will fix the issue for us.
This particular site isn't on Azure, though I've definitely had lock-issues on Azure before. This website is hosted on Simply.com. Where are those lock files located?
the path to it is there in your original post its in appdata folder
Ah - yes. Sorry, silly me :-)
My thought was permissions - it sounds like it's creating the write.lock file and then not able to delete it.
I'm sure you've probably checked it but just make sure the iis server's permissions include delete in the app_data folder - I've seen people have problems when they have modify but not full access?
Can't change permissions on folders as it's a hosted environment out of my reach.
Did you manage to fix this issue?
Nope. Umbraco 8 is still not good for running multiple sites with different domain names. To be honest - it's such a huge let down that I'm looking into using another CMS going forward. The core developer team has failed to fix this problem for more than a year.
Oh i see, thanks for the reply. I will make an effort to find a work-around, i have some ideas. I will let you know if it works:)
Got a fix for this! Worth saying is that i also Use Simply.com as host and two domains (one domain alias).
So in my case it was the both External and the Internal Index which got the exception. I noticed that my CustomProduct Index, was doing fine.
Therefore my first thought was to create another custom index for the documents. Then i rebuild the index on the "onpublish" event in Umbraco. Which worked out fine, the fix had been up and running for 12h without a problem.
In Short: Use CustomIndexes, Use this in appSettings
is working on a reply...