解决 Failed to initialize policy for cpu: 0 问题

本文分享了在更换电脑后,将Ubuntu16.04虚拟机从VMware12迁移到VMware15过程中遇到的初始化策略失败问题及解决方案。升级VMware版本后,问题得以解决。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

问题描述

  • 实验环境: VMware 12;windows10; Ubuntu 16.04

虚拟机上装了三个系统,分别是:Ubuntu16.4,CentOS4.10,Kali。最近换了台电脑,准备将这三台虚拟机迁移过去,其中两个都好使,唯有Ubuntu16.04出现故障。报错大概是:

Failed to initialize policy for cpu: 0 

问题解决

反反复复试了好多次,都不得已解决。截图下来,网上搜索,有提到版本问题。那就更新到VMware12 到15,问题解决。看着VMware 15 界面清爽呐!
在这里插入图片描述
之前花了好久配置好的Ubuntu16.04又可以用了。
在这里插入图片描述
啊啊啊!又是版本问题,花了好久个小时没解决的问题又是版本问题呐!这不止一次在版本上花时间,好在解决了,写篇文章记录下。

题外的碎碎念

既然写到到这儿,不妨也贴上自己使用过的免费许可验证码,给囊中羞涩的你们,CC190-DKZE6-089MQ-E4ZGE-MFRE2 虽然是破解的,但还是希望我们可以支持正版。

最后在吹一波,VMware15的优点。有点多,直接复制粘贴咯。

  • VMware15 的优点

1 新客户操作系统支持
oWindows 101803
oUbuntu 18.04
oFedora28
ORHEL7.5
oCentOS7.5
oDebian 9.5
oOpenSuse Leap 15.0
oFreeBSD11.2
oESXi6.7
2 DirectX10.1
Direct×10.1是Directx 10.0的增量更新。 它通过支持多样本抗锯齿提供更高的视觉质量
(MSAA)。 Directx 10.1还支持Shader Model 4.1和Cubemap Array。
3、硬件版本16
o DirectX10.1支持高达3GB的oGraphics内存
4、REST API您可以使用Workstation RESTful API通过HTTP或HTTPS上的标准JSON自动执行常见虚拟机任务。支持以下虚拟机操作:
o虚拟机库存管理
o虚拟机电源管理o虚拟机克隆o网络管理
5、高DPI支持高DPI相关功能要求主机和虚拟机的操作系统为Windows 10 1703或更高版本。
o主机级别高DPI支持 - 工作站界面自动检测主机级别DPI更改并自动调整布局以满足新的DPl。
o guest DPI与主机同步 - 当主机端发生DPl更改时,客户机操作系统调整其DPI以匹配主机DP1。
此功能需要VMware Tools 10.3.2。
6、连接到vCenter Workstation 15 Pro时,主机和群集视图在连接到远程vSphere时添加新的“主机和群集”视图。清单树现在显示两个不同视图中对象的层次结构:主机和群集以及VM。只需单击一下,即可轻松在这两个视图之间切换。
这是仅限Windows主机的功能。
·VSphere 6.7支持Workstation 15 Pro为vSphere 6.7提供无缝支持。您可以从Workstation 15 Pro连接到远程ESXi 6.7主机或vCenter Server 6.7,以管理在vSphere上运行的虚拟机的远程。您还可以将本地虚拟机上载到vSphere
6.7或将在vSphere 6.7上运行的远程虚拟机下载到本地桌面。
您还可以部署VMware VCSA 6.7(VCenter Server Appliance)OVA软件包以在Workstation 15 Pro上运行。
7、USB自动连接到虚拟机当您将Workstation 15 Pro配置为记住连接规则时,USB设备可以自动连接到已打开电源的虚拟机。
这是仅限Windows主机的功能。
8、SSH登录Linux虚拟机您现在可以使用Workstation 15 Pro提供的SSH访问Linux虚拟机。
此功能要求主机的操作系统是Windows 10版本1803或更高版本。
9、增强的用户体验oStretch guest显示对于早于Windows XP的Linux guest虚拟机和Windows guest虚拟机,启用了拉伸guest虚拟机显示功能。您可以使用“保持纵横比拉伸”功能在保持用户界面纵横比的同时拉伸虚拟机显示,也可以使用“自由拉伸”功能将虚拟机显示拉伸到用户界面。
这是仅限Windows主机的功能。
o打开虚拟机目录现在,您可以通过右键单击Workstation Pro库中的虚拟机并选择“打开VM目录”,从Windows主机轻松访问虚拟机目录。
Linux Workstation Pro已经支持此功能。
10、Linux主机Wayland支持Workstation 15 Pro现在可以在Linux主机Wayland桌面上运行。 要在Wayland桌面上安装Workstation Pro,您必须使用终端模式安装。
11、虚拟NVMe存储的性能改进
12、已解决的问题
直接使用物理磁盘的虚拟机可能显示黑屏当虚拟机直接使用物理磁盘时,在启动虚拟机后,虚拟机可能会显示黑屏。
此问题已得到解决。
13、如果并行端口映射到物理并行端口,虚拟机可能会崩溃并在启动时显示错误当虚拟机使用并行端口并且并行端口映射到主机OS物理并行端口时,启动虚拟机机器,虚拟机可能会崩溃并出现以下错误:VMware Workstation无法恢复的错误:(Vcpu-O)
此问题已得到解决。
14、连接到DELL Thunderbolt USB扩展坞的USB设备可能无法连接到虚拟机当您将USB设备连接到USB扩展坞(例如DELL Thunderbolt)时,USB设备可能无法连接到虚拟机。
此问题已得到解决1
15、连接到某些3.1 xHCI控制器的USB设备无法在Windows主机上进行直通在Windows主机上,当您选择VM>可移动设备时,未列出连接到某些USB 3.1控制器的USB设备。因此,设备无法通过虚拟机。
16、在Linux主机上使用缩放实用程序时,Workstation Pro界面可能会崩溃对于某些Linux主机,例如Ubuntu 18.04,当您使用缩放实用程序时,Workstation Pro界面可能会崩溃。
此问题已得到解决。
已知的问题
17、在主机上安装某些第三方软件时,鼠标单击功能可能会在虚拟机中停止工作当您在主机上安装某些软件(如WizMouse)时,鼠标单击功能可能会在虚拟机中停止工作。
解决方法:
1)关闭虚拟机电源。
2)将以下条目添加到。 虚拟机的vmx文件:mks。Win32的。processWin32MouseInput= “TRUE”
3)打开虚拟机电源。

