请教： obsidian 的 self-hosted livesync 自建同步服务总是报错 We can't replicate more lower value

V2EX = way to explore

V2EX 是一个关于分享和探索的地方

已注册用户请登录

这是一个创建于 1009 天前的主题，其中的信息可能已经有所发展或是发生改变。

最近我用 obsidian 的 self-hosted livesync 自建服务器。发现同步到最后总是提示如下两句错误，然后有失败标识。

TypeError:Failed to fetch ...... We can't replicate more lower value.

其中 obsidian 和 self-hosted livesync 已经是用最新版。couchdb 是用官方推荐的镜像，最新版，docker ps 看一切正常。服务器正常连接，通过插件 check db 配置也是全部 ok 的。看起来大部分内容也是同步到手机上了。但有部分文件（包括空目录，我已经配置了同步空目录）是没有同步过去。哪位高手有遇过和解决吗？

完整日志如下： 2023/2/20 13:15:46->Scanning plugins 2023/2/20 13:15:46->Nothing changed:Word Splitting for Simplified Chinese in Edit Mode and Vim Mode 2023/2/20 13:15:47->Nothing changed:Advanced URI 2023/2/20 13:15:47->Nothing changed:Image auto upload Plugin 2023/2/20 13:15:47->Nothing changed:Markdown Formatting Assistant 2023/2/20 13:15:47->Nothing changed:proxy github 2023/2/20 13:15:47->Nothing changed:Advanced Slides 2023/2/20 13:15:47->Nothing changed:Auto Link Title 2023/2/20 13:15:47->Nothing changed:Banners 2023/2/20 13:15:47->Nothing changed:Excalidraw 2023/2/20 13:15:47->Nothing changed:Obsidian Git 2023/2/20 13:15:47->Nothing changed:Kanban 2023/2/20 13:15:47->Nothing changed:obsidian markmind 2023/2/20 13:15:47->Nothing changed:Style Settings 2023/2/20 13:15:47->Nothing changed:Templater 2023/2/20 13:15:47->Nothing changed:Annotator 2023/2/20 13:15:47->Nothing changed:SimpRead Sync 2023/2/20 13:15:47->Nothing changed:Commander 2023/2/20 13:15:47->Nothing changed:Dataview 2023/2/20 13:15:47->Nothing changed:Linter 2023/2/20 13:15:47->Nothing changed:Self-hosted LiveSync 2023/2/20 13:15:47->Nothing changed:Local Images Plus 2023/2/20 13:15:47->Nothing changed:Tasks 2023/2/20 13:15:47->Nothing changed:Obsidian42 - BRAT 2023/2/20 13:15:47->Nothing changed:Advanced Tables 2023/2/20 13:15:47->Scan plugin done. 2023/2/20 13:15:47->Oneshot Sync begin... (sync) 2023/2/20 13:15:47->Looking for the point last synchronized point. 2023/2/20 13:15:47->Replication activated 2023/2/20 13:15:48->TypeError:Failed to fetch 2023/2/20 13:15:48->Replication error 2023/2/20 13:15:48->Error:Failed to fetch 2023/2/20 13:15:48->Replication stopped. 2023/2/20 13:15:48->Retry with lower batch size:27/22 2023/2/20 13:15:48->Oneshot Sync begin... (sync) 2023/2/20 13:15:48->AbortError:The user aborted a request. 2023/2/20 13:15:48->Looking for the point last synchronized point. 2023/2/20 13:15:48->Replication activated 2023/2/20 13:15:49->TypeError:Failed to fetch 2023/2/20 13:15:49->Replication error 2023/2/20 13:15:49->Error:Failed to fetch 2023/2/20 13:15:49->Replication stopped. 2023/2/20 13:15:49->Retry with lower batch size:16/13 2023/2/20 13:15:49->Oneshot Sync begin... (sync) 2023/2/20 13:15:49->AbortError:The user aborted a request. 2023/2/20 13:15:49->Looking for the point last synchronized point. 2023/2/20 13:15:49->Replication activated 2023/2/20 13:15:50->TypeError:Failed to fetch 2023/2/20 13:15:50->Replication error 2023/2/20 13:15:50->Error:Failed to fetch 2023/2/20 13:15:50->Replication stopped. 2023/2/20 13:15:50->Retry with lower batch size:10/9 2023/2/20 13:15:50->Oneshot Sync begin... (sync) 2023/2/20 13:15:50->AbortError:The user aborted a request. 2023/2/20 13:15:50->Looking for the point last synchronized point. 2023/2/20 13:15:50->Replication activated 2023/2/20 13:15:51->TypeError:Failed to fetch 2023/2/20 13:15:51->Replication error 2023/2/20 13:15:51->Error:Failed to fetch 2023/2/20 13:15:51->Replication stopped. 2023/2/20 13:15:51->Retry with lower batch size:7/7 2023/2/20 13:15:51->Oneshot Sync begin... (sync) 2023/2/20 13:15:51->AbortError:The user aborted a request. 2023/2/20 13:15:51->Looking for the point last synchronized point. 2023/2/20 13:15:51->Replication activated 2023/2/20 13:15:51->TypeError:Failed to fetch 2023/2/20 13:15:51->Replication error 2023/2/20 13:15:51->Error:Failed to fetch 2023/2/20 13:15:51->Replication stopped. 2023/2/20 13:15:51->Retry with lower batch size:6/6 2023/2/20 13:15:51->Oneshot Sync begin... (sync) 2023/2/20 13:15:51->AbortError:The user aborted a request. 2023/2/20 13:15:51->Looking for the point last synchronized point. 2023/2/20 13:15:51->Replication activated 2023/2/20 13:15:52->TypeError:Failed to fetch 2023/2/20 13:15:52->Replication error 2023/2/20 13:15:52->Error:Failed to fetch 2023/2/20 13:15:52->Replication stopped. 2023/2/20 13:15:52->We can't replicate more lower value. 2023/2/20 13:15:52->AbortError:The user aborted a request.

