cannot write now because we are going down changes may be lost - Using Umbraco 7

Press Ctrl / CMD + C to copy this to your clipboard.

Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at

Maff 141 posts 466 karma points

Jul 08, 2015 @ 14:03
1

Cannot write now because we are going down, changes may be lost.
Hi,

I've just upgraded to 7.2.6 and I'm seeing loads of this warning appearing in the log file when doing large-ish republishes (100+ items):
```
2015-07-08 14:58:53,231 [14] WARN  Umbraco.Web.PublishedCache.XmlPublishedCache.XmlCacheFilePersister - [T35/D2] Cannot write now because we are going down, changes may be lost.
```
Is anyone else seeing this and if so, any ideas what's causing it?

Thanks,

Maff
Copy Link
Chester Campbell 98 posts 209 karma points

Oct 01, 2015 @ 21:00

0

Maff, did you ever resolve this? I'm seeing the same error in an Umbraco 7.2.8 site. Can't find any other info about the error.

Thanks

Copy Link
Lewis 27 posts 90 karma points

May 09, 2016 @ 11:22

0

Also getting this issue on 7.3.8

Trying to publish 1000's of nodes and many of them are left with the 'Oops: this document is published but is not in the cache (internal error)' message in place of the URL.

Copy Link

Mark Bowser 273 posts 860 karma points c-trib

Oct 19, 2016 @ 17:45

I'm seeing this in one of our 7.4.3 sites. We are having problems with our indexes being locked. I'm suspicious of this causing the locks.

 2016-10-19 00:08:40,911 [P6648/D2/T59] WARN  Umbraco.Web.PublishedCache.XmlPublishedCache.XmlCacheFilePersister - Cannot write now because we are going down, changes may be lost.
 2016-10-19 00:08:41,223 [P6648/D4/T53] ERROR UmbracoExamine.DataServices.UmbracoLogService - Provider=InternalIndexer, NodeId=-1
    System.Exception: Cannot index queue items, the index is currently locked,, IndexSet: InternalIndexSet
 2016-10-19 00:08:41,770 [P6648/D4/T248] ERROR UmbracoExamine.DataServices.UmbracoLogService - Provider=ExternalIndexer, NodeId=-1
    System.Exception: Cannot index queue items, the index is currently locked,, IndexSet: ExternalIndexSet

Copy Link

Remko 118 posts 283 karma points

Nov 17, 2016 @ 09:45

0

Also got the problem for a while now.. We don't have a clue how to solve this.. It's causes tremendous problems with content not visible on site.

Copy Link
Sverrir Páll Sverrisson 7 posts 87 karma points

Feb 08, 2017 @ 09:10

0

Did someone figure this out already? I'm seeing the same errors.

Copy Link
Remko 118 posts 283 karma points

Feb 08, 2017 @ 09:31

0

Nope.. no one seems to know a solution for this one... We got a background process which publishes a bulk of nodes each night and every night this seems to happen, causing index mess up :(

Copy Link
Sverrir Páll Sverrisson 7 posts 87 karma points

Feb 08, 2017 @ 11:50

0

Check out this issue: http://issues.umbraco.org/issue/U4-6338

I just found out that we indeed have Windows Server 2012 R2 and the patch KB3000850 so I'm going to update the windows server tonight and see if it helps. Seems like that does the trick according to the responses to this issue.

Copy Link
Manish 373 posts 932 karma points

Mar 03, 2017 @ 12:26

0

Any solution

Copy Link
Dmitriy 168 posts 588 karma points

May 04, 2020 @ 22:43

0

Has the same issue on Windows Server 2016 and Umbraco 7.15.4 and, yep, it happens if try to publish thousands of nodes.

That advice from our helped me

Copy Link
is working on a reply...

Please Sign in or register to post replies