参考文章

; write=0.006 s, sync=0.001 s, total=0.024 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB 2025-07-25 11:25:49.627 UTC [1] LOG: database system is ready to accept connections 2025-07-25 11:25:49.628 UTC [11305] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-07-25 11:25:49.628 UTC [11306] FATAL: could not open file "global/pg_filenode.map": No such file or directory 2025-07-25 11:25:49.629 UTC [1] LOG: autovacuum launcher process (PID 11305) exited with exit code 1 2025-07-25 11:25:49.629 UTC [1] LOG: terminating any other active server processes 2025-07-25 11:25:49.630 UTC [1] LOG: background worker "logical replication launcher" (PID 11306) exited with exit code 1 2025-07-25 11:25:49.631 UTC [1] LOG: all server processes terminated; reinitializing 2025-07-25 11:25:49.680 UTC [11307] LOG: database system was interrupted; last known up at 2025-07-25 11:25:49 UTC 2025-07-25 11:25:49.753 UTC [11307] LOG: database system was not properly shut down; automatic recovery in progress 2025-07-25 11:25:49.759 UTC [11307] LOG: invalid record length at 0/1478CF0: wanted 24, got 0 2025-07-25 11:25:49.759 UTC [11318] FATAL: the database system is in recovery mode 2025-07-25 11:25:49.759 UTC [11307] LOG: redo is not required 2025-07-25 11:25:49.765 UTC [11308] LOG: checkpoint starting: end-of-recovery immediate wait 2025-07-25 11:25:49.774 UTC [1] LOG: received smart shutdown request 2025-07-25 11:25:49.789 UTC [11308] LOG: checkpoint complete: wrote 3 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.008 s, sync=0.001 s, total=0.026 s; sync files=2, longest=0.001 s, average=0.001 s; distance=0 kB, estimate=0 kB 2025-07-25 11:25:49.793 UTC [11308] LOG: shutting down 2025-07-25 11:25:49.794 UTC [11308] LOG: checkpoint starting: shutdown immediate 2025-07-25 11:25:49.810 UTC [11308] LOG: checkpoint complete: wrote 0 buffers (0.0%); 0 WAL file(s) added, 0 removed, 0 recycled; write=0.002 s, sync=0.001 s, total=0.017 s; sync files=0, longest=0.000 s, average=0.000 s; distance=0 kB, estimate=0 kB 2025-07-25 11:25:49.826 UTC [1] LOG: database system is shut down [root@k8s-master1 harbor]# [root@k8s-master1 harbor]# kubectl logs harbor-core-75cd4f54b5-b5stj -n harbor --previous Appending internal tls trust CA to ca-bundle ... find: '/etc/harbor/ssl': No such file or directory Internal tls trust CA appending is Done. init global config instance failed. If you do not use this, just ignore it. open conf/app.conf: no such file or directory 2025-07-25T11:29:52Z [INFO] [/controller/artifact/annotation/parser.go:85]: the annotation parser to parser artifact annotation version v1alpha1 registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cncf.helm.config.v1+json registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cnab.manifest.v1 registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cnai.model.manifest.v1+json registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.index.v1+json registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.list.v2+json registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.v1+prettyjws registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.config.v1+json registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.container.image.v1+json registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.goharbor.harbor.sbom.v1 registered 2025-07-25T11:29:52Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.wasm.config.v1+json registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/native/adapter.go:36]: the factory for adapter docker-registry registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/aliacr/adapter.go:40]: the factory for adapter ali-acr registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/awsecr/adapter.go:44]: the factory for adapter aws-ecr registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/azurecr/adapter.go:29]: Factory for adapter azure-acr registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/dockerhub/adapter.go:40]: Factory for adapter docker-hub registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/dtr/adapter.go:36]: the factory of dtr adapter was registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/githubcr/adapter.go:43]: the factory for adapter github-ghcr registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/gitlab/adapter.go:33]: the factory for adapter gitlab registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/googlegcr/adapter.go:37]: the factory for adapter google-gcr registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/huawei/huawei_adapter.go:40]: the factory of Huawei adapter was registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/jfrog/adapter.go:42]: the factory of jfrog artifactory adapter was registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/quay/adapter.go:53]: the factory of Quay adapter was registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/tencentcr/adapter.go:55]: the factory for adapter tencent-tcr registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/volcenginecr/adapter.go:40]: the factory for adapter volcengine-cr registered 2025-07-25T11:29:52Z [INFO] [/pkg/reg/adapter/harbor/adaper.go:31]: the factory for adapter harbor registered 2025-07-25T11:29:52Z [INFO] [/core/controllers/base.go:187]: Config path: /etc/core/app.conf 2025-07-25T11:29:52Z [INFO] [/core/main.go:148]: initializing cache ... 2025-07-25T11:29:52Z [INFO] [/core/main.go:167]: initializing configurations... 2025-07-25T11:29:52Z [INFO] [/lib/config/systemconfig.go:178]: key path: /etc/core/key 2025-07-25T11:29:52Z [INFO] [/lib/config/config.go:92]: init secret store 2025-07-25T11:29:52Z [INFO] [/core/main.go:169]: configurations initialization completed 2025-07-25T11:29:52Z [INFO] [/common/dao/base.go:67]: Registering database: type-PostgreSQL host-harbor-database port-5432 database-registry sslmode-"disable" 2025-07-25T11:29:52Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:29:54Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:29:56Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:29:58Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:00Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:02Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:04Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:06Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:08Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:10Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:12Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:14Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:16Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:18Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:20Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:22Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:24Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:26Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:28Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:30Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:32Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:34Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:36Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:38Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:40Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:42Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:44Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:46Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:48Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:50Z [ERROR] [/common/utils/utils.go:108]: failed to connect to tcp://harbor-database:5432, retry after 2 seconds :dial tcp 10.0.192.44:5432: connect: connection refused 2025-07-25T11:30:52Z [FATAL] [/core/main.go:190]: failed to initialize database: failed to connect to tcp:harbor-database:5432 after 60 seconds [root@k8s-master1 harbor]# kubectl logs harbor-jobservice-6457b57477-7qgt2 -n harbor --previous Appending internal tls trust CA to ca-bundle ... find: '/etc/harbor/ssl': No such file or directory Internal tls trust CA appending is Done. 2025-07-25T11:30:54Z [INFO] [/controller/artifact/annotation/parser.go:85]: the annotation parser to parser artifact annotation version v1alpha1 registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cncf.helm.config.v1+json registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cnab.manifest.v1 registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.cnai.model.manifest.v1+json registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.index.v1+json registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.list.v2+json registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.distribution.manifest.v1+prettyjws registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.oci.image.config.v1+json registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.docker.container.image.v1+json registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.goharbor.harbor.sbom.v1 registered 2025-07-25T11:30:54Z [INFO] [/controller/artifact/processor/processor.go:59]: the processor to process media type application/vnd.wasm.config.v1+json registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/native/adapter.go:36]: the factory for adapter docker-registry registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/aliacr/adapter.go:40]: the factory for adapter ali-acr registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/awsecr/adapter.go:44]: the factory for adapter aws-ecr registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/azurecr/adapter.go:29]: Factory for adapter azure-acr registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/dockerhub/adapter.go:40]: Factory for adapter docker-hub registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/dtr/adapter.go:36]: the factory of dtr adapter was registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/githubcr/adapter.go:43]: the factory for adapter github-ghcr registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/gitlab/adapter.go:33]: the factory for adapter gitlab registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/googlegcr/adapter.go:37]: the factory for adapter google-gcr registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/huawei/huawei_adapter.go:40]: the factory of Huawei adapter was registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/jfrog/adapter.go:42]: the factory of jfrog artifactory adapter was registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/quay/adapter.go:53]: the factory of Quay adapter was registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/tencentcr/adapter.go:55]: the factory for adapter tencent-tcr registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/volcenginecr/adapter.go:40]: the factory for adapter volcengine-cr registered 2025-07-25T11:30:54Z [INFO] [/pkg/reg/adapter/harbor/adaper.go:31]: the factory for adapter harbor registered 2025-07-25T11:30:54Z [INFO] [/pkg/config/rest/rest.go:47]: get configuration from url: http://harbor-core:80/api/v2.0/internalconfig 2025-07-25T11:30:54Z [ERROR] [/pkg/config/rest/rest.go:50]: Failed on load rest config err:Get "http://harbor-core:80/api/v2.0/internalconfig": dial tcp 10.5.232.220:80: connect: connection refused, url:http://harbor-core:80/api/v2.0/internalconfig panic: failed to load configuration, error: failed to load rest config goroutine 1 [running]: main.main() /harbor/src/jobservice/main.go:46 +0x3ae [root@k8s-master1 harbor]# 查看日子输出这些,我应该如何解决呢,目前正在用kubernetes集群搭建harbor仓库,想让root@k8s-master1 harbor]# kubectl get pod -n harbor NAME READY STATUS RESTARTS AGE harbor-core-75cd4f54b5-b5stj 0/1 CrashLoopBackOff 11 (118s ago) 26m harbor-database-0 0/1 Running 4 (3m16s ago) 26m harbor-jobservice-6457b57477-7qgt2 0/1 CrashLoopBackOff 13 (3m23s ago) 26m harbor-portal-5b6b5f7494-gcc8n 1/1 Running 1 (10m ago) 26m harbor-redis-0 1/1 Running 1 (10m ago) 26m harbor-registry-5fb967b497-d4r4r 2/2 Running 2 (10m ago) 26m harbor-trivy-0 1/1 Running 1 (10m ago) 26m全是running
最新发布
07-26
<think>好的,我需要解决Docker容器初始化日志驱动时遇到的连接被拒绝问题,错误是“failed to initialize logging driver: dial tcp [::1]:1514: connect: connection refused”。首先,我应该理解这个错误的原因。根据用户提供的引用资料,特别是引用[2]和[5],问题通常与rsyslog服务未正确配置或未运行有关。Harbor依赖rsyslog来接收日志,如果服务没有监听正确的端口(比如1514),或者防火墙阻止了连接,就会导致这个问题。 接下来,我应该按照步骤来排查和解决。首先检查rsyslog服务是否正在运行。用户提到在引用[2]中,重启rsyslog服务可以解决问题,所以可能需要执行systemctl status rsyslog来查看状态。如果服务没有运行,启动它或者重启它可能会有帮助。 然后,检查rsyslog的配置文件,确保监听的端口正确。引用[5]提到需要编辑/etc/rsyslog.conf文件,取消注释相关的模块并设置端口为1514。需要确认$ModLoad imtcp和$InputTCPServerRun 1514这两行是否已经正确配置,并且没有被注释掉。修改后,必须重启rsyslog服务才能使配置生效。 接下来,检查端口监听情况。使用netstat或ss命令来确认rsyslog是否在1514端口上监听TCP连接。例如,执行netstat -tuln | grep 1514,如果看到tcp6或tcp的监听,说明配置正确。如果没有,可能需要重新检查配置文件或者服务状态。 防火墙设置也是一个可能的原因。即使rsyslog配置正确,如果防火墙阻止了1514端口的连接,仍然会导致问题。需要检查防火墙规则,确保1514端口是开放的。用户可能使用的是firewalld或iptables,需要根据系统环境进行调整。 此外,查看Harbor的日志,特别是harbor-log容器的日志,可能会有更详细的错误信息。根据引用[4],harbor-log容器可能一直处于重启状态,这说明日志服务的问题影响到了整个Harbor的正常运行。可能需要通过docker logs命令查看具体错误。 最后,重启Harbor服务。在修改了rsyslog配置并确保其正常运行后,需要停止并重新启动Harbor服务,如引用[2]中提到的使用docker-compose命令停止和启动服务。这可以让Harbor重新连接到正确的日志服务。 如果以上步骤都正确执行,问题应该得到解决。如果仍然存在问题,可能需要进一步检查网络配置或Docker的日志驱动设置,确保没有其他冲突的配置。</think>### Docker日志驱动初始化失败问题解决方案 当Docker容器初始化日志驱动时出现`failed to initialize logging driver: dial tcp [::1]:1514: connect: connection refused`错误,通常与日志收集服务(如`rsyslog`)的配置或运行状态相关。以下是逐步解决方案: --- #### **步骤1:验证rsyslog服务状态** 1. 检查服务是否运行: ```bash systemctl status rsyslog ``` - 若未运行,启动服务: ```bash systemctl start rsyslog ``` - 若已运行但异常,重启服务: ```bash systemctl restart rsyslog ``` --- #### **步骤2:配置rsyslog监听端口** 1. 编辑配置文件`/etc/rsyslog.conf`: ```bash vim /etc/rsyslog.conf ``` 2. 确保以下两行已取消注释并修改端口为`1514`: ```plaintext $ModLoad imtcp # 加载TCP模块 $InputTCPServerRun 1514 # 监听1514端口 ``` - 修改后保存文件[^5]。 3. 重启rsyslog使配置生效: ```bash systemctl restart rsyslog ``` --- #### **步骤3:检查端口监听状态** 验证rsyslog是否在`1514`端口监听TCP请求: ```bash netstat -tuln | grep 1514 ``` 预期输出应包含: ```plaintext tcp6 0 0 :::1514 :::* LISTEN ``` --- #### **步骤4:检查防火墙设置** 确保防火墙允许`1514`端口的TCP通信: - **firewalld**: ```bash firewall-cmd --add-port=1514/tcp --permanent firewall-cmd --reload ``` - **iptables**: ```bash iptables -A INPUT -p tcp --dport 1514 -j ACCEPT service iptables save ``` --- #### **步骤5:重启Harbor服务** 1. 停止Harbor服务: ```bash docker-compose -f /path/to/harbor/docker-compose.yml stop ``` 2. 启动Harbor服务: ```bash docker-compose -f /path/to/harbor/docker-compose.yml start ``` --- #### **步骤6:验证Harbor容器状态** 检查Harbor容器是否正常运行: ```bash docker-compose ps ``` 若`harbor-log`容器仍异常,查看其日志定位问题: ```bash docker logs harbor-log-container-id ``` --- ### 关键点总结 - **根本原因**:rsyslog未正确配置或端口被阻塞导致Docker无法连接日志服务[^2]。 - **典型场景**:Harbor依赖rsyslog收集日志,配置错误会引发容器无限重启[^3][^4]。 - **扩展建议**:若使用其他日志驱动(如`syslog`、`journald`),需同步检查对应服务的配置。 ---
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值