openstack調(diào)試錯誤篇總結(jié)三

發(fā)現(xiàn)了問題，policy.jsonroot:rootnova：nova的。所以我們要修改用戶屬性chgrp-Rnova:nova好了，基本上完成了Bug再這個問題之后我發(fā)現(xiàn)還有一個問題，就是neutron-server沒有啟動。通過openstac-statusneutron-server顯示failed所以，重啟下就OK了。 icehouse2014-05-2621:58:51.5145808TRACEpute.manager[instance:6aa806d7-866b-4a13-a09a-1ecaf3500905]Traceback(mostrecentcalllast):2014-05-2621:58:51.5145808TRACEpute.manager[instance: “/usr/lib/python2.6/site-packages/nova/compute/manager.py”,line1720,in_spawn2014-05-2621:58:51.5145808TRACEpute.manager[instance:6aa806d7-866b-4a13-a09a-1ecaf3500905]block_device_info) “/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py”,line2253,inspawn 6aa806d7-866b-4a13-a09a-1ecaf3500905]block_device_info)2014-05-2621:58:51.5145808TRACEpute.manager[instance: “/usr/lib/python2.6/site-packages/nova/virt/libvirt/driver.py”,line3663,in2014-05-2621:58:51.5145808TRACEpute.manager[instance: 2014-05-2621:58:51.5145808TRACEpute.manager[instance:6aa806d7-866b-4a13-a09a-1ecaf3500905]VirtualInterfaceCreateException:VirtualInterfacecreationfailedvif_plugging_timeout=10vif_plugging_is_fatal=False3、novaresize Exitcode:255Stdout:Stderr:'Hostkeyverificationfailed.\r\n'.Settinginstancevm_stateto但手動執(zhí)行命令可以mkdirnova用戶，使用第三個命令注意后面有一個點（-p-m700.ssh&&cd#usermod-s/bin/bash#su-$chcon-usystem_u-robject_r-tuser_home_t$mkdir-p-m700--context=system_u:object_r:ssh_home_t:s0.ssh&&cd.ssDisablehostidentity$cat>config生成并分發(fā)ssh$ssh-keygen-fid_rsa-b1024-P$cp-a/var/lib/nova/.ssh/id_rsa.pub$scp/var/lib/nova/.ssh/id_rsaOK，現(xiàn)在切換到novaversion：OpenStackGrizzly2013.1.2 | || |2013-07-| | | ||image |Attempttobootfromvolume-noimagesupplied | ||||||kong.flavor|||||||[{u'name':||,|||||||||2013-07-|||| | | | | | | | | |ID|Hypervisor | | | 虛擬機正常運行，對虛擬機執(zhí)行l(wèi)ive-migration{ 6cd558d9-e924-4598-8e63-e86a20929bd9tohostcontrollerfailed","code":}} "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/amqp.py",line430,in_process_data rval=xy.dispatch(ctxt,version,method,**args) "/usr/lib/python2.7/dist-packages/nova/openstack/common/rpc/dispatcher.py",line133,indispatch returngetattr(proxyobj,method)(ctxt,**kwargs) "/usr/lib/python2.7/dist-packages/nova/scheduler/manager.py",line117,in context,ex, "/usr/lib/python2.7/contextlib.py",line24,in "/usr/lib/python2.7/dist-packages/nova/scheduler/manager.py",line96,in "/usr/lib/python2.7/dist-packages/nova/scheduler/driver.py",line196,in "/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py",line146,in filter_properties,instance_uuids)] "/usr/lib/python2.7/dist-packages/nova/scheduler/filter_scheduler.py",line336,in "/usr/lib/python2.7/dist-packages/nova/scheduler/host_manager.py",line342,in hosts,filter_properties) "/usr/lib/python2.7/dist-packages/nova/filters.py",line53,inget_filtered_objects return "/usr/lib/python2.7/dist-packages/nova/filters.py",line39,infilter_all ifself._filter_one(obj, .py",line30,in line78,in spec.get('image',{}).get('properties',{}) objecthasnoattribute'get' 2013-07-1015:07:44INFO[nova.api.openstack.wsgi673][32348]HTTPexceptionthrown:Livemigrationofinstance6cd558d9-e924-4598-8e63-e86a20929bd9toanotherhostfailed么返回None呢？從代碼追溯一下spec中的image屬性從何而來：ifnotinstance_ref['image_ref']:image=None

image='instance_type':instance_type,'image':image}再回頭看一下虛擬機信息，發(fā)現(xiàn)這個虛擬機是一個后端卷啟動的虛擬機volume修改在線遷移虛擬機的命令參數(shù)，強制指定目的主機，跳過schedule的階段，改成如下（注意，如果是后端卷啟動，就不能加--block-migrate參數(shù)，詳細(xì)/aticle/details/9186201[plain]view修改Nova的配置項scheduler_default_filters（默認(rèn)配置是['RetryFilter','AvailabilityZoneFilter','RamFilter','ComputeFilter','ComputeCapabilitiesFilter','Iageerisile']5、OpenStackIcehouseVirtualInterfacecreationfailed創(chuàng)建instance的virtualinterfaceexception導(dǎo)致createinstance的流==vif_plugging_timeout=10vif_plugging_is_fatal=False6、OpenstacklibvirtError:Unabletoreadfrommonitor:Connectionresetbypeer...Error:['Traceback(mostrecentcalllast):\n',' .py",line848,in_run_instance\n set_access_ip=set_access_ip)\n','File.py",line1107,in_spawn\n LOG.exception(_(\'Instancefailedtospawn\'),instance=instance)\n',' File"/usr/lib64/python2.6/contextlib.py",line23,inexit\n y",line1528,inspawn\n block_device_info)\n',' y",line2444,in_create_domain_and_network\n domain= y",line2405,in_create_domain\ndomain.createWithFlags(launch_flags)\n','File"/usr/lib/python2.6/site-packages/eventlet/tpool.py",line179,indoit\nresult=proxy_call(self._autowrap,f,*args,**kwargs)\n',' "/usr/lib/python2.6/site-packages/eventlet/tpool.py",line139,inproxy_call\n "/usr/lib/python2.6/site-packages/eventlet/tpool.py",line77,intworker\nrv=meth(*args,**kwargs)\n','File"/usr/lib64/python2.6/site-packages/libvirt.py",line708,increateWithFlags\n ifret==-1:raiselibvirtError(\'virDomainCreateWithFlags()failed\',dom=self)\n','libvirtError:Unabletoreadfrommonitor:Connectionresetbypeer\n']libvirtError:Unabletoreadfrommonitor:Connectionresetbyvncserver_listenvncserver_proxyclient_address的配置是否正確，正常應(yīng)該是監(jiān)聽本地的IP地址。7、Openstack報錯libvirtError:internalerrornosupportedarchitectureforos...Error:['Traceback(mostrecentcalllast):\n',' .py",line848,in_run_instance\n set_access_ip=set_access_ip)\n','File.py",line1107,in_spawn\n LOG.exception(_(\'Instancefailedtospawn\'),instance=instance)\n',' File"/usr/lib64/python2.6/contextlib.py",line23,inexit\n .py",line1103,in_spawn\n y",line1528,inspawn\n block_device_info)\n',' y",line2444,in_create_domain_and_network\n domain= y",line2404,in_create_domain\ndomain=self._conn.defineXML(xml)\n','File"/usr/lib/python2.6/site-packages/eventlet/tpool.py",line179,indoit\nresult=proxy_call(self._autowrap,f,*args,**kwargs)\n',' "/usr/lib/python2.6/site-packages/eventlet/tpool.py",line139,inproxy_call\n "/usr/lib/python2.6/site-packages/eventlet/tpool.py",line77,intworker\nrv=meth(*args,**kwargs)\n','File"/usr/lib64/python2.6/site-packages/libvirt.py",line2660,indefineXML\nifretisNone:raiselibvirtError(\'virDomainDefineXML()failed\',conn=self)\n',"libvirtError:internalerrornosupportedarchitectureforostype'hvm'\n"]nova.logCPU虛擬化的支持沒有打開，請從Bios打開即可。8、OpenStack虛擬機狀態(tài)故障處理，虛擬機狀態(tài)error在日常管理中，經(jīng)常出現(xiàn)比如物理機故障，QuantumNovaDown等等ErrorHardRebootSofteReboot的狀態(tài)，這個時候就要借助于Nova命令來解決了。novareset-state06d9d410-bd60-439d-8427-***********nova windowswindows涉及到加載驅(qū)動的問題，virtio-win-0.1-30.iso和virtio-win-1.1.16.vfd。這里主要強調(diào)兩個地方：kvm-m512-bootdile=win2003server.img,cache=writeback,if=virtio,boot=on-fdavirtio-win--cdromwindows2003_x64.iso-kvm-m1024–driveboot=on-cdromvirtio-win-0.1-30.iso-netnic,model=virtio-netuser-boot-nographic-vnc這里需要注意的地方是if=virtio,boot=on–fdavirtio-win-1.1.16.vfd和引導(dǎo)系統(tǒng)時不到驅(qū)動，所以在這里安裝鏡像生成后需要重新引導(dǎo)鏡像安裝更新網(wǎng)卡驅(qū)動為10、Unabletoattachcindervolumetoopenstackvolume服務(wù)時把lvm掛載到虛擬機實例時失敗，這其實不是cinder的錯誤，是iscsi掛載的問題。以下是計算節(jié)點nova-compute.log2012-07-2414:33:08TRACEnova.rpc.amqpProcessExecutionError:Unexpectederrorwhilerunningcommand.2012-07-2414:33:08TRACEnova.rpc.amqpCommand:sudonova-rootwrap-mnode-T.openstack:volume-00000011-p3:32602012-07-2414:33:08TRACEnova.rpc.amqpExitcode:2012-07-2414:33:08TRACEnova.rpc.amqpStdout:2012-07-2414:33:08TRACEnova.rpc.amqpStderr:‘iscsiadm:Noportal#可是問題依然無法解決，后來發(fā)現(xiàn)只要在nova.conf配置文件中添加參數(shù)iscsi_helper=tgtadm根據(jù)這個情況進行了測試查看日志才發(fā)現(xiàn)：如果使用參數(shù)：iscsi_helper=tgtadm我測試環(huán)境的問題是tgt和iscsitarget服務(wù)都已安裝并運行著（在安裝nova-commontgt服務(wù)也安裝上，這個不小心還真不會發(fā)現(xiàn)nova.conf配置中添加參數(shù)iscsi_helper=tgtadm3260發(fā)現(xiàn)是iscsitarget服務(wù)占用，所以導(dǎo)致掛載失敗，我們可以根據(jù)情況來使用哪個共享存儲服務(wù)??！將tgt和iscsi_helper=tgtadm、iscsitarget和iscsi_helper=ietadm保留一個即可。11、noVNCnovnc的問題比較多，網(wǎng)上也有關(guān)于這方面的很多配置介紹，其實配置不復(fù)雜，a、提示“Connection可能是控制節(jié)點在收到vnc請求的時候，無法解析計算節(jié)點的主機名，從而無法ip和主機名的對應(yīng)關(guān)系加入到控制節(jié)點的/etc/hosts文件中。b、提示“failedconnecttonovnc的功能需要瀏覽器支持WebSocket和HTML5.推薦使用谷歌。是XXX了。nova-compute的主機時間和controller的主機時間不一致。nova-computeservicesupdatenova-computecontrollernova-computecontrollernova-computenova-compute異常。nova-scheduler.loghost其他服務(wù)節(jié)點類同，這是nova心跳機制問題。所以講nova環(huán)境中各節(jié)點時間同步很重要。一定要確保時dashboardnova-computenova或者底層虛擬機，又或者在實例錯誤時刪除不NovainstancenotLocalfilestorageoftheimagefiles. 2013-03-0917:58:08TRACEnovaInstanceNotFound:Instanceinstance-00000002couldnotbefound.2013-03-0917:58:08TRACE$mysql–uroot–pRecreatetheCREATEDATABASEnova;(stripformattingifyoucopyandpasteanyof PRIVILEGES usenova;ASaINNERJOINnova.instancesASbONa.instance_uuid=b.idwhereDELETEFROMnova.instance_info_cachesWHEREinstance_uuid='$1';DELETEFROMnova.instancesWHEREuuid='$1';將以上文件寫入delete_insrance.sh中，然后執(zhí)行shinstrance_id可以通過novalist14、libvirt錯誤2013-03-0917:05:42TRACEnovareturnlibvirt.openAuth(uri,auth,0)2013-03-0917:05:42TRACEnovaFile“/usr/lib/python2.7/dist-line102,in libvirtError(‘virConnectOpenAuth()2013-03-0917:05:42TRACEnovalibvirtError:Failedtoconnectsocket‘/var/run/libvirt/libvirt-sock’:Nosuchfileor2013-03-0922:05:41.909+0000:12466:info:libvirtversion:2013-03-0922:05:41.909+0000:12466:error:virNetServerMDNSStart:460:internalerrorFailedtocreatemDNSclient:Daemonnotrunning出現(xiàn)這種錯誤首先要查看/var/log/libvirt/libvirtd.loglibvirt-binservicewillnotstartwithoutdbusps–ea|grepdbusdbusisrunning，然后執(zhí)行apt-getinstall二、1、OpenstackpingpingIPIP的具體原理，就不講了，這里主要是為了犯的中做測試，首先明確一點是：10.0.50..4ping通網(wǎng)關(guān)IP（01）ping一下這個浮動IP，可惜的是不能夠ping通。IP的原理，又一次回顧了下原理，發(fā)現(xiàn)它是通過Iptables規(guī)則來處理的。由于這里沒有報錯，所以沒有問題。我想從外網(wǎng)主機ping018SSH01。這時我立馬想到了安全組規(guī)則。于是我馬上添加了一條ALLTCP，遠(yuǎn)程為CIDR的規(guī)則。瞬間發(fā)現(xiàn)SSH也可以了理十三-外部網(wǎng)絡(luò)管理備忘)對/etc/neutron/l3_agent.ini配置自己創(chuàng)建外部網(wǎng)絡(luò)的網(wǎng)路ID。handle_internal_only_routers=Trueexternal_network_bridge=br-ex同時，在你創(chuàng)建路由器的時候，不會顯示路由器狀態(tài)和端口為Down的情況。nova-managenetworklistdelete掉，刪除所有以前殘留的網(wǎng)絡(luò)然后重新創(chuàng)建一個/23新網(wǎng)絡(luò)：$sudonova-managenetworkdelete/241$sudonova-managenetworkcreate/231$sudonova-managenetwork [root@station140~(keystone_admin)]#novahelp|grepfloat AddafloatingIPaddresstoaserver.

BulkcreatefloatingipsbyBulkdeletefloatingipsbyrange.Listallfloatingips. AllocateafloatingIPforthecurrenttenant. De-allocateafloatingIP. Listallfloatingip RemoveafloatingIPaddressfroma生成浮動 | |InstanceId|FixedIp|Pool |43| | |pub1 IP | |Instance |Fixed |Pool |43|93d0c9c1-b38b-4fe3-9ae3-400f43276f60|0|pub1 移除浮動4、Cannotprovisiongrenetworkfornet-idtunnelingCannotprovisiongrenetworkfornet-id=223aa5ce-3a5e-4566-82f9-a1163d2499f4tunneling我問題產(chǎn)生的原因是自己升級了KERNEL導(dǎo)致OPENVSWITVH不支持3.0KERNEL最后我降到CENTOSKERNEL2.6就出現(xiàn)了這個問題。首先一定要確定你計算節(jié)點和網(wǎng)絡(luò)節(jié)點的OPENVSWITCH然后刪除你計算節(jié)點的OPENVSWITCH。從裝從新配置你的OPENVSWITCH也就是ML2的配置 OPENVSWITCH具體5、openstacknrutronovs-gre網(wǎng)速慢Createandeditfile/etc/neutron/dnsmasq-neutron.confandputthisinside:Andrebootyourinstance.VerifythatyourMTUisinetaddr:Bcast:55Mask:inet6addr:fe80::f816:3eff:fef0:6a9f/64Scope:LinkUPBROADCASTRUNNINGMULTICASTMTU:1400Metric:1RXpackets:934855errors:0dropped:0overruns:0frame:0TXpackets:207741errors:0dropped:0overruns:0carrier:0collisions:0txqueuelen:1000RXbytes:1210256390(1.2GB)TXbytes:226172592(226.1MB)]:KEY和主機名都獲取失敗/etc/neutron/neutron.confenable_isolated_metadataTrueZEROCONFvi/etc/sysconfig/network7、openstackFailedtoconnecttoservercode我的情況是因為我把COMPUTER和NEUTRON安裝到一個節(jié)點上。查看-AINPUT-jREJECT--reject-withicmp-host-發(fā)出一條icmp-host-prohibited消息。還有一種情況是單獨安裝的網(wǎng)絡(luò)節(jié)點，可以參考一篇OPENSTACK社區(qū)的帖子8、centosopenstackVMIPTABLES的指令，開一個云主機會默認(rèn)產(chǎn)生一條臨時規(guī)則，如果重啟了將導(dǎo)致規(guī)則失效。下一次將無法獲取到IP地址。IPTABLESOK9、hasownernetwork:floatingipandthereforecannotbedeleteddirectlyviatheportAPIhasownernetwork:floatingipandthereforecannotbedeleteddirectlyviatheportReleasefloatingIP10、neutronvmIPVMIPIP解決辦法Please,settemporarydhcp_lease_duration=120inneutron.conf(neutron-*servicesrestart)toseeDHCPREQUESTfromrunningVM,andDHCPACKfromdnsmasq,likethis:-dhcp_lease_duration=12011、netdev_linux|INFO|ioctl(SIOCGIFHWADDR)ontapd7ebabc9-4fdeviceNosuchJul2420:06:41|01035|bridge|INFO|destroyedportqr-725d56fb-f7onbridgebr-intJul2420:06:41|01036|bridge|WARN|bridgebr-tun:usingdefaultbridgeEthernetaddress6a:13:96:eb:35:4eJul2420:06:41|01037|netdev_linux|INFO|ioctl(SIOCGIFHWADDR) tapd7ebabc9-4fdevicefailed:NosuchdeviceJul2420:06:41|01038|bridge|WARN|bridgebr-int:usingdefaultbridgeEthernetaddressb2:e5:c8:7e:bd:4dJul2420:06:47|01039|netdev|WARN|Dropped76logmessagesinlast12seconds(mostrecently,1secondsago)duetoexcessiverate請先檢查你系統(tǒng)的版本是否是centos/REDHATserviceneutron-l3-agentrestart三、1、Openstack出現(xiàn)"Failedtoconnecttoservercode1006)在安裝了正確的Openstack后出現(xiàn)了，打開dashboard·之后可能會出現(xiàn)下面的情PS:記得重啟NOVA服務(wù)iptables-nL|grep5900iptables-nL|grepiptables-IINPUT-ptcp--dport5900-jACCEPTiptables-IINPUT-ptcp--dport5999-jiptables-nL|grepiptables-IINPUT-ptcp--dport6088-j1、HeatHeatstackCloudFormation設(shè)計和實現(xiàn)的。所以，CloudFormationHeatIcehouse t1.template，該模板展示的是一個php應(yīng)用，ApacheWebServer、PHP和簡單的PHP應(yīng)用程序全部都由默認(rèn)安裝在AmazonLinuxAMI上的AWSCloudFormation幫助程序腳本進行安裝。cfn-hupAmazonEC2實例元數(shù)據(jù)中所定義配cfn-hup后臺程序來更新應(yīng)用程序軟件（Apache或PHP的版本AWSCloudFormationPHP應(yīng)用程序文件本身。來自于模板中同一個EC2資源的以下代碼段顯示的是，在偵測到元數(shù)據(jù)的任何更改時配置cfn-hup調(diào)用cfn-init來更新軟件所需的部件："#Startupthecfn-hupdaemontolistenforchangestotheWebServer"/opt/aws/bin/cfn-hup||error_exit'Failedtostartcfn-默認(rèn)狀態(tài)下，cfn-hup1515分鐘AWSManagementConsole更新堆棧，您將會注意到創(chuàng)建初始接口，請務(wù)必提供原來創(chuàng)建stack時的參數(shù)值。（eaaa管理員密碼(I版暫沒有實現(xiàn))對虛擬機的更新中，沒有更新管理員密碼。目前(20140519)，Nova中只有Xen更新AmazonEC2AMI時，不能只通過啟動和停止實例來修改AMI；AWSCloudFormation將其視為對資源不可變屬性的更改。為了對不可變屬性進AW即：運行新AMI的新AmazonEC2實例。在新實例運行之后，AWSCloudFormation會更新堆棧中的彈性IP地址等其他資源，以指向新資源。所有ID已隨著更新更改?！癊vent”表中的事件包含描述“所請求的更新包含HeatCloudFormation一樣，鏡像屬于不可變屬性?？梢栽谀０逯信渲胕mage_update_policy'REBUILD','REPLACE','REBUILD-PRESERVE-EPHEMERAL'REPLACE。那么默認(rèn)的行為會拋出一rebuild操作（REBUILD-PRESERVE-EPHEMERALrebuild（detach（atacautoscalingOpenStackautoscalingHeat中支持該資源類型，采用嵌套stack的方式實現(xiàn)。目前也沒有實現(xiàn)虛擬機的健康檢查功能。AutoScalingAmazonEC2AutoScaling正在運行的EC2實例。更新后的啟動配置只適用于更新之后創(chuàng)建的新實例。stackAutoScalingAutoScalingEC2實例上都不會提供任何同步或序列化行為。每個主機上的cfn-hup后臺程序都將獨立運行且會按其自己的計劃更新應(yīng)用程序。當(dāng)您使用cfn-hup更新實例上的配置時，每個實例都將按其自己的計劃運行cfn-hup程序；堆棧中的實例之AutoScalingEC2cfn-hup更改都同時運行，更新如果cfn-hup更改在不同時間運行，則新舊版軟件可能會同時運行。Heat中，autoscalingUpdatePolicy，autoscaling資源需要引用一個LaunchConfiguration資源，其屬性有：'ImageId'：鏡像ID，必選'KernelId','RamDiskId'：兼容AWS的磁盤標(biāo)識，目前不支持autoscaling'LaunchConfigurationName'：你懂的，必選，而且允許更新 現(xiàn)'HealthCheckType'：健康檢查類型，未實現(xiàn)'LoadBalancerNames'：LB名稱'Tags'：標(biāo)識，HeatCeilometer的交互，就仰仗這個TagsHeatLaunchConfigurationUpdatePolicy屬性中的AutoScalingRollingUpdatemap。autoscaling資源中的metadata中保存了AWSCloudFormation更新任何屬性；但是您應(yīng)該在進行任何更改之前考慮以下問題：更改可變屬性還是不可變屬性？對資源屬性的某些更改，如更改AmazonEC2實例上的AMI，不受基礎(chǔ)服務(wù)的支持。如果更改可變屬性，AWSCloudFormation將使用適用于基礎(chǔ)資源的“更新”或“修改”類型API。對于不可變的屬性更改，AWSCloudFormation將用更新后的屬性創(chuàng)建新資源，然后再刪除舊資源之前將此資源鏈接至stack。雖然AWSWSSDIste資t屬性，AWSClFmatin使用該數(shù)據(jù)庫實例的應(yīng)用程序?qū)⑿露丝谠O(shè)置以及您進行的任何其他更改考慮在2、/etc/init.d/ceph:line15:/lib/lsb/init-functions:Nosuchfileordirectory[controller][WARNINetc/init.d/cephline15lib/lsb/init-functionsNosuchfileor[controller][ERROR]RuntimeError:commandreturnednon-zeroexitstatus:1[ceph_deploy.mon][ERROR]Failedtoexecutecommand:/sbin/serviceceph-c[ceph_deploy][ERROR]GenericError:Failedtocreate13、FATALModulerbdnotCENTOS6.5CEPHRDBERROR:modinfo:couldnotfindmodulerbdFATAL:Modulerbdnotfound.rbd:modproberbdfailed!yum--enablerepo=elrepo-kernelinstallkernel-ml#willinstall3.11.latest,stable,#yum--enablerepo=elrepo-kernelinstallkernel-lt#willinstall3.0.latest,longterm-2.355.el6.2.cuttlefish.x86rpm--import yuminstallcephrpm-e--nodepsqemu-imgrpm-Uvhqemu-*horizon中無法刪除的話，我們需要到服務(wù)器上去手動刪除，“Can'tremoveopenlogicalvolumestop掉，再嘗試刪除。刪除完還需到數(shù)據(jù)庫cinder的volumes表里清除相關(guān)記錄。TypeErrorathasattr():attributenamemustbestringRequestMethod: DjangoVersion: ExceptionType: ExceptionValue:hasattr():attributenamemustbe init_,line78PythonExecutable: PythonVersion: PythonServertime:Fri,29Mar201312:51:09apache2errorTraceback(mostrecentcalllast):File"/usr/lib/python2.7/dist-packages/django/core/handlers/base.py",line111,inresponse=callback(request,*callback_args,returnview_func(request,*args,**kwargs)returnview_func(request,*args,**kwargs)returnview_func(request,*args,**kwargs)returnview_func(request,*args,**kwargs)returnview_func(request,*args,**kwargs)File"/usr/lib/python2.7/dist-packages/django/views/generic/base.py",line48,inFile"/usr/lib/python2.7/dist-packages/django/views/generic/base.py",line69,inreturnhandler(request,*args,File"/usr/lib/python2.7/dist-packages/horizon/tables/views.py",line155,ingethandled=self.construct_tables() handled= data= oard/dashboards/admin/overview/views.py",line41,inget_dataoard/usage/views.py",line34,inget_dataoard/usage/base.py",line115,inget_quotas_("Unabletoretrievequotaoard/usage/base.py",line112,inget_quotasFile"/usr/lib/python2.7/dist-packages/horizon/utils/memoized.py",line33,invalue=oard/usage/quotas.py",line115,intenant_quota_usagesoard/usage/quotas.py",line98,inget_tenant_quota_dataoard/usage/quotas.py",line80,in_get_quota_dataoard/api/cinder.py",line123,intenant_quota_getc_client=oard/api/cinder.py",line59,incinderclient File"/usr/lib/python2.7/dist-packages/cinderclient/client.py",line78,in ifhasattr(requests,logging):錯誤信息中指出了Cinderclient的client.py中78行hasattr()方法的屬性必ifhasattr(requestslogging):#ifhasattr(requests apache2dashboardvolume以下是計算節(jié)點nova-compute.log的錯誤日志：2012-07-2414:33:08TRACEnova.rpc.amqpProcessExecutionError:Unexpectederrorwhilerunningcommand.2012-07-2414:33:08TRACEnova.rpc.amqpCommand:sudonova-rootwrap-mnode-T.openstack:volume-00000011-p3:32602012-07-2414:33:08TRACEnova.rpc.amqpExitcode:2012-07-2414:33:08TRACEnova.rpc.amqpStdout:2012-07-2414:33:08TRACEnova.rpc.amqpStderr:‘iscsiadm:Noportal以上錯誤是沒有找到iscsiopenstack資料說要 iscsi_ip_address=#volume可是問題依然無法解決，后來發(fā)現(xiàn)只要在nova.conf配置文件中添加參數(shù)iscsi_helper=tgtadm根據(jù)這個情況進行了測試查看日志才發(fā)現(xiàn)：如果使用參數(shù)iscsi_helper=tgtadm時就必須使用tgt服務(wù)，反之使用iscsitarget服務(wù)在添加參數(shù)iscsi_helper=我測試環(huán)境的問題是tgt和iscsitarget服務(wù)都已安裝并運行著，在安裝nova-common時會把tgt服務(wù)也安裝上，在nova.conf配置中添加參數(shù)iscsi_helper=tgtadm3260iscsitarget服務(wù)占用，所以導(dǎo)致掛載iscsi_helper=ietadm加上這個參數(shù)，就是使用iscsitarget五、1Errorunabletoconnecttonoderabbit@localhost:ThedatabaseRabbitMQusesisboundtothemachine’shostname,soifyoucopiedthedatabasedirtoanothermachine,itwon’twork.Ifthisisthecase,youhavetosetupamachinewiththesamehostnameasbeforeandtransferanyoutstandingmessagestothenewmachine.Ifthere’snothingimportantinrabbit,youcouldjustcleareverythingbyremovingtheRabbitMQfilesin/var/lib/rabbitmq.rm-rf2、Accessdeniedforuser‘keystone@localhost(using super(Connection,self). (*args,**kwargs2)sqlalchemy.exc.OperationalError:(OperationalError)(1045,“Accessdeniedforuser‘keystone’@'openstack1′(usingpassword:YES)”)NoneNoneconnection=3、KeystoneNohandlerscouldbefoundforlogger“keystoneclient.client”UnabletoauthorizeNohandlerscouldbefoundforloggerUnabletoauthorizeNohandlerscouldbefoundforloggerUnabletoauthorize出現(xiàn)這種錯誤是大多數(shù)是由于keystone_data.shdriver= template_filemysql-uroot-popenstack-e“dropdatabasenova;”mysql-uroot-popenstack-e“dropdatabaseglance;”mysql-uroot-popenstack-e“dropdatabasekeystone;”nova-compute-kvmnova-docnova-networknova-apt-getautoremoverm-rf/var/lib/glancerm-rf/var/lib/nova/rm-rf六、1、ImageNotFound:Image3bb459f8-2fd9-4464-9b66-f2f34c17396fcouldnotbeGLANCE鏡像啟動原理看這個地址/nova/+bug/1029674大概意思是修改計算節(jié)點nova.conf#Shouldunusedbaseimagesberemoved?(booleanvalue)#Unusedunresizedbaseimagesyoungerthanthiswillnotbe#removed(integervalue)2、cephlibrbdimagehaswatchersnot$rbdrmRemovingimage:99%complete...failed.2013-08-0214:07:17.530470-1librbd:errorremovingheader:(16)Deviceorresourcebusyrbd:error:imagestillhaswatchersThismeanstheimageisstillopenortheclientusingitcrashed.Tryagainafterclosing/unmappingitorwaiting30sforthecrashedclienttotimeout.解決辦法$rbdidpoolimagesnapdevice1rbdmyrbd-/dev/rbd1$servicerbdmap[ok]StoppingRBDMapping:$rbdrmRemovingimage:100%$vimidpoolimagesnapdevicerbdfoo–rbdfoo–rbdfoo–rbdfoo–rbdfoo–/dev/rbd43ceph-disk:Error:unabletocreatesymlink/var/lib/ceph/osd/ceph-5->[network][INFO]Runningcommand:ceph-disk-activate–mark-initsysvinit FileJournal::_open:disablingaiofornon-blockjournal.Usejournal_force_aiotoforceuseofaioanyway FileJournal::_open:disablingaiofornon-blockjournal.Usejournal_force_aiotoforceuseofaioanyway filestore(/tmp/osd0)couldnotfind23c2fcde/osd_superblock/0//-1inindex:(2)Nosuchfileordirectory[network][WARNIN]2014-06-0918:49:07.3333647f338b54c7a0-1createdobjectstore/tmp/osd0journal/tmp/osd0/journalforosd.5fsid[network][WARNIN]2014-06-0918:49:07.3334137f338b54c7a0-1auth:errorreadingfile:/tmp/osd0/keyring:can’topen/tmp/osd0/keyring:(2)Nosuchfileor[network][WARNIN]2014-06-0918:49:07.3335317f338b54c7a0-1creatednewkeyinkeyring/tmp/osd0/keyring [network][ERROR]RuntimeError:commandreturnednon-zeroexitstatus:1 ceph-disk-activate–mark-initsysvinit–mount/tmp/osd0在節(jié)點中執(zhí)行mkdir-p/ -/[network][WARNIN]ceph-disk:Error:Noclusterconffoundin/etc/cephwithfsid