Unable to start VM
Hi, Well this is awkward a few days ago i managed, with help from here, to create an LXC cluster and launch an LXC instance. Then suddenly now i can't start any VM inside the cluster and i think is due to a network error. I checked the instance logs and the creation of it was successful but it crash when trying to start it. Here it the logs: https://pastebin.com/t1A4Z6TM This other log can also be helpful with the error https://pastebin.com/zgRtWSg0
Re: launch instance error
Ok then it's done. Thank you very much. I have a functional LXC cluster configured into my CS environment. You told me you where interested in this to work so if you have any question i'll be more than happy to help. Regards, Alejandro On Sunday, June 16, 2019, Nicolas Vazquez wrote: > Hi Alejandro, > > AFAIK it is not possible to add data disks unless you add a Ceph storage > pool. > > References: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Enhancements > https://issues.apache.org/jira/browse/CLOUDSTACK-8574 > > Regards, > Nicolas Vazquez > > De: Alejandro Ruiz Bermejo > Enviado: sábado, 15 de junio 16:15 > Asunto: Re: launch instance error > Para: users@cloudstack.apache.org > > > Hi, > I made a fresh install of the CoudStack environment with 2 nodes: > management and server. The primary and secondary storage inside the > management server, both using NFS. > > 1 Zone > 1 Pod > 1 Cluster > 1 Host (LXC) > > The secondary and console proxy VMs where created successfully and i > created an LXC template according to > > https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Template+creation#LXCTemplatecreation-CreatingtemplateonUbuntu > > > When i try to launc the new instance i get again errors thi is the log > <https://pastebin.com/rdCYMYDZ>. As i see now the manager allocate CPU, > RAM > and Root disk in a storage pool but can't find a storage pool for Data > disk. > > I can create now an instance without assign a Data Disk. How can i correct > this? > > On Fri, Jun 14, 2019 at 5:54 PM Andrija Panic > wrote: > > > I would go with 2nd aproach - I don't expect "same" issues actually - you > > can either add a new pod/cluster or just new cluster in same pod. > > > > On Fri, 14 Jun 2019 at 21:25, Alejandro Ruiz Bermejo < > > arbermejo0...@gmail.com> wrote: > > > > > I created a new zone, pod and cluster and added the LXC host to the new > > > cluster. CloudStack did everything for me. Since i am in a test > > environment > > > i used the same subnet for both zones. > > > > > > I can do 2 things: > > > 1. I will wipe the host and do a fresh install(only on the compute > host), > > > but i will probably have the same issues. I will add it to the same > zone > > in > > > the same pod as the KVM cluster and in an LXC cluster as i previously > > did. > > > > > > 2. I also can do fresh a CloudStack install (management server > included) > > > and use only LXC as hypervisor technology in order to find where the > > > troubles are. After i have LXC working can later add KVM > > > > > > Wich approach would be more helpful to find where the trouble is. > > > > > > Regards, > > > Alejandro > > > > > > > > > On Fri, Jun 14, 2019 at 2:59 PM Andrija Panic > > > > wrote: > > > > > > > I'm not sure how you moved the host to another Zone ? (Please > describe) > > > > > > > > But anyway, I would wipe that host (perhaps some settings are kept > > > locally, > > > > etc), and add it as a fresh host to a new cluster (could be in same > Pod > > > as > > > > well, ot a new one).i.e. start from scratch please - since your setup > > > seems > > > > problematic at this moment. > > > > > > > > I would be happy to learn if you managed to have it working - so > please > > > let > > > > me know. > > > > > > > > Best > > > > Andrija > > > > > > > > On Fri, Jun 14, 2019, 20:03 Alejandro Ruiz Bermejo < > > > > arbermejo0...@gmail.com> > > > > wrote: > > > > > > > > > Yes trying to find solutions i did create a new zone pod and > cluster > > > and > > > > > moved the lxc host to it, but i had the same errors. So i moved it > > back > > > > to > > > > > my original LXC cluster into my original zone. I guess thats why it > > > shows > > > > > those records. > > > > > > > > > > I made all the movements using the UI, it seems like the values on > > the > > > DB > > > > > didn't updated, how do i change that? > > > > > > > > > > On Fri, Jun 14, 2019 at 1:32 PM Andrija Panic < > > andrija.pa...@gmail.com > > > > > > > > > wrote: > > > > > > > > > > > So, there are a couple of problems I see, based on
Re: launch instance error
Hi, I made a fresh install of the CoudStack environment with 2 nodes: management and server. The primary and secondary storage inside the management server, both using NFS. 1 Zone 1 Pod 1 Cluster 1 Host (LXC) The secondary and console proxy VMs where created successfully and i created an LXC template according to https://cwiki.apache.org/confluence/display/CLOUDSTACK/LXC+Template+creation#LXCTemplatecreation-CreatingtemplateonUbuntu When i try to launc the new instance i get again errors thi is the log <https://pastebin.com/rdCYMYDZ>. As i see now the manager allocate CPU, RAM and Root disk in a storage pool but can't find a storage pool for Data disk. I can create now an instance without assign a Data Disk. How can i correct this? On Fri, Jun 14, 2019 at 5:54 PM Andrija Panic wrote: > I would go with 2nd aproach - I don't expect "same" issues actually - you > can either add a new pod/cluster or just new cluster in same pod. > > On Fri, 14 Jun 2019 at 21:25, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com> wrote: > > > I created a new zone, pod and cluster and added the LXC host to the new > > cluster. CloudStack did everything for me. Since i am in a test > environment > > i used the same subnet for both zones. > > > > I can do 2 things: > > 1. I will wipe the host and do a fresh install(only on the compute host), > > but i will probably have the same issues. I will add it to the same zone > in > > the same pod as the KVM cluster and in an LXC cluster as i previously > did. > > > > 2. I also can do fresh a CloudStack install (management server included) > > and use only LXC as hypervisor technology in order to find where the > > troubles are. After i have LXC working can later add KVM > > > > Wich approach would be more helpful to find where the trouble is. > > > > Regards, > > Alejandro > > > > > > On Fri, Jun 14, 2019 at 2:59 PM Andrija Panic > > wrote: > > > > > I'm not sure how you moved the host to another Zone ? (Please describe) > > > > > > But anyway, I would wipe that host (perhaps some settings are kept > > locally, > > > etc), and add it as a fresh host to a new cluster (could be in same Pod > > as > > > well, ot a new one).i.e. start from scratch please - since your setup > > seems > > > problematic at this moment. > > > > > > I would be happy to learn if you managed to have it working - so please > > let > > > me know. > > > > > > Best > > > Andrija > > > > > > On Fri, Jun 14, 2019, 20:03 Alejandro Ruiz Bermejo < > > > arbermejo0...@gmail.com> > > > wrote: > > > > > > > Yes trying to find solutions i did create a new zone pod and cluster > > and > > > > moved the lxc host to it, but i had the same errors. So i moved it > back > > > to > > > > my original LXC cluster into my original zone. I guess thats why it > > shows > > > > those records. > > > > > > > > I made all the movements using the UI, it seems like the values on > the > > DB > > > > didn't updated, how do i change that? > > > > > > > > On Fri, Jun 14, 2019 at 1:32 PM Andrija Panic < > andrija.pa...@gmail.com > > > > > > > wrote: > > > > > > > > > So, there are a couple of problems I see, based on your storage > pool > > DB > > > > > records: > > > > > > > > > > your storage (for LXC) is CLUSTER wide, so back to first SQL I > share, > > > as > > > > > following: > > > > > SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, > > > > > storage_pool.pool_type, storage_pool.created, storage_pool.removed, > > > > > storage_pool.update_time, storage_pool.data_center_id, > > > > storage_pool.pod_id, > > > > > storage_pool.used_bytes, storage_pool.capacity_bytes, > > > > storage_pool.status, > > > > > storage_pool.storage_provider_name, storage_pool.host_address, > > > > > storage_pool.path, storage_pool.port, storage_pool.user_info, > > > > > storage_pool.cluster_id, storage_pool.scope, storage_pool.managed, > > > > > storage_pool.capacity_iops, storage_pool.hypervisor FROM > storage_pool > > > > > WHERE storage_pool.data_center_id = 1 > > > > > AND storage_pool.status = 'Up' > > > > > AND storage_pool.scope = 'CLUSTER' > > > > > AND ( storage_pool.pod_id IS NULL OR storage_pool.pod_
Re: launch instance error
I created a new zone, pod and cluster and added the LXC host to the new cluster. CloudStack did everything for me. Since i am in a test environment i used the same subnet for both zones. I can do 2 things: 1. I will wipe the host and do a fresh install(only on the compute host), but i will probably have the same issues. I will add it to the same zone in the same pod as the KVM cluster and in an LXC cluster as i previously did. 2. I also can do fresh a CloudStack install (management server included) and use only LXC as hypervisor technology in order to find where the troubles are. After i have LXC working can later add KVM Wich approach would be more helpful to find where the trouble is. Regards, Alejandro On Fri, Jun 14, 2019 at 2:59 PM Andrija Panic wrote: > I'm not sure how you moved the host to another Zone ? (Please describe) > > But anyway, I would wipe that host (perhaps some settings are kept locally, > etc), and add it as a fresh host to a new cluster (could be in same Pod as > well, ot a new one).i.e. start from scratch please - since your setup seems > problematic at this moment. > > I would be happy to learn if you managed to have it working - so please let > me know. > > Best > Andrija > > On Fri, Jun 14, 2019, 20:03 Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com> > wrote: > > > Yes trying to find solutions i did create a new zone pod and cluster and > > moved the lxc host to it, but i had the same errors. So i moved it back > to > > my original LXC cluster into my original zone. I guess thats why it shows > > those records. > > > > I made all the movements using the UI, it seems like the values on the DB > > didn't updated, how do i change that? > > > > On Fri, Jun 14, 2019 at 1:32 PM Andrija Panic > > wrote: > > > > > So, there are a couple of problems I see, based on your storage pool DB > > > records: > > > > > > your storage (for LXC) is CLUSTER wide, so back to first SQL I share, > as > > > following: > > > SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, > > > storage_pool.pool_type, storage_pool.created, storage_pool.removed, > > > storage_pool.update_time, storage_pool.data_center_id, > > storage_pool.pod_id, > > > storage_pool.used_bytes, storage_pool.capacity_bytes, > > storage_pool.status, > > > storage_pool.storage_provider_name, storage_pool.host_address, > > > storage_pool.path, storage_pool.port, storage_pool.user_info, > > > storage_pool.cluster_id, storage_pool.scope, storage_pool.managed, > > > storage_pool.capacity_iops, storage_pool.hypervisor FROM storage_pool > > > WHERE storage_pool.data_center_id = 1 > > > AND storage_pool.status = 'Up' > > > AND storage_pool.scope = 'CLUSTER' > > > AND ( storage_pool.pod_id IS NULL OR storage_pool.pod_id = 1 ) > > > AND ( storage_pool.cluster_id IS NULL OR storage_pool.cluster_id = > 2 ) > > > AND storage_pool.removed IS NULL > > > > > > If you compare WHERE clause i.e. conditions, you will see your > > > data_center=2 instead of 1, you pod_id=2 instead of 1, your > cluster_id=3 > > > instead of 2. > > > So you probably have been adding back and forth primary storage pool > for > > > LXC or something fishy there... > > > > > > Please investigate - based on your records, it seems you have a zone > for > > > KVM, another zone for LXC, and then there are more clusters/pods than 1 > > in > > > each of them... > > > We could easily change DB records, but you need to understand why these > > > records are "shifted" by one - i.e. wrong zone, wrong pod, wrong > cluster > > > expected by CloudStack versus the actual records in storage_pool table. > > > > > > Best > > > Andrija > > > > > > > > > On Fri, 14 Jun 2019 at 18:53, Alejandro Ruiz Bermejo < > > > arbermejo0...@gmail.com> wrote: > > > > > > > this was the ouputs > > > > > > > > mysql> SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, > > > > -> storage_pool.pool_type, storage_pool.created, > > > storage_pool.removed, > > > > -> storage_pool.update_time, storage_pool.data_center_id, > > > > storage_pool.pod_id, > > > > -> storage_pool.used_bytes, storage_pool.capacity_bytes, > > > > storage_pool.s
Re: launch instance error
Yes trying to find solutions i did create a new zone pod and cluster and moved the lxc host to it, but i had the same errors. So i moved it back to my original LXC cluster into my original zone. I guess thats why it shows those records. I made all the movements using the UI, it seems like the values on the DB didn't updated, how do i change that? On Fri, Jun 14, 2019 at 1:32 PM Andrija Panic wrote: > So, there are a couple of problems I see, based on your storage pool DB > records: > > your storage (for LXC) is CLUSTER wide, so back to first SQL I share, as > following: > SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, > storage_pool.pool_type, storage_pool.created, storage_pool.removed, > storage_pool.update_time, storage_pool.data_center_id, storage_pool.pod_id, > storage_pool.used_bytes, storage_pool.capacity_bytes, storage_pool.status, > storage_pool.storage_provider_name, storage_pool.host_address, > storage_pool.path, storage_pool.port, storage_pool.user_info, > storage_pool.cluster_id, storage_pool.scope, storage_pool.managed, > storage_pool.capacity_iops, storage_pool.hypervisor FROM storage_pool > WHERE storage_pool.data_center_id = 1 > AND storage_pool.status = 'Up' > AND storage_pool.scope = 'CLUSTER' > AND ( storage_pool.pod_id IS NULL OR storage_pool.pod_id = 1 ) > AND ( storage_pool.cluster_id IS NULL OR storage_pool.cluster_id = 2 ) > AND storage_pool.removed IS NULL > > If you compare WHERE clause i.e. conditions, you will see your > data_center=2 instead of 1, you pod_id=2 instead of 1, your cluster_id=3 > instead of 2. > So you probably have been adding back and forth primary storage pool for > LXC or something fishy there... > > Please investigate - based on your records, it seems you have a zone for > KVM, another zone for LXC, and then there are more clusters/pods than 1 in > each of them... > We could easily change DB records, but you need to understand why these > records are "shifted" by one - i.e. wrong zone, wrong pod, wrong cluster > expected by CloudStack versus the actual records in storage_pool table. > > Best > Andrija > > > On Fri, 14 Jun 2019 at 18:53, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com> wrote: > > > this was the ouputs > > > > mysql> SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, > > -> storage_pool.pool_type, storage_pool.created, > storage_pool.removed, > > -> storage_pool.update_time, storage_pool.data_center_id, > > storage_pool.pod_id, > > -> storage_pool.used_bytes, storage_pool.capacity_bytes, > > storage_pool.status, > > -> storage_pool.storage_provider_name, storage_pool.host_address, > > -> storage_pool.path, storage_pool.port, storage_pool.user_info, > > -> storage_pool.cluster_id, storage_pool.scope, storage_pool.managed, > > -> storage_pool.capacity_iops, storage_pool.hypervisor FROM > > storage_pool WHERE > > -> storage_pool.data_center_id = 1 AND storage_pool.status = 'Up' > AND > > -> storage_pool.scope = 'ZONE' AND storage_pool.hypervisor = 'LXC' > > AND > > -> storage_pool.removed IS NULL; > > Empty set (0.00 sec) > > > > mysql> select * from storage_pool; > > > > > ++-+--+---+--++++++--+---+-+-+-+-++---+-++-+---+ > > | id | name| uuid | pool_type > | > > port | data_center_id | pod_id | cluster_id | used_bytes | > capacity_bytes | > > host_address | user_info | path| created | > removed > > | update_time | status | storage_provider_name | scope | hypervisor | > > managed | capacity_iops | > > > > > ++-+--+---+--++++++--+---+-+-+-+-++---+-++-+---+ > > | 1 | primary | 672631ab-5c14-3f60-97c6-1d633e60f7bd | > NetworkFilesystem | > > 2049 | 1 | NULL | NULL | 3413114880 | > 984374837248 | > > 10.8.9.235 | NULL | /export/primary | 2019-06-06 20:05:26 | NULL > > | NULL| Up | DefaultPrimary
Re: launch instance error
this was the ouputs mysql> SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, -> storage_pool.pool_type, storage_pool.created, storage_pool.removed, -> storage_pool.update_time, storage_pool.data_center_id, storage_pool.pod_id, -> storage_pool.used_bytes, storage_pool.capacity_bytes, storage_pool.status, -> storage_pool.storage_provider_name, storage_pool.host_address, -> storage_pool.path, storage_pool.port, storage_pool.user_info, -> storage_pool.cluster_id, storage_pool.scope, storage_pool.managed, -> storage_pool.capacity_iops, storage_pool.hypervisor FROM storage_pool WHERE -> storage_pool.data_center_id = 1 AND storage_pool.status = 'Up' AND -> storage_pool.scope = 'ZONE' AND storage_pool.hypervisor = 'LXC' AND -> storage_pool.removed IS NULL; Empty set (0.00 sec) mysql> select * from storage_pool; ++-+--+---+--++++++--+---+-+-+-+-++---+-++-+---+ | id | name| uuid | pool_type | port | data_center_id | pod_id | cluster_id | used_bytes | capacity_bytes | host_address | user_info | path| created | removed | update_time | status | storage_provider_name | scope | hypervisor | managed | capacity_iops | ++-+--+---+--++++++--+---+-+-+-+-++---+-++-+---+ | 1 | primary | 672631ab-5c14-3f60-97c6-1d633e60f7bd | NetworkFilesystem | 2049 | 1 | NULL | NULL | 3413114880 | 984374837248 | 10.8.9.235 | NULL | /export/primary | 2019-06-06 20:05:26 | NULL | NULL| Up | DefaultPrimary| ZONE| KVM| 0 | NULL | | 3 | lxc | 3b062c9d-0333-41c4-9ba8-f71f75a81d1f | SharedMountPoint | 0 | 2 | 2 | 3 | 3413114880 | 984374837248 | localhost| NULL | /mnt/primary| 2019-06-13 18:32:26 | NULL | NULL| Up | DefaultPrimary| CLUSTER | NULL | 0 | NULL | ++-+--+---+--++++++--+---+-+-+-+-++---+-++-+---+ 2 rows in set (0.00 sec) On Fri, Jun 14, 2019 at 12:51 PM Andrija Panic wrote: > right... based on logs, it used different sql to search for ZONE-wide > storage, execute this one please: > > SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, > storage_pool.pool_type, storage_pool.created, storage_pool.removed, > storage_pool.update_time, storage_pool.data_center_id, storage_pool.pod_id, > storage_pool.used_bytes, storage_pool.capacity_bytes, storage_pool.status, > storage_pool.storage_provider_name, storage_pool.host_address, > storage_pool.path, storage_pool.port, storage_pool.user_info, > storage_pool.cluster_id, storage_pool.scope, storage_pool.managed, > storage_pool.capacity_iops, storage_pool.hypervisor FROM storage_pool WHERE > storage_pool.data_center_id = 1 AND storage_pool.status = 'Up' AND > storage_pool.scope = 'ZONE' AND storage_pool.hypervisor = 'LXC' AND > storage_pool.removed IS NULL > > This SHOULD return 1 pool, unless there are some funny issues... > I expect the storage_pool.hypervisor might be NULL instead of "LXC" > > Anyway, execute the following: "select * from storage_pool;" > to see what you have in DB... > > Best > Andrija > > > On Fri, 14 Jun 2019 at 18:13, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com> wrote: > > > Hi and thanks again for your help, > > > > So i run the query with both level scopes of storage > > > > with storage_pool.scope = 'CLUSTER' > > > > output: > > Empty set (0.00 sec) > > > > with storage_pool.scope = 'ZONE' > > > > > > > ++-+--+---+-+-+-++++++---+--+-+--+---++---+-+---++ > > | id | name| uuid | pool_type > | > > cre
Re: launch instance error
Hi and thanks again for your help, So i run the query with both level scopes of storage with storage_pool.scope = 'CLUSTER' output: Empty set (0.00 sec) with storage_pool.scope = 'ZONE' ++-+--+---+-+-+-++++++---+--+-+--+---++---+-+---++ | id | name| uuid | pool_type | created | removed | update_time | data_center_id | pod_id | used_bytes | capacity_bytes | status | storage_provider_name | host_address | path| port | user_info | cluster_id | scope | managed | capacity_iops | hypervisor | ++-+--+---+-+-+-++++++---+--+-+--+---++---+-+---++ | 1 | primary | 672631ab-5c14-3f60-97c6-1d633e60f7bd | NetworkFilesystem | 2019-06-06 20:05:26 | NULL| NULL| 1 | NULL | 3413114880 | 984374837248 | Up | DefaultPrimary| 10.8.9.235 | /export/primary | 2049 | NULL | NULL | ZONE | 0 | NULL | KVM| ++-+--+---+-+-+-++++++---+--+-+--+---++---+-+---++ 1 row in set (0.00 sec) On Fri, Jun 14, 2019 at 11:57 AM Andrija Panic wrote: > Execute this one (from logs) against your DB - does it return/finds a > storage pool ? > > SELECT storage_pool.id, storage_pool.name, storage_pool.uuid, > storage_pool.pool_type, storage_pool.created, storage_pool.removed, > storage_pool.update_time, storage_pool.data_center_id, storage_pool.pod_id, > storage_pool.used_bytes, storage_pool.capacity_bytes, storage_pool.status, > storage_pool.storage_provider_name, storage_pool.host_address, > storage_pool.path, storage_pool.port, storage_pool.user_info, > storage_pool.cluster_id, storage_pool.scope, storage_pool.managed, > storage_pool.capacity_iops, storage_pool.hypervisor FROM storage_pool WHERE > storage_pool.data_center_id = 1 AND storage_pool.status = 'Up' AND > storage_pool.scope = 'CLUSTER' AND ( storage_pool.pod_id IS NULL OR > storage_pool.pod_id = 1 ) AND ( storage_pool.cluster_id IS NULL OR > storage_pool.cluster_id = 2 ) AND storage_pool.removed IS NULL > > tip from thre query - it seems to be looking for CLUSTER level not ZONE > level scope of storage. > > > > On Thu, 13 Jun 2019 at 16:35, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com> wrote: > > > Hi, > > > > I really need to get LXC working, I'm very interested on using CS and i > > need to move LXC instances to the new cloud. Thats's why i'm insisting on > > it. So please if you see any errors or can help me i will appreciate it. > > > > 1. I haven't used any Tag till now (should i?) > > 2. Already set the TRACE logging level here is the content for an > instance > > createion (https://pastebin.com/Yd9as8uF) > > > > Thanks for the help > > Alejandro > > > > On Wed, Jun 12, 2019 at 5:06 PM Andrija Panic > > wrote: > > > > > Well, this one still doesn't provide any usefull info. > > > > > > 1. Can you confirm if you have tags set on LXC Compute Offerings or any > > > storage used by LXC cluster? > > > 2. Consider change logging level for management-server.log to TRACE > mode, > > > which will show also all SQL queries executed, so perhaps we can see > why > > it > > > craps out. > > > 3. Not meant to discourage you, but I'm not sure weather LXC code still > > > works with any more recent ACS release - i.e. I'm not aware of any > users, > > > nor do I (personally) remember another user mentioning LXC here any > time > > > recently. > > > > > > Cheers > > > Andrija > > > > > > On Wed, 12 Jun 2019 at 15:13, Alejandro Ruiz Bermejo < > > > arbermejo0...@gmail.com> wrote: > > > > > > > Hi this is the full log for one instance cretion with the same error > ( > > > > https://pastebin.com/HHKnHi36) > > > > > > > > On Tue, Jun 11, 2019 at 5:10 PM Andrija Panic < > andrija.pa...@gmail.com > > >
Re: launch instance error
Hi,
I really need to get LXC working, I'm very interested on using CS and i
need to move LXC instances to the new cloud. Thats's why i'm insisting on
it. So please if you see any errors or can help me i will appreciate it.
1. I haven't used any Tag till now (should i?)
2. Already set the TRACE logging level here is the content for an instance
createion (https://pastebin.com/Yd9as8uF)
Thanks for the help
Alejandro
On Wed, Jun 12, 2019 at 5:06 PM Andrija Panic
wrote:
> Well, this one still doesn't provide any usefull info.
>
> 1. Can you confirm if you have tags set on LXC Compute Offerings or any
> storage used by LXC cluster?
> 2. Consider change logging level for management-server.log to TRACE mode,
> which will show also all SQL queries executed, so perhaps we can see why it
> craps out.
> 3. Not meant to discourage you, but I'm not sure weather LXC code still
> works with any more recent ACS release - i.e. I'm not aware of any users,
> nor do I (personally) remember another user mentioning LXC here any time
> recently.
>
> Cheers
> Andrija
>
> On Wed, 12 Jun 2019 at 15:13, Alejandro Ruiz Bermejo <
> arbermejo0...@gmail.com> wrote:
>
> > Hi this is the full log for one instance cretion with the same error (
> > https://pastebin.com/HHKnHi36)
> >
> > On Tue, Jun 11, 2019 at 5:10 PM Andrija Panic
> > wrote:
> >
> > > Alejandro,
> > >
> > > Please send the whole log on pastebin or similar, this one doesn't
> > provide
> > > enough information... (beside the " Found pools matching tags: [] ")
> > >
> > > On Tue, 11 Jun 2019 at 17:57, Alejandro Ruiz Bermejo <
> > > arbermejo0...@gmail.com> wrote:
> > >
> > > > ok, so i registered a new template and unset-ed the HVM option and
> > > > launched a new instance using this themplate.
> > > > Now the planner can find the host inside the LXC cluster but it seems
> > > like
> > > > it can't find now a propper storage pool. I already have everything
> > > > configured as it appears on the installation guide and configured the
> > > > secondary and primary storage on the lxc host. I attach and paste
> here
> > > the
> > > > log of the VM creation process
> > > >
> > > > root@cloudstack-manager:/home/team# grep -i "unable to"
> > > > /var/log/cloudstack/management/management-server.log
> > > > 2019-06-11 11:12:59,917 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > > > (API-Job-Executor-19:ctx-23ea94e8 job-51 ctx-06951cdb)
> (logid:0afee059)
> > > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > > create a
> > > > deployment for VM[User|i-2-11-VM]Scope=interface
> > com.cloud.dc.DataCenter;
> > > > id=1
> > > > 2019-06-11 11:12:59,917 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > > > (API-Job-Executor-19:ctx-23ea94e8 job-51 ctx-06951cdb)
> (logid:0afee059)
> > > > Unable to create a deployment for VM[User|i-2-11-VM]
> > > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > create
> > > > a deployment for VM[User|i-2-11-VM]Scope=interface
> > > com.cloud.dc.DataCenter;
> > > > id=1
> > > > 2019-06-11 11:12:59,918 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > > > (API-Job-Executor-19:ctx-23ea94e8 job-51) (logid:0afee059) Complete
> > async
> > > > job-51, jobStatus: FAILED, resultCode: 530, result:
> > > >
> > >
> >
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable
> > > > to create a deployment for VM[User|i-2-11-VM]"}
> > > > 2019-06-11 11:17:33,162 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > > > (API-Job-Executor-22:ctx-e044255f job-57 ctx-87af2b3f)
> (logid:0e16600e)
> > > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > > create a
> > > > deployment for VM[User|i-2-12-VM]Scope=interface
> > com.cloud.dc.DataCenter;
> > > > id=1
> > > > 2019-06-11 11:17:33,162 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > > > (API-Job-Executor-22:ctx-e044255f job-57 ctx-87af2b3f)
> (logid:0e16600e)
> > > > Unable to create a deployment for VM[User|i-2-12-VM]
> > > > com.cloud.exception.InsufficientServerCapacityException: Unable to
> > create
> > > > a deployment for VM[User|i-2-12-VM]Scope=interface
> > > com.cloud.dc.DataCenter;
> > > > id=1
> > > &g
launch instance erro
Hi, I already added a question related to this a few days ago but i already solved the first issue i had with it. So i thought to create a new one with the new trouble i had on it I installed Cloudstack 4.11.2.0 on Ubuntu 16.04 This is my environment: - 1 Zone - 1 Pod - 2 Clusters (LXC and KVM) - 2 Hosts (one in each cluster) i can launch perfectly VMs on the KVM cluster but when i'm trying to launch a new instance with an LXC template i'm getting that the instance couldn't be deployed I already have configured the secondary and primary storage on the environment. And when the instance is been deployed i see it gets allocated CPU and RAM from the LXC host. The issue is when the storage allocation process is been made, it can't find any storage pool. This problem isn't happening when i launch a new instance in the KVM cluster I attach here the log of the process. 2019-06-12 09:02:45,500 DEBUG [o.a.c.s.a.LocalStoragePoolAllocator] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) LocalStoragePoolAllocator trying to find storage pool to fit the vm 2019-06-12 09:02:45,500 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) ClusterScopeStoragePoolAllocator looking for storage pool 2019-06-12 09:02:45,500 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) Looking for pools in dc: 1 pod:1 cluster:2. Disabled pools will be ignored. 2019-06-12 09:02:45,500 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) Found pools matching tags: [] 2019-06-12 09:02:45,501 DEBUG [o.a.c.s.a.ClusterScopeStoragePoolAllocator] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) No storage pools available for shared volume allocation, returning 2019-06-12 09:02:45,501 DEBUG [o.a.c.s.a.ZoneWideStoragePoolAllocator] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) ZoneWideStoragePoolAllocator to find storage pool 2019-06-12 09:02:45,503 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) No suitable pools found for volume: Vol[24|vm=14|ROOT] under cluster: 2 2019-06-12 09:02:45,503 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) No suitable pools found 2019-06-12 09:02:45,503 DEBUG [c.c.d.DeploymentPlanningManagerImpl] (API-Job-Executor-26:ctx-9fa50775 job-67 ctx-624410ca) (logid:8eddb393) No suitable storagePools found under this Cluster: 2 This is the instance creation related content on the [cloudstack-management.log][1] [1]: https://pastebin.com/HHKnHi36
Re: launch instance error
Hi this is the full log for one instance cretion with the same error (
https://pastebin.com/HHKnHi36)
On Tue, Jun 11, 2019 at 5:10 PM Andrija Panic
wrote:
> Alejandro,
>
> Please send the whole log on pastebin or similar, this one doesn't provide
> enough information... (beside the " Found pools matching tags: [] ")
>
> On Tue, 11 Jun 2019 at 17:57, Alejandro Ruiz Bermejo <
> arbermejo0...@gmail.com> wrote:
>
> > ok, so i registered a new template and unset-ed the HVM option and
> > launched a new instance using this themplate.
> > Now the planner can find the host inside the LXC cluster but it seems
> like
> > it can't find now a propper storage pool. I already have everything
> > configured as it appears on the installation guide and configured the
> > secondary and primary storage on the lxc host. I attach and paste here
> the
> > log of the VM creation process
> >
> > root@cloudstack-manager:/home/team# grep -i "unable to"
> > /var/log/cloudstack/management/management-server.log
> > 2019-06-11 11:12:59,917 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > (API-Job-Executor-19:ctx-23ea94e8 job-51 ctx-06951cdb) (logid:0afee059)
> > com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a
> > deployment for VM[User|i-2-11-VM]Scope=interface com.cloud.dc.DataCenter;
> > id=1
> > 2019-06-11 11:12:59,917 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > (API-Job-Executor-19:ctx-23ea94e8 job-51 ctx-06951cdb) (logid:0afee059)
> > Unable to create a deployment for VM[User|i-2-11-VM]
> > com.cloud.exception.InsufficientServerCapacityException: Unable to create
> > a deployment for VM[User|i-2-11-VM]Scope=interface
> com.cloud.dc.DataCenter;
> > id=1
> > 2019-06-11 11:12:59,918 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (API-Job-Executor-19:ctx-23ea94e8 job-51) (logid:0afee059) Complete async
> > job-51, jobStatus: FAILED, resultCode: 530, result:
> >
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable
> > to create a deployment for VM[User|i-2-11-VM]"}
> > 2019-06-11 11:17:33,162 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > (API-Job-Executor-22:ctx-e044255f job-57 ctx-87af2b3f) (logid:0e16600e)
> > com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a
> > deployment for VM[User|i-2-12-VM]Scope=interface com.cloud.dc.DataCenter;
> > id=1
> > 2019-06-11 11:17:33,162 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > (API-Job-Executor-22:ctx-e044255f job-57 ctx-87af2b3f) (logid:0e16600e)
> > Unable to create a deployment for VM[User|i-2-12-VM]
> > com.cloud.exception.InsufficientServerCapacityException: Unable to create
> > a deployment for VM[User|i-2-12-VM]Scope=interface
> com.cloud.dc.DataCenter;
> > id=1
> > 2019-06-11 11:17:33,162 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (API-Job-Executor-22:ctx-e044255f job-57) (logid:0e16600e) Complete async
> > job-57, jobStatus: FAILED, resultCode: 530, result:
> >
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable
> > to create a deployment for VM[User|i-2-12-VM]"}
> > 2019-06-11 11:37:05,302 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768)
> > com.cloud.exception.InsufficientServerCapacityException: Unable to
> create a
> > deployment for VM[User|i-2-13-VM]Scope=interface com.cloud.dc.DataCenter;
> > id=1
> > 2019-06-11 11:37:05,302 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
> > (API-Job-Executor-24:ctx-34beda4d job-62 ctx-7fcf55ab) (logid:5b3ad768)
> > Unable to create a deployment for VM[User|i-2-13-VM]
> > com.cloud.exception.InsufficientServerCapacityException: Unable to create
> > a deployment for VM[User|i-2-13-VM]Scope=interface
> com.cloud.dc.DataCenter;
> > id=1
> > 2019-06-11 11:37:05,302 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Complete async
> > job-62, jobStatus: FAILED, resultCode: 530, result:
> >
> org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable
> > to create a deployment for VM[User|i-2-13-VM]"}
> > root@cloudstack-manager:/home/team# grep -i "job-62"
> > /var/log/cloudstack/management/management-server.log
> > 2019-06-11 11:37:03,453 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> > (API-Job-Executor-24:ctx-34beda4d job-62) (logid:fb7a7cb5) Add j
Re: launch instance error
o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Update db status
for job-62
2019-06-11 11:37:05,304 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Wake up jobs
joined with job-62 and disjoin all subjobs created from job- 62
2019-06-11 11:37:05,386 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Done executing
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin for job-62
2019-06-11 11:37:05,386 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-24:ctx-34beda4d job-62) (logid:5b3ad768) Remove job-62
from job monitoring
On Mon, Jun 10, 2019 at 2:51 PM Andrija Panic
wrote:
> Interesting lines being:
>
> FirstFitRoutingAllocator) (logid:0a0b5a30) FirstFitAllocator has 1 hosts to
> check for allocation: [Host[-4-Routing]]
> 2019-06-10 13:40:11,373 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7
> FirstFitRoutingAllocator) (logid:0a0b5a30) Not considering hosts:
> [Host[-4-Routing]] to deploy template:
> Tmpl[201-TAR-201-2-ff22b996-a840-3cce-bec2-9ea6ab3081da as they are not HVM
> enabled
> 2019-06-10 13:40:11,374 DEBUG [c.c.a.m.a.i.FirstFitAllocator]
> (API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7
> FirstFitRoutingAllocator) (logid:0a0b5a30) Found 0 hosts for allocation
> after prioritization: []
>
> i.e. remove the HVM flag from the template and try again (register a new
> template - or go to cloud.vm_templates DB table and set HVM=0 where your
> template=)
>
> Andrija
>
> On Mon, 10 Jun 2019 at 20:20, Alejandro Ruiz Bermejo <
> arbermejo0...@gmail.com> wrote:
>
> > i don't know if its ok sending files over here. In case it is here is the
> > content of the previous fail i sended
> >
> > root@cloudstack-manager:/home/team# grep -i "job-41"
> > /var/log/cloudstack/management/management-server.log
> > 2019-06-10 13:40:11,238 INFO [o.a.c.f.j.i.AsyncJobMonitor]
> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:5a0455dd) Add job-41
> into
> > job monitoring
> > 2019-06-10 13:40:11,246 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Executing
> > AsyncJobVO {id:41, userId: 2, accountId: 2, instanceType: VirtualMachine,
> > instanceId: 10, cmd:
> > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
> >
> >
> {"httpmethod":"GET","templateid":"574ce32a-cb06-4f9e-b423-cb2a3e053950","ctxAccountId":"2","uuid":"e5106e36-c36d-49e1-b8e8-4a82ce6fc025","cmdEventType":"VM.CREATE","diskofferingid":"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed","serviceofferingid":"57675b96-98fa-49a3-9437-24f9dbf3fd90","response":"json","ctxUserId":"2","hypervisor":"LXC","zoneid":"5b03beea-ffdd-45ea-84eb-64110f3ff0d0","ctxStartEventId":"108","id":"10","ctxDetails":"{\"interface
> >
> >
> com.cloud.vm.VirtualMachine\":\"e5106e36-c36d-49e1-b8e8-4a82ce6fc025\",\"interface
> >
> >
> com.cloud.offering.ServiceOffering\":\"57675b96-98fa-49a3-9437-24f9dbf3fd90\",\"interface
> >
> >
> com.cloud.dc.DataCenter\":\"5b03beea-ffdd-45ea-84eb-64110f3ff0d0\",\"interface
> >
> >
> com.cloud.offering.DiskOffering\":\"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed\",\"interface
> >
> >
> com.cloud.template.VirtualMachineTemplate\":\"574ce32a-cb06-4f9e-b423-cb2a3e053950\"}","_":"1560188536922"},
> > cmdVersion: 0, status: IN_PROGRESS, processStatus: 0, resultCode: 0,
> > result: null, initMsid: 207380201932, completeMsid: null, lastUpdated:
> > null, lastPolled: null, created: null}
> > 2019-06-10 13:40:11,248 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
> > (qtp895947612-329:ctx-37027106 ctx-58323b07) (logid:396f8582) submit
> async
> > job-41, details: AsyncJobVO {id:41, userId: 2, accountId: 2,
> instanceType:
> > VirtualMachine, instanceId: 10, cmd:
> > org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
> >
> >
> {"httpmethod":"GET","templateid":"574ce32a-cb06-4f9e-b423-cb2a3e053950","ctxAccountId":"2","uuid":"e5106e36-c36d-49e1-b8e8-4a82ce6fc025","cmdEventType":"VM.CREATE","diskofferingid":"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed
Re: launch instance error
r-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
Updating resource Type = volume count for Account = 2 Operation =
decreasing Amount = 1
2019-06-10 13:40:12,598 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
Updating resource Type = primary_storage count for Account = 2 Operation =
decreasing Amount = 21474836480
2019-06-10 13:40:12,707 WARN [o.a.c.alerts]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
AlertType:: 8 | dataCenterId:: 1 | podId:: null | clusterId:: null |
message:: Failed to deploy Vm with Id: 10, on Host with Id: null
2019-06-10 13:40:12,790 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
Updating resource Type = user_vm count for Account = 2 Operation =
decreasing Amount = 1
2019-06-10 13:40:12,873 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
Updating resource Type = cpu count for Account = 2 Operation = decreasing
Amount = 1
2019-06-10 13:40:12,957 DEBUG [c.c.r.ResourceLimitManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
Updating resource Type = memory count for Account = 2 Operation =
decreasing Amount = 1024
2019-06-10 13:40:13,124 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
com.cloud.exception.InsufficientServerCapacityException: Unable to create a
deployment for VM[User|i-2-10-VM]Scope=interface com.cloud.dc.DataCenter;
id=1
2019-06-10 13:40:13,124 INFO [o.a.c.a.c.a.v.DeployVMCmdByAdmin]
(API-Job-Executor-14:ctx-b92e08df job-41 ctx-3d41bde7) (logid:0a0b5a30)
Unable to create a deployment for VM[User|i-2-10-VM]
2019-06-10 13:40:13,124 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Complete async
job-41, jobStatus: FAILED, resultCode: 530, result:
org.apache.cloudstack.api.response.ExceptionResponse/null/{"uuidList":[],"errorcode":533,"errortext":"Unable
to create a deployment for VM[User|i-2-10-VM]"}
2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Publish async
job-41 complete on message bus
2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Wake up jobs
related to job-41
2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Update db status
for job-41
2019-06-10 13:40:13,125 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Wake up jobs
joined with job-41 and disjoin all subjobs created from job- 41
2019-06-10 13:40:13,207 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Done executing
org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin for job-41
2019-06-10 13:40:13,207 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Remove job-41
from job monitoring
On Mon, Jun 10, 2019 at 1:42 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:
> Hi Alejandro,
>
> Can you verify if the expected checksum is the correct and i that case
> update the checksum column on vm_template table fot that template and
> restart management server?
>
> Regards,
> Nicolas Vazquez
>
> From: Alejandro Ruiz Bermejo
> Sent: Monday, June 10, 2019 12:38:52 PM
> To: users@cloudstack.apache.org
> Subject: launch instance error
>
> Hi, I'm working with Cloudstack 4.11.2.0
>
> This is my environment:
> 1 Zone
> 1 Pod
> 2 Clusters (LXC and KVM)
> 2 Hosts (one in each cluster)
>
> i can launch perfectly VMs on the KVM cluster but when i'm trying to launch
> a new VM with an LXC template i'm getting this error:
>
> 2019-06-10 11:24:28,961 INFO [a.c.c.a.ApiServer]
> (qtp895947612-18:ctx-e1a5bd5e ctx-bc704f1b) (logid:2635d81d) (userId=2
> accountId=2 sessionId=node0a04x8pj44gz8mf2hb5ikizk20) 10.8.2.116 -- GET
> command=listAlerts=json=1=4&_=1560180395194 200
>
> {"listalertsresponse":{"count":16,"alert":[{"id":"c896ae0a-764b-4976-9dc1-7868f9f61e3c","type":8,"name":"ALERT.USERVM","description":"Failed
> to deploy Vm with Id: 5, on Host with Id:
>
> null","sent":"2019-06-10T11:15:19-0400"},{"id":"42988261-9238-430f-af54-1582073b35d0","type":8,"name":"ALERT.USERVM","description":"Failed
> to deploy Vm with Id: 4, on Host with Id:
>
> null","sent":"2019-06-10T10:36:40-0400"},{"id":"fc89bba6-9890-4aa7-b57a-3dc3a2e14643","type":8,"name":"ALERT.USERVM","description":"Failed
> to deploy Vm with Id: 3, on Host with Id:
>
> null","sent":"2019-06-10T10:31:05-0400"},{"id":"e3ab7e4b-5ce7-4c50-893e-0432c23f684f","type":28,"name":"ALERT.UPLOAD.FAILED","description":"Failed
> to register template: 59eaea2c-8883-11e9-bc81-003048d2c1cc with error:
> Failed post download script: checksum
> \"{MD5}292bfea2667a3a23a71d42d53d68b8fc\" didn't match the given value,
>
> \"{MD5}c2c4fa2d0978121c7977db571f132d6e\"","sent":"2019-06-10T10:28:19-0400"}]}}
>
> I'm seeing two errors here one is the Host ID: * Host with Id: null*
> And the other one is a checksum verification
>
> When i created the LXC template i had to change the Download Keyserver for
> the lxc-create -t download step so idk if this is causing the checksum
> error
>
> any help with this would be great
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK
> @shapeblue
>
>
>
>
Re: launch instance error
Hi, thanks for your answer, as an update of mi issue i've keep digging on
it and found this the log for the job. It seems like the allocation server
can't find my LXC host inside the LXC cluster. I don't know anymore if my
trouble is because the checksum. I attach here the file with the log output
In case is still a checksum trouble how can i verify wich one was the
expected?
On Mon, Jun 10, 2019 at 1:42 PM Nicolas Vazquez <
nicolas.vazq...@shapeblue.com> wrote:
> Hi Alejandro,
>
> Can you verify if the expected checksum is the correct and i that case
> update the checksum column on vm_template table fot that template and
> restart management server?
>
> Regards,
> Nicolas Vazquez
> ________
> From: Alejandro Ruiz Bermejo
> Sent: Monday, June 10, 2019 12:38:52 PM
> To: users@cloudstack.apache.org
> Subject: launch instance error
>
> Hi, I'm working with Cloudstack 4.11.2.0
>
> This is my environment:
> 1 Zone
> 1 Pod
> 2 Clusters (LXC and KVM)
> 2 Hosts (one in each cluster)
>
> i can launch perfectly VMs on the KVM cluster but when i'm trying to launch
> a new VM with an LXC template i'm getting this error:
>
> 2019-06-10 11:24:28,961 INFO [a.c.c.a.ApiServer]
> (qtp895947612-18:ctx-e1a5bd5e ctx-bc704f1b) (logid:2635d81d) (userId=2
> accountId=2 sessionId=node0a04x8pj44gz8mf2hb5ikizk20) 10.8.2.116 -- GET
> command=listAlerts=json=1=4&_=1560180395194 200
>
> {"listalertsresponse":{"count":16,"alert":[{"id":"c896ae0a-764b-4976-9dc1-7868f9f61e3c","type":8,"name":"ALERT.USERVM","description":"Failed
> to deploy Vm with Id: 5, on Host with Id:
>
> null","sent":"2019-06-10T11:15:19-0400"},{"id":"42988261-9238-430f-af54-1582073b35d0","type":8,"name":"ALERT.USERVM","description":"Failed
> to deploy Vm with Id: 4, on Host with Id:
>
> null","sent":"2019-06-10T10:36:40-0400"},{"id":"fc89bba6-9890-4aa7-b57a-3dc3a2e14643","type":8,"name":"ALERT.USERVM","description":"Failed
> to deploy Vm with Id: 3, on Host with Id:
>
> null","sent":"2019-06-10T10:31:05-0400"},{"id":"e3ab7e4b-5ce7-4c50-893e-0432c23f684f","type":28,"name":"ALERT.UPLOAD.FAILED","description":"Failed
> to register template: 59eaea2c-8883-11e9-bc81-003048d2c1cc with error:
> Failed post download script: checksum
> \"{MD5}292bfea2667a3a23a71d42d53d68b8fc\" didn't match the given value,
>
> \"{MD5}c2c4fa2d0978121c7977db571f132d6e\"","sent":"2019-06-10T10:28:19-0400"}]}}
>
> I'm seeing two errors here one is the Host ID: * Host with Id: null*
> And the other one is a checksum verification
>
> When i created the LXC template i had to change the Download Keyserver for
> the lxc-create -t download step so idk if this is causing the checksum
> error
>
> any help with this would be great
>
> nicolas.vazq...@shapeblue.com
> www.shapeblue.com
> Amadeus House, Floral Street, London WC2E 9DPUK
> @shapeblue
>
>
>
>
root@cloudstack-manager:/home/team# grep -i "job-41"
/var/log/cloudstack/management/management-server.log
2019-06-10 13:40:11,238 INFO [o.a.c.f.j.i.AsyncJobMonitor]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:5a0455dd) Add job-41 into job
monitoring
2019-06-10 13:40:11,246 DEBUG [o.a.c.f.j.i.AsyncJobManagerImpl]
(API-Job-Executor-14:ctx-b92e08df job-41) (logid:0a0b5a30) Executing AsyncJobVO
{id:41, userId: 2, accountId: 2, instanceType: VirtualMachine, instanceId: 10,
cmd: org.apache.cloudstack.api.command.admin.vm.DeployVMCmdByAdmin, cmdInfo:
{"httpmethod":"GET","templateid":"574ce32a-cb06-4f9e-b423-cb2a3e053950","ctxAccountId":"2","uuid":"e5106e36-c36d-49e1-b8e8-4a82ce6fc025","cmdEventType":"VM.CREATE","diskofferingid":"74099b7a-d7bd-44a8-b7da-b01e8e6fa2ed","serviceofferingid":"57675b96-98fa-49a3-9437-24f9dbf3fd90","response":"json","ctxUserId":"2","hypervisor":"LXC","zoneid":"5b03beea-ffdd-45ea-84eb-64110f3ff0d0","ctxStartEventId":"108","id":"10","ctxDetails":"{\"interface
com.cloud.vm.VirtualMachine\":\"e5106e36-c36d-49e1-b8e8-4a82ce6fc025\",\"interface
com.cloud.offering.ServiceOffering\":\"57675b96-98fa-49a3-9437-24f9dbf3fd90\",\"interface
com.cloud.dc.DataCenter\":\"5
launch instance error
Hi, I'm working with Cloudstack 4.11.2.0
This is my environment:
1 Zone
1 Pod
2 Clusters (LXC and KVM)
2 Hosts (one in each cluster)
i can launch perfectly VMs on the KVM cluster but when i'm trying to launch
a new VM with an LXC template i'm getting this error:
2019-06-10 11:24:28,961 INFO [a.c.c.a.ApiServer]
(qtp895947612-18:ctx-e1a5bd5e ctx-bc704f1b) (logid:2635d81d) (userId=2
accountId=2 sessionId=node0a04x8pj44gz8mf2hb5ikizk20) 10.8.2.116 -- GET
command=listAlerts=json=1=4&_=1560180395194 200
{"listalertsresponse":{"count":16,"alert":[{"id":"c896ae0a-764b-4976-9dc1-7868f9f61e3c","type":8,"name":"ALERT.USERVM","description":"Failed
to deploy Vm with Id: 5, on Host with Id:
null","sent":"2019-06-10T11:15:19-0400"},{"id":"42988261-9238-430f-af54-1582073b35d0","type":8,"name":"ALERT.USERVM","description":"Failed
to deploy Vm with Id: 4, on Host with Id:
null","sent":"2019-06-10T10:36:40-0400"},{"id":"fc89bba6-9890-4aa7-b57a-3dc3a2e14643","type":8,"name":"ALERT.USERVM","description":"Failed
to deploy Vm with Id: 3, on Host with Id:
null","sent":"2019-06-10T10:31:05-0400"},{"id":"e3ab7e4b-5ce7-4c50-893e-0432c23f684f","type":28,"name":"ALERT.UPLOAD.FAILED","description":"Failed
to register template: 59eaea2c-8883-11e9-bc81-003048d2c1cc with error:
Failed post download script: checksum
\"{MD5}292bfea2667a3a23a71d42d53d68b8fc\" didn't match the given value,
\"{MD5}c2c4fa2d0978121c7977db571f132d6e\"","sent":"2019-06-10T10:28:19-0400"}]}}
I'm seeing two errors here one is the Host ID: * Host with Id: null*
And the other one is a checksum verification
When i created the LXC template i had to change the Download Keyserver for
the lxc-create -t download step so idk if this is causing the checksum error
any help with this would be great
Re: multi-hipervisor deployment
This is the output of systemctl status libvirt-bin on the lxc hipervisor node. Is that what you asked for? libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2019-05-27 18:06:38 CDT; 22h ago Docs: man:libvirtd(8) http://libvirt.org Main PID: 5008 (libvirtd) Tasks: 18 Memory: 36.1M CPU: 23.816s CGroup: /system.slice/libvirt-bin.service ├─2006 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvi ├─2007 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvi └─5008 /usr/sbin/libvirtd May 27 18:06:38 cloudstack systemd[1]: Starting Virtualization daemon... May 27 18:06:38 cloudstack systemd[1]: Started Virtualization daemon. May 27 18:06:59 cloudstack dnsmasq[2006]: read /etc/hosts - 5 addresses May 27 18:06:59 cloudstack dnsmasq[2006]: read /var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses May 27 18:06:59 cloudstack dnsmasq-dhcp[2006]: read /var/lib/libvirt/dnsmasq/default.hostsfile May 27 18:07:01 cloudstack libvirtd[5008]: libvirt version: 1.3.1, package: 1ubuntu10.26 (Marc Deslauriers May 27 18:07:01 cloudstack libvirtd[5008]: hostname: cloudstack May 27 18:07:01 cloudstack libvirtd[5008]: Configured security driver "none" disables default policy to create confined guests May 27 18:07:03 cloudstack libvirtd[5008]: unsupported configuration: Security driver apparmor not enabled On Mon, May 27, 2019 at 7:13 PM Ivan Kudryavtsev wrote: > Alejandro, what hv libvirt logs show? > > вт, 28 мая 2019 г., 4:49 Alejandro Ruiz Bermejo : > > > Hi, > > I have installed cloudstack 4.11.2 on ubuntu 16 with one management > server > > and one compute node with kvm. > > > > I want to add a new compute node with a different hipervisor (lxc) on > > another server with ubuntu 16. I'm following the docs instructions but > when > > i try to add the new host i get the following error on > > /var/log/cloudstack/agent.log > > > > 2019-05-27 17:43:53,280 WARN [cloud.resource.ServerResourceBase] > > (main:null) (logid:) Incorrect details for private Nic during > > initialization of ServerResourceBase > > 2019-05-27 17:43:53,281 ERROR [cloud.agent.AgentShell] (main:null) > (logid:) > > Unable to start agent: Unable to configure LibvirtComputingResource > > > > can someone please help with this? > > > > Regards, > > Alejandro > > >
multi-hipervisor deployment
Hi, I have installed cloudstack 4.11.2 on ubuntu 16 with one management server and one compute node with kvm. I want to add a new compute node with a different hipervisor (lxc) on another server with ubuntu 16. I'm following the docs instructions but when i try to add the new host i get the following error on /var/log/cloudstack/agent.log 2019-05-27 17:43:53,280 WARN [cloud.resource.ServerResourceBase] (main:null) (logid:) Incorrect details for private Nic during initialization of ServerResourceBase 2019-05-27 17:43:53,281 ERROR [cloud.agent.AgentShell] (main:null) (logid:) Unable to start agent: Unable to configure LibvirtComputingResource can someone please help with this? Regards, Alejandro
Instance creation troubles
Hi, I've installed CloudStack 4.11.2.0 on Ubuntu 16. My current deployment is very simple I have two nodes(1 manger and 1 compute), i'm using KVM as hypervisor and already created zone, pod, KVM cluster, and configured primary and secondary storage. Within the zone there are already the Secondary Storage VM and the Console Proxy VM, both up and running. My problem is when i try to create a new guest instance in my cloudstack environment on the dashboard i can't see any available templates to choose. I downloaded via the UI and added a template but it seems to be active in the zone but not ready I already loogged into the secondary storage VM and checked his status with /usr/local/cloud/systemvm/ssvm-check.sh and everything seems to be working ok this is the output root@s-7-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh First DNS server is 10.8.6.69 PING 10.8.6.69 (10.8.6.69): 56 data bytes 64 bytes from 10.8.6.69: icmp_seq=0 ttl=63 time=0.694 ms 64 bytes from 10.8.6.69: icmp_seq=1 ttl=63 time=0.410 ms --- 10.8.6.69 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.410/0.552/0.694/0.142 ms Good: Can ping DNS server Good: DNS resolves cloudstack.apache.org nfs is currently mounted Mount point is /mnt/SecStorage/b303ab68-3602-357a-a983-e7cb8e1d1788 Good: Can write to mount point Management server is 10.8.9.235. Checking connectivity. /usr/local/cloud/systemvm/ssvm-check.sh: line 121: warning: command substitution: ignored null byte in input Good: Can connect to management server port 8250 Good: Java process is running Tests Complete. Look for ERROR or WARNING above. As Data for troubleshooting my subnet for the public and private networks are the same (i already allowed in General Settings the full 10.8.9.0/24 subnet load to the cloud) Can someone please help me with this? Regards, Alejandro
ADD LXC HOST
I'm deploying LXC Hipervisor in a new cluster in my zone in Apache CloudStack 4.11.0 I followed the documentation directions and already configured networking and libvirt. When i try to add the new host Libvirtd is crashing this is the output of systemctl status libvirt-bin on the hipevisor node libvirt-bin.service - Virtualization daemon Loaded: loaded (/lib/systemd/system/libvirt-bin.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit-hit) since Mon 2019-05-20 10:28:14 CDT; 13min ago Docs: man:libvirtd(8) http://libvirt.org Process: 3368 ExecStart=/usr/sbin/libvirtd $libvirtd_opts (code=exited, status=1/FAILURE) Main PID: 3368 (code=exited, status=1/FAILURE) Tasks: 18 Memory: 29.5M CPU: 22ms CGroup: /system.slice/libvirt-bin.service ├─2185 /usr/sbin/libvirtd -d -l ├─2495 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelpe └─2496 /usr/sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro --dhcp-script=/usr/lib/libvirt/libvirt_leaseshelpe May 20 10:28:14 cloudstak-lxc-host systemd[1]: Failed to start Virtualization daemon. May 20 10:28:14 cloudstak-lxc-host systemd[1]: libvirt-bin.service: Unit entered failed state. May 20 10:28:14 cloudstak-lxc-host systemd[1]: libvirt-bin.service: Failed with result 'exit-code'. May 20 10:28:14 cloudstak-lxc-host systemd[1]: libvirt-bin.service: Service hold-off time over, scheduling restart. May 20 10:28:14 cloudstak-lxc-host systemd[1]: Stopped Virtualization daemon. May 20 10:28:14 cloudstak-lxc-host systemd[1]: libvirt-bin.service: Start request repeated too quickly. May 20 10:28:14 cloudstak-lxc-host systemd[1]: Failed to start Virtualization daemon. May 20 10:28:14 cloudstak-lxc-host systemd[1]: libvirt-bin.service: Unit entered failed state. May 20 10:28:14 cloudstak-lxc-host systemd[1]: libvirt-bin.service: Failed with result 'start-limit-hit'. can someone help with this error? If i restart the host libvirt-bin status is okok. But when i try to add the host it crash
Add KVM host
hi, I'm setting up CloudStack 4.12. I've already deployed the management server, and right now i'm adding the first KVM Host but it is giving me errors. I already recondigured everything and read the guidelines on the official docs site. This is the output of *grep -i -E 'exception|unable|fail|invalid|leak|warn|error' /var/log/cloudstack/management/management-server.log* 2019-05-15 10:59:28,507 WARN [c.c.a.d.ParamGenericValidationWorker] (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Received unknown parameters for command addHost. Unknown parameters : clustertype 2019-05-15 10:59:33,105 WARN [c.c.h.k.d.LibvirtServerDiscoverer] (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) can't setup agent, due to com.cloud.utils.exception.CloudRuntimeException: Failed to setup keystore on the KVM host: 10.8.9.236 - Failed to setup keystore on the KVM host: 10.8.9.236 2019-05-15 10:59:33,106 WARN [c.c.r.ResourceManagerImpl] (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Unable to find the server resources at http://10.8.9.236 2019-05-15 10:59:33,106 INFO [c.c.u.e.CSExceptionErrorCode] (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Could not find exception: com.cloud.exception.DiscoveryException in error code list for exceptions 2019-05-15 10:59:33,106 WARN [o.a.c.a.c.a.h.AddHostCmd] (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Exception: com.cloud.exception.DiscoveryException: Unable to add the host 2019-05-15 10:59:33,108 INFO [c.c.a.ApiServer] (qtp858242339-256:ctx-1c43c232 ctx-b610) (logid:02d95edb) Unable to add the host
Re: installation-database
can't see any problem there this is the full output of the previous command
root@cloudstack1:/home/team# cloudstack-setup-databases cloud:123@10.8.9.230
--deploy-as=root:123 -i 10.8.9.230
Mysql user name:cloud
[ OK ]
Mysql user password:**
[ OK ]
Mysql server ip:10.8.9.230
[ OK ]
Mysql server port:3306
[ OK ]
Mysql root user name:root
[ OK ]
Mysql root user password:**
[ OK ]
Using specified cluster management server node IP 10.8.9.230
[ OK ]
Checking Cloud database files ...
[ OK ]
Checking local machine hostname ...
[ OK ]
Checking SELinux setup ...
[ OK ]
Preparing /etc/cloudstack/management/db.properties
[ OK ]
Applying /usr/share/cloudstack-management/setup/create-database.sql
We apologize for below error:
***
Encountering an error when executing mysql script
--
table:
/usr/share/cloudstack-management/setup/create-database.sql
Error:
mysql: [Warning] Using a password on the command line interface can be
insecure.
ERROR 2003 (HY000): Can't connect to MySQL server on '10.8.9.230' (111)
Sql parameters:
{'passwd': '123', 'host': '10.8.9.230', 'user': 'root', 'port': 3306}
--
On Wed, Feb 20, 2019 at 2:02 PM Ivan Kudryavtsev
wrote:
> Looks like this is what exactly means. Check your mysql configuration for
> root connection from the host you use to deploy. First try with 'mysql'
> cli utility.
>
> ср, 20 февр. 2019 г. в 13:46, Alejandro Ruiz Bermejo <
> arbermejo0...@gmail.com>:
>
> > i got this error when creating the cloudstack management database and
> don't
> > know where the problem is. Any idea??
> >
> > the command i use was cloudstack-setup-databases cloud:123@10.8.9.230
> > --deploy-as=root:123 -i 10.8.9.230
> >
> >
> > ERROR 2003 (HY000): Can't connect to MySQL server on '10.8.9.230' (111)
> >
> >
> > Sql parameters:
> > {'passwd': '123', 'host': '10.8.9.230', 'user': 'root', 'port': 3306}
> >
> > this is the content of /etc/cloudstack/management/db.properties
> >
> > cluster.node.IP=10.8.9.230
> > cluster.servlet.port=9090
> > region.id=1
> >
> > # CloudStack database settings
> > db.cloud.username=cloud
> > db.cloud.password=cloud
> > db.cloud.host=localhost
> > db.cloud.driver=jdbc:mysql
> > db.cloud.port=3306
> > db.cloud.name=cloud
> >
>
>
> --
> With best regards, Ivan Kudryavtsev
> Bitworks LLC
> Cell RU: +7-923-414-1515
> Cell USA: +1-201-257-1512
> WWW: http://bitworks.software/ <http://bw-sw.com/>
>
installation-database
i got this error when creating the cloudstack management database and don't
know where the problem is. Any idea??
the command i use was cloudstack-setup-databases cloud:123@10.8.9.230
--deploy-as=root:123 -i 10.8.9.230
ERROR 2003 (HY000): Can't connect to MySQL server on '10.8.9.230' (111)
Sql parameters:
{'passwd': '123', 'host': '10.8.9.230', 'user': 'root', 'port': 3306}
this is the content of /etc/cloudstack/management/db.properties
cluster.node.IP=10.8.9.230
cluster.servlet.port=9090
region.id=1
# CloudStack database settings
db.cloud.username=cloud
db.cloud.password=cloud
db.cloud.host=localhost
db.cloud.driver=jdbc:mysql
db.cloud.port=3306
db.cloud.name=cloud
Re: installation troubles
IT WORKS!!! thanks Ivan On Wed, Feb 20, 2019 at 12:18 PM Alejandro Ruiz Bermejo < arbermejo0...@gmail.com> wrote: > ok let me try. Thanks > > On Wed, Feb 20, 2019 at 12:15 PM Ivan Kudryavtsev < > kudryavtsev...@bw-sw.com> wrote: > >> That's OK. Just go ahead. >> >> ср, 20 февр. 2019 г. в 12:14, Alejandro Ruiz Bermejo < >> arbermejo0...@gmail.com>: >> >> > when i try with that option i'm getting signature errors. Even after >> wget >> > -O - http://download.cloudstack.org/release.asc|apt-key add - >> > >> > On Wed, Feb 20, 2019 at 12:11 PM Ivan Kudryavtsev < >> > kudryavtsev...@bw-sw.com> >> > wrote: >> > >> > > This looks strange to me. I always use repo >> > > >> > > root@cs2-head1:~# cat /etc/apt/sources.list.d/cloudstack.list >> > > deb http://cloudstack.apt-get.eu/ubuntu xenial 4.11 >> > > >> > > and it works just fine. >> > > >> > > ср, 20 февр. 2019 г. в 12:08, Alejandro Ruiz Bermejo < >> > > arbermejo0...@gmail.com>: >> > > >> > > > but i'm following the instrucions of the oficial guide at >> > > > >> http://docs.cloudstack.apache.org/en/4.11.2.0/installguide/index.html >> > > > >> > > > It is why i'm asking >> > > > >> > > > what other way do i have >> > > > >> > > > On Wed, Feb 20, 2019 at 12:05 PM Ivan Kudryavtsev < >> > > > kudryavtsev...@bw-sw.com> >> > > > wrote: >> > > > >> > > > > Alejandro, >> > > > > I'm not sure the community is able to help you with local DEB repo >> > you >> > > > host >> > > > > in the network. Try to use the guide and install from the official >> > > > > repository. >> > > > > >> > > > > ср, 20 февр. 2019 г. в 11:55, Alejandro Ruiz Bermejo < >> > > > > arbermejo0...@gmail.com>: >> > > > > >> > > > > > i'm the network administrator, and the repository is a local one >> > that >> > > > we >> > > > > > ave. But that's not the problem. the thing is with the one with >> IP >> > > > > address >> > > > > > 10.8.9.230, wich is where i'm serving the .deb packages as the >> > guide >> > > > says >> > > > > > >> > > > > > On Wed, Feb 20, 2019 at 11:35 AM Ivan Kudryavtsev < >> > > > > > kudryavtsev...@bw-sw.com> >> > > > > > wrote: >> > > > > > >> > > > > > > Hi. The network 10.X.X.X/8 is a private network which resides >> > > inside >> > > > > your >> > > > > > > LAN. Consult with your network administrator. Doesn't look >> like >> > you >> > > > are >> > > > > > > getting packages from the right download repository. >> > > > > > > >> > > > > > > ср, 20 февр. 2019 г. в 11:30, Alejandro Ruiz Bermejo < >> > > > > > > arbermejo0...@gmail.com>: >> > > > > > > >> > > > > > > > Hi i'm new with openstack and i'm following the installation >> > > guide >> > > > of >> > > > > > the >> > > > > > > > oficial site. Untill now i already got compiled the source >> > > > packages >> > > > > > and >> > > > > > > > i'm adding the apt repository but when i run the apt-get >> update >> > > i'm >> > > > > > > having >> > > > > > > > this error >> > > > > > > > >> > > > > > > > Ign:1 http://10.8.9.230/cloudstack/repo/binary ./ InRelease >> > > > > > > > Ign:2 http://10.8.9.230/cloudstack/repo/binary ./ Release >> > > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ >> > > > Translation-en_US >> > > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ >> > Translation-en >> > > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > > > > &
Re: installation troubles
ok let me try. Thanks On Wed, Feb 20, 2019 at 12:15 PM Ivan Kudryavtsev wrote: > That's OK. Just go ahead. > > ср, 20 февр. 2019 г. в 12:14, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com>: > > > when i try with that option i'm getting signature errors. Even after wget > > -O - http://download.cloudstack.org/release.asc|apt-key add - > > > > On Wed, Feb 20, 2019 at 12:11 PM Ivan Kudryavtsev < > > kudryavtsev...@bw-sw.com> > > wrote: > > > > > This looks strange to me. I always use repo > > > > > > root@cs2-head1:~# cat /etc/apt/sources.list.d/cloudstack.list > > > deb http://cloudstack.apt-get.eu/ubuntu xenial 4.11 > > > > > > and it works just fine. > > > > > > ср, 20 февр. 2019 г. в 12:08, Alejandro Ruiz Bermejo < > > > arbermejo0...@gmail.com>: > > > > > > > but i'm following the instrucions of the oficial guide at > > > > > http://docs.cloudstack.apache.org/en/4.11.2.0/installguide/index.html > > > > > > > > It is why i'm asking > > > > > > > > what other way do i have > > > > > > > > On Wed, Feb 20, 2019 at 12:05 PM Ivan Kudryavtsev < > > > > kudryavtsev...@bw-sw.com> > > > > wrote: > > > > > > > > > Alejandro, > > > > > I'm not sure the community is able to help you with local DEB repo > > you > > > > host > > > > > in the network. Try to use the guide and install from the official > > > > > repository. > > > > > > > > > > ср, 20 февр. 2019 г. в 11:55, Alejandro Ruiz Bermejo < > > > > > arbermejo0...@gmail.com>: > > > > > > > > > > > i'm the network administrator, and the repository is a local one > > that > > > > we > > > > > > ave. But that's not the problem. the thing is with the one with > IP > > > > > address > > > > > > 10.8.9.230, wich is where i'm serving the .deb packages as the > > guide > > > > says > > > > > > > > > > > > On Wed, Feb 20, 2019 at 11:35 AM Ivan Kudryavtsev < > > > > > > kudryavtsev...@bw-sw.com> > > > > > > wrote: > > > > > > > > > > > > > Hi. The network 10.X.X.X/8 is a private network which resides > > > inside > > > > > your > > > > > > > LAN. Consult with your network administrator. Doesn't look like > > you > > > > are > > > > > > > getting packages from the right download repository. > > > > > > > > > > > > > > ср, 20 февр. 2019 г. в 11:30, Alejandro Ruiz Bermejo < > > > > > > > arbermejo0...@gmail.com>: > > > > > > > > > > > > > > > Hi i'm new with openstack and i'm following the installation > > > guide > > > > of > > > > > > the > > > > > > > > oficial site. Untill now i already got compiled the source > > > > packages > > > > > > and > > > > > > > > i'm adding the apt repository but when i run the apt-get > update > > > i'm > > > > > > > having > > > > > > > > this error > > > > > > > > > > > > > > > > Ign:1 http://10.8.9.230/cloudstack/repo/binary ./ InRelease > > > > > > > > Ign:2 http://10.8.9.230/cloudstack/repo/binary ./ Release > > > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > > > Translation-en_US > > > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ > > Translation-en > > > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > > > Hit:6 http://10.8.11.4/ubuntu xenial InRelease > > > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > > > Translation-en_US > > > > > > > > Hit:7 http://10.8.11.4/ubuntu xenial-updates InRelease > > > > > > > > Hit:8 http://10.8.11.4/ubuntu xenial-backports InRelease > > > > > > > > Hit:9 http://10.8.11.4/ubuntu xenial-security InRelease > > > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ > &
Re: installation troubles
when i try with that option i'm getting signature errors. Even after wget -O - http://download.cloudstack.org/release.asc|apt-key add - On Wed, Feb 20, 2019 at 12:11 PM Ivan Kudryavtsev wrote: > This looks strange to me. I always use repo > > root@cs2-head1:~# cat /etc/apt/sources.list.d/cloudstack.list > deb http://cloudstack.apt-get.eu/ubuntu xenial 4.11 > > and it works just fine. > > ср, 20 февр. 2019 г. в 12:08, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com>: > > > but i'm following the instrucions of the oficial guide at > > http://docs.cloudstack.apache.org/en/4.11.2.0/installguide/index.html > > > > It is why i'm asking > > > > what other way do i have > > > > On Wed, Feb 20, 2019 at 12:05 PM Ivan Kudryavtsev < > > kudryavtsev...@bw-sw.com> > > wrote: > > > > > Alejandro, > > > I'm not sure the community is able to help you with local DEB repo you > > host > > > in the network. Try to use the guide and install from the official > > > repository. > > > > > > ср, 20 февр. 2019 г. в 11:55, Alejandro Ruiz Bermejo < > > > arbermejo0...@gmail.com>: > > > > > > > i'm the network administrator, and the repository is a local one that > > we > > > > ave. But that's not the problem. the thing is with the one with IP > > > address > > > > 10.8.9.230, wich is where i'm serving the .deb packages as the guide > > says > > > > > > > > On Wed, Feb 20, 2019 at 11:35 AM Ivan Kudryavtsev < > > > > kudryavtsev...@bw-sw.com> > > > > wrote: > > > > > > > > > Hi. The network 10.X.X.X/8 is a private network which resides > inside > > > your > > > > > LAN. Consult with your network administrator. Doesn't look like you > > are > > > > > getting packages from the right download repository. > > > > > > > > > > ср, 20 февр. 2019 г. в 11:30, Alejandro Ruiz Bermejo < > > > > > arbermejo0...@gmail.com>: > > > > > > > > > > > Hi i'm new with openstack and i'm following the installation > guide > > of > > > > the > > > > > > oficial site. Untill now i already got compiled the source > > packages > > > > and > > > > > > i'm adding the apt repository but when i run the apt-get update > i'm > > > > > having > > > > > > this error > > > > > > > > > > > > Ign:1 http://10.8.9.230/cloudstack/repo/binary ./ InRelease > > > > > > Ign:2 http://10.8.9.230/cloudstack/repo/binary ./ Release > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > Translation-en_US > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > Hit:6 http://10.8.11.4/ubuntu xenial InRelease > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > Translation-en_US > > > > > > Hit:7 http://10.8.11.4/ubuntu xenial-updates InRelease > > > > > > Hit:8 http://10.8.11.4/ubuntu xenial-backports InRelease > > > > > > Hit:9 http://10.8.11.4/ubuntu xenial-security InRelease > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > Translation-en_US > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > Translation-en_US > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > Translation-en_US > > > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > > > Err:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > > > 404 Not Found > > > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ > > Translation-en_US > &g
Re: installation troubles
but i'm following the instrucions of the oficial guide at http://docs.cloudstack.apache.org/en/4.11.2.0/installguide/index.html It is why i'm asking what other way do i have On Wed, Feb 20, 2019 at 12:05 PM Ivan Kudryavtsev wrote: > Alejandro, > I'm not sure the community is able to help you with local DEB repo you host > in the network. Try to use the guide and install from the official > repository. > > ср, 20 февр. 2019 г. в 11:55, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com>: > > > i'm the network administrator, and the repository is a local one that we > > ave. But that's not the problem. the thing is with the one with IP > address > > 10.8.9.230, wich is where i'm serving the .deb packages as the guide says > > > > On Wed, Feb 20, 2019 at 11:35 AM Ivan Kudryavtsev < > > kudryavtsev...@bw-sw.com> > > wrote: > > > > > Hi. The network 10.X.X.X/8 is a private network which resides inside > your > > > LAN. Consult with your network administrator. Doesn't look like you are > > > getting packages from the right download repository. > > > > > > ср, 20 февр. 2019 г. в 11:30, Alejandro Ruiz Bermejo < > > > arbermejo0...@gmail.com>: > > > > > > > Hi i'm new with openstack and i'm following the installation guide of > > the > > > > oficial site. Untill now i already got compiled the source packages > > and > > > > i'm adding the apt repository but when i run the apt-get update i'm > > > having > > > > this error > > > > > > > > Ign:1 http://10.8.9.230/cloudstack/repo/binary ./ InRelease > > > > Ign:2 http://10.8.9.230/cloudstack/repo/binary ./ Release > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > Hit:6 http://10.8.11.4/ubuntu xenial InRelease > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > > > Hit:7 http://10.8.11.4/ubuntu xenial-updates InRelease > > > > Hit:8 http://10.8.11.4/ubuntu xenial-backports InRelease > > > > Hit:9 http://10.8.11.4/ubuntu xenial-security InRelease > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > Err:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > > > 404 Not Found > > > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > > > Reading package lists... Done > > > > W: The repository 'http://10.8.9.230/cloudstack/repo/binary ./ > > Release' > > > > does not have a Release file. > > > > N: Data from such a repository can't be authenticated and is > therefore > > > > potentially dangerous to use. > > > > N: See apt-secure(8) manpage for repository creation and user > > > configuration > > > > details. > > > > E: Failed to fetch > http://10.8.9.230/cloudstack/repo/binary/./Packages > > > > 404 Not Found > > > > E: Some index files failed to download. They have been ignored, or > old > > > ones > > > > used instead. > > > > > > > > > > > > Can anyone help me fix this problem > > > > > > > > > > > > > -- > > > With best regards, Ivan Kudryavtsev > > > Bitworks LLC > > > Cell RU: +7-923-414-1515 > > > Cell USA: +1-201-257-1512 > > > WWW: http://bitworks.software/ <http://bw-sw.com/> > > > > > > > > -- > With best regards, Ivan Kudryavtsev > Bitworks LLC > Cell RU: +7-923-414-1515 > Cell USA: +1-201-257-1512 > WWW: http://bitworks.software/ <http://bw-sw.com/> >
Re: installation troubles
this is what i have in /etc/apt/sources.list.d/cloudstack.list deb http://10.8.9.230/cloudstack/repo/binary ./ and this is what i have in /etc/apache2/sites-available/000-default.conf DocumentRoot /var/www/cloudstack/repo/binary On Wed, Feb 20, 2019 at 11:56 AM Alejandro Ruiz Bermejo < arbermejo0...@gmail.com> wrote: > i'm the network administrator, and the repository is a local one that we > ave. But that's not the problem. the thing is with the one with IP address > 10.8.9.230, wich is where i'm serving the .deb packages as the guide says > > On Wed, Feb 20, 2019 at 11:35 AM Ivan Kudryavtsev < > kudryavtsev...@bw-sw.com> wrote: > >> Hi. The network 10.X.X.X/8 is a private network which resides inside your >> LAN. Consult with your network administrator. Doesn't look like you are >> getting packages from the right download repository. >> >> ср, 20 февр. 2019 г. в 11:30, Alejandro Ruiz Bermejo < >> arbermejo0...@gmail.com>: >> >> > Hi i'm new with openstack and i'm following the installation guide of >> the >> > oficial site. Untill now i already got compiled the source packages and >> > i'm adding the apt repository but when i run the apt-get update i'm >> having >> > this error >> > >> > Ign:1 http://10.8.9.230/cloudstack/repo/binary ./ InRelease >> > Ign:2 http://10.8.9.230/cloudstack/repo/binary ./ Release >> > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US >> > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en >> > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > Hit:6 http://10.8.11.4/ubuntu xenial InRelease >> > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US >> > Hit:7 http://10.8.11.4/ubuntu xenial-updates InRelease >> > Hit:8 http://10.8.11.4/ubuntu xenial-backports InRelease >> > Hit:9 http://10.8.11.4/ubuntu xenial-security InRelease >> > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en >> > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US >> > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en >> > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US >> > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en >> > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US >> > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en >> > Err:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages >> > 404 Not Found >> > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US >> > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en >> > Reading package lists... Done >> > W: The repository 'http://10.8.9.230/cloudstack/repo/binary ./ Release' >> > does not have a Release file. >> > N: Data from such a repository can't be authenticated and is therefore >> > potentially dangerous to use. >> > N: See apt-secure(8) manpage for repository creation and user >> configuration >> > details. >> > E: Failed to fetch http://10.8.9.230/cloudstack/repo/binary/./Packages >> > 404 Not Found >> > E: Some index files failed to download. They have been ignored, or old >> ones >> > used instead. >> > >> > >> > Can anyone help me fix this problem >> > >> >> >> -- >> With best regards, Ivan Kudryavtsev >> Bitworks LLC >> Cell RU: +7-923-414-1515 >> Cell USA: +1-201-257-1512 >> WWW: http://bitworks.software/ <http://bw-sw.com/> >> >
Re: installation troubles
i'm the network administrator, and the repository is a local one that we ave. But that's not the problem. the thing is with the one with IP address 10.8.9.230, wich is where i'm serving the .deb packages as the guide says On Wed, Feb 20, 2019 at 11:35 AM Ivan Kudryavtsev wrote: > Hi. The network 10.X.X.X/8 is a private network which resides inside your > LAN. Consult with your network administrator. Doesn't look like you are > getting packages from the right download repository. > > ср, 20 февр. 2019 г. в 11:30, Alejandro Ruiz Bermejo < > arbermejo0...@gmail.com>: > > > Hi i'm new with openstack and i'm following the installation guide of the > > oficial site. Untill now i already got compiled the source packages and > > i'm adding the apt repository but when i run the apt-get update i'm > having > > this error > > > > Ign:1 http://10.8.9.230/cloudstack/repo/binary ./ InRelease > > Ign:2 http://10.8.9.230/cloudstack/repo/binary ./ Release > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > Hit:6 http://10.8.11.4/ubuntu xenial InRelease > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > Hit:7 http://10.8.11.4/ubuntu xenial-updates InRelease > > Hit:8 http://10.8.11.4/ubuntu xenial-backports InRelease > > Hit:9 http://10.8.11.4/ubuntu xenial-security InRelease > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > Err:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages > > 404 Not Found > > Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US > > Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en > > Reading package lists... Done > > W: The repository 'http://10.8.9.230/cloudstack/repo/binary ./ Release' > > does not have a Release file. > > N: Data from such a repository can't be authenticated and is therefore > > potentially dangerous to use. > > N: See apt-secure(8) manpage for repository creation and user > configuration > > details. > > E: Failed to fetch http://10.8.9.230/cloudstack/repo/binary/./Packages > > 404 Not Found > > E: Some index files failed to download. They have been ignored, or old > ones > > used instead. > > > > > > Can anyone help me fix this problem > > > > > -- > With best regards, Ivan Kudryavtsev > Bitworks LLC > Cell RU: +7-923-414-1515 > Cell USA: +1-201-257-1512 > WWW: http://bitworks.software/ <http://bw-sw.com/> >
Fwd: installation troubles
Hi i'm new with openstack and i'm following the installation guide of the oficial site. Untill now i already got compiled the source packages and i'm adding the apt repository but when i run the apt-get update i'm having this error Ign:1 http://10.8.9.230/cloudstack/repo/binary ./ InRelease Ign:2 http://10.8.9.230/cloudstack/repo/binary ./ Release Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages Hit:6 http://10.8.11.4/ubuntu xenial InRelease Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US Hit:7 http://10.8.11.4/ubuntu xenial-updates InRelease Hit:8 http://10.8.11.4/ubuntu xenial-backports InRelease Hit:9 http://10.8.11.4/ubuntu xenial-security InRelease Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en Ign:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en Err:3 http://10.8.9.230/cloudstack/repo/binary ./ Packages 404 Not Found Ign:4 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en_US Ign:5 http://10.8.9.230/cloudstack/repo/binary ./ Translation-en Reading package lists... Done W: The repository 'http://10.8.9.230/cloudstack/repo/binary ./ Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch http://10.8.9.230/cloudstack/repo/binary/./Packages 404 Not Found E: Some index files failed to download. They have been ignored, or old ones used instead. Can anyone help me fix this problem
