drliufei 发表于 2023-10-3 12:52:04

系统意外自动重启问题

在板子上用NeZhaModel进行语义提取,只要模型一开始运行,Linux系统就自动重启。查看message日志,重启时刻的日志:
Oct2 11:38:16 master systemd: NetworkManager-dispatcher.service: Deactivated successfully.
Oct2 11:38:40 master registry: time="2023-10-02T11:38:40.968800283Z" level=info msg="response completed" go.version=go1.20.1 http.request.host=registry.cluster.local http.request.id=1a8c7777-dfab-4052-a22a-be81641e81c7 http.request.method=HEAD http.request.remoteaddr="10.233.0.3:43114" http.request.uri=/v2/newben/binfmt-arm64/manifests/latest http.request.useragent=containerd/v1.6.8-k3s1 http.response.contenttype=application/vnd.docker.distribution.manifest.v2+json http.response.duration=1.105417ms http.response.status=200 http.response.written=593 instance.id=15d25959-b814-4da2-b337-fd4e162f2205 service=registry vars.name=newben/binfmt-arm64 vars.reference=latest version=v2.8.2-6f094c79
Oct2 11:38:40 master registry: 10.233.0.3 - - "HEAD /v2/newben/binfmt-arm64/manifests/latest HTTP/1.1" 200 593 "" "containerd/v1.6.8-k3s1"
Oct2 11:38:47 master etcd: {"level":"warn","ts":"2023-10-02T11:38:47.031Z","caller":"grpclog/grpclog.go:60","msg":"transport: http2Server.HandleStreams failed to read frame: read tcp 172.178.28.17:2379->172.178.28.17:47196: read: connection reset by peer"}
Oct2 11:38:57 master etcd: {"level":"warn","ts":"2023-10-02T11:38:57.032Z","caller":"grpclog/grpclog.go:60","msg":"transport: http2Server.HandleStreams failed to read frame: read tcp 172.178.28.17:2379->172.178.28.17:47242: read: connection reset by peer"}
Oct2 11:39:11 master registry: time="2023-10-02T11:39:11.177737026Z" level=info msg="response completed" go.version=go1.20.1 http.request.host=registry.cluster.local http.request.id=c252cddf-0897-42aa-8d50-158d3ce86eb3 http.request.method=HEAD http.request.remoteaddr="10.233.0.3:43212" http.request.uri=/v2/newben/binfmt-arm64/manifests/latest http.request.useragent=containerd/v1.6.8-k3s1 http.response.contenttype=application/vnd.docker.distribution.manifest.v2+json http.response.duration=1.096667ms http.response.status=200 http.response.written=593 instance.id=15d25959-b814-4da2-b337-fd4e162f2205 service=registry vars.name=newben/binfmt-arm64 vars.reference=latest version=v2.8.2-6f094c79
Oct2 11:39:11 master registry: 10.233.0.3 - - "HEAD /v2/newben/binfmt-arm64/manifests/latest HTTP/1.1" 200 593 "" "containerd/v1.6.8-k3s1"
Oct2 11:39:12 master etcd: {"level":"warn","ts":"2023-10-02T11:39:12.034Z","caller":"grpclog/grpclog.go:60","msg":"transport: http2Server.HandleStreams failed to read frame: read tcp 172.178.28.17:2379->172.178.28.17:47268: read: connection reset by peer"}
Oct2 11:39:41 master registry: time="2023-10-02T11:39:41.391153187Z" level=info msg="response completed" go.version=go1.20.1 http.request.host=registry.cluster.local http.request.id=d6ac4b64-d366-4c20-9c72-cde62c4b20a8 http.request.method=HEAD http.request.remoteaddr="10.233.0.3:43252" http.request.uri=/v2/newben/binfmt-arm64/manifests/latest http.request.useragent=containerd/v1.6.8-k3s1 http.response.contenttype=application/vnd.docker.distribution.manifest.v2+json http.response.duration=1.081792ms http.response.status=200 http.response.written=593 instance.id=15d25959-b814-4da2-b337-fd4e162f2205 service=registry vars.name=newben/binfmt-arm64 vars.reference=latest version=v2.8.2-6f094c79
Oct2 11:39:41 master registry: 10.233.0.3 - - "HEAD /v2/newben/binfmt-arm64/manifests/latest HTTP/1.1" 200 593 "" "containerd/v1.6.8-k3s1"
Oct2 11:50:00 master systemd: Time has been changed
Oct2 11:50:00 master etcd: {"level":"warn","ts":"2023-10-02T11:50:00.441Z","caller":"grpclog/grpclog.go:60","msg":"transport: http2Server.HandleStreams failed to read frame: read tcp 172.178.28.17:2379->172.178.28.17:47308: read: connection reset by peer"}
Oct2 11:50:20 master etcd: {"level":"warn","ts":"2023-10-02T11:50:20.432Z","caller":"grpclog/grpclog.go:60","msg":"transport: http2Server.HandleStreams failed to read frame: read tcp 172.178.28.17:2379->172.178.28.17:47362: read: connection reset by peer"}
Oct2 11:50:30 master registry: time="2023-10-02T11:50:30.016603557Z" level=info msg="response completed" go.version=go1.20.1 http.request.host=registry.cluster.local http.request.id=605f2087-9b13-4209-a76e-f2f636e3e4fe http.request.method=HEAD http.request.remoteaddr="10.233.0.3:43350" http.request.uri=/v2/newben/binfmt-arm64/manifests/latest http.request.useragent=containerd/v1.6.8-k3s1 http.response.contenttype=application/vnd.docker.distribution.manifest.v2+json http.response.duration=1.054083ms http.response.status=200 http.response.written=593 instance.id=15d25959-b814-4da2-b337-fd4e162f2205 service=registry vars.name=newben/binfmt-arm64 vars.reference=latest version=v2.8.2-6f094c79
Oct2 11:50:30 master registry: 10.233.0.3 - - "HEAD /v2/newben/binfmt-arm64/manifests/latest HTTP/1.1" 200 593 "" "containerd/v1.6.8-k3s1"
Oct2 11:50:35 master etcd: {"level":"warn","ts":"2023-10-02T11:50:35.433Z","caller":"grpclog/grpclog.go:60","msg":"transport: http2Server.HandleStreams failed to read frame: read tcp 172.178.28.17:2379->172.178.28.17:47408: read: connection reset by peer"}
Jan1 00:00:03 master kernel: [    3.436293] Booting Linux on physical CPU 0x0000000000
页: [1]
查看完整版本: 系统意外自动重启问题