收起左侧

更新0.8.43后,开机一段时间后必失联。

5
回复
293
查看
[ 复制链接 ]

3

主题

5

回帖

0

牛值

江湖小虾

2025-4-5 13:54:19 显示全部楼层 阅读模式

<p>BUG现象:(我通过局域网任何设备访问,开机一段时间后,出现了死机断联情况,必须重启才能恢复正常,看pve日志跟内存有关,但是pve其他虚拟机又都正常运行。)</p> <p>设备环境:(pve虚拟机、局域网/公网/、0.8.43)</p> <p>出现频率:(必现)</p> <p>联系方式:(飞牛私有云 fnOS254群-52HzWhale)</p> <p>日志文件:(web端进入日志-更多-拷贝Debug Log-上传到社区;app进入设置-App日志上报-上报后提供设备id)</p> <p><img src="data/attachment/forum/202504/05/135201lpjon63ilape0zrp.jpg" alt="1000007808.jpg" title="1000007808.jpg" /></p>

收藏
送赞
分享

39

主题

8000

回帖

0

牛值

管理员

2025-4-8 18:23:59 显示全部楼层
之前部分虚拟机安装的系统会出现内存溢出的情况,该问题已进行记录需要等待后续计划。
部分在虚拟机上使用飞牛的网友,通过关闭swap分区解决了内存溢出问题可以尝试一下

1

主题

10

回帖

0

牛值

江湖小虾

2025-4-9 14:46:28 显示全部楼层

你好,你的飞牛nas失联的问题找到了么,我的飞牛nas也是频繁出现这个问题,我重装了飞牛系统也是这个样

还没有找到问题。我在等下次的更新。更新看看有没有改善。现在几乎天天失联。要想使用必须重启。pve的其他虚拟机都正常,就fnos一直死机失联。所以不会是硬件问题。  详情 回复
2025-4-10 11:57

3

主题

5

回帖

0

牛值

江湖小虾

2025-4-10 11:57:35 楼主 显示全部楼层
虫虫 发表于 2025-4-9 14:46
你好,你的飞牛nas失联的问题找到了么,我的飞牛nas也是频繁出现这个问题,我重装了飞牛系统也是这个样
...

还没有找到问题。我在等下次的更新。更新看看有没有改善。现在几乎天天失联。要想使用必须重启。pve的其他虚拟机都正常,就fnos一直死机失联。所以不会是硬件问题。
我也怀疑是飞牛的系统问题,我把dockermgr关掉后,20分钟后系统会自动奔溃,还不能随意关闭飞牛系统的进程  详情 回复
2025-4-10 17:55

1

主题

10

回帖

0

牛值

江湖小虾

2025-4-10 17:55:52 显示全部楼层
fucefu 发表于 2025-4-10 11:57
还没有找到问题。我在等下次的更新。更新看看有没有改善。现在几乎天天失联。要想使用必须重启。pve的其 ...

我也怀疑是飞牛的系统问题,我把dockermgr关掉后,20分钟后系统会自动奔溃,还不能随意关闭飞牛系统的进程

0

主题

5

回帖

0

牛值

江湖小虾

2025-4-15 16:49:21 显示全部楼层

我物理机直接安装的,也是一样的问题,基本上每二到三天崩溃一次。

查日志就是dockermgr和dsmgr两个服务。崩溃前是dockermgr,重启后完全关掉docker服务,还有dsmgr这个服务一直冒出来。

崩溃前:

