Not sure if this is a permissions thing, but whenever i recycle the app pool or restart the website the indexes fail to get built on start up, which in return stops the site from loading, as the content is "published but not in the cache".
I have given full permissions to the app pool, iusr and iis_iusrs onto the whole wwwroot directory.
And unhelpfully nothing gets logged.
If i log into the back office, and manually rebuild the indexes, and then rebuild the database and memory cache, and manually republish the affected pages, it works again...
until it starts again after the app pool recycle or website restarts
I have solved the problem, it was caused by some children nodes being linked to a parent node which somehow had been deleted (possibly via an uSync import)
This was causing the NuCache to crash on startup, stopping the indexes being generated.
I had to recreate the affected parent page, and then move the children under this, and delete the old parent from the tree.
Emptied the cache and Examine index directories, done an app recycle and all is good again!
Index not generating on startup
Not sure if this is a permissions thing, but whenever i recycle the app pool or restart the website the indexes fail to get built on start up, which in return stops the site from loading, as the content is "published but not in the cache".
I have given full permissions to the app pool, iusr and iis_iusrs onto the whole wwwroot directory.
And unhelpfully nothing gets logged.
If i log into the back office, and manually rebuild the indexes, and then rebuild the database and memory cache, and manually republish the affected pages, it works again...
until it starts again after the app pool recycle or website restarts
The site is running Umbraco 8.5.2
Help is appreciated!
I have solved the problem, it was caused by some children nodes being linked to a parent node which somehow had been deleted (possibly via an uSync import)
This was causing the NuCache to crash on startup, stopping the indexes being generated.
I had to recreate the affected parent page, and then move the children under this, and delete the old parent from the tree.
Emptied the cache and Examine index directories, done an app recycle and all is good again!
is working on a reply...