8 条回复 2025-04-05 06:07:30 +08:00

byteboy

2023-02-20 13:46:15 +08:00

不好意思，不知道为什么回车断行消失了

QUC062IzY3M1Y6dg

2023-02-20 14:03:33 +08:00

大致看了一下 self-hosted livesync 这个仓库，感觉还没有 syncthing 方便

sorcerer

2023-02-20 14:09:34 +08:00 via iPhone

没啥私密内容的话还是通过 github 管理方便

byteboy

2023-02-20 15:45:04 +08:00

@shuxhan 主要是两台手机的 app 无法支持 syncthing

SenLief

2023-02-20 15:51:49 +08:00 via iPhone

还是用 remotely save 插件吧

byteboy

2023-02-20 15:57:26 +08:00

@SenLief 主要原因是感觉 remotely save 插件的作者已经弃坑而去了，快一年没有更新也不回复了。
而 self-hosted livesync 作者 /团队更新比较频繁，似乎活得不错。而且插件底层依赖的是 couchdb ，本身做同步应该是有保证的。就是不知道最底层 6 个批次发生了什么问题。前面的批次都成功复制到不同终端上了。

byteboy

2023-03-04 17:59:08 +08:00

此问题已经解决。当在 self-hosted livesync 打开允许插件同步这功能时，如果电脑端本地使用了非官方社区认证的插件，同步会失败。关闭插件同步开关后，用以本地文件为源重建远端和近端数据库后即可恢复。self-hosted livesync 这个插件更新还是比较快，一个月发布了多个版本。

amazingTT

235 天前

我用了一年,感觉挺拉的, 重置过好几次了还是经常遇到一些文件 conflict 或者 invalid; 然而对比并没有任何差异, 也 resolve 不了. 算上平板和手机大概五六台设备同步, 总是总是总是出问题, 太不可靠了. 每次浪费很久时间弄好过几天又不行