RAC下grid校验安装包引出的yum低级错误
grid
rac
yum
Pasang
semak
***********************************************声明********************************************** 原创作品，出自 深蓝的blog 博客，欢迎转载，转载时请务必注明出处，否则追究版权法律责任。 表述有错误之处，请您留言或邮件（hyldba@163.com）指明，
***********************************************声明**********************************************
原创作品，出自 “深蓝的blog” 博客，欢迎转载，转载时请务必注明出处，否则追究版权法律责任。
表述有错误之处，请您留言或邮件（hyldba@163.com）指明，不胜感激。
本文转载必须保留此处：http://blog.csdn.net/huangyanlong/article/details/39227577
深蓝的blog：http://blog.csdn.net/huangyanlong
***************************************************************************************************
***************************************
集群下安装包的检测
***************************************[grid@node1 grid]$ ./runcluvfy.sh stage -pre crsinst -n node1,node2 -fixup -verbose 缺失的包： Check: Package existence for "libaio-devel-0.3.105 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing libaio-devel-0.3.105 (i386) failed node1 missing libaio-devel-0.3.105 (i386) failed Result: Package existence check failed for "libaio-devel-0.3.105 (i386)" Check: Package existence for "libaio-devel-0.3.105 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing libaio-devel-0.3.105 (x86_64) failed node1 missing libaio-devel-0.3.105 (x86_64) failed Result: Package existence check failed for "libaio-devel-0.3.105 (x86_64)" Check: Package existence for "sysstat-5.0.5" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing sysstat-5.0.5 failed node1 missing sysstat-5.0.5 failed Result: Package existence check failed for "sysstat-5.0.5" Check: Package existence for "unixODBC-2.2.11 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-2.2.11 (i386) failed node1 missing unixODBC-2.2.11 (i386) failed Result: Package existence check failed for "unixODBC-2.2.11 (i386)" Check: Package existence for "unixODBC-2.2.11 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-2.2.11 (x86_64) failed node1 missing unixODBC-2.2.11 (x86_64) failed Result: Package existence check failed for "unixODBC-2.2.11 (x86_64)" Check: Package existence for "unixODBC-devel-2.2.11 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-devel-2.2.11 (i386) failed node1 missing unixODBC-devel-2.2.11 (i386) failed Result: Package existence check failed for "unixODBC-devel-2.2.11 (i386)" Check: Package existence for "unixODBC-devel-2.2.11 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-devel-2.2.11 (x86_64) failed node1 missing unixODBC-devel-2.2.11 (x86_64) failed Result: Package existence check failed for "unixODBC-devel-2.2.11 (x86_64)" Check: Package existence for "pdksh-5.2.14" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing pdksh-5.2.14 failed node1 missing pdksh-5.2.14 failed Result: Package existence check failed for "pdksh-5.2.14"
Salin selepas log masuk
yum安装包不成功提示
***************************************[root@node1 ~]# yum install unixO* -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile file:///cd1/repodata/repomd.xml: [Errno 5] OSError: [Errno 2] No such file or directory: '/cd1/repodata/repomd.xml' Trying other mirror. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package unixODBC.i386 0:2.2.11-7.1 set to be updated ---> Package unixODBC.x86_64 0:2.2.11-7.1 set to be updated ---> Package unixODBC-devel.i386 0:2.2.11-7.1 set to be updated ---> Package unixODBC-devel.x86_64 0:2.2.11-7.1 set to be updated ---> Package unixODBC-kde.i386 0:2.2.11-7.1 set to be updated ---> Package unixODBC-kde.x86_64 0:2.2.11-7.1 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: unixODBC i386 2.2.11-7.1 debug 832 k unixODBC x86_64 2.2.11-7.1 debug 835 k unixODBC-devel i386 2.2.11-7.1 debug 739 k unixODBC-devel x86_64 2.2.11-7.1 debug 796 k unixODBC-kde i386 2.2.11-7.1 debug 560 k unixODBC-kde x86_64 2.2.11-7.1 debug 595 k Transaction Summary ================================================================================ Install 6 Package(s) Upgrade 0 Package(s) Total download size: 4.3 M Downloading Packages: Error Downloading Packages: unixODBC-devel-2.2.11-7.1.i386: failure: CentOS/unixODBC-devel-2.2.11-7.1.i386.rpm from debug: [Errno 256] No more mirrors to try. unixODBC-devel-2.2.11-7.1.x86_64: failure: CentOS/unixODBC-devel-2.2.11-7.1.x86_64.rpm from debug: [Errno 256] No more mirrors to try. unixODBC-2.2.11-7.1.x86_64: failure: CentOS/unixODBC-2.2.11-7.1.x86_64.rpm from debug: [Errno 256] No more mirrors to try. unixODBC-kde-2.2.11-7.1.i386: failure: CentOS/unixODBC-kde-2.2.11-7.1.i386.rpm from debug: [Errno 256] No more mirrors to try. unixODBC-kde-2.2.11-7.1.x86_64: failure: CentOS/unixODBC-kde-2.2.11-7.1.x86_64.rpm from debug: [Errno 256] No more mirrors to try. unixODBC-2.2.11-7.1.i386: failure: CentOS/unixODBC-2.2.11-7.1.i386.rpm from debug: [Errno 256] No more mirrors to try.
Salin selepas log masuk
yum list查看，出现错误提示
***************************************[root@node1 ~]# yum list Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile file:///cd1/repodata/repomd.xml: [Errno 5] OSError: [Errno 2] No such file or directory: '/cd1/repodata/repomd.xml' Trying other mirror. Installed Packages Deployment_Guide-zh-CN.noarch 5.2-11.el5.centos installed Deployment_Guide-zh-TW.noarch 5.2-11.el5.centos installed GConf2.i386 2.14.0-9.el5 installed GConf2.x86_64 2.14.0-9.el5 installed GConf2-devel.i386 2.14.0-9.el5 installed GConf2-devel.x86_64 2.14.0-9.el5 installed MAKEDEV.x86_64 3.23-1.2 installed NetworkManager.i386 1:0.7.0-10.el5_5.2 installed NetworkManager.x86_64 1:0.7.0-10.el5_5.2 installed NetworkManager-glib.i386 1:0.7.0-10.el5_5.2 installed NetworkManager-glib.x86_64 1:0.7.0-10.el5_5.2 installed NetworkManager-gnome.x86_64 1:0.7.0-10.el5_5.2 installed ORBit2.i386 2.14.3-5.el5 installed ORBit2.x86_64 2.14.3-5.el5 installed ORBit2-devel.i386 2.14.3-5.el5 installed ORBit2-devel.x86_64 2.14.3-5.el5 installed OpenIPMI.x86_64 2.0.16-11.el5 installed OpenIPMI-libs.x86_64 2.0.16-11.el5 installed PyQt.x86_64 3.16-4 installed PyQt-devel.i386 3.16-4 installed ...... ...... ...... yum-security.noarch 1.1.16-14.el5.centos.1 debug yum-tmprepo.noarch 1.1.16-14.el5.centos.1 debug yum-tsflags.noarch 1.1.16-14.el5.centos.1 debug yum-updateonboot.noarch 1.1.16-14.el5.centos.1 debug yum-upgrade-helper.noarch 1.1.16-14.el5.centos.1 debug yum-utils.noarch 1.1.16-14.el5.centos.1 debug yum-verify.noarch 1.1.16-14.el5.centos.1 debug yum-versionlock.noarch 1.1.16-14.el5.centos.1 debug zsh-html.x86_64 4.2.6-5.el5 debug
Salin selepas log masuk
检查安装包：竟无一安装包安装成功
***************************************[grid@node1 grid]$ ./runcluvfy.sh stage -pre crsinst -n node1,node2 -fixup -verbose 缺失的包： Check: Package existence for "libaio-devel-0.3.105 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing libaio-devel-0.3.105 (i386) failed node1 missing libaio-devel-0.3.105 (i386) failed Result: Package existence check failed for "libaio-devel-0.3.105 (i386)" Check: Package existence for "libaio-devel-0.3.105 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing libaio-devel-0.3.105 (x86_64) failed node1 missing libaio-devel-0.3.105 (x86_64) failed Result: Package existence check failed for "libaio-devel-0.3.105 (x86_64)" Check: Package existence for "sysstat-5.0.5" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing sysstat-5.0.5 failed node1 missing sysstat-5.0.5 failed Result: Package existence check failed for "sysstat-5.0.5" Check: Package existence for "unixODBC-2.2.11 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-2.2.11 (i386) failed node1 missing unixODBC-2.2.11 (i386) failed Result: Package existence check failed for "unixODBC-2.2.11 (i386)" Check: Package existence for "unixODBC-2.2.11 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-2.2.11 (x86_64) failed node1 missing unixODBC-2.2.11 (x86_64) failed Result: Package existence check failed for "unixODBC-2.2.11 (x86_64)" Check: Package existence for "unixODBC-devel-2.2.11 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-devel-2.2.11 (i386) failed node1 missing unixODBC-devel-2.2.11 (i386) failed Result: Package existence check failed for "unixODBC-devel-2.2.11 (i386)" Check: Package existence for "unixODBC-devel-2.2.11 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing unixODBC-devel-2.2.11 (x86_64) failed node1 missing unixODBC-devel-2.2.11 (x86_64) failed Result: Package existence check failed for "unixODBC-devel-2.2.11 (x86_64)" Check: Package existence for "pdksh-5.2.14" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 missing pdksh-5.2.14 failed node1 missing pdksh-5.2.14 failed Result: Package existence check failed for "pdksh-5.2.14"
Salin selepas log masuk
假意的yum安装
***************************************由于没有任何一个包安装成功，怀疑yum配置有问题，同样怀疑之前看到的相关包安装的信息似乎不正确。
于是查看CRT日志，如下所示：在初始处已经提示错误的路径！！！
问题找到了！
[root@node1 ~]# yum install libaio* -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile file:///cd1/repodata/repomd.xml: [Errno 5] OSError: [Errno 2] No such file or directory: '/cd1/repodata/repomd.xml' Trying other mirror. Setting up Install Process Package libaio-0.3.106-5.x86_64 already installed and latest version Package libaio-0.3.106-5.i386 already installed and latest version Resolving Dependencies --> Running transaction check ---> Package libaio-devel.i386 0:0.3.106-5 set to be updated ---> Package libaio-devel.x86_64 0:0.3.106-5 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: libaio-devel i386 0.3.106-5 debug 12 k libaio-devel x86_64 0.3.106-5 debug 11 k Transaction Summary ================================================================================ Install 2 Package(s) Upgrade 0 Package(s) Total download size: 23 k Downloading Packages: Error Downloading Packages: libaio-devel-0.3.106-5.i386: failure: CentOS/libaio-devel-0.3.106-5.i386.rpm from debug: [Errno 256] No more mirrors to try. libaio-devel-0.3.106-5.x86_64: failure: CentOS/libaio-devel-0.3.106-5.x86_64.rpm from debug: [Errno 256] No more mirrors to try. [root@node1 ~]# yum install syssta* -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile file:///cd1/repodata/repomd.xml: [Errno 5] OSError: [Errno 2] No such file or directory: '/cd1/repodata/repomd.xml' Trying other mirror. Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package sysstat.x86_64 0:7.0.2-3.el5_5.1 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: sysstat x86_64 7.0.2-3.el5_5.1 debug 174 k Transaction Summary ================================================================================ Install 1 Package(s) Upgrade 0 Package(s) Total download size: 174 k Downloading Packages: Error Downloading Packages: sysstat-7.0.2-3.el5_5.1.x86_64: failure: CentOS/sysstat-7.0.2-3.el5_5.1.x86_64.rpm from debug: [Errno 256] No more mirrors to try.
Salin selepas log masuk
检查yum指向光盘的路径yum.repo文件
***************************************检查发现，路径配置没有问题
[root@node1 yum.repos.d]# cat /etc/yum.repos.d/yum.repo # CentOS-Base.repo # # The mirror system uses the connecting IP address of the client and the # update status of each mirror to pick mirrors that are updated to and # geographically close to the client. You should use this for CentOS updates # unless you are manually picking other mirrors. # # All debug packages from all the various CentOS-5 releases # are merged into a single repo, split by BaseArch # # Note: packages in the debuginfo repo are currently not signed # [debug] name=CentOS-5 - Debuginfo #baseurl=http://debuginfo.centos.org/5/$basearch/ baseurl=file:///cd1 gpgcheck=0 #gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-5 enabled=1
Salin selepas log masuk
检查光盘是否被mount到指定路径
***************************************果然不出所料，没有对光盘进行mount，如下所示：
[root@node1 yum.repos.d]# df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 35G 8.4G 25G 26% / /dev/sda1 487M 24M 438M 6% /boot tmpfs 872M 0 872M 0% /dev/shm none 872M 104K 872M 1% /var/lib/xenstored /dev/hdc 4.0G 4.0G 0 100% /media/CentOS_5.6_Final [root@node1 yum.repos.d]# mount /dev/hdc /cd1 --mount光盘
Salin selepas log masuk
安装缺失的包
***************************************操作语句：
[root@node1 ~]# yum install libaio* -y
[root@node1 ~]# yum install syssta* -y
[root@node1 ~]# yum install unixO* -y
[root@node1 ~]# yum install pdk* -y
过程信息如下： [root@node1 /]# yum install libaio* -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Install Process Package libaio-0.3.106-5.x86_64 already installed and latest version Package libaio-0.3.106-5.i386 already installed and latest version Resolving Dependencies --> Running transaction check ---> Package libaio-devel.i386 0:0.3.106-5 set to be updated ---> Package libaio-devel.x86_64 0:0.3.106-5 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: libaio-devel i386 0.3.106-5 debug 12 k libaio-devel x86_64 0.3.106-5 debug 11 k Transaction Summary ================================================================================ Install 2 Package(s) Upgrade 0 Package(s) Total download size: 23 k Downloading Packages: -------------------------------------------------------------------------------- Total 1.1 MB/s | 23 kB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : libaio-devel 1/2 Installing : libaio-devel 2/2 Installed: libaio-devel.i386 0:0.3.106-5 libaio-devel.x86_64 0:0.3.106-5 Complete! [root@node1 /]# yum install syssta* -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package sysstat.x86_64 0:7.0.2-3.el5_5.1 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: sysstat x86_64 7.0.2-3.el5_5.1 debug 174 k Transaction Summary ================================================================================ Install 1 Package(s) Upgrade 0 Package(s) Total download size: 174 k Downloading Packages: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : sysstat 1/1 Installed: sysstat.x86_64 0:7.0.2-3.el5_5.1 Complete! [root@node1 /]# yum install unixO* -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package unixODBC.i386 0:2.2.11-7.1 set to be updated ---> Package unixODBC.x86_64 0:2.2.11-7.1 set to be updated ---> Package unixODBC-devel.i386 0:2.2.11-7.1 set to be updated ---> Package unixODBC-devel.x86_64 0:2.2.11-7.1 set to be updated ---> Package unixODBC-kde.i386 0:2.2.11-7.1 set to be updated ---> Package unixODBC-kde.x86_64 0:2.2.11-7.1 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: unixODBC i386 2.2.11-7.1 debug 832 k unixODBC x86_64 2.2.11-7.1 debug 835 k unixODBC-devel i386 2.2.11-7.1 debug 739 k unixODBC-devel x86_64 2.2.11-7.1 debug 796 k unixODBC-kde i386 2.2.11-7.1 debug 560 k unixODBC-kde x86_64 2.2.11-7.1 debug 595 k Transaction Summary ================================================================================ Install 6 Package(s) Upgrade 0 Package(s) Total download size: 4.3 M Downloading Packages: -------------------------------------------------------------------------------- Total 456 MB/s | 4.3 MB 00:00 Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : unixODBC 1/6 Installing : unixODBC 2/6 Installing : unixODBC-devel 3/6 Installing : unixODBC-devel 4/6 Installing : unixODBC-kde 5/6 Installing : unixODBC-kde 6/6 Installed: unixODBC.i386 0:2.2.11-7.1 unixODBC.x86_64 0:2.2.11-7.1 unixODBC-devel.i386 0:2.2.11-7.1 unixODBC-devel.x86_64 0:2.2.11-7.1 unixODBC-kde.i386 0:2.2.11-7.1 unixODBC-kde.x86_64 0:2.2.11-7.1 Complete! [root@node1 /]# yum install pdk* -y Loaded plugins: fastestmirror Loading mirror speeds from cached hostfile Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package pdksh.x86_64 0:5.2.14-36.el5 set to be updated --> Finished Dependency Resolution Dependencies Resolved ================================================================================ Package Arch Version Repository Size ================================================================================ Installing: pdksh x86_64 5.2.14-36.el5 debug 205 k Transaction Summary ================================================================================ Install 1 Package(s) Upgrade 0 Package(s) Total download size: 205 k Downloading Packages: Running rpm_check_debug Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction Installing : pdksh 1/1 Installed: pdksh.x86_64 0:5.2.14-36.el5 Complete!
Salin selepas log masuk
复查安装的包：全部通过检查
***************************************[grid@node1 grid]$ ./runcluvfy.sh stage -pre crsinst -n node1,node2 -fixup -verbose Performing pre-checks for cluster services setup Checking node reachability... Check: Node reachability from node "node1" Destination Node Reachable? ------------------------------------ ------------------------ node1 yes node2 yes Result: Node reachability check passed from node "node1" Checking user equivalence... Check: User equivalence for user "grid" Node Name Comment ------------------------------------ ------------------------ node2 passed node1 passed Result: User equivalence check passed for user "grid" Checking node connectivity... Checking hosts config file... Node Name Status Comment ------------ ------------------------ ------------------------ node2 passed node1 passed Verification of the hosts config file successful Interface information for node "node2" Name IP Address Subnet Gateway Def. Gateway HW Address MTU ------ --------------- --------------- --------------- --------------- ----------------- ------ eth1 10.53.105.23 10.53.105.0 0.0.0.0 10.53.105.1 08:00:27:65:54:09 1500 virbr0 192.168.122.1 192.168.122.0 0.0.0.0 10.53.105.1 00:00:00:00:00:00 1500 eth0 10.53.105.21 10.53.105.0 0.0.0.0 10.53.105.1 08:00:27:4F:6D:90 1500 Interface information for node "node1" Name IP Address Subnet Gateway Def. Gateway HW Address MTU ------ --------------- --------------- --------------- --------------- ----------------- ------ eth1 10.53.105.22 10.53.105.0 0.0.0.0 10.53.105.1 08:00:27:BE:74:D3 1500 virbr0 192.168.122.1 192.168.122.0 0.0.0.0 10.53.105.1 00:00:00:00:00:00 1500 eth0 10.53.105.20 10.53.105.0 0.0.0.0 10.53.105.1 08:00:27:37:EE:50 1500 Check: Node connectivity of subnet "10.53.105.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- node2:eth1 node2:eth0 yes node2:eth1 node1:eth1 yes node2:eth1 node1:eth0 yes node2:eth0 node1:eth1 yes node2:eth0 node1:eth0 yes node1:eth1 node1:eth0 yes Result: Node connectivity passed for subnet "10.53.105.0" with node(s) node2,node1 Check: TCP connectivity of subnet "10.53.105.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- node1:10.53.105.22 node2:10.53.105.23 passed node1:10.53.105.22 node2:10.53.105.21 passed node1:10.53.105.22 node1:10.53.105.20 passed Result: TCP connectivity check passed for subnet "10.53.105.0" Check: Node connectivity of subnet "192.168.122.0" Source Destination Connected? ------------------------------ ------------------------------ ---------------- node2:virbr0 node1:virbr0 yes Result: Node connectivity passed for subnet "192.168.122.0" with node(s) node2,node1 Check: TCP connectivity of subnet "192.168.122.0" Result: TCP connectivity check failed for subnet "192.168.122.0" Interfaces found on subnet "10.53.105.0" that are likely candidates for VIP are: node2 eth1:10.53.105.23 node1 eth1:10.53.105.22 Interfaces found on subnet "10.53.105.0" that are likely candidates for VIP are: node2 eth0:10.53.105.21 node1 eth0:10.53.105.20 Interfaces found on subnet "192.168.122.0" that are likely candidates for a private interconnect are: node2 virbr0:192.168.122.1 node1 virbr0:192.168.122.1 Result: Node connectivity check passed Check: Total memory Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 1.7GB (1785856.0KB) 1.5GB (1572864.0KB) passed node1 1.7GB (1785856.0KB) 1.5GB (1572864.0KB) passed Result: Total memory check passed Check: Available memory Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 1.45GB (1523976.0KB) 50MB (51200.0KB) passed node1 1.31GB (1375400.0KB) 50MB (51200.0KB) passed Result: Available memory check passed Check: Swap space Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 4GB (4192956.0KB) 2.55GB (2678784.0KB) passed node1 4GB (4192956.0KB) 2.55GB (2678784.0KB) passed Result: Swap space check passed Check: Free disk space for "node2:/tmp" Path Node Name Mount point Available Required Comment ---------------- ------------ ------------ ------------ ------------ ------------ /tmp node2 / 29.24GB 1GB passed Result: Free disk space check passed for "node2:/tmp" Check: Free disk space for "node1:/tmp" Path Node Name Mount point Available Required Comment ---------------- ------------ ------------ ------------ ------------ ------------ /tmp node1 / 25.45GB 1GB passed Result: Free disk space check passed for "node1:/tmp" Check: User existence for "grid" Node Name Status Comment ------------ ------------------------ ------------------------ node2 exists passed node1 exists passed Result: User existence check passed for "grid" Check: Group existence for "oinstall" Node Name Status Comment ------------ ------------------------ ------------------------ node2 exists passed node1 exists passed Result: Group existence check passed for "oinstall" Check: Group existence for "dba" Node Name Status Comment ------------ ------------------------ ------------------------ node2 exists passed node1 exists passed Result: Group existence check passed for "dba" Check: Membership of user "grid" in group "oinstall" [as Primary] Node Name User Exists Group Exists User in Group Primary Comment ---------------- ------------ ------------ ------------ ------------ ------------ node2 yes yes yes yes passed node1 yes yes yes yes passed Result: Membership check for user "grid" in group "oinstall" [as Primary] passed Check: Membership of user "grid" in group "dba" Node Name User Exists Group Exists User in Group Comment ---------------- ------------ ------------ ------------ ---------------- node2 yes yes yes passed node1 yes yes yes passed Result: Membership check for user "grid" in group "dba" passed Check: Run level Node Name run level Required Comment ------------ ------------------------ ------------------------ ---------- node2 5 3,5 passed node1 5 3,5 passed Result: Run level check passed Check: Hard limits for "maximum open file descriptors" Node Name Type Available Required Comment ---------------- ------------ ------------ ------------ ---------------- node2 hard 65536 65536 passed node1 hard 65536 65536 passed Result: Hard limits check passed for "maximum open file descriptors" Check: Soft limits for "maximum open file descriptors" Node Name Type Available Required Comment ---------------- ------------ ------------ ------------ ---------------- node2 soft 1024 1024 passed node1 soft 1024 1024 passed Result: Soft limits check passed for "maximum open file descriptors" Check: Hard limits for "maximum user processes" Node Name Type Available Required Comment ---------------- ------------ ------------ ------------ ---------------- node2 hard 16384 16384 passed node1 hard 16384 16384 passed Result: Hard limits check passed for "maximum user processes" Check: Soft limits for "maximum user processes" Node Name Type Available Required Comment ---------------- ------------ ------------ ------------ ---------------- node2 soft 2047 2047 passed node1 soft 2047 2047 passed Result: Soft limits check passed for "maximum user processes" Check: System architecture Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 x86_64 x86_64 passed node1 x86_64 x86_64 passed Result: System architecture check passed Check: Kernel version Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 2.6.18-238.el5xen 2.6.9 passed node1 2.6.18-238.el5xen 2.6.9 passed Result: Kernel version check passed Check: Kernel parameter for "semmsl" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 250 250 passed node1 250 250 passed Result: Kernel parameter check passed for "semmsl" Check: Kernel parameter for "semmns" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 32000 32000 passed node1 32000 32000 passed Result: Kernel parameter check passed for "semmns" Check: Kernel parameter for "semopm" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 100 100 passed node1 100 100 passed Result: Kernel parameter check passed for "semopm" Check: Kernel parameter for "semmni" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 128 128 passed node1 128 128 passed Result: Kernel parameter check passed for "semmni" Check: Kernel parameter for "shmmax" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 536870912 536870912 passed node1 536870912 536870912 passed Result: Kernel parameter check passed for "shmmax" Check: Kernel parameter for "shmmni" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 4096 4096 passed node1 4096 4096 passed Result: Kernel parameter check passed for "shmmni" Check: Kernel parameter for "shmall" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 2097152 2097152 passed node1 2097152 2097152 passed Result: Kernel parameter check passed for "shmall" Check: Kernel parameter for "file-max" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 6815744 6815744 passed node1 6815744 6815744 passed Result: Kernel parameter check passed for "file-max" Check: Kernel parameter for "ip_local_port_range" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 between 9000 & 65500 between 9000 & 65500 passed node1 between 9000 & 65500 between 9000 & 65500 passed Result: Kernel parameter check passed for "ip_local_port_range" Check: Kernel parameter for "rmem_default" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 262144 262144 passed node1 262144 262144 passed Result: Kernel parameter check passed for "rmem_default" Check: Kernel parameter for "rmem_max" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 4194304 4194304 passed node1 4194304 4194304 passed Result: Kernel parameter check passed for "rmem_max" Check: Kernel parameter for "wmem_default" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 262144 262144 passed node1 262144 262144 passed Result: Kernel parameter check passed for "wmem_default" Check: Kernel parameter for "wmem_max" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 1048586 1048576 passed node1 1048586 1048576 passed Result: Kernel parameter check passed for "wmem_max" Check: Kernel parameter for "aio-max-nr" Node Name Configured Required Comment ------------ ------------------------ ------------------------ ---------- node2 1048576 1048576 passed node1 1048576 1048576 passed Result: Kernel parameter check passed for "aio-max-nr" Check: Package existence for "make-3.80" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 make-3.81-3.el5 make-3.80 passed node1 make-3.81-3.el5 make-3.80 passed Result: Package existence check passed for "make-3.80" Check: Package existence for "binutils-2.15.92.0.2" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 binutils-2.17.50.0.6-14.el5 binutils-2.15.92.0.2 passed node1 binutils-2.17.50.0.6-14.el5 binutils-2.15.92.0.2 passed Result: Package existence check passed for "binutils-2.15.92.0.2" Check: Package existence for "gcc-3.4.6" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 gcc-4.1.2-50.el5 gcc-3.4.6 passed node1 gcc-4.1.2-50.el5 gcc-3.4.6 passed Result: Package existence check passed for "gcc-3.4.6" Check: Package existence for "libaio-0.3.105 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libaio-0.3.106-5 (i386) libaio-0.3.105 (i386) passed node1 libaio-0.3.106-5 (i386) libaio-0.3.105 (i386) passed Result: Package existence check passed for "libaio-0.3.105 (i386)" Check: Package existence for "libaio-0.3.105 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libaio-0.3.106-5 (x86_64) libaio-0.3.105 (x86_64) passed node1 libaio-0.3.106-5 (x86_64) libaio-0.3.105 (x86_64) passed Result: Package existence check passed for "libaio-0.3.105 (x86_64)" Check: Package existence for "glibc-2.3.4-2.41 (i686)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 glibc-2.5-58 (i686) glibc-2.3.4-2.41 (i686) passed node1 glibc-2.5-58 (i686) glibc-2.3.4-2.41 (i686) passed Result: Package existence check passed for "glibc-2.3.4-2.41 (i686)" Check: Package existence for "glibc-2.3.4-2.41 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 glibc-2.5-58 (x86_64) glibc-2.3.4-2.41 (x86_64) passed node1 glibc-2.5-58 (x86_64) glibc-2.3.4-2.41 (x86_64) passed Result: Package existence check passed for "glibc-2.3.4-2.41 (x86_64)" Check: Package existence for "compat-libstdc++-33-3.2.3 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 compat-libstdc++-33-3.2.3-61 (i386) compat-libstdc++-33-3.2.3 (i386) passed node1 compat-libstdc++-33-3.2.3-61 (i386) compat-libstdc++-33-3.2.3 (i386) passed Result: Package existence check passed for "compat-libstdc++-33-3.2.3 (i386)" Check: Package existence for "compat-libstdc++-33-3.2.3 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 compat-libstdc++-33-3.2.3-61 (x86_64) compat-libstdc++-33-3.2.3 (x86_64) passed node1 compat-libstdc++-33-3.2.3-61 (x86_64) compat-libstdc++-33-3.2.3 (x86_64) passed Result: Package existence check passed for "compat-libstdc++-33-3.2.3 (x86_64)" Check: Package existence for "elfutils-libelf-0.97 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 elfutils-libelf-0.137-3.el5 (x86_64) elfutils-libelf-0.97 (x86_64) passed node1 elfutils-libelf-0.137-3.el5 (x86_64) elfutils-libelf-0.97 (x86_64) passed Result: Package existence check passed for "elfutils-libelf-0.97 (x86_64)" Check: Package existence for "elfutils-libelf-devel-0.97" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 elfutils-libelf-devel-0.137-3.el5 elfutils-libelf-devel-0.97 passed node1 elfutils-libelf-devel-0.137-3.el5 elfutils-libelf-devel-0.97 passed Result: Package existence check passed for "elfutils-libelf-devel-0.97" Check: Package existence for "glibc-common-2.3.4" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 glibc-common-2.5-58 glibc-common-2.3.4 passed node1 glibc-common-2.5-58 glibc-common-2.3.4 passed Result: Package existence check passed for "glibc-common-2.3.4" Check: Package existence for "glibc-devel-2.3.4 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 glibc-devel-2.5-58 (x86_64) glibc-devel-2.3.4 (x86_64) passed node1 glibc-devel-2.5-58 (x86_64) glibc-devel-2.3.4 (x86_64) passed Result: Package existence check passed for "glibc-devel-2.3.4 (x86_64)" Check: Package existence for "glibc-headers-2.3.4" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 glibc-headers-2.5-58 glibc-headers-2.3.4 passed node1 glibc-headers-2.5-58 glibc-headers-2.3.4 passed Result: Package existence check passed for "glibc-headers-2.3.4" Check: Package existence for "gcc-c++-3.4.6" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 gcc-c++-4.1.2-50.el5 gcc-c++-3.4.6 passed node1 gcc-c++-4.1.2-50.el5 gcc-c++-3.4.6 passed Result: Package existence check passed for "gcc-c++-3.4.6" Check: Package existence for "libaio-devel-0.3.105 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libaio-devel-0.3.106-5 (i386) libaio-devel-0.3.105 (i386) passed node1 libaio-devel-0.3.106-5 (i386) libaio-devel-0.3.105 (i386) passed Result: Package existence check passed for "libaio-devel-0.3.105 (i386)" Check: Package existence for "libaio-devel-0.3.105 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libaio-devel-0.3.106-5 (x86_64) libaio-devel-0.3.105 (x86_64) passed node1 libaio-devel-0.3.106-5 (x86_64) libaio-devel-0.3.105 (x86_64) passed Result: Package existence check passed for "libaio-devel-0.3.105 (x86_64)" Check: Package existence for "libgcc-3.4.6 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libgcc-4.1.2-50.el5 (i386) libgcc-3.4.6 (i386) passed node1 libgcc-4.1.2-50.el5 (i386) libgcc-3.4.6 (i386) passed Result: Package existence check passed for "libgcc-3.4.6 (i386)" Check: Package existence for "libgcc-3.4.6 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libgcc-4.1.2-50.el5 (x86_64) libgcc-3.4.6 (x86_64) passed node1 libgcc-4.1.2-50.el5 (x86_64) libgcc-3.4.6 (x86_64) passed Result: Package existence check passed for "libgcc-3.4.6 (x86_64)" Check: Package existence for "libstdc++-3.4.6 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libstdc++-4.1.2-50.el5 (i386) libstdc++-3.4.6 (i386) passed node1 libstdc++-4.1.2-50.el5 (i386) libstdc++-3.4.6 (i386) passed Result: Package existence check passed for "libstdc++-3.4.6 (i386)" Check: Package existence for "libstdc++-3.4.6 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libstdc++-4.1.2-50.el5 (x86_64) libstdc++-3.4.6 (x86_64) passed node1 libstdc++-4.1.2-50.el5 (x86_64) libstdc++-3.4.6 (x86_64) passed Result: Package existence check passed for "libstdc++-3.4.6 (x86_64)" Check: Package existence for "libstdc++-devel-3.4.6 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 libstdc++-devel-4.1.2-50.el5 (x86_64) libstdc++-devel-3.4.6 (x86_64) passed node1 libstdc++-devel-4.1.2-50.el5 (x86_64) libstdc++-devel-3.4.6 (x86_64) passed Result: Package existence check passed for "libstdc++-devel-3.4.6 (x86_64)" Check: Package existence for "sysstat-5.0.5" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 sysstat-7.0.2-3.el5_5.1 sysstat-5.0.5 passed node1 sysstat-7.0.2-3.el5_5.1 sysstat-5.0.5 passed Result: Package existence check passed for "sysstat-5.0.5" Check: Package existence for "unixODBC-2.2.11 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 unixODBC-2.2.11-7.1 (i386) unixODBC-2.2.11 (i386) passed node1 unixODBC-2.2.11-7.1 (i386) unixODBC-2.2.11 (i386) passed Result: Package existence check passed for "unixODBC-2.2.11 (i386)" Check: Package existence for "unixODBC-2.2.11 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 unixODBC-2.2.11-7.1 (x86_64) unixODBC-2.2.11 (x86_64) passed node1 unixODBC-2.2.11-7.1 (x86_64) unixODBC-2.2.11 (x86_64) passed Result: Package existence check passed for "unixODBC-2.2.11 (x86_64)" Check: Package existence for "unixODBC-devel-2.2.11 (i386)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 unixODBC-devel-2.2.11-7.1 (i386) unixODBC-devel-2.2.11 (i386) passed node1 unixODBC-devel-2.2.11-7.1 (i386) unixODBC-devel-2.2.11 (i386) passed Result: Package existence check passed for "unixODBC-devel-2.2.11 (i386)" Check: Package existence for "unixODBC-devel-2.2.11 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 unixODBC-devel-2.2.11-7.1 (x86_64) unixODBC-devel-2.2.11 (x86_64) passed node1 unixODBC-devel-2.2.11-7.1 (x86_64) unixODBC-devel-2.2.11 (x86_64) passed Result: Package existence check passed for "unixODBC-devel-2.2.11 (x86_64)" Check: Package existence for "pdksh-5.2.14" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 pdksh-5.2.14-36.el5 pdksh-5.2.14 passed node1 pdksh-5.2.14-36.el5 pdksh-5.2.14 passed Result: Package existence check passed for "pdksh-5.2.14" Check: Package existence for "expat-1.95.7 (x86_64)" Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 expat-1.95.8-8.3.el5_5.3 (x86_64) expat-1.95.7 (x86_64) passed node1 expat-1.95.8-8.3.el5_5.3 (x86_64) expat-1.95.7 (x86_64) passed Result: Package existence check passed for "expat-1.95.7 (x86_64)" Checking for multiple users with UID value 0 Result: Check for multiple users with UID value 0 passed Check: Current group ID Result: Current group ID check passed Checking Core file name pattern consistency... Core file name pattern consistency check passed. Checking to make sure user "grid" is not in "root" group Node Name Status Comment ------------ ------------------------ ------------------------ node2 does not exist passed node1 does not exist passed Result: User "grid" is not part of "root" group. Check passed Check default user file creation mask Node Name Available Required Comment ------------ ------------------------ ------------------------ ---------- node2 0022 0022 passed node1 0022 0022 passed Result: Default user file creation mask check passed Starting Clock synchronization checks using Network Time Protocol(NTP)... NTP Configuration file check started... Network Time Protocol(NTP) configuration file not found on any of the nodes. Oracle Cluster Time Synchronization Service(CTSS) can be used instead of NTP for time synchronization on the cluster nodes Result: Clock synchronization check using Network Time Protocol(NTP) passed Pre-check for cluster services setup was successful.
Salin selepas log masuk
***************************************
小结
***************************************其实这次错误非常低级，于是借此机会想了下无法安装包可能出现的几种情况：
1、rpm安装时缺少依赖关系；
2、安装包版本不对；
3、yum路径配置不正确；
4、yum配置的路径没有mount上光盘信息；
5、使用yum时注意包名的书写格式：例如：# yum install libaio* -y。
***********************************************声明**********************************************
原创作品，出自 “深蓝的blog” 博客，欢迎转载，转载时请务必注明出处，否则追究版权法律责任。
表述有错误之处，请您留言或邮件（hyldba@163.com）指明，不胜感激。
本文转载必须保留此处：http://blog.csdn.net/huangyanlong/article/details/39227577
深蓝的blog：http://blog.csdn.net/huangyanlong
***************************************************************************************************
Kenyataan Laman Web ini
Kandungan artikel ini disumbangkan secara sukarela oleh netizen, dan hak cipta adalah milik pengarang asal. Laman web ini tidak memikul tanggungjawab undang-undang yang sepadan. Jika anda menemui sebarang kandungan yang disyaki plagiarisme atau pelanggaran, sila hubungi admin@php.cn
Alat AI Hot
Undresser.AI Undress
Apl berkuasa AI untuk mencipta foto bogel yang realistik
AI Clothes Remover
Alat AI dalam talian untuk mengeluarkan pakaian daripada foto.
Undress AI Tool
Gambar buka pakaian secara percuma
Clothoff.io
Penyingkiran pakaian AI
AI Hentai Generator
Menjana ai hentai secara percuma.
Artikel Panas
R.E.P.O. Kristal tenaga dijelaskan dan apa yang mereka lakukan (kristal kuning)
3 minggu yang lalu
By 尊渡假赌尊渡假赌尊渡假赌
R.E.P.O. Tetapan grafik terbaik
3 minggu yang lalu
By 尊渡假赌尊渡假赌尊渡假赌
Assassin's Creed Shadows: Penyelesaian Riddle Seashell
1 minggu yang lalu
By DDD
R.E.P.O. Cara Memperbaiki Audio Jika anda tidak dapat mendengar sesiapa
3 minggu yang lalu
By 尊渡假赌尊渡假赌尊渡假赌
Di mana untuk mencari kad kunci kawalan kren di atomfall
1 minggu yang lalu
By DDD
Alat panas
Notepad++7.3.1
Editor kod yang mudah digunakan dan percuma
SublimeText3 versi Cina
Versi Cina, sangat mudah digunakan
Hantar Studio 13.0.1
Persekitaran pembangunan bersepadu PHP yang berkuasa
Dreamweaver CS6
Alat pembangunan web visual
SublimeText3 versi Mac
Perisian penyuntingan kod peringkat Tuhan (SublimeText3)
Topik panas
Tutorial CakePHP
1359
52
1359
52
Penyelesaian kepada masalah bahawa sistem Win11 tidak dapat memasang pek bahasa Cina
Mar 09, 2024 am 09:48 AM
Penyelesaian kepada masalah sistem Win11 tidak dapat memasang pek bahasa Cina Dengan pelancaran sistem Windows 11, ramai pengguna mula menaik taraf sistem pengendalian mereka untuk mengalami fungsi dan antara muka baharu. Walau bagaimanapun, sesetengah pengguna mendapati bahawa mereka tidak dapat memasang pek bahasa Cina selepas menaik taraf, yang menyusahkan pengalaman mereka. Dalam artikel ini, kami akan membincangkan sebab mengapa sistem Win11 tidak dapat memasang pek bahasa Cina dan menyediakan beberapa penyelesaian untuk membantu pengguna menyelesaikan masalah ini. Analisis sebab Pertama, mari kita menganalisis ketidakupayaan sistem Win11 untuk
Tidak dapat memasang tambahan tetamu dalam VirtualBox
Mar 10, 2024 am 09:34 AM
Anda mungkin tidak dapat memasang tambahan tetamu pada mesin maya dalam OracleVirtualBox. Apabila kita mengklik pada Devices>InstallGuestAdditionsCDImage, ia hanya membuang ralat seperti yang ditunjukkan di bawah: VirtualBox - Ralat: Tidak dapat memasukkan cakera maya C: Programming FilesOracleVirtualBoxVBoxGuestAdditions.iso ke dalam mesin ubuntu Dalam siaran ini kita akan memahami apa yang berlaku apabila anda Apa yang perlu dilakukan apabila anda tidak boleh memasang tambahan tetamu dalam VirtualBox. Tidak dapat memasang tambahan tetamu dalam VirtualBox Jika anda tidak boleh memasangnya dalam Virtua
Apakah yang perlu saya lakukan jika Baidu Netdisk berjaya dimuat turun tetapi tidak boleh dipasang?
Mar 13, 2024 pm 10:22 PM
Jika anda telah berjaya memuat turun fail pemasangan Baidu Netdisk, tetapi tidak dapat memasangnya seperti biasa, mungkin terdapat ralat dalam integriti fail perisian atau terdapat masalah dengan baki fail dan entri pendaftaran Biarkan tapak ini mengambil jaga ia untuk pengguna Mari perkenalkan analisis masalah yang Baidu Netdisk berjaya dimuat turun tetapi tidak boleh dipasang. Analisis masalah yang berjaya dimuat turun oleh Baidu Netdisk tetapi tidak dapat dipasang 1. Semak integriti fail pemasangan: Pastikan fail pemasangan yang dimuat turun lengkap dan tidak rosak. Anda boleh memuat turunnya semula atau cuba memuat turun fail pemasangan daripada sumber lain yang dipercayai. 2. Matikan perisian anti-virus dan tembok api: Sesetengah perisian anti-virus atau program tembok api mungkin menghalang program pemasangan daripada berjalan dengan betul. Cuba lumpuhkan atau keluar dari perisian anti-virus dan tembok api, kemudian jalankan semula pemasangan
Bagaimana untuk memasang apl Android pada Linux?
Mar 19, 2024 am 11:15 AM
Memasang aplikasi Android di Linux sentiasa menjadi kebimbangan ramai pengguna Terutamanya bagi pengguna Linux yang suka menggunakan aplikasi Android, adalah sangat penting untuk menguasai cara memasang aplikasi Android pada sistem Linux. Walaupun menjalankan aplikasi Android secara langsung pada Linux tidak semudah pada platform Android, dengan menggunakan emulator atau alatan pihak ketiga, kami masih boleh menikmati aplikasi Android di Linux dengan gembira. Berikut akan memperkenalkan cara memasang aplikasi Android pada sistem Linux.
Bagaimana untuk memasang Podman pada Ubuntu 24.04
Mar 22, 2024 am 11:26 AM
Jika anda telah menggunakan Docker, anda mesti memahami daemon, bekas dan fungsinya. Daemon ialah perkhidmatan yang berjalan di latar belakang apabila bekas sudah digunakan dalam mana-mana sistem. Podman ialah alat pengurusan percuma untuk mengurus dan mencipta bekas tanpa bergantung pada mana-mana daemon seperti Docker. Oleh itu, ia mempunyai kelebihan dalam menguruskan kontena tanpa memerlukan perkhidmatan backend jangka panjang. Selain itu, Podman tidak memerlukan kebenaran peringkat akar untuk digunakan. Panduan ini membincangkan secara terperinci cara memasang Podman pada Ubuntu24. Untuk mengemas kini sistem, kami perlu mengemas kini sistem terlebih dahulu dan membuka shell Terminal Ubuntu24. Semasa kedua-dua proses pemasangan dan peningkatan, kita perlu menggunakan baris arahan. yang mudah
Cara Memasang dan Menjalankan Apl Nota Ubuntu pada Ubuntu 24.04
Mar 22, 2024 pm 04:40 PM
Semasa belajar di sekolah menengah, sesetengah pelajar mengambil nota yang sangat jelas dan tepat, mengambil lebih banyak nota daripada yang lain dalam kelas yang sama. Bagi sesetengah orang, mencatat nota adalah hobi, manakala bagi yang lain, ia adalah satu keperluan apabila mereka mudah melupakan maklumat kecil tentang apa-apa perkara penting. Aplikasi NTFS Microsoft amat berguna untuk pelajar yang ingin menyimpan nota penting di luar kuliah biasa. Dalam artikel ini, kami akan menerangkan pemasangan aplikasi Ubuntu pada Ubuntu24. Mengemas kini Sistem Ubuntu Sebelum memasang pemasang Ubuntu, pada Ubuntu24 kita perlu memastikan bahawa sistem yang baru dikonfigurasikan telah dikemas kini. Kita boleh menggunakan "a" yang paling terkenal dalam sistem Ubuntu
Bagaimana untuk memasang tutorial pemasangan creo-creo
Mar 04, 2024 pm 10:30 PM
Ramai rakan pemula masih tidak tahu cara memasang creo, jadi editor di bawah akan membawakan tutorial yang berkaitan tentang pemasangan creo. Rakan yang memerlukan saya harap ia dapat membantu anda. 1. Buka pakej pemasangan yang dimuat turun dan cari folder Lesen, seperti yang ditunjukkan dalam rajah di bawah: 2. Kemudian salinnya ke direktori pada pemacu C, seperti yang ditunjukkan dalam rajah di bawah: 3. Klik dua kali untuk masuk dan lihat jika terdapat fail lesen, seperti yang ditunjukkan di bawah Seperti yang ditunjukkan dalam rajah: 4. Kemudian salin fail lesen ke fail ini, seperti yang ditunjukkan dalam rajah di bawah: 5. Dalam fail PROGRAMFILES pada pemacu C, buat folder PLC baharu, seperti yang ditunjukkan dalam rajah di bawah: 6. Salin fail lesen serta Klik masuk, seperti yang ditunjukkan dalam rajah di bawah: 7. Klik dua kali fail pemasangan program utama. Untuk memasang, tandai kotak untuk memasang perisian baharu.
Langkah terperinci untuk memasang bahasa Go pada komputer Win7
Mar 27, 2024 pm 02:00 PM
Langkah terperinci untuk memasang bahasa Go pada komputer Win7 Go (juga dikenali sebagai Golang) ialah bahasa pengaturcaraan sumber terbuka yang dibangunkan oleh Google Ia mudah, cekap dan mempunyai prestasi serentak yang sangat baik Ia sesuai untuk pembangunan perkhidmatan awan, aplikasi rangkaian dan sistem hujung belakang. Memasang bahasa Go pada komputer Win7 membolehkan anda memulakan bahasa dengan cepat dan mula menulis program Go. Berikut akan memperkenalkan secara terperinci langkah-langkah untuk memasang bahasa Go pada komputer Win7, dan melampirkan contoh kod tertentu. Langkah 1: Muat turun pakej pemasangan bahasa Go dan lawati tapak web rasmi Go
