ORACLE VM建立SERVER POOLS後狀態為ERR的解決
環境介紹：
oracle vm 2.2.1 32bit
oracle vm server 2.2.1
oracle vm manager 2.2.0
ERROR:
| Select | Server Pool Name | Status | High Availability Status | Servers | Users | Logs |
|---|---|---|---|---|---|---|
| spoo12 | ERR | Disabled |
今天在搭建ORACLE VM環境的時候，VM SERVER和VM MANAGER安裝都很順利的完成，但是在建立SERVER POOL後發現每次建立完後，狀態總是ERRO不可用，透過檢視後臺日誌：var/log/ovm-manager/oc4j.log發現以下錯誤：
2011-04-08 11:02:27.992 WARNING failed:errcode=00000, errmsg=Unexpected error:
StackTrace:
File "/opt/ovs-agent-2.3/OVSSiteHA.py", line 276, in ha_check_hostname_ip
raise Exception("Invalid hostname/IP configuration: hostname=%s;ip=%s" % (rs["hostname"], rs["ip"]))
>
StackTrace:
File "/opt/ovs-agent-2.3/OVSSiteHA.py", line 279, in ha_check_hostname_ip
raise Exception("check srv('%s') hostname/IP failed! => %s" % (hostname, errmsg))
>
StackTrace:
File "/opt/ovs-agent-2.3/OVSSiteCluster.py", line 602, in cluster_check_prerequisite
raise Exception(msg)
StackTrace:
File "/opt/ovs-agent-2.3/OVSSiteCluster.py", line 639, in _cluster_setup
_check(ret)
File "/opt/ovs-agent-2.3/OVSXCluster.py", line 344, in _check
raise OVSException(error=ret["error"])
2011-04-08 11:02:27.993 NOTIFICATION Failed setup cluster for agent 2.2.0...
2011-04-08 11:02:27.995 NOTIFICATION get one server pool
2011-04-08 11:02:27.996 ERROR Cluster Setup
2011-04-08 11:02:28.014 ERROR [Server Pool Management][Server Pool][spoo2]:During creating server pool (spoo2), cluster setup failed: (OVM-1011 OVM Manager communication with 192.168.30.127 for operation HA Setup for Oracle VM Agent 2.2.0 failed:
errcode=00000, errmsg=Unexpected error:
)
2011-04-08 11:03:31.750 NOTIFICATION [Server Pool Management][Server Pool][null]:Starting to refresh server pool data...
從以上黑字部分發現在驗證主機名/IP的時候沒有驗證透過導致的錯誤，在檢視hosts檔案後發現沒有設定192.168.30.127的資訊，於是新增進去：
[root@qqovm ~]# more /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6
192.168.30.127 qqovm[root@qqovm ~]#
再重新發布，問題解決:
2011-04-08 11:04:36.012 NOTIFICATION [Server Pool Management][Server Pool][spoo12]:Check prerequisites to create server pool (spoo12) succeed
2011-04-08 11:04:36.044 NOTIFICATION getUserListTable.
2011-04-08 11:04:46.075 NOTIFICATION Getting agent version for agent:192.168.30.127 ...
2011-04-08 11:04:46.669 NOTIFICATION The agent version is 2.3-38
2011-04-08 11:04:46.680 NOTIFICATION Start to create server pool process...
2011-04-08 11:04:46.681 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:04:46.685 NOTIFICATION Starting to register master server...
2011-04-08 11:04:46.695 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:04:46.695 NOTIFICATION Regisering server:192.168.30.127...
2011-04-08 11:04:49.532 NOTIFICATION Register Server: 192.168.30.127 success
2011-04-08 11:04:49.533 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:04:49.533 NOTIFICATION Getting host info for server:192.168.30.127 ...
2011-04-08 11:04:51.293 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:04:51.294 NOTIFICATION Starting to persist the server pool...
2011-04-08 11:04:51.294 NOTIFICATION Before commit insert data into manager db....
2011-04-08 11:04:51.298 NOTIFICATION Start to setup cluster for agent 2.2: HA status:false
2011-04-08 11:04:51.336 NOTIFICATION After commit insert data into manager db....
2011-04-08 11:04:51.336 NOTIFICATION After persist the server pool...
2011-04-08 11:04:51.337 NOTIFICATION [Server Pool Management][Server Pool][spoo12]:Create server pool (spoo12) starting.
2011-04-08 11:04:59.299 NOTIFICATION Success setup cluster for agent 2.2.0...
2011-04-08 11:04:59.299 NOTIFICATION Start to clean up virtual ip for server pool 2.2
2011-04-08 11:04:59.929 NOTIFICATION Success to clean up virtual ip for server pool 2.2...
2011-04-08 11:04:59.929 NOTIFICATION Making dir/OVS/iso_pool for master agent 192.168.30.127
2011-04-08 11:05:00.086 NOTIFICATION Making dir/OVS/seed_pool for master agent 192.168.30.127
2011-04-08 11:05:00.228 NOTIFICATION Making dir/OVS/publish_pool for master agent 192.168.30.127
2011-04-08 11:05:00.359 NOTIFICATION Making dir/OVS/sharedDisk for master agent 192.168.30.127
2011-04-08 11:05:00.502 NOTIFICATION Making dir/OVS/running_pool for master agent 192.168.30.127
2011-04-08 11:05:00.638 NOTIFICATION get one server pool
2011-04-08 11:05:15.086 NOTIFICATION [Server Pool Management][Server Pool][null]:Starting to refresh server pool data...
2011-04-08 11:05:15.902 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:05:17.391 NOTIFICATION ServerPoolSync.run: sync OVM server status succeeded.
2011-04-08 11:05:17.478 NOTIFICATION ServerPoolSync.run: sync OVM server VT status succeeded.
2011-04-08 11:05:17.643 NOTIFICATION ServerPoolSync.run: update virtual machines performance statistics succeeded.
2011-04-08 11:05:20.149 NOTIFICATION ServerPoolSync.run: sync virtual machines status succeeded.
2011-04-08 11:05:20.217 NOTIFICATION ServerPoolSync.run: sync cluster master status succeeded.
2011-04-08 11:05:20.218 NOTIFICATION ServerPoolSync.run: sync agent version succeeded.
2011-04-08 11:05:20.218 NOTIFICATION [Server Pool Management][Server Pool][null]:End of refresh server pool data...
2011-04-08 11:05:25.500 NOTIFICATION [Server Pool Management][Server Pool][null]:Starting to refresh server pool data...
2011-04-08 11:05:25.621 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:05:26.753 NOTIFICATION [Server Pool Management][Server Pool][null]:Starting to refresh server pool data...
2011-04-08 11:05:27.122 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:05:27.312 NOTIFICATION ServerPoolSync.run: sync OVM server status succeeded.
2011-04-08 11:05:27.440 NOTIFICATION ServerPoolSync.run: sync OVM server VT status succeeded.
2011-04-08 11:05:28.106 NOTIFICATION ServerPoolSync.run: update virtual machines performance statistics succeeded.
2011-04-08 11:05:29.185 NOTIFICATION ServerPoolSync.run: sync OVM server status succeeded.
2011-04-08 11:05:29.248 NOTIFICATION ServerPoolSync.run: sync OVM server VT status succeeded.
2011-04-08 11:05:29.921 NOTIFICATION ServerPoolSync.run: update virtual machines performance statistics succeeded.
2011-04-08 11:05:30.436 NOTIFICATION ServerPoolSync.run: sync virtual machines status succeeded.
2011-04-08 11:05:30.485 NOTIFICATION ServerPoolSync.run: sync cluster master status succeeded.
2011-04-08 11:05:30.485 NOTIFICATION ServerPoolSync.run: sync agent version succeeded.
2011-04-08 11:05:30.485 NOTIFICATION [Server Pool Management][Server Pool][null]:End of refresh server pool data...
2011-04-08 11:05:30.972 NOTIFICATION ServerPoolSync.run: sync virtual machines status succeeded.
2011-04-08 11:05:31.030 NOTIFICATION ServerPoolSync.run: sync cluster master status succeeded.
2011-04-08 11:05:31.030 NOTIFICATION ServerPoolSync.run: sync agent version succeeded.
2011-04-08 11:05:31.030 NOTIFICATION [Server Pool Management][Server Pool][null]:End of refresh server pool data...
2011-04-08 11:05:59.315 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:06:00.659 NOTIFICATION ServerPoolSync.run: sync OVM server status succeeded.
2011-04-08 11:06:00.721 NOTIFICATION ServerPoolSync.run: sync OVM server VT status succeeded.
2011-04-08 11:06:01.404 NOTIFICATION ServerPoolSync.run: update virtual machines performance statistics succeeded.
2011-04-08 11:06:03.693 NOTIFICATION ServerPoolSync.run: sync virtual machines status succeeded.
2011-04-08 11:06:03.748 NOTIFICATION ServerPoolSync.run: sync cluster master status succeeded.
2011-04-08 11:06:03.748 NOTIFICATION ServerPoolSync.run: sync agent version succeeded.
2011-04-08 11:08:05.794 NOTIFICATION master server is:192.168.30.127
2011-04-08 11:08:07.120 NOTIFICATION ServerPoolSync.run: sync OVM server status succeeded.
2011-04-08 11:08:07.194 NOTIFICATION ServerPoolSync.run: sync OVM server VT status succeeded.
2011-04-08 11:08:07.894 NOTIFICATION ServerPoolSync.run: update virtual machines performance statistics succeeded.
2011-04-08 11:08:10.154 NOTIFICATION ServerPoolSync.run: sync virtual machines status succeeded.
2011-04-08 11:08:10.208 NOTIFICATION ServerPoolSync.run: sync cluster master status succeeded.
2011-04-08 11:08:10.208 NOTIFICATION ServerPoolSync.run: sync agent version succeeded.
來自 “ ITPUB部落格 ” ，連結：http://blog.itpub.net/10130206/viewspace-1048410/，如需轉載，請註明出處，否則將追究法律責任。
相關文章
- openstack上建立vm例項後，狀態為ERROR問題解決Error
- Oracle中JOB的建立後不執行解決方法Oracle
- Oracle VM Server安裝手冊OracleServer
- 解決crs_stat狀態為UNKNOWN問題
- 通過Python檢視Azure VM的狀態Python
- VCS叢集狀態為 STALE_ADMIN_WAIT的解決AI
- 11g R2 RAC: SERVER POOLSServer
- vm安裝ubuntu後，update報錯問題解決Ubuntu
- RAC10g下crs狀態為unknown的解決辦法
- oracle日誌狀態為STALE案例分析Oracle
- Oracle10g RAC 服務的狀態是UNKNOWN解決方法Oracle
- 程式的建立和程式的狀態
- JavaScript物件的的建立及屬性狀態維護詳解JavaScript物件
- Docker容器的退出狀態碼及解決方法Docker
- Android透明狀態列解決方案Android
- 解決IIS無響應假死狀態
- oracle 11G RAC的建立(VM虛擬環境)Oracle
- Oracle VM SERVER+WINDOWS2003 SERVER 問題總結OracleServerWindows
- MSSQL Server 遷移至 ORACLE解決方案SQLServerOracle
- ORACLE CRS 狀態 UNKNOWN 變為offlineOracle
- 執行powermt 顯示儲存鏈路狀態為dead的解決辦法
- 分散式centreon後，新增完poller之後centreon中檢視poller狀態始終為非執行狀態分散式
- oracle中會話的狀態Oracle會話
- Oracle資料庫的靜默狀態和掛起狀態Oracle資料庫
- 【使用者狀態】詳細解讀Oracle使用者ACCOUNT_STATUS的九種狀態Oracle
- oracle 817 archive err,oracle hangOracleHive
- 行為型設計模式 - 狀態模式詳解設計模式
- Elasticsearch叢集狀態健康值處於red狀態問題分析與解決（圖文詳解）Elasticsearch
- dell poweredge r410安裝Oracle VM Server 3.2.2OracleServer
- rac oracle10 asm+raw for centos5.6 on vm serverOracleASMCentOSServer
- 狀態機解決複雜邏輯及使用
- HTTP協議無狀態，該怎麼解決？HTTP協議
- 行為和狀態的關係
- SQL Server建立Linked Server訪問OracleSQLServerOracle
- 玩家——受傷後的保護狀態
- MTS方式連線V$SESSION中的SERVER狀態SessionServer
- oracle使用者狀態（account_status）詳解 .Oracle
- npm ERR! Error: CERT_UNTRUSTED的問題解決NPMErrorRust