'
```
---
### Author:  [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [2016年十一月10日 19:29 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/25 "2016-11-10T19:29:54Z")
> [@zogstrip](#):
>
> Is there any chances you could update to latest?
You guys rename ‘stable’ to ‘old stuff’ and ‘latest’ to ‘stable’ and I’ll switch.
---
### Author:  [@gkln](https://meta.discourse.org/u/gkln)
#### Post date: [2016年十一月11日 10:27 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/26 "2016-11-11T10:27:03Z")
Is it safe to run `redis-cli flushall` daily?
The workaround I have currently in mind is to setup a cronjob that runs:
```plaintext
docker exec data /usr/bin/redis-cli flushall
```
every night after (or before) the backup so the forum is in a good state to run the next backup.
But I’m unsure how clearing the forum state every night impacts its daily operation. Any recommandation on this matter?
Thank you. 😉
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [2016年十一月11日 16:43 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/27 "2016-11-11T16:43:46Z")
What’s preventing you from updating to latest version? That bug has been fixed and should not happen anymore. There should be no need to flush redis.
---
### Author:  [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [2016年十一月11日 17:05 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/28 "2016-11-11T17:05:07Z")
> [@zogstrip](#):
>
> What’s preventing you from updating to latest version? That bug has been fixed and should not happen anymore. There should be no need to flush redis.
Why is there a version called ‘stable’?
@sam, @codinghorror : Is it an official recommendation from discourse that the correct solution to a bug in the `stable` branch is to switch to the `latest` branch? If it is, I’ll switch. If it’s not, are you guys going to fix this or what?
---
### Author:  [@gkln](https://meta.discourse.org/u/gkln)
#### Post date: [2016年十一月11日 17:10 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/29 "2016-11-11T17:10:19Z")
I understand that the bug no more exists on latest. We are currently on stable, well, for feature stability. We have a development environment on beta to prepare the next stable release (mostly to deal with breaking changes that impact our CSS customizations).
Maybe it is after all a safer bet for us to use beta in production.
But what’s the point of the stable branch if it is not recommended to use anyway?
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2016年十一月11日 17:30 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/30 "2016-11-11T17:30:26Z")
Guys,
Just got a brand new Droplet and the problem is still happening on stable.
I’m not sure WHY it doesn’t happen on latest. I’m not sure why it didn’t happen when I last tested it.
However, this bug is very hard to debug, because it happens in a `fork` inside a wrapper to Chrome engine that we use to parse markdown.
So, yes, we want `stable` to be stable and bug free. We know the bug is happening. And will fix as soon as possible.
* * *
If necessary you can choose to disable automatic backups and run `RAILS_ENV=production bundle exec ruby script/discourse backup` manually while we triage this.
---
### Author:  [@gkln](https://meta.discourse.org/u/gkln)
#### Post date: [2016年十一月11日 19:03 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/31 "2016-11-11T19:03:35Z")
Thank you for taking the time to reproduce the bug.
Sam made these commits in an attempt to fix this bug:
[https://github.com/discourse/discourse/commit/7e43e73df69a5ca70e7f4546465525c7392612fb](https://github.com/discourse/discourse/commit/7e43e73df69a5ca70e7f4546465525c7392612fb)
[https://github.com/discourse/discourse/commit/c995fd65be3896de23c00c3d063cb9e4c55f24d8](https://github.com/discourse/discourse/commit/c995fd65be3896de23c00c3d063cb9e4c55f24d8)
They are not on stable. Aren’t they required to fully fix the bug?
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [2016年十一月11日 22:12 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/32 "2016-11-11T22:12:58Z")
You’re right 👍 We **_only_** backported the first 2 commits which were parts of the fix… We’ll get it fixed pretty soon (_unless there’s a merge conflict…_)
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [2016年十一月14日 21:52 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/33 "2016-11-14T21:52:18Z")
Hey guys, sorry this is my bad.
Version 1.6.7 with working backups is now out.
---
### Author:  [@pjv](https://meta.discourse.org/u/pjv)
#### Post date: [2016年十一月15日 11:14 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/34 "2016-11-15T11:14:14Z")
Clean auto backup last night with v. 1.6.7. Thanks for fixing it.
---
### Author:  [@gkln](https://meta.discourse.org/u/gkln)
#### Post date: [2016年十一月16日 07:13 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/35 "2016-11-16T07:13:27Z")
I confirm. Things seem to run smoothly again. Thanks!
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [2016年十一月16日 07:20 UTC](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682/36 "2016-11-16T07:20:12Z")
[上一頁](https://meta.discourse.org/t/discourse-failed-to-backup-on-stable/52682.md?page=1)