HelloZeroNet / HelloZeroNet/ZeroNet

Content.json write error: false This file still in sync [SKIPPED] content.json

未关闭
#2,441 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
JavaScript
星标
18.8k
派生
2.3k
PR 合并指标
30 天内没有已合并 PR

描述

### Step 1: Please describe your environment

* ZeroNet version: 4455
* Operating system: W10
* Web browser: FF beta

### Step 2: Describe the problem:

Hello, suddenly when i tried to publish changes on my zeroblog clone, it shown on site error:

> Content.json write error: false

and prompt:

> This file still in sync, if you write it now, then the previous content may be lost. [ Write content anyway ]

in debug log is:

> INFO Site:1abc..def Opening site data directory: C:/ZeroNet-win-dist-win64/data/1abc...def/...
> INFO Site:1abc..def - [SKIPPED] content.json

same for:
"[SKIPPED] data/users/content.json"
"[SKIPPED] data/data.json-old"

> INFO Site:1abc..def Signing content.json...
> INFO Site:1abc..def Saving to content.json...
> INFO Site:1abc..def File content.json signed!

then i reload the site (F5) and after two hours without restarting or updating Zeronet, the publishing on that site works again without any messages mentioned above.

HDD has enough disk space. Though my RAM was exhausted.

Maybe you have clue what can cause this. If no and i can do something to discover more details, let me know and i will provide it.

贡献指南

这个仓库没有索引到贡献指南

调研方向

首先复现 ZeroBlog 克隆的发布流程,并检查 content.json、data/users/content.json 和 data/data.json-old 的调试日志条目,尤其是 [SKIPPED] 消息。比较 RAM 耗尽时以及之后发布成功后的行为;完成的标准是确定一个可靠的原因或复现方法,并记录由此产生的修复或诊断证据。

由索引模型根据 Issue 内容生成。

评估

领域
backend, distributed-systems
Issue 类型
缺陷
难度
4/5
预计耗时
3-5 天
活跃度
停滞
描述清晰度
需要澄清
新手友好度
25/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。