Just trying a 4.5 deployment after moving my secondary storage to a
dedicated nic and vlan (it was on management) I checked the firewall rulls
that I am allowing traffic between the hypervisor network and the secondary
storage network. I can mount the nfs share of secondary storage on the
hypervisor.
I just sent my network admin to an email to make sure that ports were
assigned to the correct Vlan but I won't hear back from him until the
morning and I'd like to work on this tonight if you can give me some
guidance
Deployment error
tail -f /var/log/cloudstack/management/management-server.log | grep -i -E
'exception|unable|fail|invalid|leak|warn|error'
2015-03-18 21:08:57,226 DEBUG [c.c.a.ConsoleProxyAlertAdapter]
(consoleproxy-1:ctx-3d6d3304) Console proxy creation failure, zone: chlt-1
2015-03-18 21:08:57,231 WARN [o.a.c.alerts] (consoleproxy-1:ctx-3d6d3304)
alertType:: 10 // dataCenterId:: 1 // podId:: null // clusterId:: null //
message:: Console proxy creation failure. zone: chlt-1, error details: null
2015-03-18 21:08:57,249 ERROR [c.c.u.d.DbUtil] (consoleproxy-1:ctx-3d6d3304)
RELEASE_LOCK() throws exception
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
at
com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3520)
Caused by: java.io.EOFException: Can not read response from server. Expected
to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
2015-03-18 21:09:00,456 WARN [c.c.c.ConsoleProxyManagerImpl]
(consoleproxy-1:ctx-2eda35b6) Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[ConsoleProxy|v-14-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
2015-03-18 21:09:00,457 DEBUG [c.c.a.ConsoleProxyAlertAdapter]
(consoleproxy-1:ctx-2eda35b6) Console proxy creation failure, zone: chlt-1
2015-03-18 21:09:00,464 WARN [o.a.c.alerts] (consoleproxy-1:ctx-2eda35b6)
alertType:: 10 // dataCenterId:: 1 // podId:: null // clusterId:: null //
message:: Console proxy creation failure. zone: chlt-1, error details: null
2015-03-18 21:09:03,235 WARN [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-14a45ef5) Exception while trying to start secondary
storage vm
com.cloud.exception.AgentUnavailableException: Resource [Host:1] is
unreachable: Host 1: Unable to start instance due to Unable to acquire lock
on VMTemplateStoragePool: 124
Caused by: com.cloud.utils.exception.CloudRuntimeException: Unable to
acquire lock on VMTemplateStoragePool: 124
2015-03-18 21:09:03,238 ERROR [c.c.u.d.DbUtil] (secstorage-1:ctx-14a45ef5)
RELEASE_LOCK() throws exception
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
at
com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3520)
Caused by: java.io.EOFException: Can not read response from server. Expected
to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
2015-03-18 21:09:03,240 INFO [o.a.c.s.SecondaryStorageManagerImpl]
(secstorage-1:ctx-14a45ef5) Unable to start secondary storage vm for standby
capacity, secStorageVm vm Id : 17, will recycle it and start a new one
2015-03-18 21:09:06,729 DEBUG [c.c.a.SecondaryStorageVmAlertAdapter]
(secstorage-1:ctx-14a45ef5) Secondary Storage Vm creation failure, zone:
chlt-1
2015-03-18 21:09:06,733 WARN [o.a.c.alerts] (secstorage-1:ctx-14a45ef5)
alertType:: 19 // dataCenterId:: 1 // podId:: null // clusterId:: null //
message:: Secondary Storage Vm creation failure. zone: chlt-1, error
details: null
2015-03-18 21:09:06,755 ERROR [c.c.u.d.DbUtil] (secstorage-1:ctx-14a45ef5)
RELEASE_LOCK() throws exception
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link
failure
at
com.mysql.jdbc.SQLError.createCommunicationsException(SQLError.java:1116)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3520)
Caused by: java.io.EOFException: Can not read response from server. Expected
to read 4 bytes, read 0 bytes before connection was unexpectedly lost.