2025-04-15T07:54:29.161627+08:00 fnOS dockermgr[3316]: [07:54:29.161] [info] [3331] [SAC]Register 1 ports finished
2025-04-15T07:54:29.161698+08:00 fnOS dockermgr[3316]: [07:54:29.161] [info] [3331] [SAC]Try to update ports for penpot-penpot-redis-1(8cb0fe2e0125c349a0afe9c70001102f0a3316585240e6642e848c41e8b8460e)
2025-04-15T07:54:29.161729+08:00 fnOS dockermgr[3316]: [07:54:29.161] [info] [3331] [SAC]Try to update ports for penpot-penpot-mailcatch-1(898de2f3d79458e5f0193a8cb31d48f44109f666ea4c531276278e64e33e05f4)
2025-04-15T07:54:29.161752+08:00 fnOS dockermgr[3316]: [07:54:29.161] [info] [3331] [SAC]Register 1 ports for 898de2f3d79458e5f0193a8cb31d48f44109f666ea4c531276278e64e33e05f4
2025-04-15T07:54:29.161974+08:00 fnOS dockermgr[3316]: [07:54:29.161] [info] [3331] [SAC]Register 1 ports finished
2025-04-15T07:54:29.162007+08:00 fnOS dockermgr[3316]: [07:54:29.161] [info] [3331] [SAC]Try to update ports for xteve(211c44cf6ad03cfe7c85705417f0323ef46445f64cc0e00ea5b5072b847c7fea)
2025-04-15T07:54:29.162044+08:00 fnOS dockermgr[3316]: [07:54:29.161] [info] [3331] [SAC]Register 2 ports for 211c44cf6ad03cfe7c85705417f0323ef46445f64cc0e00ea5b5072b847c7fea
2025-04-15T07:54:29.162676+08:00 fnOS dockermgr[3316]: [07:54:29.162] [info] [3331] [SAC]Register 2 ports finished
2025-04-15T07:54:29.162709+08:00 fnOS dockermgr[3316]: [07:54:29.162] [info] [3331] [SAC]Try to update ports for navidrome-navidrome-1(3f485035a7395dde9495b6700f3d6ca2a76c8727ba14f64446d085587474c944)
2025-04-15T07:54:29.162738+08:00 fnOS dockermgr[3316]: [07:54:29.162] [info] [3331] [SAC]Register 1 ports for 3f485035a7395dde9495b6700f3d6ca2a76c8727ba14f64446d085587474c944
2025-04-15T07:54:29.162933+08:00 fnOS dockermgr[3316]: [07:54:29.162] [info] [3331] [SAC]Register 1 ports finished
2025-04-15T07:54:29.162970+08:00 fnOS dockermgr[3316]: [07:54:29.162] [info] [3331] [SAC]Try to update ports for speedtest-x(97c62e3f5f98a40ed22a7259ecc2883b41819e7c0c0d6778dfb93b00df3b4e0b)
2025-04-15T07:54:29.163032+08:00 fnOS dockermgr[3316]: [07:54:29.162] [info] [3331] [SAC]Register 1 ports for 97c62e3f5f98a40ed22a7259ecc2883b41819e7c0c0d6778dfb93b00df3b4e0b
2025-04-15T07:54:29.163152+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Register 1 ports finished
2025-04-15T07:54:29.163219+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Try to update ports for immich_server(6c0ddc7c504f9f17eabf9c43c926c1d98a6c35d165a765a6c9276a1b951fa764)
2025-04-15T07:54:29.163244+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Register 1 ports for 6c0ddc7c504f9f17eabf9c43c926c1d98a6c35d165a765a6c9276a1b951fa764
2025-04-15T07:54:29.163393+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Register 1 ports finished
2025-04-15T07:54:29.163430+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Try to update ports for immich_postgres(69fdbdcaab9731b02df9cf136f394c64bc1532a238095b29e2f0b05adfbfb68d)
2025-04-15T07:54:29.163455+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Try to update ports for immich_machine_learning(67983b382541aa980603f2c09c4a6492b9b34f7104a2dbbf283aebe610db7ffe)
2025-04-15T07:54:29.163477+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Try to update ports for immich_redis(8064c0096798cf1bb691375a9b36b04204a20d4c9165613fa4539847deac93be)
2025-04-15T07:54:29.163497+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Try to update ports for memos(085ee89f9aa7795a6e76cac595a0af200213bc11a716c8aa64dce020c6e3c851)
2025-04-15T07:54:29.163516+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Register 1 ports for 085ee89f9aa7795a6e76cac595a0af200213bc11a716c8aa64dce020c6e3c851
2025-04-15T07:54:29.163608+08:00 fnOS dockermgr[3316]: [07:54:29.163] [info] [3331] [SAC]Register 1 ports finished
2025-04-15T07:54:34.422427+08:00 fnOS systemd[1]: run-docker-runtime\x2drunc-moby-ed4ecb0700b44a0e97890ebd1f0b165d3271873e5f079466e581030d9159bc42-runc.QuYJji.mount: Deactivated successfully.
2025-04-15T07:54:42.538477+08:00 fnOS systemd[1]: run-docker-runtime\x2drunc-moby-8cb0fe2e0125c349a0afe9c70001102f0a3316585240e6642e848c41e8b8460e-runc.6QyZsn.mount: Deactivated successfully.
2025-04-15T07:54:44.138511+08:00 fnOS systemd[1]: run-docker-runtime\x2drunc-moby-06966c8e2f93dc9467b1002af39a66feccc81ea7d527b748c3858502816ae909-runc.OghPiu.mount: Deactivated successfully.
2025-04-15T07:54:45.718453+08:00 fnOS systemd[1]: run-docker-runtime\x2drunc-moby-38420d36f94dfb5938ebf9a7a5f19a1521295f774521a2d04d86ffc226c560f5-runc.cAFUoe.mount: Deactivated successfully.
2025-04-15T07:54:46.870455+08:00 fnOS systemd[1]: run-docker-runtime\x2drunc-moby-ed4ecb0700b44a0e97890ebd1f0b165d3271873e5f079466e581030d9159bc42-runc.bsLBTv.mount: Deactivated successfully.
2025-04-15T07:54:51.984143+08:00 fnOS systemd[1]: run-docker-runtime\x2drunc-moby-67983b382541aa980603f2c09c4a6492b9b34f7104a2dbbf283aebe610db7ffe-runc.gquVrE.mount: Deactivated successfully.

重启关闭docker服务后:

2025-04-15T14:27:45.949678+08:00 fnOS dsmgr[192614]: [Stats]Run stats cnt:1402, size:0
2025-04-15T14:27:45.949766+08:00 fnOS dsmgr[192614]: [Stats]start begin
2025-04-15T14:27:45.949797+08:00 fnOS dsmgr[192614]: [Stats]wait for container event
2025-04-15T14:27:45.949844+08:00 fnOS dsmgr[192614]: [Stats]closing event monitor
2025-04-15T14:27:45.949872+08:00 fnOS dsmgr[192614]: [Stats]closed event monitor
2025-04-15T14:27:45.949897+08:00 fnOS dsmgr[192614]: [Stats]exit from getContainerList
2025-04-15T14:27:45.949922+08:00 fnOS dsmgr[192614]: [Stats]Close the channel, err:Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
2025-04-15T14:27:45.949948+08:00 fnOS dsmgr[192614]: time="2025-04-15T14:27:45+08:00" level=error msg="runStats err:Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?"

每10秒钟就运行一次

您需要登录后才可以回帖 登录 | 立即注册

本版积分规则