Linux动态链接库加载失败一例
安装pacemakerrpm包后，遇到启动失败的情况，原因和动态链接库的加载有关，以下是详细。 -android100学习网
Linux动态链接库加载失败一例
安装pacemakerrpm包后，遇到启动失败的情况，原因和动态链接库的加载有关，以下是详细。
Linux动态链接库加载失败一例
安装pacemakerrpm包后，遇到启动失败的情况，原因和动态链接库的加载有关，以下是详细。
问题 编译生成pacemaker 1.1.15的rpm包，然...
Linux动态链接库加载失败一例
安装pacemakerrpm包后，遇到启动失败的情况，原因和动态链接库的加载有关，以下是详细。
编译生成pacemaker 1.1.15的rpm包，然后在其它机器上安装pacemaker rpm包后，启动失败。
[root@srdsdevapp73 ~]# service pacemaker startStarting Pacemaker Cluster Manager
CentOS 6.3 64bit
通过strace发现pacemaker启动失败由于加载库libcoroipcc.so.4失败
[root@srdsdevapp73 ~]# strace -f service pacemaker start...[pid 19960] writev(2, [{"pacemakerd", 10}, {": ", 2}, {"error while loading shared libra"..., 36}, {": ", 2}, {"libcoroipcc.so.4", 16}, {": ", 2}, {"cannot open shared object file", 30}, {": ...
再用ldd检查pacemakerd，发现总共有3个库找不到
[root@srdsdevapp73 ~]# ldd /usr/sbin/pacemakerd
linux-vdso.so.1 =&
(0x00007fffc4c9f000)
libcrmcluster.so.4 =& /usr/lib/libcrmcluster.so.4 (0x0000003cbac00000)
libstonithd.so.2 =& /usr/lib/libstonithd.so.2 (0x0000003cba400000)
libcrmcommon.so.3 =& /usr/lib/libcrmcommon.so.3 (0xc00000)
libm.so.6 =& /lib64/libm.so.6 (0xc00000)
libcpg.so.4 =& /usr/lib64/libcpg.so.4 (0x99000)
libcfg.so.6 =& /usr/lib64/libcfg.so.6 (0xf95000)
libcmap.so.4 =& /usr/lib64/libcmap.so.4 (0xd8f000)
libquorum.so.5 =& /usr/lib64/libquorum.so.5 (0xb8b000)
libgnutls.so.26 =& /usr/lib64/libgnutls.so.26 (0x00000)
libcorosync_common.so.4 =& /usr/lib64/libcorosync_common.so.4 (0x88000)
libplumb.so.2 =& /usr/lib64/libplumb.so.2 (0x54000)
libpils.so.2 =& /usr/lib64/libpils.so.2 (0x4b000)
libqb.so.0 =& /usr/lib64/libqb.so.0 (0xe6000)
libpthread.so.0 =& /lib64/libpthread.so.0 (0xc00000)
libbz2.so.1 =& /lib64/libbz2.so.1 (0x00000)
libxslt.so.1 =& /usr/lib64/libxslt.so.1 (0x00000)
libxml2.so.2 =& /usr/lib64/libxml2.so.2 (0x00000)
libc.so.6 =& /lib64/libc.so.6 (0x00000)
libuuid.so.1 =& /lib64/libuuid.so.1 (0x00000)
libpam.so.0 =& /lib64/libpam.so.0 (0xc00000)
librt.so.1 =& /lib64/librt.so.1 (0x00000)
libdl.so.2 =& /lib64/libdl.so.2 (0x00000)
libglib-2.0.so.0 =& /lib64/libglib-2.0.so.0 (0x00000)
libltdl.so.7 =& /usr/lib64/libltdl.so.7 (0x00000)
libcoroipcc.so.4 =& not found
libcfg.so.4 =& not found
libconfdb.so.4 =& not found
libtasn1.so.3 =& /usr/lib64/libtasn1.so.3 (0x00000)
libz.so.1 =& /lib64/libz.so.1 (0x00000)
libgcrypt.so.11 =& /lib64/libgcrypt.so.11 (0x00000)
/lib64/ld-linux-x86-64.so.2 (0x00000)
libaudit.so.1 =& /lib64/libaudit.so.1 (0x00000)
libcrypt.so.1 =& /lib64/libcrypt.so.1 (0xc00000)
libgpg-error.so.0 =& /lib64/libgpg-error.so.0 (0x00000)
libfreebl3.so =& /lib64/libfreebl3.so (0x00000)
上面有一段"/usr/lib/libcrmcluster.so.4"比较奇怪，确认后发现文件不对，是以前安装的版本(不清楚当初怎么安装的了)。 正确的库位置应该是"/usr/lib64/libcrmcluster.so.4"。 将老版本的pacemaker删除后，一切正常
[root@srdsdevapp73 ~]# rm -f /usr/lib/libcrm*[root@srdsdevapp73 ~]# rm -f /usr/lib/libstonithd.*[root@srdsdevapp73 ~]# ldd /usr/sbin/pacemakerd
linux-vdso.so.1 =&
(0x00007fff9a3ff000)
libcrmcluster.so.4 =& /usr/lib64/libcrmcluster.so.4 (0xfc000)
libstonithd.so.2 =& /usr/lib64/libstonithd.so.2 (0xfea000)
libcrmcommon.so.3 =& /usr/lib64/libcrmcommon.so.3 (0xd93000)
libm.so.6 =& /lib64/libm.so.6 (0xc00000)
libcpg.so.4 =& /usr/lib64/libcpg.so.4 (0xb8c000)
libcfg.so.6 =& /usr/lib64/libcfg.so.6 (0x8000)
libcmap.so.4 =& /usr/lib64/libcmap.so.4 (0x2000)
libquorum.so.5 =& /usr/lib64/libquorum.so.5 (0xe000)
libgnutls.so.26 =& /usr/lib64/libgnutls.so.26 (0x00000)
libcorosync_common.so.4 =& /usr/lib64/libcorosync_common.so.4 (0xb000)
libplumb.so.2 =& /usr/lib64/libplumb.so.2 (0x7000)
libpils.so.2 =& /usr/lib64/libpils.so.2 (0xf3e000)
libqb.so.0 =& /usr/lib64/libqb.so.0 (0xcd9000)
libpthread.so.0 =& /lib64/libpthread.so.0 (0xc00000)
libbz2.so.1 =& /lib64/libbz2.so.1 (0x00000)
libxslt.so.1 =& /usr/lib64/libxslt.so.1 (0x00000)
libxml2.so.2 =& /usr/lib64/libxml2.so.2 (0x00000)
libc.so.6 =& /lib64/libc.so.6 (0x00000)
libuuid.so.1 =& /lib64/libuuid.so.1 (0x00000)
libpam.so.0 =& /lib64/libpam.so.0 (0xc00000)
librt.so.1 =& /lib64/librt.so.1 (0x00000)
libdl.so.2 =& /lib64/libdl.so.2 (0x00000)
libglib-2.0.so.0 =& /lib64/libglib-2.0.so.0 (0x00000)
libltdl.so.7 =& /usr/lib64/libltdl.so.7 (0x00000)
libtasn1.so.3 =& /usr/lib64/libtasn1.so.3 (0x00000)
libz.so.1 =& /lib64/libz.so.1 (0x00000)
libgcrypt.so.11 =& /lib64/libgcrypt.so.11 (0x00000)
/lib64/ld-linux-x86-64.so.2 (0x00000)
libaudit.so.1 =& /lib64/libaudit.so.1 (0x00000)
libcrypt.so.1 =& /lib64/libcrypt.so.1 (0xc00000)
libgpg-error.so.0 =& /lib64/libgpg-error.so.0 (0x00000)
libfreebl3.so =& /lib64/libfreebl3.so (0x00000)[root@srdsdevapp73 ~]# service pacemaker startStarting Pacemaker Cluster Manager
Linux下查找动态链接库的默认路径(未在/etc/ld.so.conf中设置，动态链接库加载时会优先查找/etc/ld.so.cache中库)的顺序如下，如果有同名的库文件挡在前面，可能导致动态链接库加载失败。
/usr/lib64CentOS7安装vncserver（启动失败及连接黑屏解决办法） - 博客频道 - CSDN.NET
Fang的博客
生活不只是眼前的苟且，还有Code和Debug
以root用户运行以下命令来安装
yum install tigervnc-server&
同样运行以下命令来安装
yum install vnc
停止并禁用防火墙；
systemctl stop firewalld.service
systemctl&disable firewalld.service
vncviewer基本上不用配置；
vncserver的配置，创建一个新的配置文件，以开启1号窗口为例（也可以同时开启多个窗口，修改数字即可），方法如下：
cp&/lib/systemd/system/vncserver@.service&/lib/systemd/system/vncserver@:1.service
或者再增加一个窗口：
cp&/lib/systemd/system/vncserver@.service&/lib/systemd/system/vncserver@:2.service
编辑/lib/systemd/system/vncserver@:1.service,设置用户root相关参数,最终内容如下：
Description=Remote&desktop&service&(VNC)
After=syslog.target&network.target
Type=forking
ExecStartPre=/bin/sh&-c&'/usr/bin/vncserver&-kill&%i&&&/dev/null&2&&1&||&:'
ExecStart=/sbin/runuser&-l&root&-c&&/usr/bin/vncserver&%i&
PIDFile=/root/.vnc/%H%i.pid
ExecStop=/bin/sh&-c&'/usr/bin/vncserver&-kill&%i&&&/dev/null&2&&1&||&:'
1.设置为非root用户报错：
[root@localhost system]# systemctl status -l vncserver@:2.service
vncserver@:2.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver@:2. vendor preset:
Active: failed (Result: exit-code) since 一
19:07:23 CST; 7s ago
Process: 10305 ExecStart=/usr/sbin/runuser -l fang -c /usr/bin/vncserver %i (code=exited,
status=1/FAILURE)
Process: 10291 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i & /dev/null 2&&1 || :
(code=exited, status=0/SUCCESS)
?4月 25 19:07:23 localhost.localdomain systemd[1]: Starting Remote desktop service (VNC)...
4月 25 19:07:23 localhost.localdomain systemd[1]: vncserver@:2.service: control process
exited, code=exited status=1
4月 25 19:07:23 localhost.localdomain systemd[1]: Failed to start Remote desktop service
4月 25 19:07:23 localhost.localdomain systemd[1]: Unit vncserver@:2.service entered failed
4月 25 19:07:23 localhost.localdomain systemd[1]: vncserver@:2.service failed.
2.Type=forking报错，改为Type=simple
[root@localhost
system]# systemctl start vncserver@:2.service
Job for vncserver@:2.service failed because the control process exited with error code. See
&systemctl status vncserver@:2.service& and &journalctl -xe& for details.
[root@localhost system]# systemctl status -l vncserver@:2.service
● vncserver@:2.service - Remote desktop service (VNC)
Loaded: loaded (/etc/systemd/system/vncserver@:2. vendor preset:
Active: failed (Result: exit-code) since 一
19:09:41 CST; 6s ago
Process: 12367 ExecStart=/usr/sbin/runuser -l root -c /usr/bin/vncserver %i (code=exited,
status=98)
Process: 12354 ExecStartPre=/bin/sh -c /usr/bin/vncserver -kill %i & /dev/null 2&&1 || :
(code=exited, status=0/SUCCESS)
?4月 25 19:09:41 localhost.localdomain systemd[1]: Starting Remote desktop service (VNC)...
4月 25 19:09:41 localhost.localdomain systemd[1]: vncserver@:2.service: control process
exited, code=exited status=98
4月 25 19:09:41 localhost.localdomain systemd[1]: Failed to start Remote desktop service
4月 25 19:09:41 localhost.localdomain systemd[1]: Unit vncserver@:2.service entered failed
4月 25 19:09:41 localhost.localdomain systemd[1]: vncserver@:2.service failed.
viewer客户端连接黑屏
改变xstartup的权限
这个问题是很多人容易忽视的问题，也是造成连接成功后黑屏的原因之一。
在CentOS中，xstartup的文件路径为：/root/.vnc/ （可以通过locate xstartup来查看xstartup的文件路径）
所以需要执行：chmod 777 /root/.vnc/xstartup
关闭防火墙
systemctl stop firewalld.service #停止
systemctl disable firewalld.service #禁用
更新systemctl以使其生效；
systemctl daemon-reload&
设置vncserver的密码；
&vncpasswd root
按提示输入密码以及确认密码
启动该服务用来启用vnc的1号窗口；
systemctl&start&vncserver@:1.service&&或者&vncserver&:1
关闭1号窗口：
systemctl&stop&vncserver@:1.service&&&或者&vncserver&-kill&:1
设置为开机自动启动；
systemctl&enable&vncserver@:1.service
转载自：http://hsuehwee./2211
排名：千里之外
（7）（0）（3）（2）（2）（6）（3）