新聞中心
解決Arch無法注冊(cè)問題:發(fā)現(xiàn)數(shù)據(jù)庫已登記

鐘山ssl適用于網(wǎng)站、小程序/APP、API接口等需要進(jìn)行數(shù)據(jù)傳輸應(yīng)用場(chǎng)景,ssl證書未來市場(chǎng)廣闊!成為創(chuàng)新互聯(lián)的ssl證書銷售渠道,可以享受市場(chǎng)價(jià)格4-6折優(yōu)惠!如果有意向歡迎電話聯(lián)系或者加微信:13518219792(備注:SSL證書合作)期待與您的合作!
Arch Linux是一款流行的Linux操作系統(tǒng)。它基于Rolling Release模型,意味著你可以持續(xù)獲得最新的軟件更新和系統(tǒng)改進(jìn)。但是,有時(shí)候,用戶會(huì)遇到一些問題,例如無法完成系統(tǒng)注冊(cè)。本文將向你介紹如何解決Arch無法注冊(cè)的問題,并告訴你如何發(fā)現(xiàn)數(shù)據(jù)庫已登記的解決方法。
1. 確認(rèn)網(wǎng)路連接是否暢通
在開始解決Arch無法注冊(cè)問題之前,更好先檢查一下網(wǎng)絡(luò)連接。 確保你的設(shè)備已連接到互聯(lián)網(wǎng),并且可以正常訪問網(wǎng)站。如果你無法訪問網(wǎng)站,那么你的操作系統(tǒng)也無法與注冊(cè)數(shù)據(jù)庫交互。你需要解決網(wǎng)絡(luò)問題以啟用系統(tǒng)注冊(cè)。
2. 查看 /var/log/pacman.log
如果網(wǎng)絡(luò)正常,但你仍然無法注冊(cè)Arch Linux,那么你可以查看 /var/log/pacman.log 文件,以檢查發(fā)生什么錯(cuò)誤。使用以下命令打開文件:
$ less /var/log/pacman.log
然后,搜索“ Registering ” ,看看是否出現(xiàn)任何錯(cuò)誤。如果你看到“ Fled to register system (…) ”的消息,那么你的Arch Linux操作系統(tǒng)可能已經(jīng)被注冊(cè)過了。
3. 使用pacman-key工具
如果Arch Linux已經(jīng)注冊(cè)過了,并且你的系統(tǒng)認(rèn)為它沒有被注冊(cè),那么你需要使用pacman-key工具進(jìn)行修復(fù)。pacman-key 工具用于管理PACMAN軟件包管理器的密鑰環(huán)。密鑰環(huán)是一組用于識(shí)別和驗(yàn)證PACMAN軟件包的數(shù)字證書。
你需要以root用戶身份打開終端。然后運(yùn)行以下命令:
# pacman-key –init
這將初始化你的密鑰環(huán)。如果你的密鑰環(huán)已經(jīng)初始化過了,那么你可以跳過這一步。
接下來,從密鑰服務(wù)器導(dǎo)入Arch Linux密鑰:
# pacman-key –recv-keys 9741E8AC
然后,通過以下命令導(dǎo)入密鑰:
# pacman-key –lsign-key 9741E8AC
接下來,再次嘗試注冊(cè)系統(tǒng):
# pacman-key –init
現(xiàn)在,你應(yīng)該能夠成功注冊(cè)Arch Linux操作系統(tǒng)。
4. 在網(wǎng)站上手動(dòng)注冊(cè)系統(tǒng)
如果你仍然無法完成系統(tǒng)注冊(cè),那么你可以嘗試在Arch Linux網(wǎng)站上手動(dòng)注冊(cè)系統(tǒng)。你需要登錄Arch Linux帳戶。然后,點(diǎn)擊右上方的“ My Account ”,然后點(diǎn)擊“ Register System ” 。
在表單中,輸入你的系統(tǒng)信息(例如,系統(tǒng)的名稱、版本、CPU架構(gòu)等)。然后,點(diǎn)擊“ Register ”按鈕。這應(yīng)該會(huì)將你的系統(tǒng)信息添加到Arch Linux的注冊(cè)數(shù)據(jù)庫中。
Arch Linux是一款流行的Linux操作系統(tǒng)。當(dāng)你遇到無法注冊(cè)系統(tǒng)的問題時(shí),可能是由于系統(tǒng)已經(jīng)被注冊(cè)過了。你可以通過檢查網(wǎng)絡(luò)連接、查看PACMAN日志、使用pacman-key工具和手動(dòng)注冊(cè)系統(tǒng)來解決這個(gè)問題。希望這篇文章能幫助你解決Arch Linux無法進(jìn)行系統(tǒng)注冊(cè)的問題。
相關(guān)問題拓展閱讀:
- 10gRAC系列之使用srvctl管理RAC數(shù)據(jù)庫
10gRAC系列之使用srvctl管理RAC數(shù)據(jù)庫
srvctl即Server Control 是一個(gè)命令行工具 用以管理Oracle的RAC環(huán)境 srvctl在Oracle i中引入 Oracle g對(duì)其功能進(jìn)行了大大增強(qiáng)
在命令行下 使用 h參碧頃數(shù)可以察看srvctl支持的命令及參數(shù):
bash $ srvctl hUsage: srvctl Usage: srvctl add an i o
Usage: srvctl config databaseUsage: srvctl config database d Usage: srvctl config service d Usage: srvctl config nodeapps n Usage: srvctl config an Usage: srvctl config listener n Usage: srvctl disable database d
常用的命令主要如下: 使用srvctl status查看數(shù)據(jù)庫梁慧棗及實(shí)例狀態(tài)查看數(shù)據(jù)庫的狀態(tài)
bash $ srvctl status database d eygle Instance eygle is running on node db rac Instance eygle is running on node db rac
查看數(shù)據(jù)庫實(shí)例的狀態(tài)
bash $ srvctl status instance d eygle i eygle eygle Instance eygle is running on node db rac Instance eygle is running on node db rac
使用srvctl stop停止數(shù)據(jù)庫或?qū)嵗V箤?shí)例使用srvctl stop instance命令:
bash $ srvctl stop instance PRKO : Invalid mand line syntaxbash $ srvctl stop instance hUsage: srvctl stop instance d i d Unique name for the database i Comma separated instance names o Options to shutdown mand (e g normal transactional immediate or abort) c Connect string (default: / as sysdba) q Query connect string from standard input h Print usage
橡拆 在命令行發(fā)出如下命令
bash $ srvctl stop instance d eygle i eygle
在該節(jié)點(diǎn)的警告日志文件中就可以看到如下關(guān)閉信息:
Thu Dec : : Shutting down instance: further logons disabledThu Dec : : Stopping background process QMNCThu Dec : : Stopping background process CJQ Thu Dec : : Stopping background process MMNLThu Dec : : Stopping background process MMONThu Dec : : Shutting down instance (immediate)License high water mark = Thu Dec : : Stopping Job queue slave processesThu Dec : : Job queue slave processes stoppedThu Dec : : PMON failed to acquire latch see PMON dumpThu Dec : : ALTER DATABASE CLOSE NORMALThu Dec : : ON: disabling tx recoveryON: disabling cache recoveryThu Dec : : Shutting down archive processesArchiving is disabledArchive process shutdown avoided: activeThread closed at log sequence Successful close of redo thread Thu Dec : : Completed: ALTER DATABASE CLOSE NORMALThu Dec : : ALTER DATABASE DIOUNTCompleted: ALTER DATABASE DIOUNTARCH: Archival disabled due to shutdown: Shutting down archive processesArchiving is disabledArchive process shutdown avoided: activeARCH: Archival disabled due to shutdown: Shutting down archive processesArchiving is disabledArchive process shutdown avoided: activeThu Dec : : freeing rdom
停止數(shù)據(jù)庫使用srvctl stop database命令
bash $ srvctl stop database hUsage: srvctl stop database d d Unique name for the database o Options to shutdown mand (e g normal transactional immediate or abort) c Connect string (default: / as sysdba) q Query connect string from standard input h Print usage
發(fā)出如下命令后 數(shù)據(jù)庫停止:
bash $ srvctl stop database d eygle
日志文件記錄如下過程:
Thu Dec : : Shutting down instance: further logons disabledThu Dec : : Stopping background process CJQ Thu Dec : : Stopping background process QMNCThu Dec : : Stopping background process MMNLThu Dec : : Stopping background process MMONThu Dec : : Shutting down instance (immediate)License high water mark = Thu Dec : : Stopping Job queue slave processesThu Dec : : Job queue slave processes stoppedThu Dec : : PMON failed to acquire latch see PMON dumpPMON failed to acquire latch see PMON dumpPMON failed to acquire latch see PMON dumpThu Dec : : PMON failed to acquire latch see PMON dumpThu Dec : : ALTER DATABASE CLOSE NORMALThu Dec : : ON: disabling tx recoveryON: disabling cache recoveryThu Dec : : Shutting down archive processesArchiving is disabledArchive process shutdown avoided: activeThread closed at log sequence Successful close of redo thread Thu Dec : : Completed: ALTER DATABASE CLOSE NORMALThu Dec : : ALTER DATABASE DIOUNTCompleted: ALTER DATABASE DIOUNTARCH: Archival disabled due to shutdown: Shutting down archive processesArchiving is disabledArchive process shutdown avoided: activeARCH: Archival disabled due to shutdown: Shutting down archive processesArchiving is disabledArchive process shutdown avoided: activeThu Dec : : freeing rdom
使用srvctl start命令啟動(dòng)數(shù)據(jù)庫或?qū)嵗褂胹rvctl start database可以啟動(dòng)數(shù)據(jù)庫的所有實(shí)例:
bash $ srvctl start database d eygle
在之一個(gè)節(jié)點(diǎn) 警告日志記錄了如下啟動(dòng)過程
Thu Dec : : Starting ORACLE instance (normal)LICENSE_MAX_SESSION = LICENSE_SESSIONS_WARNING = Interface type bge configured from OCR for use as a cluster interconnectInterface type bge configured from OCR for use as a cluster interconnectInterface type bge configured from OCR for use as a public interfacePicked latch free SCN scheme Using LOG_ARCHIVE_DEST_ parameter default value as /opt/oracle/product/ /db/dbs/archAutotune of undo retention is turned on LICENSE_MAX_USERS = SYS auditing is disabledksdpec: called for event prior to event group initializationStarting up ORACLE RDBMS Version: System parameters with non default values:processes = __shared_pool_size = __large_pool_size = __java_pool_size = __streams_pool_size = spfile = /dev/vx/rdsk/xxfdg/spfilesga_target = control_files = /dev/vx/rdsk/xxfdg/ctlfile /dev/vx/rdsk/xxfdg/ctlfile db_block_size = __db_cache_size = patible = db_file_multiblock_read_count= cluster_database = TRUEcluster_database_instances= thread = instance_number = undo_management = AUTOundo_tablespace = UNDOTBS remote_login_passwordfile= EXCLUSIVEdb_domain = remote_listener = LISTENERS_EYGLEjob_queue_processes = background_dump_dest = /opt/oracle/admin/eygle/bdumpuser_dump_dest = /opt/oracle/admin/eygle/udumpcore_dump_dest = /opt/oracle/admin/eygle/cdumpaudit_file_dest = /opt/oracle/admin/eygle/adumpdb_name = eygleopen_cursors = pga_aggregate_target = Cluster munication is configured to use the following interface(s) for this instance Thu Dec : : cluster interconnect IPC version:Oracle UDP/IPIPC Vendor proto DIAG started with pid= OS id= PMON started with pid= OS id= PSP started with pid= OS id= LMON started with pid= OS id= Thu Dec : : WARNING: Failed to set buffer limit on IPC interconnect socketOracle requires that the SocketReceive buffer size be tunable upto MBPlease make sure the kernel parameterwhich limits SO_RCVBUF value set byapplications is atleast MBLMD started with pid= OS id= LMS started with pid= OS id= LMS started with pid= OS id= MMAN started with pid= OS id= DBW started with pid= OS id= LGWR started with pid= OS id= CKPT started with pid= OS id= ON started with pid= OS id= RECO started with pid= OS id= CJQ started with pid= OS id= MMON started with pid= OS id= MMNL started with pid= OS id= Thu Dec : : lmon registered with NM instance id (internal mem no )Thu Dec : : Reconfiguration started (old inc new inc )List of nodes: Global Resource Directory frozen* allocate domain invalid = TRUE Communication channels reestablishedMaster broadcasted resource hash value bitmapsNon local Process blocks cleaned outThu Dec : : LMS : GCS shadows cancelled closedThu Dec : : LMS : GCS shadows cancelled closedSet master node info Submitted all remote enqueue requestsDwn cvts replayed VALBLKs dubiousAll grantable enqueues grantedThu Dec : : LMS : GCS shadows traversed replayedThu Dec : : LMS : GCS shadows traversed replayedThu Dec : : Submitted all GCS remote cache requestsFix write in gcs resourcesReconfiguration pleteLCK started with pid= OS id= Thu Dec : : ALTER DATABASE MOUNTThu Dec : : This instance was first to mountSetting recovery target incarnation to Thu Dec : : Successful mount of redo thread with mount id Thu Dec : : Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)Completed: ALTER DATABASE MOUNTThu Dec : : ALTER DATABASE OPENThis instance was first to openPicked broadcast on mit scheme to generate SCNsThu Dec : : Thread advanced to log sequence Thread opened at log sequence Current log# seq# mem# : /dev/vx/rdsk/xxfdg/redo Successful open of redo thread Thu Dec : : MTTR advisory is disabled because FAST_START_MTTR_TARGET is not setThu Dec : : ON: enabling cache recoveryThu Dec : : Instance recovery: looking for dead threadsInstance recovery: lock domain invalid but no dead threadsThu Dec : : Successfully onlined Undo Tablespace Thu Dec : : ON: enabling tx recoveryThu Dec : : Database Characterset is ZHS GBKreplication_dependency_tracking turned off (no async multimaster replication found)Starting background process QMNCQMNC started with pid= OS id= Thu Dec : : Completed: ALTER DATABASE OPEN
節(jié)點(diǎn) 記錄了如下啟動(dòng)過程:
Thu Dec : : Starting ORACLE instance (normal)LICENSE_MAX_SESSION = LICENSE_SESSIONS_WARNING = Interface type bge configured from OCR for use as a cluster interconnectInterface type bge configured from OCR for use as a cluster interconnectInterface type bge configured from OCR for use as a public interfacePicked latch free SCN scheme Using LOG_ARCHIVE_DEST_ parameter default value as /opt/oracle/product/ /db/dbs/archAutotune of undo retention is turned on LICENSE_MAX_USERS = SYS auditing is disabledksdpec: called for event prior to event group initializationStarting up ORACLE RDBMS Version: System parameters with non default values:processes = __shared_pool_size = __large_pool_size = __java_pool_size = __streams_pool_size = spfile = /dev/vx/rdsk/xxfdg/spfilesga_target = control_files = /dev/vx/rdsk/xxfdg/ctlfile /dev/vx/rdsk/xxfdg/ctlfile db_block_size = __db_cache_size = patible = db_file_multiblock_read_count= cluster_database = TRUEcluster_database_instances= thread = instance_number = undo_management = AUTOundo_tablespace = UNDOTBS remote_login_passwordfile= EXCLUSIVEdb_domain = remote_listener = LISTENERS_EYGLEjob_queue_processes = background_dump_dest = /opt/oracle/admin/eygle/bdumpuser_dump_dest = /opt/oracle/admin/eygle/udumpcore_dump_dest = /opt/oracle/admin/eygle/cdumpaudit_file_dest = /opt/oracle/admin/eygle/adumpdb_name = eygleopen_cursors = pga_aggregate_target = Cluster munication is configured to use the following interface(s) for this instance Thu Dec : : cluster interconnect IPC version:Oracle UDP/IPIPC Vendor proto PMON started with pid= OS id= DIAG started with pid= OS id= PSP started with pid= OS id= LMON started with pid= OS id= Thu Dec : : WARNING: Failed to set buffer limit on IPC interconnect socketOracle requires that the SocketReceive buffer size be tunable upto MBPlease make sure the kernel parameterwhich limits SO_RCVBUF value set byapplications is atleast MBLMD started with pid= OS id= LMS started with pid= OS id= LMS started with pid= OS id= MMAN started with pid= OS id= DBW started with pid= OS id= LGWR started with pid= OS id= CKPT started with pid= OS id= ON started with pid= OS id= RECO started with pid= OS id= CJQ started with pid= OS id= MMON started with pid= OS id= MMNL started with pid= OS id= Thu Dec : : lmon registered with NM instance id (internal mem no )Thu Dec : : Reconfiguration started (old inc new inc )List of nodes: Global Resource Directory frozen* allocate domain invalid = TRUE Communication channels reestablishedMaster broadcasted resource hash value bitmapsNon local Process blocks cleaned outThu Dec : : LMS : GCS shadows cancelled closedThu Dec : : LMS : GCS shadows cancelled closedSet master node info Submitted all remote enqueue requestsDwn cvts replayed VALBLKs dubiousAll grantable enqueues grantedPost ON to start st pass IRThu Dec : : LMS : GCS shadows traversed replayedThu Dec : : LMS : GCS shadows traversed replayedThu Dec : : Submitted all GCS remote cache requestsPost ON to start st pass IRFix write in gcs resourcesReconfiguration pleteLCK started with pid= OS id= Thu Dec : : ALTER DATABASE MOUNTThu Dec : : Setting recovery target incarnation to Thu Dec : : Successful mount of redo thread with mount id Thu Dec : : Database mounted in Shared Mode (CLUSTER_DATABASE=TRUE)Completed: ALTER DATABASE MOUNTThu Dec : : ALTER DATABASE OPENPicked broadcast on mit scheme to generate SCNsThu Dec : : Thread opened at log sequence Current log# seq# mem# : /dev/vx/rdsk/xxfdg/redo Successful open of redo thread Thu Dec : : MTTR advisory is disabled because FAST_START_MTTR_TARGET is not setThu Dec : : ON: enabling cache recoveryThu Dec : : Successfully onlined Undo Tablespace Thu Dec : : ON: enabling tx recoveryThu Dec : : Database Characterset is ZHS GBKreplication_dependency_tracking turned off (no async multimaster replication found)Starting background process QMNCQMNC started with pid= OS id= Thu Dec : : Completed: ALTER DATABASE OPEN
lishixinzhi/Article/program/Oracle/202311/18569
關(guān)于arch 無法注冊(cè) 數(shù)據(jù)庫已登記的介紹到此就結(jié)束了,不知道你從中找到你需要的信息了嗎 ?如果你還想了解更多這方面的信息,記得收藏關(guān)注本站。
成都創(chuàng)新互聯(lián)科技有限公司,是一家專注于互聯(lián)網(wǎng)、IDC服務(wù)、應(yīng)用軟件開發(fā)、網(wǎng)站建設(shè)推廣的公司,為客戶提供互聯(lián)網(wǎng)基礎(chǔ)服務(wù)!
創(chuàng)新互聯(lián)(www.cdcxhl.com)提供簡(jiǎn)單好用,價(jià)格厚道的香港/美國(guó)云服務(wù)器和獨(dú)立服務(wù)器。創(chuàng)新互聯(lián)成都老牌IDC服務(wù)商,專注四川成都IDC機(jī)房服務(wù)器托管/機(jī)柜租用。為您精選優(yōu)質(zhì)idc數(shù)據(jù)中心機(jī)房租用、服務(wù)器托管、機(jī)柜租賃、大帶寬租用,可選線路電信、移動(dòng)、聯(lián)通等。
分享題目:解決arch無法注冊(cè)問題:發(fā)現(xiàn)數(shù)據(jù)庫已登記(arch無法注冊(cè)數(shù)據(jù)庫已登記)
文章位置:http://www.dlmjj.cn/article/dpejije.html


咨詢
建站咨詢
