euca-describe-availability-zones verbose shows 0 max

 

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.

• Login or register to post comments

byzhang (Offline)

solved
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!

• Login or register to post comments

sudha (Offline)

Similar problem - unsolved
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

• Login or register to post comments

vikas_saxena (Offline)

try this out...
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