Arch Linux corosync无法启动问题-已解决

最新推荐文章于 2024-05-25 13:37:07 发布
最新推荐文章于 2024-05-25 13:37:07 发布
阅读量1.6k 收藏 1
点赞数 1
分类专栏： Linux
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_43869959/article/details/119829181
版权

Arch Linux corosync无法启动问题-已解决

参考 Arch Linux源码安装corosync成功

弄个软链接，方便找文件

[root@archlinux ~]# ln -s /usr/etc/corosync/ /etc/corosync/
ln: failed to create symbolic link '/etc/corosync/': No such file or directory
[root@archlinux ~]# ln -s /usr/etc/corosync/ /etc/corosync
[root@archlinux ~]#

看出配置文件的帮助也正常 man corosync.conf

啥都没有，没有crm，没有服务，没有启动

[root@archlinux corosync]# crm status
bash: crm: command not found
[root@archlinux corosync]# service corosync status
bash: service: command not found
[root@archlinux corosync]# systemctl status corosync
Unit corosync.service could not be found.
[root@archlinux corosync]# ps -ef|grep corosync
root       33903   33853  0 11:57 pts/0    00:00:00 grep corosync
[root@archlinux corosync]# man corosync

参考Ubuntu的，实际没有写服务

root@ubuntu18a:/var/lib/heartbeat/lrm# service corosync status
● corosync.service - Corosync Cluster Engine
   Loaded: loaded (/lib/systemd/system/corosync.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2021-08-20 09:49:18 CST; 2h 9min ago
     Docs: man:corosync
           man:corosync.conf
           man:corosync_overview
 Main PID: 1237 (corosync)
    Tasks: 2 (limit: 4656)
   CGroup: /system.slice/corosync.service
           └─1237 /usr/sbin/corosync -f

Aug 20 09:49:18 ubuntu18a corosync[1237]:   [QB    ] server name: cmap
Aug 20 09:49:18 ubuntu18a corosync[1237]:   [QB    ] server name: cfg
Aug 20 09:49:18 ubuntu18a corosync[1237]:   [QB    ] server name: cpg
Aug 20 09:49:18 ubuntu18a corosync[1237]:   [QB    ] server name: votequorum
Aug 20 09:49:18 ubuntu18a corosync[1237]:   [QB    ] server name: quorum
Aug 20 09:49:18 ubuntu18a corosync[1237]:   [TOTEM ] A new membership (192.168.56.101:44) was formed. Members joined: 1234
Aug 20 09:49:18 ubuntu18a systemd[1]: Started Corosync Cluster Engine.
Aug 20 10:55:07 ubuntu18a corosync[1237]:   [TOTEM ] A processor failed, forming new configuration.
Aug 20 10:55:07 ubuntu18a corosync[1237]:   [TOTEM ] A new membership (192.168.56.101:48) was formed. Members
Aug 20 11:20:37 ubuntu18a corosync[1237]:   [TOTEM ] A new membership (192.168.56.101:52) was formed. Members joined: 1235
root@ubuntu18a:/var/lib/heartbeat/lrm# ll /lib/systemd/system/corosync.service
-rw-r--r-- 1 root root 857 Mar 11 02:00 /lib/systemd/system/corosync.service
root@ubuntu18a:/var/lib/heartbeat/lrm# cat /lib/systemd/system/corosync.service
[Unit]
Description=Corosync Cluster Engine
Documentation=man:corosync man:corosync.conf man:corosync_overview
ConditionKernelCommandLine=!nocluster
Requires=network-online.target
After=network-online.target

[Service]
EnvironmentFile=-/etc/default/corosync
ExecStart=/usr/sbin/corosync -f $COROSYNC_OPTIONS
Type=notify

# The following config is for corosync with enabled watchdog service.
#
#  When corosync watchdog service is being enabled and using with
#  pacemaker.service, and if you want to exert the watchdog when a
#  corosync process is terminated abnormally,
#  uncomment the line of the following Restart= and RestartSec=.
#Restart=on-failure
#  Specify a period longer than soft_margin as RestartSec.
#RestartSec=70
#  rewrite according to environment.
#ExecStartPre=/sbin/modprobe softdog soft_margin=60

[Install]
WantedBy=multi-user.target
root@ubuntu18a:/var/lib/heartbeat/lrm#

验证配置文件

[root@archlinux corosync]# corosync -t
Can't read file /usr/etc/corosync/corosync.conf: No such file or directory
[root@archlinux etc]# cd /etc/corosync
[root@archlinux corosync]# ll
bash: ll: command not found
[root@archlinux corosync]# ls
corosync.conf.example  service.d  uidgid.d
[root@archlinux corosync]# ls -l *
-rw-r--r-- 1 root root 1917 Aug 20 11:48 corosync.conf.example

service.d:
total 0

uidgid.d:
total 0
[root@archlinux corosync]# cp -p corosync.conf.example corosync.conf
[root@archlinux corosync]# vi corosync.conf

啥都没有修改

[root@archlinux corosync]# corosync -t
parse error in config: Can't open logfile '/var/log/cluster/corosync.log' for reason: No such file or directory (2).
[root@archlinux corosync]# mkdir /var/log/cluster/
[root@archlinux corosync]# corosync -t
Aug 20 12:07:04.706 error   [MAIN  ] parse error in config: No interfaces defined
Aug 20 12:07:04.706 error   [MAIN  ] Corosync Cluster Engine exiting with status 8 at main.c:1445.
[root@archlinux corosync]#

修改一下IP地址，测试通过
在nodelist {
node {
下修改 ring0_addr

[root@archlinux corosync]# vi corosync.conf
[root@archlinux corosync]# corosync -t
Aug 20 12:09:10.319 notice  [MAIN  ] Corosync Cluster Engine exiting normally
[root@archlinux corosync]# diff corosync.conf.example corosync.conf
56c56
<               #ring0_addr: 192.168.0.1
---
>               ring0_addr: 192.168.56.103
[root@archlinux corosync]#

启动不了

[root@archlinux corosync]# ps -ef|grep coro
root       33944   33853  0 12:10 pts/0    00:00:00 grep coro
[root@archlinux corosync]# corosync
Aug 20 12:10:49.029 notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 12:10:49.029 info    [MAIN  ] Corosync built-in features: pie relro bindnow
[root@archlinux corosync]# ps -ef|grep coro
root       33949   33853  0 12:10 pts/0    00:00:00 grep coro
[root@archlinux corosync]# corosync -f
Aug 20 12:11:03.386 notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 12:11:03.386 info    [MAIN  ] Corosync built-in features: pie relro bindnow
Aug 20 12:11:03.389 error   [MAIN  ] Corosync Executive couldn't create lock file.
Aug 20 12:11:03.389 error   [MAIN  ] Corosync Cluster Engine exiting with status 17 at main.c:1590.
[root@archlinux corosync]# man corosync
[root@archlinux corosync]# ps -ef|grep coro
root       33967   33853  0 12:12 pts/0    00:00:00 grep coro
[root@archlinux corosync]#
[root@archlinux corosync]#

版本号：自编译的3.1.5，ubuntu的2.4.3，配置文件差异很大。

[root@archlinux corosync]# corosync -v
Corosync Cluster Engine, version '3.1.5'
Copyright (c) 2006-2021 Red Hat, Inc.

Built-in features: pie relro bindnow
Available crypto models: nss openssl gcrypt
Available compression models: zlib lz4 lz4hc lzo2 lzma bzip2 zstd
[root@archlinux corosync]#


root@ubuntu18a:~# apt list corosync
Listing... Done
corosync/bionic-updates,now 2.4.3-0ubuntu1.2 amd64 [installed,automatic]
N: There are 2 additional versions. Please use the '-a' switch to see them.
root@ubuntu18a:~# apt list corosync -a
Listing... Done
corosync/bionic-updates,now 2.4.3-0ubuntu1.2 amd64 [installed,automatic]
corosync/bionic-security 2.4.3-0ubuntu1.1 amd64
corosync/bionic 2.4.3-0ubuntu1 amd64

根据帮助，UDPU模式下，不用配置interface，在nodelist下配置就可以了。
For UDPU an interface section is not needed and it is recommended that the nodelist is used to define cluster nodes.

开启debug，查看日志
debug: on
logfile: /var/log/cluster/corosync.log

[root@archlinux exec]# corosync
Aug 20 14:29:43.069 notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 14:29:43.073 info    [MAIN  ] Corosync built-in features: pie relro bindnow
Aug 20 14:29:43.073 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
Aug 20 14:29:43.073 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
Aug 20 14:29:43.073 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.101 resolved as 192.168.56.101
Aug 20 14:29:43.073 debug   [TOTEM ] Configuring link 0 params
Aug 20 14:29:43.073 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
[root@archlinux exec]#

debug日志可以看到已经探测到另外2台服务器了，但是对启动失败没有更多信息。

[root@archlinux exec]# cat /var/log/cluster/corosync.log
Aug 20 12:07:04.706 [33933] archlinux corosync error   [MAIN  ] parse error in config: No interfaces defined
Aug 20 12:07:04.706 [33933] archlinux corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 8 at main.c:1445.
Aug 20 12:09:10.319 [33941] archlinux corosync notice  [MAIN  ] Corosync Cluster Engine exiting normally
Aug 20 12:10:49.029 [33945] archlinux corosync notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 12:10:49.029 [33945] archlinux corosync info    [MAIN  ] Corosync built-in features: pie relro bindnow
Aug 20 12:10:49.043 [33945] archlinux corosync error   [MAIN  ] Corosync Executive couldn't create lock file.
Aug 20 12:10:49.043 [33945] archlinux corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 17 at main.c:1590.
Aug 20 12:11:03.386 [33950] archlinux corosync notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 12:11:03.386 [33950] archlinux corosync info    [MAIN  ] Corosync built-in features: pie relro bindnow
Aug 20 12:11:03.389 [33950] archlinux corosync error   [MAIN  ] Corosync Executive couldn't create lock file.
Aug 20 12:11:03.389 [33950] archlinux corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 17 at main.c:1590.
Aug 20 14:23:33.726 [34042] archlinux corosync notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 14:23:33.729 [34042] archlinux corosync info    [MAIN  ] Corosync built-in features: pie relro bindnow
Aug 20 14:23:33.739 [34042] archlinux corosync error   [MAIN  ] Corosync Executive couldn't create lock file.
Aug 20 14:23:33.739 [34042] archlinux corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 17 at main.c:1590.
Aug 20 14:29:43.069 [34058] archlinux corosync notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 14:29:43.073 [34058] archlinux corosync info    [MAIN  ] Corosync built-in features: pie relro bindnow
Aug 20 14:29:43.073 [34058] archlinux corosync debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
Aug 20 14:29:43.073 [34058] archlinux corosync debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
Aug 20 14:29:43.073 [34058] archlinux corosync debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.101 resolved as 192.168.56.101
Aug 20 14:29:43.073 [34058] archlinux corosync debug   [TOTEM ] Configuring link 0 params
Aug 20 14:29:43.073 [34058] archlinux corosync debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
Aug 20 14:29:43.076 [34058] archlinux corosync debug   [QB    ] shm size:8388621; real_size:8392704; rb->word_size:2098176
Aug 20 14:29:43.076 [34058] archlinux corosync debug   [MAIN  ] Corosync TTY detached
Aug 20 14:29:43.079 [34058] archlinux corosync error   [MAIN  ] Corosync Executive couldn't create lock file.
Aug 20 14:29:43.079 [34058] archlinux corosync error   [MAIN  ] Corosync Cluster Engine exiting with status 17 at main.c:1590.
[root@archlinux exec]#

我现在可以分析源代码啦！
在exec目录下的main.c可以看到报错信息：Corosync Executive couldn’t create lock file.
前面是在corosync_flock函数中，调用了open函数失败

  1102  static enum e_corosync_done corosync_flock (const char *lockfile, pid_t pid)
  1103  {
  1104          struct flock lock;
  1105          enum e_corosync_done err;
  1106          char pid_s[17];
  1107          int fd_flag;
  1108
  1109          err = COROSYNC_DONE_EXIT;
  1110
  1111          lockfile_fd = open (lockfile, O_WRONLY | O_CREAT, 0640);
  1112          if (lockfile_fd == -1) {
  1113                  log_printf (LOGSYS_LEVEL_ERROR, "Corosync Executive couldn't create lock file.");
  1114                  return (COROSYNC_DONE_ACQUIRE_LOCK);
  1115          }

搜索_flock

  1589          if ((flock_err = corosync_flock (corosync_lock_file, getpid ())) != COROSYNC_DONE_EXIT) {
  1590                  corosync_exit_error (flock_err);

搜索corosync_lock_file，继续找pid文件路径

   166  static const char *corosync_lock_file = LOCALSTATEDIR"/run/corosync.pid";

搜索LOCALSTATEDIR来找具体路径

[root@archlinux corosync]# grep -r LOCALSTATEDIR *  2>/dev/null
   -r在子目录中搜索   2>/dev/null不显示错误
   剔除后
   config.log:#define LOCALSTATEDIR "/usr/var"

最终得到 /usr/var/run/corosync.pid，创建目录

[root@archlinux corosync]# ls -l /usr/var/run/corosync.pid
ls: cannot access '/usr/var/run/corosync.pid': No such file or directory
[root@archlinux corosync]# ls -l /var/run/corosync.pid
ls: cannot access '/var/run/corosync.pid': No such file or directory
[root@archlinux corosync]# cd /usr/var/run
bash: cd: /usr/var/run: No such file or directory
[root@archlinux var]# cd
[root@archlinux ~]# mkdir /usr/var/run
[root@archlinux ~]#

验证启动正常

[root@archlinux ~]# corosync
Aug 20 17:58:40.213 notice  [MAIN  ] Corosync Cluster Engine 3.1.5 starting up
Aug 20 17:58:40.216 info    [MAIN  ] Corosync built-in features: pie relro bindnow
Aug 20 17:58:40.216 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
Aug 20 17:58:40.216 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
Aug 20 17:58:40.216 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.101 resolved as 192.168.56.101
Aug 20 17:58:40.216 debug   [TOTEM ] Configuring link 0 params
Aug 20 17:58:40.216 debug   [TOTEM ] totemip_parse: IPv4 address of 192.168.56.103 resolved as 192.168.56.103
[root@archlinux ~]# ps -ef|grep corosync
root       34172       1  2 17:58 ?        00:00:00 corosync
root       34186   34146  0 17:58 pts/0    00:00:00 grep corosync
[root@archlinux ~]# corosync-cfgtool -s
Local node ID 1, transport knet
LINK ID 0 udp
        addr    = 192.168.56.103
        status:
                nodeid:          1:     localhost
                nodeid:       1234:     disconnected
[root@archlinux ~]#
乡路
关注
  • 1
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
proxmox 控制台无法连接_Proxmox运维 /etc/pve无法访问 cluster filesystem启动失败
weixin_39873325的博客
12-19 4623
StudyOverseas大佬：原文：https://www.liujason.com/article/565.html今天下午一个pve集群出了点问题，排查修复了。还是那句话，希望各位不要碰到，碰到了看看能省不少时间。问题描述Proxmox集群单节点丢失，能够ping通，但是ssh通过key连接时卡住，使用密码正常。使用ssh -vvv查看发现在验证key的时候无任何反馈，表明故障节点存publ...
corosync
liyao130608的博客
07-30 989
Corosync 是心跳信息传输层，它在传递信息时可通过简单的配置文件来定义信息的传递方式和协议等。它可以实现HA心跳信息传输的功能。
pacemaker错误状态下删除集群导致corosync服务启动错误
255.255.255.0
03-31 773
#查看服务状态 service corosync status journalctl -xe #报错/etc/corosync/corosync.conf不存在 #解决 #集群其他节点拷贝配置解决 cp authkey corosync.conf node2:/etc/corosync/ service corosync start
Shell脚本防止Linux远程SSH暴力破解
最新发布
伪·宅猫一枚
05-25 299
针对在Linux（CentOS8）系统上的持续ssh暴力破解访问，识别对端IP地址，将其加入防火墙黑名单
LINUX 高可用群集之 ~Corosync~
chuifuhuo6864的博客
07-29 450
Corosync：它属于OpenAIS(开放式应用接口规范)中的一个项目corosync一版本中本身不具 备投票功能，到了corosync 2.0之后引入了votequorum子系统也具备了投票功能了，如果我们用的是1版本的，又需要用到票数做决策时那该如何是好呢；当然，在红帽上把 cman +...
pacemaker+corosync+pcs实验
sujin的博客
06-26 3597
https://blog.51cto.com/9652359/2109398 https://blog.csdn.net/abel_dwh/article/details/78475630 2018-05-01 11:37:44 实验目的：使用corosync作为集群消息事务层（Massage Layer），pacemaker作为集群资源管理器（Cluster Resource Manage...
blackarch-slim-iso:BlackArch Linux Slim ISO
05-09
图像用于测试： : sha1sum：a795e9067e4fa93a23469f67882ac41bf7520757 参考提交：0274bafed80e90cec13d7d7fd2b23314afd3841f 重要：此Live ISO可能已过时，不能反映存储库的实际状态。地图build.sh：用于创建映像的...
Bridge Linux:Arch Linux变得容易。-开源
05-06
Bridge Linux是Arch的派生产品，包括GUI和标准应用程序。 它打算坚持与拱形基地，不会叉。
vagrant-arch64-base：用于Vagrant的简约，快速启动的Arch Linux盒
02-06
这个“vagrant-arch64-base”项目是专为Vagrant设计的一个轻量级、快速启动的Arch Linux虚拟机镜像，非常适合那些希望在Arch Linux环境下进行开发或测试的用户。 首先，我们要理解Vagrant的核心概念。Vagrant通过...
Arch Linux的配置管理器-C/C++开发
05-26
aconfmgr：Arch Linux的配置管理器aconfmgr是一个软件包，用于跟踪，管理和还原Arch Linux系统的配置。 其目标是：通过aconfmgr快速配置新系统或还原现有系统：Arch Linux aconfmgr的配置管理器是一个软件包，用于...
arch-linux-base-setup：一些模块一起帮助那些对Arch Linux感到好奇的家伙
02-17
arch-linux-base-setup复制和运行curl -fsSL ...linux-base-setup.sh
马哥运维corosync+pacemaker部署运维笔记整理
Vic的博客
06-17 5857
corosync是集群框架引擎程序，pacemaker是高可用集群资源管理器，crmsh是pacemaker的命令行工具。 一、NTP对时，免密钥登陆 [root@node-1 ~]# vim /etc/hosts 192.168.43.128 node-2 192.168.43.129 node-1 [root@node-1 ~]# ssh-keygen [root@node-1 ~]# ss...
shell错误 sed: can't read : No such file or directory
whatday的专栏
01-10 2万+
出现这样的问题主要是在于 空字符 造成的，情况分为3种 第一种是windows上的文件，在Linux上运行，这种可以通过查看文件编码确认，unix + utf-8 可以解决。 第二种是网页复制的shell代码，里边有些未知编码的空格字符，这种情况多次全局替换，可以解决，实在不行照着代码敲一遍总可以解决。 第三种是 sed命令使用了换行符 \ 且在换行符后加入了空格，例如： value1=...
corosync+drbd+mysql(实现mysql服务器的高可用性群集)
weixin_34206899的博客
05-13 7245
drbd+corosync+pacemaker 实现mysql服务器的高可用性群集 实验环境： node1 node1.a.com 192.168.10.10 node2node2.a.com 192.168.10.20 vip:192.168.50.100 实验步骤： 修改群集中各节点的网络参数 node1 [root@node1 ~]# vim /etc...
最佳解决方法 Error: No such file or directory @ rb_sysopen
yuchangyuan5237的博客
09-19 6260
最佳解决方法 Error: No such file or directory @ rb_sysopen
corosync基本使用
weixin_30929295的博客
06-30 2897
相关rpm: corosync-2.4.0-4.el6.x86_64.rpm　　　　　　　　　　　　　The Corosync Cluster Engine and Application Programming Interfaces。 corosynclib-2.4.0-4.el6.x86_64.rpm　　　　　　　　　　　　The Corosync Cluster Engine L...
【BUG】Linux目录下明明有可执行文件却提示找不到，“No such file or directory”，解决：为64位Ubuntu安装32位程序的运行架构
qq_46106285的博客
05-24 2万+
Ubuntu64位不能运行32位程序的解决办法
cmake 成功后， make 出现 No such file or directory 问题解决
热门推荐
banpozhi3270的博客
05-16 3万+
出现这种问题是说明没有找到相关的文件，例如： <gio/gio.h> No such file or directory 查看CMakeLists.txt, 发现包含的该头文件确实没有 include 进去 include_directories(${CMAKE_CURRENT_SOURCE_DIR}/_dev-fs/usr/include/libmm-glib)i...
./configure --arch=arm --target-os=linux --enable-gpl --enable-nonfree --enable-shared --enable-pic --cross-prefix=arm-linux-gnueabihf- --prefix=/usr/local/arm/ffmpeg --extra-cflags="-I/usr/local/arm/include" make make install ffplay是下x86的
06-09
你的问题是关于FFmpeg的配置和编译，你使用了ARM架构的交叉编译器，指定了目标操作系统和一些编译选项，并设置了安装路径。你使用了make命令编译并使用了make install命令安装FFmpeg。你还提到ffplay是为x86架构编译的，这可能是因为你没有指定ARM架构的编译选项，或者你使用的是预编译的二进制文件。 如果你需要为ARM架构编译ffplay，请重新配置和编译FFmpeg，确保指定了正确的编译选项和交叉编译器，并使用生成的二进制文件。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值