euca-describe-availability-zones verbose shows 0 max
来源:互联网 发布:淘宝保证金是什么意思 编辑:程序博客网 时间:2024/05/21 19:28
Eucalyptus version: 1.6~bzr931
Installed from Ubuntu Enterprise Cloud CD, following the instruction: https://help.ubuntu.com/community/UEC/CDInstall
Topology: 1 front end, 1 node
My problem:
when I run into this step euca-describe-availability-zones verbose of the ubuntu instruction, I got this result:
AVAILABILITYZONE vm 192.168.218.128
AVAILABILITYZONE |- vm types free / max cpu ram disk
AVAILABILITYZONE |- m1.small 0000 / 0000 1 128 2
AVAILABILITYZONE |- c1.medium 0000 / 0000 1 256 5
AVAILABILITYZONE |- m1.large 0000 / 0000 2 512 10
AVAILABILITYZONE |- m1.xlarge 0000 / 0000 2 1024 20
AVAILABILITYZONE |- c1.xlarge 0000 / 0000 4 2048 20
I searched the problem in the forum, and found it is related with the connectivity between front end and the node. But it seems not be the case this time, since sudo euca_conf --no-rsync --discover-nodes runs smooth.
the last error in cloud-error.log happened before my command ran, and it's
23:11:38 [EntityWrapper:SystemClockTimer] ERROR org.hibernate.exception.JDBCConnectionException: Cannot open connection
org.hibernate.exception.JDBCConnectionException: Cannot open connection
at org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:97)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:66)
at org.hibernate.exception.JDBCExceptionHelper.convert(JDBCExceptionHelper.java:52)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:449)
at org.hibernate.jdbc.ConnectionManager.getConnection(ConnectionManager.java:167)
at org.hibernate.jdbc.JDBCContext.connection(JDBCContext.java:142)
at org.hibernate.transaction.JDBCTransaction.begin(JDBCTransaction.java:85)
at org.hibernate.impl.SessionImpl.beginTransaction(SessionImpl.java:1353)
at org.hibernate.ejb.TransactionImpl.begin(TransactionImpl.java:38)
at com.eucalyptus.util.TxHandle.(TxHandle.java:40)
at com.eucalyptus.util.EntityWrapper.(EntityWrapper.java:100)
at com.eucalyptus.util.EntityWrapper.(EntityWrapper.java:93)
at edu.ucsb.eucalyptus.cloud.cluster.VmTypes.update(VmTypes.java:111)
at edu.ucsb.eucalyptus.cloud.cluster.VmTypes.list(VmTypes.java:140)
at com.eucalyptus.cluster.handlers.ResourceStateHandler.trigger(ResourceStateHandler.java:31)
at com.eucalyptus.cluster.handlers.AbstractClusterMessageDispatcher.fireTimedStatefulTrigger(AbstractClusterMessageDispatcher.java:140)
at com.eucalyptus.cluster.handlers.ResourceStateHandler.fireEvent(ResourceStateHandler.java:39)
at com.eucalyptus.event.ReentrantListenerRegistry.fireEvent(ReentrantListenerRegistry.java:80)
at com.eucalyptus.event.ReentrantListenerRegistry.fireEvent(ReentrantListenerRegistry.java:65)
at com.eucalyptus.event.ListenerRegistry.fireEvent(ListenerRegistry.java:69)
at com.eucalyptus.event.SystemClock.run(SystemClock.java:35)
at java.util.TimerThread.mainLoop(Timer.java:534)
at java.util.TimerThread.run(Timer.java:484)
Caused by: java.sql.SQLException: Connection is broken: java.net.SocketException: Connection timed out
at org.hsqldb.jdbc.Util.sqlException(Unknown Source)
at org.hsqldb.jdbc.jdbcConnection.getAutoCommit(Unknown Source)
at com.mchange.v2.c3p0.impl.NewProxyConnection.getAutoCommit(NewProxyConnection.java:1083)
at org.hibernate.connection.C3P0ConnectionProvider.getConnection(C3P0ConnectionProvider.java:82)
at org.hibernate.jdbc.ConnectionManager.openConnection(ConnectionManager.java:446)
... 19 more
I really appreciate the kind help since I plan to setup a bigger cloud in the lab to facilitate other researchers.
Posted: Tue, 07/13/2010 - 12:14
Hi all,
Even I have similar problem. The same error in the log file. I have tried every thing suggested here. Please help
Thanks
Sudha
Posted: Wed, 07/14/2010 - 23:17
In case your euca-describe-availability-zones verbose shows all instances as 0(zero)
try this out....
using euca_conf:
deregister all nodes, clusters, sc (storage clusters), walrus(optional)
stop all eucalyptus services i.e. cloud, walarus, cc, nc (on each node) etc.
start all eucalyptus services and register everything that you deregistered in the first step.
Hope it works out for you as it did for me.
Cheers,
Vikas Saxena
- euca-describe-availability-zones verbose shows 0 max
- neutron availability zones
- Openstack关于Regions和Availability Zones
- OpenStack Grizzly Webinar Preview: Availability Zones vs. Host Aggregates
- openstack ice版availability zones host aggregates 实战详解
- Availability Zones and Host Aggregates in OpenStack Compute (Nova)
- OpenStack重要概念理解(Regions+Cells+Availability Zones+Host Aggregates等)
- OpenStack重要概念理解(Regions+Cells+Availability Zones+Host Aggregates等)
- DESCRIBE
- euca环境变量设置
- RMAN backups in Max Performance/Max Availability Data Guard Environment [ID 331924.1]
- RMAN backups in Max Performance/Max Availability Data Guard Environment [ID 331924.1]
- 了解Zones
- Tcode Shows
- Fashion Shows
- Listener --describe
- dw.Describe
- describe fun
- libavformat/libavcodec学习(mplayer)
- 局域网共享权限设置和指定ip设置
- 无法卸载office 2010 beta的解决方案
- 首次Oracle SQL Tuning经历
- Android sax解析XML数据
- euca-describe-availability-zones verbose shows 0 max
- MYSQL中的CREATE TEMPORARY TABLE
- Rebuild MySQL Slave Server
- android 数据库与 provider uri 之间的关系
- 如何保护.net中的dll文件(防止破解、反编译dll)
- slf4j, Simple Logging Facade for Java 的包使用说明
- C#打包应用程序(安装程序)
- 我的电信账单
- 关于在windows下部署发布QT程序的总结
Posted: Fri, 04/02/2010 - 22:52
I find in a previous post, it's suggested to re-register the node.
I ran this cmd: sudo euca_conf --no-rsync --register-nodes 192.168.218.129
and now the euca-describe-availability-zones verbose is good!