Secondary Storage Not working properly (CS 4.2.1 CentOS 6.5 64bits)

2014-02-26 Thread Jardel Marceno
I'm really having a hard time puting a CS enviroment to work (management
server, DB and host [kvm] on the same machine).

I installed and evething appears to be working just fine and as expected,
except for the secondary storage.

As an impact I can't use create a new VM, as ISO and Templates are not
showing up when I try to run the wizard and they get a host time out
message when I try to use add then.

I can't really understand whats is going on:

1. NFS is mounting:

Filesystem  Size  Used Avail Use% Mounted on
/dev/sda3   1.4T  2.2G  1.3T   1% /
tmpfs   7.7G 0  7.7G   0% /dev/shm
/dev/sda1   504M   43M  436M   9% /boot
/dev/sdb1   1.4T  2.5G  1.3T   1% /mnt/disk1
127.0.0.1:/mnt/disk1/exports/secondary  1.4T  2.5G  1.3T   1%
/var/cloudstack/mnt/secStorage/12586151-8de7-34fe-bdf5-966fbfa71853

2. Service VM's are getting a hard time starting (machine is empty and have
8 cores and 16GB RAM, so it can't be resources):

2014-02-26 15:26:38,956 DEBUG [db.Transaction.Transaction]
(consoleproxy-1:null) Rolling back the transaction: Time = 2 Name =
 
-SystemVmLoadScanner$1.run:70-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701;
called by
-Transaction.rollback:897-Transaction.removeUpTo:840-Transaction.close:664-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-NetworkManagerImpl.assignPublicIpAddress:376-DirectPodBasedNetworkGuru.getIp:186-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-DirectPodBasedNetworkGuru.reserve:153-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-NetworkManagerImpl.prepareNic:2166-NetworkManagerImpl.prepare:2136
com.cloud.exception.InsufficientAddressCapacityException: Insufficient
address capacityScope=interface com.cloud.dc.Pod; id=1
2014-02-26 15:26:39,797 DEBUG [cloud.capacity.CapacityManagerImpl]
(secstorage-1:null) VM state transitted from :Starting to Stopped with
event: OperationFailedvm's original host id: null new host id: null host id
before state transition: 1
2014-02-26 15:26:40,220 WARN
 [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null)
Exception while trying to start secondary storage vm
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[SecondaryStorageVm|s-31-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
2014-02-26 15:26:40,221 INFO
 [storage.secondary.SecondaryStorageManagerImpl] (secstorage-1:null) Unable
to start secondary storage vm for standby capacity, secStorageVm vm Id :
31, will recycle it and start a new one
2014-02-26 15:26:40,339 DEBUG [cloud.capacity.CapacityManagerImpl]
(consoleproxy-1:null) VM state transitted from :Starting to Stopped with
event: OperationFailedvm's original host id: null new host id: null host id
before state transition: 1
2014-02-26 15:26:40,689 WARN  [cloud.consoleproxy.ConsoleProxyManagerImpl]
(consoleproxy-1:null) Exception while trying to start console proxy
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[ConsoleProxy|v-2-VM]Scope=interface
com.cloud.dc.DataCenter; id=1
2014-02-26 15:27:08,829 DEBUG [db.Transaction.Transaction]
(consoleproxy-1:null) Rolling back the transaction: Time = 3 Name =
 
-SystemVmLoadScanner$1.run:70-Executors$RunnableAdapter.call:471-FutureTask$Sync.innerRunAndReset:351-FutureTask.runAndReset:178-ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201:165-ScheduledThreadPoolExecutor$ScheduledFutureTask.run:267-ThreadPoolExecutor.runWorker:1146-ThreadPoolExecutor$Worker.run:615-Thread.run:701;
called by
-Transaction.rollback:897-Transaction.removeUpTo:840-Transaction.close:664-TransactionContextBuilder.interceptException:63-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:133-NetworkManagerImpl.assignPublicIpAddress:376-DirectPodBasedNetworkGuru.getIp:186-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-DirectPodBasedNetworkGuru.reserve:153-ComponentInstantiationPostProcessor$InterceptorDispatcher.intercept:125-NetworkManagerImpl.prepareNic:2166-NetworkManagerImpl.prepare:2136
com.cloud.exception.InsufficientAddressCapacityException: Insufficient
address capacityScope=interface com.cloud.dc.Pod; id=1
2014-02-26 15:27:09,335 DEBUG [db.Transaction.Transaction]
(secstorage-1:null) Rolling back the transaction: Time = 3 Name =
 

Re: Secondary Storage Not working properly (CS 4.2.1 CentOS 6.5 64bits)

2014-02-26 Thread Nux!

On 26.02.2014 14:49, Jardel Marceno wrote:
I'm really having a hard time puting a CS enviroment to work 
(management

server, DB and host [kvm] on the same machine).



Give this a read:
https://cwiki.apache.org/confluence/display/CLOUDSTACK/SSVM,+templates,+Secondary+storage+troubleshooting

--
Sent from the Delta quadrant using Borg technology!

Nux!
www.nux.ro


Re: Secondary Storage Not working properly (CS 4.2.1 CentOS 6.5 64bits)

2014-02-26 Thread Erdősi Péter

Hello!

2014.02.26. 15:49 keltezéssel, Jardel Marceno írta:

com.cloud.exception.InsufficientAddressCapacityException: Insufficient
address capacityScope=interface


It's looks like IP address space problem for me..
How your network(s) looks like?
Did you configured public and management space too? (are you using basic 
or advanced setup?)


Regards,
 Fazy