Re: Secondary storage is not secondary properly
Hi Dag After changing localhost to management server ip oin global configuration I dont see the management server error. But the NFS error still persist Thanks and Regards Asanka On 8 August 2017 at 23:33, Asanka Gunasekarawrote: > Hi Dag, thanks for reply > > Did the change and the VMs are being rebuilt > > NFS server configuration, I took this from the installation guied > > [root@share ~]# cat /etc/exports > /share_smb/export/secondary *(rw,async,no_root_squash,no_subtree_check) > /share_smb/export/primary *(rw,async,no_root_squash,no_subtree_check) > [root@share ~]# > > > On 8 August 2017 at 17:06, Dag Sonstebo > wrote: > >> Hi Asanka, >> >> Can you change your “host” global setting to your management server IP >> (it’s currently set to “localhost”), restart your management service and >> then destroy your SSVM + let this recreate. >> >> Once done run the check again and let us know the outcome. >> >> Can you also show us the configuration of your NFS share – i.e. what >> parameters are set etc. >> >> Regards, >> Dag Sonstebo >> Cloud Architect >> ShapeBlue >> >> On 08/08/2017, 10:28, "Asanka Gunasekara" wrote: >> >> Hi Guys, >> >> ssvm-check.sh command output >> >> https://snag.gy/bzpE5n.jpg >> >> Details of my nfs share >> >> https://snag.gy/WgJxCY.jpg >> >> Thanks and Best Regards >> >> Asanka >> >> >> >> >> dag.sonst...@shapeblue.com >> www.shapeblue.com >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >> @shapeblue >> >> >> >> On 8 August 2017 at 14:48, Asanka Gunasekara wrote: >> >> > Thanks Makrand >> > >> > On 8 August 2017 at 14:42, Makrand wrote: >> > >> >> Asanka, >> >> >> >> The email list blocks the screen shots. I guess no one in the list >> can see >> >> your posted screens in emal chain. >> >> >> >> Better paste text output of the result or upload screens to image >> hosting >> >> (e.g. snag.gy). >> >> >> >> -- >> >> Makrand >> >> >> >> >> >> On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekara < >> asa...@nimbus.lk> >> >> wrote: >> >> >> >> > Hi Guys, thanks for replying buy running ssvm-check.sh I got >> below >> >> output >> >> > >> >> > >> >> > [image: Inline images 1] >> >> > >> >> > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 >> which is the >> >> > gateway and the Management server is 172.17.101.248 but it is >> looking >> >> in to >> >> > Loval host >> >> > >> >> > >> >> > >> >> > >> >> > [image: Inline images 2] >> >> > >> >> > What is going on, have I done something wrong? >> >> > >> >> > On 8 August 2017 at 14:22, Dag Sonstebo < >> dag.sonst...@shapeblue.com> >> >> > wrote: >> >> > >> >> >> Hi Asanka, >> >> >> >> >> >> One quick thing to check – log in to your SSVM and run >> >> >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you >> if the >> >> SSVM >> >> >> can mount and write to secondary storage. >> >> >> >> >> >> Regards, >> >> >> Dag Sonstebo >> >> >> Cloud Architect >> >> >> ShapeBlue >> >> >> >> >> >> From: Asanka Gunasekara >> >> >> Reply-To: "users@cloudstack.apache.org" < >> users@cloudstack.apache.org> >> >> >> Date: Tuesday, 8 August 2017 at 09:27 >> >> >> To: "users@cloudstack.apache.org" >> >> >> Subject: Re: Secondary storage is not secondary properly >> >> >> >> >> >> I am sorry Eric, thank you for replying, please see below for >> the rest >> >> >> results >> >> >> >> >> >> * Make sure that it's accessible from the *storage* network (the >> >> network >> >> >> that you configured as storage when you created the zone, >> assuming you >> >> >> selected advanced networking). >> >> >> Asanka > Since this is a test environemt I have just made it >> all in one >> >> >> subnet (is that the issue) >> >> >> >> >> >> * Is the secondary storage virtual machine up and running? >> Check your >> >> >> Infrastructure tab. >> >> >> Asanka > Yes both system VMs are up and running >> >> >> >> >> >> * If the secondary storage virtual machine is up and running, >> open its >> >> >> console and log in as root / password. Then check 'ip addr >> list' to >> >> make >> >> >> sure that it has IP addresses. >> >> >> Asanka > Yes it IP are assigned >> >> >> >> >> >> * If it has IP addresses, try pinging your secondary storage >> NFS server >> >> >> (still within the SSVM). >> >> >> Asanka > I can ping secondary storage >> >> >> >> >> >> * If you can ping your secondary storage NFS server, try >> mounting the >> >> NFS >> >> >> share at some random place in your filesystem to make sure you >> can >> >> mount it >> >> >>
Re: Secondary storage is not secondary properly
Hi Dag, thanks for reply Did the change and the VMs are being rebuilt NFS server configuration, I took this from the installation guied [root@share ~]# cat /etc/exports /share_smb/export/secondary *(rw,async,no_root_squash,no_subtree_check) /share_smb/export/primary *(rw,async,no_root_squash,no_subtree_check) [root@share ~]# On 8 August 2017 at 17:06, Dag Sonstebowrote: > Hi Asanka, > > Can you change your “host” global setting to your management server IP > (it’s currently set to “localhost”), restart your management service and > then destroy your SSVM + let this recreate. > > Once done run the check again and let us know the outcome. > > Can you also show us the configuration of your NFS share – i.e. what > parameters are set etc. > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > On 08/08/2017, 10:28, "Asanka Gunasekara" wrote: > > Hi Guys, > > ssvm-check.sh command output > > https://snag.gy/bzpE5n.jpg > > Details of my nfs share > > https://snag.gy/WgJxCY.jpg > > Thanks and Best Regards > > Asanka > > > > > dag.sonst...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > On 8 August 2017 at 14:48, Asanka Gunasekara wrote: > > > Thanks Makrand > > > > On 8 August 2017 at 14:42, Makrand wrote: > > > >> Asanka, > >> > >> The email list blocks the screen shots. I guess no one in the list > can see > >> your posted screens in emal chain. > >> > >> Better paste text output of the result or upload screens to image > hosting > >> (e.g. snag.gy). > >> > >> -- > >> Makrand > >> > >> > >> On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekara > > >> wrote: > >> > >> > Hi Guys, thanks for replying buy running ssvm-check.sh I got below > >> output > >> > > >> > > >> > [image: Inline images 1] > >> > > >> > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which > is the > >> > gateway and the Management server is 172.17.101.248 but it is > looking > >> in to > >> > Loval host > >> > > >> > > >> > > >> > > >> > [image: Inline images 2] > >> > > >> > What is going on, have I done something wrong? > >> > > >> > On 8 August 2017 at 14:22, Dag Sonstebo < > dag.sonst...@shapeblue.com> > >> > wrote: > >> > > >> >> Hi Asanka, > >> >> > >> >> One quick thing to check – log in to your SSVM and run > >> >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if > the > >> SSVM > >> >> can mount and write to secondary storage. > >> >> > >> >> Regards, > >> >> Dag Sonstebo > >> >> Cloud Architect > >> >> ShapeBlue > >> >> > >> >> From: Asanka Gunasekara > >> >> Reply-To: "users@cloudstack.apache.org" < > users@cloudstack.apache.org> > >> >> Date: Tuesday, 8 August 2017 at 09:27 > >> >> To: "users@cloudstack.apache.org" > >> >> Subject: Re: Secondary storage is not secondary properly > >> >> > >> >> I am sorry Eric, thank you for replying, please see below for > the rest > >> >> results > >> >> > >> >> * Make sure that it's accessible from the *storage* network (the > >> network > >> >> that you configured as storage when you created the zone, > assuming you > >> >> selected advanced networking). > >> >> Asanka > Since this is a test environemt I have just made it all > in one > >> >> subnet (is that the issue) > >> >> > >> >> * Is the secondary storage virtual machine up and running? Check > your > >> >> Infrastructure tab. > >> >> Asanka > Yes both system VMs are up and running > >> >> > >> >> * If the secondary storage virtual machine is up and running, > open its > >> >> console and log in as root / password. Then check 'ip addr list' > to > >> make > >> >> sure that it has IP addresses. > >> >> Asanka > Yes it IP are assigned > >> >> > >> >> * If it has IP addresses, try pinging your secondary storage NFS > server > >> >> (still within the SSVM). > >> >> Asanka > I can ping secondary storage > >> >> > >> >> * If you can ping your secondary storage NFS server, try > mounting the > >> NFS > >> >> share at some random place in your filesystem to make sure you > can > >> mount it > >> >> from the SSVM. e.g., 'mkdir /tmp/t; mount > myserver:/export/secstorage > >> >> /tmp/t' > >> >> Asanka > I can mount the secondary storage as below > >> >> > >> >> > >> >> [nline images 1] > >> >> > >> >> > >> >> dag.sonst...@shapeblue.com > >> >> www.shapeblue.com > >> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK > >> >> @shapeblue > >> >> > >> >> > >> >> >
Multi secondary storage use in one cluster
Hi, Community I have add two secondary storage to one kvm cluster. one is almost full, the other one is not full . But When I make a volume snapshot , It will upload snapshot file to the full one. How can I avoid it?
Re: Secondary storage is not secondary properly
Hi Asanka, Can you change your “host” global setting to your management server IP (it’s currently set to “localhost”), restart your management service and then destroy your SSVM + let this recreate. Once done run the check again and let us know the outcome. Can you also show us the configuration of your NFS share – i.e. what parameters are set etc. Regards, Dag Sonstebo Cloud Architect ShapeBlue On 08/08/2017, 10:28, "Asanka Gunasekara"wrote: Hi Guys, ssvm-check.sh command output https://snag.gy/bzpE5n.jpg Details of my nfs share https://snag.gy/WgJxCY.jpg Thanks and Best Regards Asanka dag.sonst...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue On 8 August 2017 at 14:48, Asanka Gunasekara wrote: > Thanks Makrand > > On 8 August 2017 at 14:42, Makrand wrote: > >> Asanka, >> >> The email list blocks the screen shots. I guess no one in the list can see >> your posted screens in emal chain. >> >> Better paste text output of the result or upload screens to image hosting >> (e.g. snag.gy). >> >> -- >> Makrand >> >> >> On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekara >> wrote: >> >> > Hi Guys, thanks for replying buy running ssvm-check.sh I got below >> output >> > >> > >> > [image: Inline images 1] >> > >> > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which is the >> > gateway and the Management server is 172.17.101.248 but it is looking >> in to >> > Loval host >> > >> > >> > >> > >> > [image: Inline images 2] >> > >> > What is going on, have I done something wrong? >> > >> > On 8 August 2017 at 14:22, Dag Sonstebo >> > wrote: >> > >> >> Hi Asanka, >> >> >> >> One quick thing to check – log in to your SSVM and run >> >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the >> SSVM >> >> can mount and write to secondary storage. >> >> >> >> Regards, >> >> Dag Sonstebo >> >> Cloud Architect >> >> ShapeBlue >> >> >> >> From: Asanka Gunasekara >> >> Reply-To: "users@cloudstack.apache.org" >> >> Date: Tuesday, 8 August 2017 at 09:27 >> >> To: "users@cloudstack.apache.org" >> >> Subject: Re: Secondary storage is not secondary properly >> >> >> >> I am sorry Eric, thank you for replying, please see below for the rest >> >> results >> >> >> >> * Make sure that it's accessible from the *storage* network (the >> network >> >> that you configured as storage when you created the zone, assuming you >> >> selected advanced networking). >> >> Asanka > Since this is a test environemt I have just made it all in one >> >> subnet (is that the issue) >> >> >> >> * Is the secondary storage virtual machine up and running? Check your >> >> Infrastructure tab. >> >> Asanka > Yes both system VMs are up and running >> >> >> >> * If the secondary storage virtual machine is up and running, open its >> >> console and log in as root / password. Then check 'ip addr list' to >> make >> >> sure that it has IP addresses. >> >> Asanka > Yes it IP are assigned >> >> >> >> * If it has IP addresses, try pinging your secondary storage NFS server >> >> (still within the SSVM). >> >> Asanka > I can ping secondary storage >> >> >> >> * If you can ping your secondary storage NFS server, try mounting the >> NFS >> >> share at some random place in your filesystem to make sure you can >> mount it >> >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >> >> /tmp/t' >> >> Asanka > I can mount the secondary storage as below >> >> >> >> >> >> [nline images 1] >> >> >> >> >> >> dag.sonst...@shapeblue.com >> >> www.shapeblue.com >> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >> >> @shapeblue >> >> >> >> >> >> >> >> On 8 August 2017 at 12:54, Eric Green to: >> >> eric.lee.gr...@gmail.com>> wrote: >> >> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara > > >> asa...@nimbus.lk>> wrote: >> >> > NFS is running on a different server, I can manual mount this share >> as >> >> NFS >> >> > and SMB >> >> > Cloud stack - 4.9 >> >> > Os is Centos 7 (64) >> >> >> >> * Make sure that it's accessible from the *storage* network (the >> network >> >> that you configured as storage when you created the zone, assuming you >> >> selected advanced networking). >> >> * Is
Re: Secondary storage is not secondary properly
Hi Makrand, as per http://docs.cloudstack.apache.org/projects/cloudstack-installation/en/4.9/management-server/_systemvm.html step 2, I have removed the mounts and mount points once the seeding process was complete Thanks and Regards Asanka On 8 August 2017 at 12:36, Makrandwrote: > Hi, > > Secondary storage is mounted in (normally /mnt/secondary) on > the management server. If it is appearing zero, ACS management may not see > be able see the NFS. Can you paste df -h output from management server CLI? > > Check if your SSVM is running properly by running > /usr/local/cloud/systemvm/ssvm-check.sh > . > > > Sometimes reboot/recreating SSVM solves issues with sec storage. > > > > -- > Makrand > > > On Tue, Aug 8, 2017 at 12:14 PM, Asanka Gunasekara > wrote: > > > Hi, I am setting up a test platform CloudStack 4.9 and intigrate with > > Vmware. All things was fine till I dashboard it shows the capacity of > > Secondary storage as 0.00Kb/0.00Kb. When I try to register a ISO logs > shows > > "Image store doesn't has enough capacity, so skip downloading template to > > this image store 1" message > > > > # df -h gives me below output where the nfs share is located > > > > /dev/xvdb150G 6.6G 41G 15% /share > > > > Can any one let me know what is going on, I have tried adding NFS as well > > as samba all shows 0/0Kb. > > > > NFS is running on a different server, I can manual mount this share as > NFS > > and SMB > > Cloud stack - 4.9 > > Os is Centos 7 (64) > > > > I am sorry for the duble post as I was registered under an alious > > (preciously my mail) > > > > Thanks and Regards > > >
Re: Secondary storage is not secondary properly
Hi Guys, I tried to destroy the VM and restart the management server but as soon as I delete then some process kicks in and re-spawns the both system VMs :( On 8 August 2017 at 15:40, Asanka Gunasekarawrote: > Hi Guys, what would happen if I destroy and restart the management server, > will it create new system vms with correct entries > > Thanks and Regards > > On 8 August 2017 at 14:58, Asanka Gunasekara wrote: > >> Hi Guys, >> >> ssvm-check.sh command output >> >> https://snag.gy/bzpE5n.jpg >> >> Details of my nfs share >> >> https://snag.gy/WgJxCY.jpg >> >> Thanks and Best Regards >> >> Asanka >> >> >> >> On 8 August 2017 at 14:48, Asanka Gunasekara wrote: >> >>> Thanks Makrand >>> >>> On 8 August 2017 at 14:42, Makrand wrote: >>> Asanka, The email list blocks the screen shots. I guess no one in the list can see your posted screens in emal chain. Better paste text output of the result or upload screens to image hosting (e.g. snag.gy). -- Makrand On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekara wrote: > Hi Guys, thanks for replying buy running ssvm-check.sh I got below output > > > [image: Inline images 1] > > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which is the > gateway and the Management server is 172.17.101.248 but it is looking in to > Loval host > > > > > [image: Inline images 2] > > What is going on, have I done something wrong? > > On 8 August 2017 at 14:22, Dag Sonstebo > wrote: > >> Hi Asanka, >> >> One quick thing to check – log in to your SSVM and run >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the SSVM >> can mount and write to secondary storage. >> >> Regards, >> Dag Sonstebo >> Cloud Architect >> ShapeBlue >> >> From: Asanka Gunasekara >> Reply-To: "users@cloudstack.apache.org" >> Date: Tuesday, 8 August 2017 at 09:27 >> To: "users@cloudstack.apache.org" >> Subject: Re: Secondary storage is not secondary properly >> >> I am sorry Eric, thank you for replying, please see below for the rest >> results >> >> * Make sure that it's accessible from the *storage* network (the network >> that you configured as storage when you created the zone, assuming you >> selected advanced networking). >> Asanka > Since this is a test environemt I have just made it all in one >> subnet (is that the issue) >> >> * Is the secondary storage virtual machine up and running? Check your >> Infrastructure tab. >> Asanka > Yes both system VMs are up and running >> >> * If the secondary storage virtual machine is up and running, open its >> console and log in as root / password. Then check 'ip addr list' to make >> sure that it has IP addresses. >> Asanka > Yes it IP are assigned >> >> * If it has IP addresses, try pinging your secondary storage NFS server >> (still within the SSVM). >> Asanka > I can ping secondary storage >> >> * If you can ping your secondary storage NFS server, try mounting the NFS >> share at some random place in your filesystem to make sure you can mount it >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >> /tmp/t' >> Asanka > I can mount the secondary storage as below >> >> >> [nline images 1] >> >> >> dag.sonst...@shapeblue.com >> www.shapeblue.com >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >> @shapeblue >> >> >> >> On 8 August 2017 at 12:54, Eric Green >> to: >> eric.lee.gr...@gmail.com>> wrote: >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara >> >> asa...@nimbus.lk>> wrote: >> > NFS is running on a different server, I can manual mount this share as >> NFS >> > and SMB >> > Cloud stack - 4.9 >> > Os is Centos 7 (64) >> >> * Make sure that it's accessible from the *storage* network (the network >> that you configured as storage when you created the zone, assuming you >> selected advanced networking). >> * Is the secondary storage virtual machine up and running? Check your >> Infrastructure tab. >> * If the secondary storage virtual machine is up and running, open its >> console and log in as root / password. Then check 'ip addr list' to make >> sure that it has IP addresses. >> * If it has IP addresses, try
Re: Secondary storage is not secondary properly
Hi Guys, what would happen if I destroy and restart the management server, will it create new system vms with correct entries Thanks and Regards On 8 August 2017 at 14:58, Asanka Gunasekarawrote: > Hi Guys, > > ssvm-check.sh command output > > https://snag.gy/bzpE5n.jpg > > Details of my nfs share > > https://snag.gy/WgJxCY.jpg > > Thanks and Best Regards > > Asanka > > > > On 8 August 2017 at 14:48, Asanka Gunasekara wrote: > >> Thanks Makrand >> >> On 8 August 2017 at 14:42, Makrand wrote: >> >>> Asanka, >>> >>> The email list blocks the screen shots. I guess no one in the list can >>> see >>> your posted screens in emal chain. >>> >>> Better paste text output of the result or upload screens to image hosting >>> (e.g. snag.gy). >>> >>> -- >>> Makrand >>> >>> >>> On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekara >>> wrote: >>> >>> > Hi Guys, thanks for replying buy running ssvm-check.sh I got below >>> output >>> > >>> > >>> > [image: Inline images 1] >>> > >>> > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which is >>> the >>> > gateway and the Management server is 172.17.101.248 but it is looking >>> in to >>> > Loval host >>> > >>> > >>> > >>> > >>> > [image: Inline images 2] >>> > >>> > What is going on, have I done something wrong? >>> > >>> > On 8 August 2017 at 14:22, Dag Sonstebo >>> > wrote: >>> > >>> >> Hi Asanka, >>> >> >>> >> One quick thing to check – log in to your SSVM and run >>> >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the >>> SSVM >>> >> can mount and write to secondary storage. >>> >> >>> >> Regards, >>> >> Dag Sonstebo >>> >> Cloud Architect >>> >> ShapeBlue >>> >> >>> >> From: Asanka Gunasekara >>> >> Reply-To: "users@cloudstack.apache.org" >>> >> Date: Tuesday, 8 August 2017 at 09:27 >>> >> To: "users@cloudstack.apache.org" >>> >> Subject: Re: Secondary storage is not secondary properly >>> >> >>> >> I am sorry Eric, thank you for replying, please see below for the rest >>> >> results >>> >> >>> >> * Make sure that it's accessible from the *storage* network (the >>> network >>> >> that you configured as storage when you created the zone, assuming you >>> >> selected advanced networking). >>> >> Asanka > Since this is a test environemt I have just made it all in >>> one >>> >> subnet (is that the issue) >>> >> >>> >> * Is the secondary storage virtual machine up and running? Check your >>> >> Infrastructure tab. >>> >> Asanka > Yes both system VMs are up and running >>> >> >>> >> * If the secondary storage virtual machine is up and running, open its >>> >> console and log in as root / password. Then check 'ip addr list' to >>> make >>> >> sure that it has IP addresses. >>> >> Asanka > Yes it IP are assigned >>> >> >>> >> * If it has IP addresses, try pinging your secondary storage NFS >>> server >>> >> (still within the SSVM). >>> >> Asanka > I can ping secondary storage >>> >> >>> >> * If you can ping your secondary storage NFS server, try mounting the >>> NFS >>> >> share at some random place in your filesystem to make sure you can >>> mount it >>> >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >>> >> /tmp/t' >>> >> Asanka > I can mount the secondary storage as below >>> >> >>> >> >>> >> [nline images 1] >>> >> >>> >> >>> >> dag.sonst...@shapeblue.com >>> >> www.shapeblue.com >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >>> >> @shapeblue >>> >> >>> >> >>> >> >>> >> On 8 August 2017 at 12:54, Eric Green > to: >>> >> eric.lee.gr...@gmail.com>> wrote: >>> >> >>> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara >> >> >> asa...@nimbus.lk>> wrote: >>> >> > NFS is running on a different server, I can manual mount this share >>> as >>> >> NFS >>> >> > and SMB >>> >> > Cloud stack - 4.9 >>> >> > Os is Centos 7 (64) >>> >> >>> >> * Make sure that it's accessible from the *storage* network (the >>> network >>> >> that you configured as storage when you created the zone, assuming you >>> >> selected advanced networking). >>> >> * Is the secondary storage virtual machine up and running? Check your >>> >> Infrastructure tab. >>> >> * If the secondary storage virtual machine is up and running, open its >>> >> console and log in as root / password. Then check 'ip addr list' to >>> make >>> >> sure that it has IP addresses. >>> >> * If it has IP addresses, try pinging your secondary storage NFS >>> server >>> >> (still within the SSVM). >>> >> * If you can ping your secondary storage NFS server, try mounting the >>> NFS >>> >> share at some random place in your filesystem to make sure you can >>> mount it >>> >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >>> >> /tmp/t' >>> >> * Make sure you're using the NFS server's *storage* network IP address >>> >> when
Re: Secondary storage is not secondary properly
Hi Guys, ssvm-check.sh command output https://snag.gy/bzpE5n.jpg Details of my nfs share https://snag.gy/WgJxCY.jpg Thanks and Best Regards Asanka On 8 August 2017 at 14:48, Asanka Gunasekarawrote: > Thanks Makrand > > On 8 August 2017 at 14:42, Makrand wrote: > >> Asanka, >> >> The email list blocks the screen shots. I guess no one in the list can see >> your posted screens in emal chain. >> >> Better paste text output of the result or upload screens to image hosting >> (e.g. snag.gy). >> >> -- >> Makrand >> >> >> On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekara >> wrote: >> >> > Hi Guys, thanks for replying buy running ssvm-check.sh I got below >> output >> > >> > >> > [image: Inline images 1] >> > >> > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which is the >> > gateway and the Management server is 172.17.101.248 but it is looking >> in to >> > Loval host >> > >> > >> > >> > >> > [image: Inline images 2] >> > >> > What is going on, have I done something wrong? >> > >> > On 8 August 2017 at 14:22, Dag Sonstebo >> > wrote: >> > >> >> Hi Asanka, >> >> >> >> One quick thing to check – log in to your SSVM and run >> >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the >> SSVM >> >> can mount and write to secondary storage. >> >> >> >> Regards, >> >> Dag Sonstebo >> >> Cloud Architect >> >> ShapeBlue >> >> >> >> From: Asanka Gunasekara >> >> Reply-To: "users@cloudstack.apache.org" >> >> Date: Tuesday, 8 August 2017 at 09:27 >> >> To: "users@cloudstack.apache.org" >> >> Subject: Re: Secondary storage is not secondary properly >> >> >> >> I am sorry Eric, thank you for replying, please see below for the rest >> >> results >> >> >> >> * Make sure that it's accessible from the *storage* network (the >> network >> >> that you configured as storage when you created the zone, assuming you >> >> selected advanced networking). >> >> Asanka > Since this is a test environemt I have just made it all in one >> >> subnet (is that the issue) >> >> >> >> * Is the secondary storage virtual machine up and running? Check your >> >> Infrastructure tab. >> >> Asanka > Yes both system VMs are up and running >> >> >> >> * If the secondary storage virtual machine is up and running, open its >> >> console and log in as root / password. Then check 'ip addr list' to >> make >> >> sure that it has IP addresses. >> >> Asanka > Yes it IP are assigned >> >> >> >> * If it has IP addresses, try pinging your secondary storage NFS server >> >> (still within the SSVM). >> >> Asanka > I can ping secondary storage >> >> >> >> * If you can ping your secondary storage NFS server, try mounting the >> NFS >> >> share at some random place in your filesystem to make sure you can >> mount it >> >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >> >> /tmp/t' >> >> Asanka > I can mount the secondary storage as below >> >> >> >> >> >> [nline images 1] >> >> >> >> >> >> dag.sonst...@shapeblue.com >> >> www.shapeblue.com >> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >> >> @shapeblue >> >> >> >> >> >> >> >> On 8 August 2017 at 12:54, Eric Green to: >> >> eric.lee.gr...@gmail.com>> wrote: >> >> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara > > >> asa...@nimbus.lk>> wrote: >> >> > NFS is running on a different server, I can manual mount this share >> as >> >> NFS >> >> > and SMB >> >> > Cloud stack - 4.9 >> >> > Os is Centos 7 (64) >> >> >> >> * Make sure that it's accessible from the *storage* network (the >> network >> >> that you configured as storage when you created the zone, assuming you >> >> selected advanced networking). >> >> * Is the secondary storage virtual machine up and running? Check your >> >> Infrastructure tab. >> >> * If the secondary storage virtual machine is up and running, open its >> >> console and log in as root / password. Then check 'ip addr list' to >> make >> >> sure that it has IP addresses. >> >> * If it has IP addresses, try pinging your secondary storage NFS server >> >> (still within the SSVM). >> >> * If you can ping your secondary storage NFS server, try mounting the >> NFS >> >> share at some random place in your filesystem to make sure you can >> mount it >> >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >> >> /tmp/t' >> >> * Make sure you're using the NFS server's *storage* network IP address >> >> when you make this attempt. >> >> >> >> It is possible that your NFS server has a firewall configured? But from >> >> my experiments, the secondary storage VM not providing secondary >> storage >> >> usually is a networking problem, things not set up properly in your >> zone's >> >> networking so that the secondary storage VM can't reach the secondary >> >> storage. Are you using advanced networking,
Re: Secondary storage is not secondary properly
Thanks Makrand On 8 August 2017 at 14:42, Makrandwrote: > Asanka, > > The email list blocks the screen shots. I guess no one in the list can see > your posted screens in emal chain. > > Better paste text output of the result or upload screens to image hosting > (e.g. snag.gy). > > -- > Makrand > > > On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekara > wrote: > > > Hi Guys, thanks for replying buy running ssvm-check.sh I got below output > > > > > > [image: Inline images 1] > > > > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which is the > > gateway and the Management server is 172.17.101.248 but it is looking in > to > > Loval host > > > > > > > > > > [image: Inline images 2] > > > > What is going on, have I done something wrong? > > > > On 8 August 2017 at 14:22, Dag Sonstebo > > wrote: > > > >> Hi Asanka, > >> > >> One quick thing to check – log in to your SSVM and run > >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the > SSVM > >> can mount and write to secondary storage. > >> > >> Regards, > >> Dag Sonstebo > >> Cloud Architect > >> ShapeBlue > >> > >> From: Asanka Gunasekara > >> Reply-To: "users@cloudstack.apache.org" > >> Date: Tuesday, 8 August 2017 at 09:27 > >> To: "users@cloudstack.apache.org" > >> Subject: Re: Secondary storage is not secondary properly > >> > >> I am sorry Eric, thank you for replying, please see below for the rest > >> results > >> > >> * Make sure that it's accessible from the *storage* network (the network > >> that you configured as storage when you created the zone, assuming you > >> selected advanced networking). > >> Asanka > Since this is a test environemt I have just made it all in one > >> subnet (is that the issue) > >> > >> * Is the secondary storage virtual machine up and running? Check your > >> Infrastructure tab. > >> Asanka > Yes both system VMs are up and running > >> > >> * If the secondary storage virtual machine is up and running, open its > >> console and log in as root / password. Then check 'ip addr list' to make > >> sure that it has IP addresses. > >> Asanka > Yes it IP are assigned > >> > >> * If it has IP addresses, try pinging your secondary storage NFS server > >> (still within the SSVM). > >> Asanka > I can ping secondary storage > >> > >> * If you can ping your secondary storage NFS server, try mounting the > NFS > >> share at some random place in your filesystem to make sure you can > mount it > >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage > >> /tmp/t' > >> Asanka > I can mount the secondary storage as below > >> > >> > >> [nline images 1] > >> > >> > >> dag.sonst...@shapeblue.com > >> www.shapeblue.com > >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK > >> @shapeblue > >> > >> > >> > >> On 8 August 2017 at 12:54, Eric Green > eric.lee.gr...@gmail.com>> wrote: > >> > >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara > asa...@nimbus.lk>> wrote: > >> > NFS is running on a different server, I can manual mount this share as > >> NFS > >> > and SMB > >> > Cloud stack - 4.9 > >> > Os is Centos 7 (64) > >> > >> * Make sure that it's accessible from the *storage* network (the network > >> that you configured as storage when you created the zone, assuming you > >> selected advanced networking). > >> * Is the secondary storage virtual machine up and running? Check your > >> Infrastructure tab. > >> * If the secondary storage virtual machine is up and running, open its > >> console and log in as root / password. Then check 'ip addr list' to make > >> sure that it has IP addresses. > >> * If it has IP addresses, try pinging your secondary storage NFS server > >> (still within the SSVM). > >> * If you can ping your secondary storage NFS server, try mounting the > NFS > >> share at some random place in your filesystem to make sure you can > mount it > >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage > >> /tmp/t' > >> * Make sure you're using the NFS server's *storage* network IP address > >> when you make this attempt. > >> > >> It is possible that your NFS server has a firewall configured? But from > >> my experiments, the secondary storage VM not providing secondary storage > >> usually is a networking problem, things not set up properly in your > zone's > >> networking so that the secondary storage VM can't reach the secondary > >> storage. Are you using advanced networking, or basic networking? > >> > >> > > >
Re: Secondary storage is not secondary properly
Asanka, The email list blocks the screen shots. I guess no one in the list can see your posted screens in emal chain. Better paste text output of the result or upload screens to image hosting (e.g. snag.gy). -- Makrand On Tue, Aug 8, 2017 at 2:28 PM, Asanka Gunasekarawrote: > Hi Guys, thanks for replying buy running ssvm-check.sh I got below output > > > [image: Inline images 1] > > My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which is the > gateway and the Management server is 172.17.101.248 but it is looking in to > Loval host > > > > > [image: Inline images 2] > > What is going on, have I done something wrong? > > On 8 August 2017 at 14:22, Dag Sonstebo > wrote: > >> Hi Asanka, >> >> One quick thing to check – log in to your SSVM and run >> /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the SSVM >> can mount and write to secondary storage. >> >> Regards, >> Dag Sonstebo >> Cloud Architect >> ShapeBlue >> >> From: Asanka Gunasekara >> Reply-To: "users@cloudstack.apache.org" >> Date: Tuesday, 8 August 2017 at 09:27 >> To: "users@cloudstack.apache.org" >> Subject: Re: Secondary storage is not secondary properly >> >> I am sorry Eric, thank you for replying, please see below for the rest >> results >> >> * Make sure that it's accessible from the *storage* network (the network >> that you configured as storage when you created the zone, assuming you >> selected advanced networking). >> Asanka > Since this is a test environemt I have just made it all in one >> subnet (is that the issue) >> >> * Is the secondary storage virtual machine up and running? Check your >> Infrastructure tab. >> Asanka > Yes both system VMs are up and running >> >> * If the secondary storage virtual machine is up and running, open its >> console and log in as root / password. Then check 'ip addr list' to make >> sure that it has IP addresses. >> Asanka > Yes it IP are assigned >> >> * If it has IP addresses, try pinging your secondary storage NFS server >> (still within the SSVM). >> Asanka > I can ping secondary storage >> >> * If you can ping your secondary storage NFS server, try mounting the NFS >> share at some random place in your filesystem to make sure you can mount it >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >> /tmp/t' >> Asanka > I can mount the secondary storage as below >> >> >> [nline images 1] >> >> >> dag.sonst...@shapeblue.com >> www.shapeblue.com >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK >> @shapeblue >> >> >> >> On 8 August 2017 at 12:54, Eric Green eric.lee.gr...@gmail.com>> wrote: >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara asa...@nimbus.lk>> wrote: >> > NFS is running on a different server, I can manual mount this share as >> NFS >> > and SMB >> > Cloud stack - 4.9 >> > Os is Centos 7 (64) >> >> * Make sure that it's accessible from the *storage* network (the network >> that you configured as storage when you created the zone, assuming you >> selected advanced networking). >> * Is the secondary storage virtual machine up and running? Check your >> Infrastructure tab. >> * If the secondary storage virtual machine is up and running, open its >> console and log in as root / password. Then check 'ip addr list' to make >> sure that it has IP addresses. >> * If it has IP addresses, try pinging your secondary storage NFS server >> (still within the SSVM). >> * If you can ping your secondary storage NFS server, try mounting the NFS >> share at some random place in your filesystem to make sure you can mount it >> from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage >> /tmp/t' >> * Make sure you're using the NFS server's *storage* network IP address >> when you make this attempt. >> >> It is possible that your NFS server has a firewall configured? But from >> my experiments, the secondary storage VM not providing secondary storage >> usually is a networking problem, things not set up properly in your zone's >> networking so that the secondary storage VM can't reach the secondary >> storage. Are you using advanced networking, or basic networking? >> >> >
Re: Secondary storage is not secondary properly
Hi Guys, thanks for replying buy running ssvm-check.sh I got below output [image: Inline images 1] My nfs is 172.17.101.253 but it is looking for 172.17.101.1 which is the gateway and the Management server is 172.17.101.248 but it is looking in to Loval host [image: Inline images 2] What is going on, have I done something wrong? On 8 August 2017 at 14:22, Dag Sonstebowrote: > Hi Asanka, > > One quick thing to check – log in to your SSVM and run > /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the SSVM > can mount and write to secondary storage. > > Regards, > Dag Sonstebo > Cloud Architect > ShapeBlue > > From: Asanka Gunasekara > Reply-To: "users@cloudstack.apache.org" > Date: Tuesday, 8 August 2017 at 09:27 > To: "users@cloudstack.apache.org" > Subject: Re: Secondary storage is not secondary properly > > I am sorry Eric, thank you for replying, please see below for the rest > results > > * Make sure that it's accessible from the *storage* network (the network > that you configured as storage when you created the zone, assuming you > selected advanced networking). > Asanka > Since this is a test environemt I have just made it all in one > subnet (is that the issue) > > * Is the secondary storage virtual machine up and running? Check your > Infrastructure tab. > Asanka > Yes both system VMs are up and running > > * If the secondary storage virtual machine is up and running, open its > console and log in as root / password. Then check 'ip addr list' to make > sure that it has IP addresses. > Asanka > Yes it IP are assigned > > * If it has IP addresses, try pinging your secondary storage NFS server > (still within the SSVM). > Asanka > I can ping secondary storage > > * If you can ping your secondary storage NFS server, try mounting the NFS > share at some random place in your filesystem to make sure you can mount it > from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage > /tmp/t' > Asanka > I can mount the secondary storage as below > > > [nline images 1] > > > dag.sonst...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > > On 8 August 2017 at 12:54, Eric Green > wrote: > > > On Aug 7, 2017, at 23:44, Asanka Gunasekara > wrote: > > NFS is running on a different server, I can manual mount this share as > NFS > > and SMB > > Cloud stack - 4.9 > > Os is Centos 7 (64) > > * Make sure that it's accessible from the *storage* network (the network > that you configured as storage when you created the zone, assuming you > selected advanced networking). > * Is the secondary storage virtual machine up and running? Check your > Infrastructure tab. > * If the secondary storage virtual machine is up and running, open its > console and log in as root / password. Then check 'ip addr list' to make > sure that it has IP addresses. > * If it has IP addresses, try pinging your secondary storage NFS server > (still within the SSVM). > * If you can ping your secondary storage NFS server, try mounting the NFS > share at some random place in your filesystem to make sure you can mount it > from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage > /tmp/t' > * Make sure you're using the NFS server's *storage* network IP address > when you make this attempt. > > It is possible that your NFS server has a firewall configured? But from my > experiments, the secondary storage VM not providing secondary storage > usually is a networking problem, things not set up properly in your zone's > networking so that the secondary storage VM can't reach the secondary > storage. Are you using advanced networking, or basic networking? > >
Re: Secondary storage is not secondary properly
Hi Asanka, One quick thing to check – log in to your SSVM and run /use/local/cloud/systemvm/ssvm-check.sh – this will tell you if the SSVM can mount and write to secondary storage. Regards, Dag Sonstebo Cloud Architect ShapeBlue From: Asanka GunasekaraReply-To: "users@cloudstack.apache.org" Date: Tuesday, 8 August 2017 at 09:27 To: "users@cloudstack.apache.org" Subject: Re: Secondary storage is not secondary properly I am sorry Eric, thank you for replying, please see below for the rest results * Make sure that it's accessible from the *storage* network (the network that you configured as storage when you created the zone, assuming you selected advanced networking). Asanka > Since this is a test environemt I have just made it all in one subnet (is that the issue) * Is the secondary storage virtual machine up and running? Check your Infrastructure tab. Asanka > Yes both system VMs are up and running * If the secondary storage virtual machine is up and running, open its console and log in as root / password. Then check 'ip addr list' to make sure that it has IP addresses. Asanka > Yes it IP are assigned * If it has IP addresses, try pinging your secondary storage NFS server (still within the SSVM). Asanka > I can ping secondary storage * If you can ping your secondary storage NFS server, try mounting the NFS share at some random place in your filesystem to make sure you can mount it from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage /tmp/t' Asanka > I can mount the secondary storage as below [nline images 1] dag.sonst...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue On 8 August 2017 at 12:54, Eric Green > wrote: > On Aug 7, 2017, at 23:44, Asanka Gunasekara > > wrote: > NFS is running on a different server, I can manual mount this share as NFS > and SMB > Cloud stack - 4.9 > Os is Centos 7 (64) * Make sure that it's accessible from the *storage* network (the network that you configured as storage when you created the zone, assuming you selected advanced networking). * Is the secondary storage virtual machine up and running? Check your Infrastructure tab. * If the secondary storage virtual machine is up and running, open its console and log in as root / password. Then check 'ip addr list' to make sure that it has IP addresses. * If it has IP addresses, try pinging your secondary storage NFS server (still within the SSVM). * If you can ping your secondary storage NFS server, try mounting the NFS share at some random place in your filesystem to make sure you can mount it from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage /tmp/t' * Make sure you're using the NFS server's *storage* network IP address when you make this attempt. It is possible that your NFS server has a firewall configured? But from my experiments, the secondary storage VM not providing secondary storage usually is a networking problem, things not set up properly in your zone's networking so that the secondary storage VM can't reach the secondary storage. Are you using advanced networking, or basic networking?
Re: Secondary storage is not secondary properly
I am sorry Eric, thank you for replying, please see below for the rest results * Make sure that it's accessible from the *storage* network (the network that you configured as storage when you created the zone, assuming you selected advanced networking). Asanka > Since this is a test environemt I have just made it all in one subnet (is that the issue) * Is the secondary storage virtual machine up and running? Check your Infrastructure tab. Asanka > Yes both system VMs are up and running * If the secondary storage virtual machine is up and running, open its console and log in as root / password. Then check 'ip addr list' to make sure that it has IP addresses. Asanka > Yes it IP are assigned * If it has IP addresses, try pinging your secondary storage NFS server (still within the SSVM). Asanka > I can ping secondary storage * If you can ping your secondary storage NFS server, try mounting the NFS share at some random place in your filesystem to make sure you can mount it from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage /tmp/t' Asanka > I can mount the secondary storage as below [image: Inline images 1] On 8 August 2017 at 12:54, Eric Greenwrote: > > > On Aug 7, 2017, at 23:44, Asanka Gunasekara wrote: > > NFS is running on a different server, I can manual mount this share as > NFS > > and SMB > > Cloud stack - 4.9 > > Os is Centos 7 (64) > > * Make sure that it's accessible from the *storage* network (the network > that you configured as storage when you created the zone, assuming you > selected advanced networking). > * Is the secondary storage virtual machine up and running? Check your > Infrastructure tab. > * If the secondary storage virtual machine is up and running, open its > console and log in as root / password. Then check 'ip addr list' to make > sure that it has IP addresses. > * If it has IP addresses, try pinging your secondary storage NFS server > (still within the SSVM). > * If you can ping your secondary storage NFS server, try mounting the NFS > share at some random place in your filesystem to make sure you can mount it > from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage > /tmp/t' > * Make sure you're using the NFS server's *storage* network IP address > when you make this attempt. > > It is possible that your NFS server has a firewall configured? But from my > experiments, the secondary storage VM not providing secondary storage > usually is a networking problem, things not set up properly in your zone's > networking so that the secondary storage VM can't reach the secondary > storage. Are you using advanced networking, or basic networking? > >
Re: Secondary storage is not secondary properly
Hi Makrand thank you for replying, please see below for the rest results * Make sure that it's accessible from the *storage* network (the network that you configured as storage when you created the zone, assuming you selected advanced networking). Asanka > Since this is a test environemt I have just made it all in one subnet (is that the issue) * Is the secondary storage virtual machine up and running? Check your Infrastructure tab. Asanka > Yes both system VMs are up and running * If the secondary storage virtual machine is up and running, open its console and log in as root / password. Then check 'ip addr list' to make sure that it has IP addresses. Asanka > Yes it IP are assigned * If it has IP addresses, try pinging your secondary storage NFS server (still within the SSVM). Asanka > I can ping secondary storage * If you can ping your secondary storage NFS server, try mounting the NFS share at some random place in your filesystem to make sure you can mount it from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage /tmp/t' Asanka > I can mount the secondary storage as below [image: Inline images 1] On 8 August 2017 at 12:54, Eric Greenwrote: > > > On Aug 7, 2017, at 23:44, Asanka Gunasekara wrote: > > NFS is running on a different server, I can manual mount this share as > NFS > > and SMB > > Cloud stack - 4.9 > > Os is Centos 7 (64) > > * Make sure that it's accessible from the *storage* network (the network > that you configured as storage when you created the zone, assuming you > selected advanced networking). > * Is the secondary storage virtual machine up and running? Check your > Infrastructure tab. > * If the secondary storage virtual machine is up and running, open its > console and log in as root / password. Then check 'ip addr list' to make > sure that it has IP addresses. > * If it has IP addresses, try pinging your secondary storage NFS server > (still within the SSVM). > * If you can ping your secondary storage NFS server, try mounting the NFS > share at some random place in your filesystem to make sure you can mount it > from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage > /tmp/t' > * Make sure you're using the NFS server's *storage* network IP address > when you make this attempt. > > It is possible that your NFS server has a firewall configured? But from my > experiments, the secondary storage VM not providing secondary storage > usually is a networking problem, things not set up properly in your zone's > networking so that the secondary storage VM can't reach the secondary > storage. Are you using advanced networking, or basic networking? > >
Re: Secondary storage is not secondary properly
> On Aug 7, 2017, at 23:44, Asanka Gunasekarawrote: > NFS is running on a different server, I can manual mount this share as NFS > and SMB > Cloud stack - 4.9 > Os is Centos 7 (64) * Make sure that it's accessible from the *storage* network (the network that you configured as storage when you created the zone, assuming you selected advanced networking). * Is the secondary storage virtual machine up and running? Check your Infrastructure tab. * If the secondary storage virtual machine is up and running, open its console and log in as root / password. Then check 'ip addr list' to make sure that it has IP addresses. * If it has IP addresses, try pinging your secondary storage NFS server (still within the SSVM). * If you can ping your secondary storage NFS server, try mounting the NFS share at some random place in your filesystem to make sure you can mount it from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage /tmp/t' * Make sure you're using the NFS server's *storage* network IP address when you make this attempt. It is possible that your NFS server has a firewall configured? But from my experiments, the secondary storage VM not providing secondary storage usually is a networking problem, things not set up properly in your zone's networking so that the secondary storage VM can't reach the secondary storage. Are you using advanced networking, or basic networking?
RE: Secondary storage is not secondary properly
Hi Asanka, You may need to take a step back - do you have a secondary storage VM up and running (you'll find that under instrastructure -> System VMs). If you do, then you should log into the secondary storage VM that you have running and run the command Makrand suggested. If you do not, then you'd need to look further into the logs to discover why not. Kind regards, Paul Angus paul.an...@shapeblue.com www.shapeblue.com 53 Chandos Place, Covent Garden, London WC2N 4HSUK @shapeblue -Original Message- From: Makrand [mailto:makrandsa...@gmail.com] Sent: 08 August 2017 08:06 To: users@cloudstack.apache.org Subject: Re: Secondary storage is not secondary properly Hi, Secondary storage is mounted in (normally /mnt/secondary) on the management server. If it is appearing zero, ACS management may not see be able see the NFS. Can you paste df -h output from management server CLI? Check if your SSVM is running properly by running /usr/local/cloud/systemvm/ssvm-check.sh . Sometimes reboot/recreating SSVM solves issues with sec storage. -- Makrand On Tue, Aug 8, 2017 at 12:14 PM, Asanka Gunasekarawrote: > Hi, I am setting up a test platform CloudStack 4.9 and intigrate with > Vmware. All things was fine till I dashboard it shows the capacity of > Secondary storage as 0.00Kb/0.00Kb. When I try to register a ISO logs > shows "Image store doesn't has enough capacity, so skip downloading > template to this image store 1" message > > # df -h gives me below output where the nfs share is located > > /dev/xvdb150G 6.6G 41G 15% /share > > Can any one let me know what is going on, I have tried adding NFS as > well as samba all shows 0/0Kb. > > NFS is running on a different server, I can manual mount this share as > NFS and SMB Cloud stack - 4.9 Os is Centos 7 (64) > > I am sorry for the duble post as I was registered under an alious > (preciously my mail) > > Thanks and Regards >
Re: Secondary storage is not secondary properly
Hi, Secondary storage is mounted in (normally /mnt/secondary) on the management server. If it is appearing zero, ACS management may not see be able see the NFS. Can you paste df -h output from management server CLI? Check if your SSVM is running properly by running /usr/local/cloud/systemvm/ssvm-check.sh . Sometimes reboot/recreating SSVM solves issues with sec storage. -- Makrand On Tue, Aug 8, 2017 at 12:14 PM, Asanka Gunasekarawrote: > Hi, I am setting up a test platform CloudStack 4.9 and intigrate with > Vmware. All things was fine till I dashboard it shows the capacity of > Secondary storage as 0.00Kb/0.00Kb. When I try to register a ISO logs shows > "Image store doesn't has enough capacity, so skip downloading template to > this image store 1" message > > # df -h gives me below output where the nfs share is located > > /dev/xvdb150G 6.6G 41G 15% /share > > Can any one let me know what is going on, I have tried adding NFS as well > as samba all shows 0/0Kb. > > NFS is running on a different server, I can manual mount this share as NFS > and SMB > Cloud stack - 4.9 > Os is Centos 7 (64) > > I am sorry for the duble post as I was registered under an alious > (preciously my mail) > > Thanks and Regards >
Secondary storage is not secondary properly
Hi, I am setting up a test platform CloudStack 4.9 and intigrate with Vmware. All things was fine till I dashboard it shows the capacity of Secondary storage as 0.00Kb/0.00Kb. When I try to register a ISO logs shows "Image store doesn't has enough capacity, so skip downloading template to this image store 1" message # df -h gives me below output where the nfs share is located /dev/xvdb150G 6.6G 41G 15% /share Can any one let me know what is going on, I have tried adding NFS as well as samba all shows 0/0Kb. NFS is running on a different server, I can manual mount this share as NFS and SMB Cloud stack - 4.9 Os is Centos 7 (64) I am sorry for the duble post as I was registered under an alious (preciously my mail) Thanks and Regards