You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Asanka Gunasekara <as...@nimbus.lk> on 2017/08/08 06:44:15 UTC
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/xvdb1 50G 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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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, Makrand <ma...@gmail.com> wrote:
> Hi,
>
> Secondary storage is mounted in <mount path> (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 <as...@nimbus.lk>
> 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/xvdb1 50G 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
Posted by Paul Angus <pa...@shapeblue.com>.
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.angus@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
-----Original Message-----
From: Makrand [mailto:makrandsanap@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 <mount path> (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 <as...@nimbus.lk> 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/xvdb1 50G 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
Posted by Makrand <ma...@gmail.com>.
Hi,
Secondary storage is mounted in <mount path> (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 <as...@nimbus.lk> 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/xvdb1 50G 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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 Green <er...@gmail.com> wrote:
>
> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <as...@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi All, sorry for the delay in replying, the hardware that I was playing
was taken in for some other testing.
After rebuilding from the scratch all storages are visible
Thank you for the help all of you extended
Hi Dag, just saw your signature with this mail thread; Thank you
Best of regards
Asanka
On 22 August 2017 at 22:08, Dag Sonstebo <Da...@shapeblue.com> wrote:
> Hi Asanka,
>
>
>
> Sure, let us know how you get on. I am slowly starting to suspect you have
> some sort of issue with your NFS server – I think from earlier screen dumps
> it looked like this is from a Windows box? I suggest to review this once
> you have reset everything and set the zone up again + tested.
>
>
>
> Regards,
>
> Dag Sonstebo
>
> Cloud Architect
>
> ShapeBlue
>
>
>
>
> Cloud Architect
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
>
>
>
>
>
>
>
> *From: *Asanka Gunasekara <as...@nimbus.lk>
> *Date: *Tuesday, 22 August 2017 at 17:16
> *To: *Dag Sonstebo <Da...@shapeblue.com>
> *Cc: *"users@cloudstack.apache.org" <us...@cloudstack.apache.org>
> *Subject: *Re: Secondary storage is not secondary properly
>
>
>
> Hi Guya, I tried replacing the template but did not work, Java process or
> the NFS worked. Since this is a lap environment for a migration, guess its
> best to try from scratch!
>
> SSVM
>
> 1. Java process is not starting
>
> 2. NFS is not mounting and it is looking for for the IP 172.17.101.1 which
> ic my Gateway where nfs server is 172.17.101.253
>
> Console Proxy VM
>
> 1. JavaProcess Running
>
> 2. NFS is not mounting but it is looking for an ip 255.255.255.255 :(
>
> Its wired!! Any how I will try to do the reset of the database and ESXi
> server and try again.Will keep you posted on the things
>
> Thanks and Regards
>
> Asanka
>
>
>
> On 21 August 2017 at 10:46, Asanka Gunasekara <as...@nimbus.lk> wrote:
>
> Hi Dag/Eric, thank you both for the reply, let me do your advice and will
> update you on the results
>
> Thank you and best Regards
>
> Asanka
>
>
>
> On 19 August 2017 at 14:45, Dag Sonstebo <Da...@shapeblue.com>
> wrote:
>
> Hi Asanka,
>
> Agree with Eric, doesn’t look right.,
>
> The quickest solution here is to:
>
> 1) disable zone
> 2) delete system VMs
> 3) remove secondary storage from cloudstack
> 4) try the secondary storage seeding again with images from
> http://packages.shapeblue.com/systemvmtemplate/4.6/new/ - but use the
> “-F” option when you call /usr/share/cloudstack-common/
> scripts/storage/secondary/cloud-install-sys-tmplt > this will clean up
> previous template
> 5) add secondary storage to CloudStack again
> 6) enable zone and monitor
>
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 18/08/2017, 18:35, "Eric Green" <er...@gmail.com> wrote:
>
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N&entry=gmail&source=g>
> WC2N
> <https://maps.google.com/?q=53+Chandos+Place,+Covent+Garden,+London%C2%A0+WC2N&entry=gmail&source=g>
> 4HSUK
> @shapeblue
>
>
> > On Aug 18, 2017, at 03:22, Asanka Gunasekara <as...@nimbus.lk> wrote:
> >
> > Hi Eric,
> >
> > SSVM can access my nfs and I an manual mount :(
> >
> > This "s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand
> /var/log/cloud.log" did not produced any output, but found below error
> >
> > From the VM's /var/log/cloud.log:
> > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent:
> Resource class not found: com.cloud.storage.resource.
> PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageResource
>
>
> Hmm. That doesn't look good. So the agent is never even able to start
> because of that exception. This looks like a mismatch between your SSVM
> template and your version of Cloudstack. It looks like you're using a
> version of Cloudstack that has been compiled with premium features that is
> expecting a template that supports premium features.
>
> Someone else will have to tell you how to change the SSVM template, I
> don't know that. Or since this is a zone that has never been operational,
> you may choose to simply wipe the current install entirely and start over
> again from scratch with a Cloudstack and SSVM template all from the same
> source. Remember to drop and recreate the database as part of that process,
> as well as remove all the contents of the secondary store and follow the
> directions again to reinitialize with the initial template.
>
> For the record, I got my Cloudstack from this source:
>
> [cloudstack]
> name=cloudstack
> baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.9/
> enabled=1
> gpgcheck=0
>
> My template similarly came from that source (but the 4.6 version, as
> you specified).
>
> Once I got my networking sorted out, which you seem to have done, it
> Just Worked.
>
>
>
>
>
>
Re: Secondary storage is not secondary properly
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Guya, I tried replacing the template but did not work, Java process or
the NFS worked. Since this is a lap environment for a migration, guess its
best to try from scratch!
SSVM
1. Java process is not starting
2. NFS is not mounting and it is looking for for the IP 172.17.101.1 which
ic my Gateway where nfs server is 172.17.101.253
Console Proxy VM
1. JavaProcess Running
2. NFS is not mounting but it is looking for an ip 255.255.255.255 :(
Its wired!! Any how I will try to do the reset of the database and ESXi
server and try again.Will keep you posted on the things
Thanks and Regards
Asanka
On 21 August 2017 at 10:46, Asanka Gunasekara <as...@nimbus.lk> wrote:
> Hi Dag/Eric, thank you both for the reply, let me do your advice and will
> update you on the results
>
> Thank you and best Regards
>
> Asanka
>
> On 19 August 2017 at 14:45, Dag Sonstebo <Da...@shapeblue.com>
> wrote:
>
>> Hi Asanka,
>>
>> Agree with Eric, doesn’t look right.,
>>
>> The quickest solution here is to:
>>
>> 1) disable zone
>> 2) delete system VMs
>> 3) remove secondary storage from cloudstack
>> 4) try the secondary storage seeding again with images from
>> http://packages.shapeblue.com/systemvmtemplate/4.6/new/ - but use the
>> “-F” option when you call /usr/share/cloudstack-common/s
>> cripts/storage/secondary/cloud-install-sys-tmplt > this will clean up
>> previous template
>> 5) add secondary storage to CloudStack again
>> 6) enable zone and monitor
>>
>>
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>>
>> On 18/08/2017, 18:35, "Eric Green" <er...@gmail.com> wrote:
>>
>>
>>
>> Dag.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> > On Aug 18, 2017, at 03:22, Asanka Gunasekara <as...@nimbus.lk> wrote:
>> >
>> > Hi Eric,
>> >
>> > SSVM can access my nfs and I an manual mount :(
>> >
>> > This "s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand
>> /var/log/cloud.log" did not produced any output, but found below error
>> >
>> > From the VM's /var/log/cloud.log:
>> > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent:
>> Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource
>> due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.Pre
>> miumSecondaryStorageResource
>>
>>
>> Hmm. That doesn't look good. So the agent is never even able to start
>> because of that exception. This looks like a mismatch between your SSVM
>> template and your version of Cloudstack. It looks like you're using a
>> version of Cloudstack that has been compiled with premium features that is
>> expecting a template that supports premium features.
>>
>> Someone else will have to tell you how to change the SSVM template, I
>> don't know that. Or since this is a zone that has never been operational,
>> you may choose to simply wipe the current install entirely and start over
>> again from scratch with a Cloudstack and SSVM template all from the same
>> source. Remember to drop and recreate the database as part of that process,
>> as well as remove all the contents of the secondary store and follow the
>> directions again to reinitialize with the initial template.
>>
>> For the record, I got my Cloudstack from this source:
>>
>> [cloudstack]
>> name=cloudstack
>> baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.9/
>> enabled=1
>> gpgcheck=0
>>
>> My template similarly came from that source (but the 4.6 version, as
>> you specified).
>>
>> Once I got my networking sorted out, which you seem to have done, it
>> Just Worked.
>>
>>
>>
>>
>
Re: Secondary storage is not secondary properly
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Dag/Eric, thank you both for the reply, let me do your advice and will
update you on the results
Thank you and best Regards
Asanka
On 19 August 2017 at 14:45, Dag Sonstebo <Da...@shapeblue.com> wrote:
> Hi Asanka,
>
> Agree with Eric, doesn’t look right.,
>
> The quickest solution here is to:
>
> 1) disable zone
> 2) delete system VMs
> 3) remove secondary storage from cloudstack
> 4) try the secondary storage seeding again with images from
> http://packages.shapeblue.com/systemvmtemplate/4.6/new/ - but use the
> “-F” option when you call /usr/share/cloudstack-common/
> scripts/storage/secondary/cloud-install-sys-tmplt > this will clean up
> previous template
> 5) add secondary storage to CloudStack again
> 6) enable zone and monitor
>
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 18/08/2017, 18:35, "Eric Green" <er...@gmail.com> wrote:
>
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> > On Aug 18, 2017, at 03:22, Asanka Gunasekara <as...@nimbus.lk> wrote:
> >
> > Hi Eric,
> >
> > SSVM can access my nfs and I an manual mount :(
> >
> > This "s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand
> /var/log/cloud.log" did not produced any output, but found below error
> >
> > From the VM's /var/log/cloud.log:
> > ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent:
> Resource class not found: com.cloud.storage.resource.
> PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException:
> com.cloud.storage.resource.PremiumSecondaryStorageResource
>
>
> Hmm. That doesn't look good. So the agent is never even able to start
> because of that exception. This looks like a mismatch between your SSVM
> template and your version of Cloudstack. It looks like you're using a
> version of Cloudstack that has been compiled with premium features that is
> expecting a template that supports premium features.
>
> Someone else will have to tell you how to change the SSVM template, I
> don't know that. Or since this is a zone that has never been operational,
> you may choose to simply wipe the current install entirely and start over
> again from scratch with a Cloudstack and SSVM template all from the same
> source. Remember to drop and recreate the database as part of that process,
> as well as remove all the contents of the secondary store and follow the
> directions again to reinitialize with the initial template.
>
> For the record, I got my Cloudstack from this source:
>
> [cloudstack]
> name=cloudstack
> baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.9/
> enabled=1
> gpgcheck=0
>
> My template similarly came from that source (but the 4.6 version, as
> you specified).
>
> Once I got my networking sorted out, which you seem to have done, it
> Just Worked.
>
>
>
>
Re: Secondary storage is not secondary properly
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Hi Asanka,
Agree with Eric, doesn’t look right.,
The quickest solution here is to:
1) disable zone
2) delete system VMs
3) remove secondary storage from cloudstack
4) try the secondary storage seeding again with images from http://packages.shapeblue.com/systemvmtemplate/4.6/new/ - but use the “-F” option when you call /usr/share/cloudstack-common/scripts/storage/secondary/cloud-install-sys-tmplt > this will clean up previous template
5) add secondary storage to CloudStack again
6) enable zone and monitor
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 18/08/2017, 18:35, "Eric Green" <er...@gmail.com> wrote:
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
> On Aug 18, 2017, at 03:22, Asanka Gunasekara <as...@nimbus.lk> wrote:
>
> Hi Eric,
>
> SSVM can access my nfs and I an manual mount :(
>
> This "s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand /var/log/cloud.log" did not produced any output, but found below error
>
> From the VM's /var/log/cloud.log:
> ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource
Hmm. That doesn't look good. So the agent is never even able to start because of that exception. This looks like a mismatch between your SSVM template and your version of Cloudstack. It looks like you're using a version of Cloudstack that has been compiled with premium features that is expecting a template that supports premium features.
Someone else will have to tell you how to change the SSVM template, I don't know that. Or since this is a zone that has never been operational, you may choose to simply wipe the current install entirely and start over again from scratch with a Cloudstack and SSVM template all from the same source. Remember to drop and recreate the database as part of that process, as well as remove all the contents of the secondary store and follow the directions again to reinitialize with the initial template.
For the record, I got my Cloudstack from this source:
[cloudstack]
name=cloudstack
baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.9/
enabled=1
gpgcheck=0
My template similarly came from that source (but the 4.6 version, as you specified).
Once I got my networking sorted out, which you seem to have done, it Just Worked.
Re: Secondary storage is not secondary properly
Posted by Eric Green <er...@gmail.com>.
> On Aug 18, 2017, at 03:22, Asanka Gunasekara <as...@nimbus.lk> wrote:
>
> Hi Eric,
>
> SSVM can access my nfs and I an manual mount :(
>
> This "s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand /var/log/cloud.log" did not produced any output, but found below error
>
> From the VM's /var/log/cloud.log:
> ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource due to: java.lang.ClassNotFoundException: com.cloud.storage.resource.PremiumSecondaryStorageResource
Hmm. That doesn't look good. So the agent is never even able to start because of that exception. This looks like a mismatch between your SSVM template and your version of Cloudstack. It looks like you're using a version of Cloudstack that has been compiled with premium features that is expecting a template that supports premium features.
Someone else will have to tell you how to change the SSVM template, I don't know that. Or since this is a zone that has never been operational, you may choose to simply wipe the current install entirely and start over again from scratch with a Cloudstack and SSVM template all from the same source. Remember to drop and recreate the database as part of that process, as well as remove all the contents of the secondary store and follow the directions again to reinitialize with the initial template.
For the record, I got my Cloudstack from this source:
[cloudstack]
name=cloudstack
baseurl=http://cloudstack.apt-get.eu/centos/$releasever/4.9/
enabled=1
gpgcheck=0
My template similarly came from that source (but the 4.6 version, as you specified).
Once I got my networking sorted out, which you seem to have done, it Just Worked.
Re: Secondary storage is not secondary properly
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Eric,
SSVM can access my nfs and I an manual mount :(
This "s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand
/var/log/cloud.log" did not produced any output, but found below error
From the VM's /var/log/cloud.log:
ERROR [cloud.agent.AgentShell] (main:null) Unable to start agent: Resource
class not found: com.cloud.storage.resource.PremiumSecondaryStorageResource
due to: java.lang.ClassNotFoundException:
com.cloud.storage.resource.PremiumSecondaryStorageResource
I used cloudstac from http://www.shapeblue.com/packages/ and the SSVM
template from
http://cloudstack.apt-get.eu/systemvm/4.6/systemvm64template-4.6.0-vmware.ova
Do you think I need to use http://packages.shapeblue.com/systemvmtemplate/
If it so how can I replace an existing SSVM template?
Sorry to be of a asking these question, I am new to this setup
Thank you and Best Regards
Asanka
On 18 August 2017 at 03:38, Eric Lee Green <er...@gmail.com> wrote:
> On 08/17/2017 11:17 AM, Asanka Gunasekara wrote:
>
>> Hi Dag, the ip 172.17.101.1 which it is looking for is my gateway IP.
>> Below
>> are the urls for the the requested query output files
>>
>> SELECT * FROM cloud.image_store;
>>
> Interesting. The only row with a NULL 'removed' column looks good, so it
> looks like your database configuration is correct:
>
> 5 | NFS_Secondary | NFS | nfs | nfs://172.17.101.253/share_smb
> /export/secondary | 1 | ZONE | Image |
> a4e17aca-dc16-494e-b696-8f8fae58a391 | 2017-08-14 19:12:50.0 |||
>
> Compare with my own query of my own image store, which is basically
> identical
>
> MariaDB [cloud]> select * from cloud.image_store;
> +----+------------+---------------------+----------+--------
> -----------------------------+----------------+-------+-----
> --+--------------------------------------+------------------
> --------------------+---------------------+---------+-------
> -----+------------+
> | id | name | image_provider_name | protocol | url
> | data_center_id | scope | role | uuid
> | parent | created |
> removed | total_size | used_bytes |
> +----+------------+---------------------+----------+--------
> -----------------------------+----------------+-------+-----
> --+--------------------------------------+------------------
> --------------------+---------------------+---------+-------
> -----+------------+
> | 1 | secondary1 | NFS | nfs | nfs://
> 10.100.255.1/export/secondary | 1 | ZONE | Image |
> fdaab425-a102-484b-b746-c07c4b564edd | 50d77b6b-4d99-3695-b830-24ed10d0155c
> | 2017-07-31 00:55:06 | NULL | NULL | NULL |
> +----+------------+---------------------+----------+--------
> -----------------------------+----------------+-------+-----
> --+--------------------------------------+------------------
> --------------------+---------------------+---------+-------
> -----+------------+
> 1 row in set (0.00 sec)
>
> Note that 10.100.255.1 is on my management network, which is also my
> storage network (I have everything coming in on VLAN's on a 10Gbit bond,
> the 10.100.x.x network is on VLAN 100). When I go into my secondary
> storage VM, here is what I see:
>
> Now, getting into my secondary storage VM and asking it for a list of
> addresses, here is what I see:
>
> root@s-397-VM:~# ip addr list | grep inet
> inet 127.0.0.1/8 scope host lo
> inet 169.254.0.95/16 brd 169.254.255.255 scope global eth0
> inet 10.100.196.66/16 brd 10.100.255.255 scope global eth1
> inet 10.101.199.255/16 brd 10.101.255.255 scope global eth2
> inet 10.100.250.159/16 brd 10.100.255.255 scope global eth3
>
> So as you can see, it definitely has access to the management network
> (10.100.x.x), as well as my public IP pool (10.101.x.x) and storage pool
> (the second 10.100 address). As well as the local agent-visible IP (the
> 169.254.0.95) that ssh is listening on so that the agent can configure the
> VM via its shared keys.
>
> Here is what my ssvm-check says:
>
> root@s-397-VM:/opt# /usr/local/cloud/systemvm/ssvm-check.sh
> ================================================
> First DNS server is 10.100.255.2
> PING 10.100.255.2 (10.100.255.2): 48 data bytes
> 56 bytes from 10.100.255.2: icmp_seq=0 ttl=64 time=0.189 ms
> 56 bytes from 10.100.255.2: icmp_seq=1 ttl=64 time=0.438 ms
> --- 10.100.255.2 ping statistics ---
> 2 packets transmitted, 2 packets received, 0% packet loss
> round-trip min/avg/max/stddev = 0.189/0.314/0.438/0.125 ms
> Good: Can ping DNS server
> ================================================
> Good: DNS resolves download.cloud.com
> ================================================
> nfs is currently mounted
> Mount point is /mnt/SecStorage/50d77b6b-4d99-3695-b830-24ed10d0155c
> Good: Can write to mount point
> ================================================
> Management server is 10.100.255.2. Checking connectivity.
> Good: Can connect to management server port 8250
> ================================================
> Good: Java process is running
> ================================================
> Tests Complete. Look for ERROR or WARNING above.
>
>
> Your says 'Java process not running'. I wonder if your 169 address is
> working? Let's check your cloud.log to see if you ever got a setup command:
>
> s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand
> /var/log/cloud.log
>
> Mine replies with:
>
> 2017-08-17 02:21:12,975 DEBUG [cloud.agent.Agent]
> (agentRequest-Handler-1:null) Request:Seq 9-231372430856159233: { Cmd ,
> MgmtId: 11967559506, via: 9, Ver: v1, Flags: 100111,
> [{"com.cloud.agent.api.SecStorageSetupCommand":{"store":{"
> com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.100.255.1/export/secondary
> ","_role":"Image"}},"secUrl":"nfs://10.100.255.1/export/secondary","
> postUploadKey":"KZQd8G06ABN3D_CGAJiKBmhLe3e5dim5hfA7ouuZnvQt
> ZNoHxE3T4WiqTxOdVPBh5hHhNtvX8e9Gac0Tw7gM5g","wait":0}}] }
>
> See if you got a similar command with your own NFS server's address.
>
>
Re: Secondary storage is not secondary properly
Posted by Eric Lee Green <er...@gmail.com>.
On 08/17/2017 11:17 AM, Asanka Gunasekara wrote:
> Hi Dag, the ip 172.17.101.1 which it is looking for is my gateway IP. Below
> are the urls for the the requested query output files
>
> SELECT * FROM cloud.image_store;
Interesting. The only row with a NULL 'removed' column looks good, so
it looks like your database configuration is correct:
5 | NFS_Secondary | NFS | nfs |
nfs://172.17.101.253/share_smb/export/secondary | 1 | ZONE |
Image | a4e17aca-dc16-494e-b696-8f8fae58a391 | 2017-08-14
19:12:50.0 |||
Compare with my own query of my own image store, which is basically
identical
MariaDB [cloud]> select * from cloud.image_store;
+----+------------+---------------------+----------+-------------------------------------+----------------+-------+-------+--------------------------------------+--------------------------------------+---------------------+---------+------------+------------+
| id | name | image_provider_name | protocol |
url | data_center_id | scope | role |
uuid |
parent | created | removed |
total_size | used_bytes |
+----+------------+---------------------+----------+-------------------------------------+----------------+-------+-------+--------------------------------------+--------------------------------------+---------------------+---------+------------+------------+
| 1 | secondary1 | NFS | nfs |
nfs://10.100.255.1/export/secondary | 1 | ZONE | Image |
fdaab425-a102-484b-b746-c07c4b564edd |
50d77b6b-4d99-3695-b830-24ed10d0155c | 2017-07-31 00:55:06 | NULL
| NULL | NULL |
+----+------------+---------------------+----------+-------------------------------------+----------------+-------+-------+--------------------------------------+--------------------------------------+---------------------+---------+------------+------------+
1 row in set (0.00 sec)
Note that 10.100.255.1 is on my management network, which is also my
storage network (I have everything coming in on VLAN's on a 10Gbit bond,
the 10.100.x.x network is on VLAN 100). When I go into my secondary
storage VM, here is what I see:
Now, getting into my secondary storage VM and asking it for a list of
addresses, here is what I see:
root@s-397-VM:~# ip addr list | grep inet
inet 127.0.0.1/8 scope host lo
inet 169.254.0.95/16 brd 169.254.255.255 scope global eth0
inet 10.100.196.66/16 brd 10.100.255.255 scope global eth1
inet 10.101.199.255/16 brd 10.101.255.255 scope global eth2
inet 10.100.250.159/16 brd 10.100.255.255 scope global eth3
So as you can see, it definitely has access to the management network
(10.100.x.x), as well as my public IP pool (10.101.x.x) and storage pool
(the second 10.100 address). As well as the local agent-visible IP (the
169.254.0.95) that ssh is listening on so that the agent can configure
the VM via its shared keys.
Here is what my ssvm-check says:
root@s-397-VM:/opt# /usr/local/cloud/systemvm/ssvm-check.sh
================================================
First DNS server is 10.100.255.2
PING 10.100.255.2 (10.100.255.2): 48 data bytes
56 bytes from 10.100.255.2: icmp_seq=0 ttl=64 time=0.189 ms
56 bytes from 10.100.255.2: icmp_seq=1 ttl=64 time=0.438 ms
--- 10.100.255.2 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.189/0.314/0.438/0.125 ms
Good: Can ping DNS server
================================================
Good: DNS resolves download.cloud.com
================================================
nfs is currently mounted
Mount point is /mnt/SecStorage/50d77b6b-4d99-3695-b830-24ed10d0155c
Good: Can write to mount point
================================================
Management server is 10.100.255.2. Checking connectivity.
Good: Can connect to management server port 8250
================================================
Good: Java process is running
================================================
Tests Complete. Look for ERROR or WARNING above.
Your says 'Java process not running'. I wonder if your 169 address is
working? Let's check your cloud.log to see if you ever got a setup command:
s-397-VM:/# grep com.cloud.agent.api.SecStorageSetupCommand
/var/log/cloud.log
Mine replies with:
2017-08-17 02:21:12,975 DEBUG [cloud.agent.Agent]
(agentRequest-Handler-1:null) Request:Seq 9-231372430856159233: { Cmd ,
MgmtId: 11967559506, via: 9, Ver: v1, Flags: 100111,
[{"com.cloud.agent.api.SecStorageSetupCommand":{"store":{"com.cloud.agent.api.to.NfsTO":{"_url":"nfs://10.100.255.1/export/secondary","_role":"Image"}},"secUrl":"nfs://10.100.255.1/export/secondary","postUploadKey":"KZQd8G06ABN3D_CGAJiKBmhLe3e5dim5hfA7ouuZnvQtZNoHxE3T4WiqTxOdVPBh5hHhNtvX8e9Gac0Tw7gM5g","wait":0}}]
}
See if you got a similar command with your own NFS server's address.
Re: Secondary storage is not secondary properly
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Dag, the ip 172.17.101.1 which it is looking for is my gateway IP. Below
are the urls for the the requested query output files
SELECT * FROM cloud.image_store;
http://wikisend.com/download/727732/01.htm
SELECT id,name,url,state FROM cloud.vm_template where type='SYSTEM';
http://wikisend.com/download/229028/02.htm
Thank you and best regards
Asanka
On 17 August 2017 at 15:47, Dag Sonstebo <Da...@shapeblue.com> wrote:
> Hi Asanka,
>
> This looks odd – your SSVM is connecting to your management server but as
> far as I can see it is still trying to connect to the wrong NFS server.
>
> Can you give me the output from the following MySQL queries:
>
> SELECT * FROM cloud.image_store;
>
> SELECT id,name,url,state FROM cloud.vm_template where type='SYSTEM';
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
> http://www.shapeblue.com <http://www.shapeblue.com/> | Twitter:@ShapeBlue
> <https://twitter.com/#!/shapeblue>
>
>
> On 17/08/2017, 07:41, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>
> Hi Dag, still the error persists, please find the screen shot url
>
> https://snag.gy/xecXiP.jpg
>
> Could it be the cloudstack version that I am using, since the vmware
> support is not built in to the download cloudstack provided, I used
> below
> url but the system vm template is from cloudstack
>
> http://www.shapeblue.com/packages/
>
> Thanks and Reagrds
>
> Asanka
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> On 17 August 2017 at 11:37, Asanka Gunasekara <as...@nimbus.lk> wrote:
>
> > Thank you, Rodrigo
> >
> > Best Regards
> >
> > Asanka
> >
> > On 15 August 2017 at 23:04, Rodrigo Baldasso <
> rodrigo@loophost.com.br>
> > wrote:
> >
> >> Put the zone in maitenance mode, that will not auto create the
> ssvm's.
> >>
> >> - - - - - - - - - - - - - - - - - - -
> >>
> >> Rodrigo Baldasso - LHOST
> >>
> >> (51) 9 8419-9861
> >> - - - - - - - - - - - - - - - - - - -
> >> On 15/08/2017 14:00:45, Asanka Gunasekara <as...@nimbus.lk> wrote:
> >> Hi Dag, restart did not work but updating the tables initiate the
> >> recreation of the system VMs. But it does not give me the chance to
> >> restart
> >> cloudstack server, as soon as destroy the VMs it starts the VM
> recreation.
> >> Is there a way to stop this behaviour
> >>
> >> Thanks and Regards
> >>
> >> Asanka
> >>
> >> On 15 August 2017 at 14:19, Asanka Gunasekara wrote:
> >>
> >> > Thank you Dag
> >> >
> >> > Best Regards
> >> >
> >> > Asanka
> >> >
> >> > On 15 August 2017 at 13:18, Dag Sonstebo
> >> > wrote:
> >> >
> >> >> Hi Asanka,
> >> >>
> >> >> Maybe give you management server a reboot first of all.
> >> >>
> >> >> If this fails then yes we sometimes set status to stopped or
> destroyed
> >> in
> >> >> the DB – you also need to set the removed date and last update
> date.
> >> >>
> >> >> Regards,
> >> >> Dag Sonstebo
> >> >> Cloud Architect
> >> >> ShapeBlue
> >> >>
> >> >> On 15/08/2017, 07:07, "Asanka Gunasekara" wrote:
> >> >>
> >> >> Hi Guys, what would happen if i change the column in the table
> >> >> VM_instance,
> >> >> to Destroyed or running
> >> >>
> >> >> :(
> >> >>
> >> >> On 15 Aug 2017 8:28 am, "Asanka Gunasekara" wrote:
> >> >>
> >> >> > Hi Guys, when a system VM is in start state in ui, it does not
> give
> >> >> any
> >> >> > option to delete stop start etc. What if it to change db entry
> of
> >> >> the
> >> >> > system VMS to running state. Will it give me the option to
> destroy?
> >> >> If so
> >> >> > what would be the database relation?
> >> >> >
> >> >> > Thanks and regards
> >> >> >
> >> >> > Asanka
> >> >> >
> >> >> > On 15 Aug 2017 6:42 am, "Asanka Gunasekara"
> >> >> wrote:
> >> >> >
> >> >> >> Hi Dag, I deleted both the system VMs and from the cloudstack
> it
> >> >> says
> >> >> >> starting but I dont see the the VM been generated, now its
> since
> >> >> more than
> >> >> >> 12 houres
> >> >> >>
> >> >> >> Thanks and Regards
> >> >> >>
> >> >> >> Asanka
> >> >> >>
> >> >> >
> >> >> Dag.Sonstebo@shapeblue.com
> >> >> www.shapeblue.com
> >> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> >> @shapeblue
> >> >>
> >> >>
> >> >>
> >> >> > On 10 August 2017 at 21:47, Asanka Gunasekara wrote:
> >> >> >>
> >> >> >>> Thank you Dag,
> >> >> >>>
> >> >> >>>
> >> >> >>> On 10 Aug 2017 3:09 am, "Dag Sonstebo"
> >> >> Dag.Sonstebo@shapeblue.com>
> >> >> >>> wrote:
> >> >> >>>
> >> >> >>> Sure, let us know how you get on. The fact that the previous
> ssvm
> >> >> check
> >> >> >>> showed up with 172.17.101.1 was probably down to the wrong
> “host”
> >> >> global
> >> >> >>> setting – since the SSVM didn’t know where to contact
> management
> >> >> I would
> >> >> >>> guess it used a default override.
> >> >> >>>
> >> >> >>> Regards,
> >> >> >>> Dag Sonstebo
> >> >> >>> Cloud Architect
> >> >> >>> ShapeBlue
> >> >> >>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
> >> >> >>> http://www.shapeblue.com |
> >> >> >>> Twitter:@ShapeBlue
> >> >> >>>
> >> >> >>>
> >> >> >>> On 09/08/2017, 17:54, "Asanka Gunasekara"
> >> >> wrote:
> >> >> >>>
> >> >> >>> Hi Dag, pleas give me few days as I am on an implementation
> >> >> visit to
> >> >> >>> a
> >> >> >>> remote site. But below are some of the test I performed
> >> >> before.
> >> >> >>>
> >> >> >>> 1. Ping from ssvm to NFS is possible
> >> >> >>> 2. Manually mounting NFS to /tmp/secondary is possible
> >> >> without any
> >> >> >>> Issy
> >> >> >>>
> >> >> >>> From the previous run of the ssvm check it is looking for a
> >> >> serve IP
> >> >> >>> 172.17.101.1. Where registered NFS share is 172.17.101.253
> >> >> >>>
> >> >> >>> I will run the check again on the first chance I get
> >> >> >>>
> >> >> >>> Thank you and best regards
> >> >> >>>
> >> >> >>> Asanka
> >> >> >>>
> >> >> >>>
> >> >> >>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo"
> >> >> Dag.Sonstebo@shapeblue.com>
> >> >> >>> wrote:
> >> >> >>>
> >> >> >>> OK , can you post up the results of the ssvm check again?
> >> >> >>>
> >> >> >>> As suggested previously on this thread – can you try to
> >> >> >>> 1) Ping the NFS server from the SSVM (SSVM check does this as
> >> >> well)
> >> >> >>> – if
> >> >> >>> this doesn’t work then you have a networking issue.
> >> >> >>> 2) Depending on ping - manually mount the secondary NFS share
> >> >> on
> >> >> >>> your SSVM.
> >> >> >>> If this doesn’t work then you need to investigate the logs at
> >> >> the
> >> >> >>> NFS end
> >> >> >>> to see why the NFS handshake fails.
> >> >> >>>
> >> >> >>> Regards,
> >> >> >>> Dag Sonstebo
> >> >> >>> Cloud Architect
> >> >> >>> ShapeBlue
> >> >> >>>
> >> >> >>> On 08/08/2017, 19:14, "Asanka Gunasekara"
> >> >> wrote:
> >> >> >>>
> >> >> >>> 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
> >> >> >>>
> >> >> >>>
> >> >> >>> Dag.Sonstebo@shapeblue.com
> >> >> >>> www.shapeblue.com
> >> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> >> >>> @shapeblue
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>> Dag.Sonstebo@shapeblue.com
> >> >> >>> www.shapeblue.com
> >> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> >> >>> @shapeblue
> >> >> >>>
> >> >> >>>
> >> >> >>>
> >> >> >>> On 8 August 2017 at 23:33, Asanka Gunasekara
> >> >> wrote:
> >> >> >>>
> >> >> >>> > 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_s
> >> >> >>> ubtree_check)
> >> >> >>> > [root@share ~]#
> >> >> >>> >
> >> >> >>> >
> >> >> >>> > On 8 August 2017 at 17:06, Dag Sonstebo
> >> >> >>> Dag.Sonstebo@shapeblue.com>
> >> >> >>> > 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"
> >> >> asanka@nimbus.lk>
> >> >> >>> 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.Sonstebo@shapeblue.com
> >> >> >>> >> www.shapeblue.com
> >> >> >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> >> >>> >> @shapeblue
> >> >> >>> >>
> >> >> >>> >>
> >> >> >>> >>
> >> >> >>> >> On 8 August 2017 at 14:48, Asanka Gunasekara
> >> >> >>> asanka@nimbus.lk>
> >> >> >>> wrote:
> >> >> >>> >>
> >> >> >>> >> > Thanks Makrand
> >> >> >>> >> >
> >> >> >>> >> > On 8 August 2017 at 14:42, Makrand
> >> >> >>> makrandsanap@gmail.com>
> >> >> >>> 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
> >> >> >>> >> asanka@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.Sonstebo@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"
> >> >> >>> 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.Sonstebo@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.green@gmail.com
> >> >> >>> >>
> >> >> >>> >> >> to:
> >> >> >>> >> >> >> eric.lee.green@gmail.com>> wrote:
> >> >> >>> >> >> >>
> >> >> >>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka
> >> >> Gunasekara
> >> >> >>> asanka@nimbus.lk
> >> >> >>> >> >>
> >> >> >>> >> >> >> asanka@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
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Hi Asanka,
This looks odd – your SSVM is connecting to your management server but as far as I can see it is still trying to connect to the wrong NFS server.
Can you give me the output from the following MySQL queries:
SELECT * FROM cloud.image_store;
SELECT id,name,url,state FROM cloud.vm_template where type='SYSTEM';
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com | http://www.shapeblue.com <http://www.shapeblue.com/> | Twitter:@ShapeBlue <https://twitter.com/#!/shapeblue>
On 17/08/2017, 07:41, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
Hi Dag, still the error persists, please find the screen shot url
https://snag.gy/xecXiP.jpg
Could it be the cloudstack version that I am using, since the vmware
support is not built in to the download cloudstack provided, I used below
url but the system vm template is from cloudstack
http://www.shapeblue.com/packages/
Thanks and Reagrds
Asanka
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 17 August 2017 at 11:37, Asanka Gunasekara <as...@nimbus.lk> wrote:
> Thank you, Rodrigo
>
> Best Regards
>
> Asanka
>
> On 15 August 2017 at 23:04, Rodrigo Baldasso <ro...@loophost.com.br>
> wrote:
>
>> Put the zone in maitenance mode, that will not auto create the ssvm's.
>>
>> - - - - - - - - - - - - - - - - - - -
>>
>> Rodrigo Baldasso - LHOST
>>
>> (51) 9 8419-9861
>> - - - - - - - - - - - - - - - - - - -
>> On 15/08/2017 14:00:45, Asanka Gunasekara <as...@nimbus.lk> wrote:
>> Hi Dag, restart did not work but updating the tables initiate the
>> recreation of the system VMs. But it does not give me the chance to
>> restart
>> cloudstack server, as soon as destroy the VMs it starts the VM recreation.
>> Is there a way to stop this behaviour
>>
>> Thanks and Regards
>>
>> Asanka
>>
>> On 15 August 2017 at 14:19, Asanka Gunasekara wrote:
>>
>> > Thank you Dag
>> >
>> > Best Regards
>> >
>> > Asanka
>> >
>> > On 15 August 2017 at 13:18, Dag Sonstebo
>> > wrote:
>> >
>> >> Hi Asanka,
>> >>
>> >> Maybe give you management server a reboot first of all.
>> >>
>> >> If this fails then yes we sometimes set status to stopped or destroyed
>> in
>> >> the DB – you also need to set the removed date and last update date.
>> >>
>> >> Regards,
>> >> Dag Sonstebo
>> >> Cloud Architect
>> >> ShapeBlue
>> >>
>> >> On 15/08/2017, 07:07, "Asanka Gunasekara" wrote:
>> >>
>> >> Hi Guys, what would happen if i change the column in the table
>> >> VM_instance,
>> >> to Destroyed or running
>> >>
>> >> :(
>> >>
>> >> On 15 Aug 2017 8:28 am, "Asanka Gunasekara" wrote:
>> >>
>> >> > Hi Guys, when a system VM is in start state in ui, it does not give
>> >> any
>> >> > option to delete stop start etc. What if it to change db entry of
>> >> the
>> >> > system VMS to running state. Will it give me the option to destroy?
>> >> If so
>> >> > what would be the database relation?
>> >> >
>> >> > Thanks and regards
>> >> >
>> >> > Asanka
>> >> >
>> >> > On 15 Aug 2017 6:42 am, "Asanka Gunasekara"
>> >> wrote:
>> >> >
>> >> >> Hi Dag, I deleted both the system VMs and from the cloudstack it
>> >> says
>> >> >> starting but I dont see the the VM been generated, now its since
>> >> more than
>> >> >> 12 houres
>> >> >>
>> >> >> Thanks and Regards
>> >> >>
>> >> >> Asanka
>> >> >>
>> >> >
>> >> Dag.Sonstebo@shapeblue.com
>> >> www.shapeblue.com
>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> @shapeblue
>> >>
>> >>
>> >>
>> >> > On 10 August 2017 at 21:47, Asanka Gunasekara wrote:
>> >> >>
>> >> >>> Thank you Dag,
>> >> >>>
>> >> >>>
>> >> >>> On 10 Aug 2017 3:09 am, "Dag Sonstebo"
>> >> Dag.Sonstebo@shapeblue.com>
>> >> >>> wrote:
>> >> >>>
>> >> >>> Sure, let us know how you get on. The fact that the previous ssvm
>> >> check
>> >> >>> showed up with 172.17.101.1 was probably down to the wrong “host”
>> >> global
>> >> >>> setting – since the SSVM didn’t know where to contact management
>> >> I would
>> >> >>> guess it used a default override.
>> >> >>>
>> >> >>> Regards,
>> >> >>> Dag Sonstebo
>> >> >>> Cloud Architect
>> >> >>> ShapeBlue
>> >> >>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
>> >> >>> http://www.shapeblue.com |
>> >> >>> Twitter:@ShapeBlue
>> >> >>>
>> >> >>>
>> >> >>> On 09/08/2017, 17:54, "Asanka Gunasekara"
>> >> wrote:
>> >> >>>
>> >> >>> Hi Dag, pleas give me few days as I am on an implementation
>> >> visit to
>> >> >>> a
>> >> >>> remote site. But below are some of the test I performed
>> >> before.
>> >> >>>
>> >> >>> 1. Ping from ssvm to NFS is possible
>> >> >>> 2. Manually mounting NFS to /tmp/secondary is possible
>> >> without any
>> >> >>> Issy
>> >> >>>
>> >> >>> From the previous run of the ssvm check it is looking for a
>> >> serve IP
>> >> >>> 172.17.101.1. Where registered NFS share is 172.17.101.253
>> >> >>>
>> >> >>> I will run the check again on the first chance I get
>> >> >>>
>> >> >>> Thank you and best regards
>> >> >>>
>> >> >>> Asanka
>> >> >>>
>> >> >>>
>> >> >>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo"
>> >> Dag.Sonstebo@shapeblue.com>
>> >> >>> wrote:
>> >> >>>
>> >> >>> OK , can you post up the results of the ssvm check again?
>> >> >>>
>> >> >>> As suggested previously on this thread – can you try to
>> >> >>> 1) Ping the NFS server from the SSVM (SSVM check does this as
>> >> well)
>> >> >>> – if
>> >> >>> this doesn’t work then you have a networking issue.
>> >> >>> 2) Depending on ping - manually mount the secondary NFS share
>> >> on
>> >> >>> your SSVM.
>> >> >>> If this doesn’t work then you need to investigate the logs at
>> >> the
>> >> >>> NFS end
>> >> >>> to see why the NFS handshake fails.
>> >> >>>
>> >> >>> Regards,
>> >> >>> Dag Sonstebo
>> >> >>> Cloud Architect
>> >> >>> ShapeBlue
>> >> >>>
>> >> >>> On 08/08/2017, 19:14, "Asanka Gunasekara"
>> >> wrote:
>> >> >>>
>> >> >>> 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
>> >> >>>
>> >> >>>
>> >> >>> Dag.Sonstebo@shapeblue.com
>> >> >>> www.shapeblue.com
>> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> >>> @shapeblue
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Dag.Sonstebo@shapeblue.com
>> >> >>> www.shapeblue.com
>> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> >>> @shapeblue
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On 8 August 2017 at 23:33, Asanka Gunasekara
>> >> wrote:
>> >> >>>
>> >> >>> > 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_s
>> >> >>> ubtree_check)
>> >> >>> > [root@share ~]#
>> >> >>> >
>> >> >>> >
>> >> >>> > On 8 August 2017 at 17:06, Dag Sonstebo
>> >> >>> Dag.Sonstebo@shapeblue.com>
>> >> >>> > 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"
>> >> asanka@nimbus.lk>
>> >> >>> 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.Sonstebo@shapeblue.com
>> >> >>> >> www.shapeblue.com
>> >> >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> >>> >> @shapeblue
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> On 8 August 2017 at 14:48, Asanka Gunasekara
>> >> >>> asanka@nimbus.lk>
>> >> >>> wrote:
>> >> >>> >>
>> >> >>> >> > Thanks Makrand
>> >> >>> >> >
>> >> >>> >> > On 8 August 2017 at 14:42, Makrand
>> >> >>> makrandsanap@gmail.com>
>> >> >>> 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
>> >> >>> >> asanka@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.Sonstebo@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"
>> >> >>> 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.Sonstebo@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.green@gmail.com
>> >> >>> >>
>> >> >>> >> >> to:
>> >> >>> >> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >>> >> >> >>
>> >> >>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka
>> >> Gunasekara
>> >> >>> asanka@nimbus.lk
>> >> >>> >> >>
>> >> >>> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Dag, still the error persists, please find the screen shot url
https://snag.gy/xecXiP.jpg
Could it be the cloudstack version that I am using, since the vmware
support is not built in to the download cloudstack provided, I used below
url but the system vm template is from cloudstack
http://www.shapeblue.com/packages/
Thanks and Reagrds
Asanka
On 17 August 2017 at 11:37, Asanka Gunasekara <as...@nimbus.lk> wrote:
> Thank you, Rodrigo
>
> Best Regards
>
> Asanka
>
> On 15 August 2017 at 23:04, Rodrigo Baldasso <ro...@loophost.com.br>
> wrote:
>
>> Put the zone in maitenance mode, that will not auto create the ssvm's.
>>
>> - - - - - - - - - - - - - - - - - - -
>>
>> Rodrigo Baldasso - LHOST
>>
>> (51) 9 8419-9861
>> - - - - - - - - - - - - - - - - - - -
>> On 15/08/2017 14:00:45, Asanka Gunasekara <as...@nimbus.lk> wrote:
>> Hi Dag, restart did not work but updating the tables initiate the
>> recreation of the system VMs. But it does not give me the chance to
>> restart
>> cloudstack server, as soon as destroy the VMs it starts the VM recreation.
>> Is there a way to stop this behaviour
>>
>> Thanks and Regards
>>
>> Asanka
>>
>> On 15 August 2017 at 14:19, Asanka Gunasekara wrote:
>>
>> > Thank you Dag
>> >
>> > Best Regards
>> >
>> > Asanka
>> >
>> > On 15 August 2017 at 13:18, Dag Sonstebo
>> > wrote:
>> >
>> >> Hi Asanka,
>> >>
>> >> Maybe give you management server a reboot first of all.
>> >>
>> >> If this fails then yes we sometimes set status to stopped or destroyed
>> in
>> >> the DB – you also need to set the removed date and last update date.
>> >>
>> >> Regards,
>> >> Dag Sonstebo
>> >> Cloud Architect
>> >> ShapeBlue
>> >>
>> >> On 15/08/2017, 07:07, "Asanka Gunasekara" wrote:
>> >>
>> >> Hi Guys, what would happen if i change the column in the table
>> >> VM_instance,
>> >> to Destroyed or running
>> >>
>> >> :(
>> >>
>> >> On 15 Aug 2017 8:28 am, "Asanka Gunasekara" wrote:
>> >>
>> >> > Hi Guys, when a system VM is in start state in ui, it does not give
>> >> any
>> >> > option to delete stop start etc. What if it to change db entry of
>> >> the
>> >> > system VMS to running state. Will it give me the option to destroy?
>> >> If so
>> >> > what would be the database relation?
>> >> >
>> >> > Thanks and regards
>> >> >
>> >> > Asanka
>> >> >
>> >> > On 15 Aug 2017 6:42 am, "Asanka Gunasekara"
>> >> wrote:
>> >> >
>> >> >> Hi Dag, I deleted both the system VMs and from the cloudstack it
>> >> says
>> >> >> starting but I dont see the the VM been generated, now its since
>> >> more than
>> >> >> 12 houres
>> >> >>
>> >> >> Thanks and Regards
>> >> >>
>> >> >> Asanka
>> >> >>
>> >> >
>> >> Dag.Sonstebo@shapeblue.com
>> >> www.shapeblue.com
>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> @shapeblue
>> >>
>> >>
>> >>
>> >> > On 10 August 2017 at 21:47, Asanka Gunasekara wrote:
>> >> >>
>> >> >>> Thank you Dag,
>> >> >>>
>> >> >>>
>> >> >>> On 10 Aug 2017 3:09 am, "Dag Sonstebo"
>> >> Dag.Sonstebo@shapeblue.com>
>> >> >>> wrote:
>> >> >>>
>> >> >>> Sure, let us know how you get on. The fact that the previous ssvm
>> >> check
>> >> >>> showed up with 172.17.101.1 was probably down to the wrong “host”
>> >> global
>> >> >>> setting – since the SSVM didn’t know where to contact management
>> >> I would
>> >> >>> guess it used a default override.
>> >> >>>
>> >> >>> Regards,
>> >> >>> Dag Sonstebo
>> >> >>> Cloud Architect
>> >> >>> ShapeBlue
>> >> >>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
>> >> >>> http://www.shapeblue.com |
>> >> >>> Twitter:@ShapeBlue
>> >> >>>
>> >> >>>
>> >> >>> On 09/08/2017, 17:54, "Asanka Gunasekara"
>> >> wrote:
>> >> >>>
>> >> >>> Hi Dag, pleas give me few days as I am on an implementation
>> >> visit to
>> >> >>> a
>> >> >>> remote site. But below are some of the test I performed
>> >> before.
>> >> >>>
>> >> >>> 1. Ping from ssvm to NFS is possible
>> >> >>> 2. Manually mounting NFS to /tmp/secondary is possible
>> >> without any
>> >> >>> Issy
>> >> >>>
>> >> >>> From the previous run of the ssvm check it is looking for a
>> >> serve IP
>> >> >>> 172.17.101.1. Where registered NFS share is 172.17.101.253
>> >> >>>
>> >> >>> I will run the check again on the first chance I get
>> >> >>>
>> >> >>> Thank you and best regards
>> >> >>>
>> >> >>> Asanka
>> >> >>>
>> >> >>>
>> >> >>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo"
>> >> Dag.Sonstebo@shapeblue.com>
>> >> >>> wrote:
>> >> >>>
>> >> >>> OK , can you post up the results of the ssvm check again?
>> >> >>>
>> >> >>> As suggested previously on this thread – can you try to
>> >> >>> 1) Ping the NFS server from the SSVM (SSVM check does this as
>> >> well)
>> >> >>> – if
>> >> >>> this doesn’t work then you have a networking issue.
>> >> >>> 2) Depending on ping - manually mount the secondary NFS share
>> >> on
>> >> >>> your SSVM.
>> >> >>> If this doesn’t work then you need to investigate the logs at
>> >> the
>> >> >>> NFS end
>> >> >>> to see why the NFS handshake fails.
>> >> >>>
>> >> >>> Regards,
>> >> >>> Dag Sonstebo
>> >> >>> Cloud Architect
>> >> >>> ShapeBlue
>> >> >>>
>> >> >>> On 08/08/2017, 19:14, "Asanka Gunasekara"
>> >> wrote:
>> >> >>>
>> >> >>> 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
>> >> >>>
>> >> >>>
>> >> >>> Dag.Sonstebo@shapeblue.com
>> >> >>> www.shapeblue.com
>> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> >>> @shapeblue
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> Dag.Sonstebo@shapeblue.com
>> >> >>> www.shapeblue.com
>> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> >>> @shapeblue
>> >> >>>
>> >> >>>
>> >> >>>
>> >> >>> On 8 August 2017 at 23:33, Asanka Gunasekara
>> >> wrote:
>> >> >>>
>> >> >>> > 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_s
>> >> >>> ubtree_check)
>> >> >>> > [root@share ~]#
>> >> >>> >
>> >> >>> >
>> >> >>> > On 8 August 2017 at 17:06, Dag Sonstebo
>> >> >>> Dag.Sonstebo@shapeblue.com>
>> >> >>> > 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"
>> >> asanka@nimbus.lk>
>> >> >>> 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.Sonstebo@shapeblue.com
>> >> >>> >> www.shapeblue.com
>> >> >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> >>> >> @shapeblue
>> >> >>> >>
>> >> >>> >>
>> >> >>> >>
>> >> >>> >> On 8 August 2017 at 14:48, Asanka Gunasekara
>> >> >>> asanka@nimbus.lk>
>> >> >>> wrote:
>> >> >>> >>
>> >> >>> >> > Thanks Makrand
>> >> >>> >> >
>> >> >>> >> > On 8 August 2017 at 14:42, Makrand
>> >> >>> makrandsanap@gmail.com>
>> >> >>> 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
>> >> >>> >> asanka@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.Sonstebo@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"
>> >> >>> 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.Sonstebo@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.green@gmail.com
>> >> >>> >>
>> >> >>> >> >> to:
>> >> >>> >> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >>> >> >> >>
>> >> >>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka
>> >> Gunasekara
>> >> >>> asanka@nimbus.lk
>> >> >>> >> >>
>> >> >>> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Thank you, Rodrigo
Best Regards
Asanka
On 15 August 2017 at 23:04, Rodrigo Baldasso <ro...@loophost.com.br>
wrote:
> Put the zone in maitenance mode, that will not auto create the ssvm's.
>
> - - - - - - - - - - - - - - - - - - -
>
> Rodrigo Baldasso - LHOST
>
> (51) 9 8419-9861
> - - - - - - - - - - - - - - - - - - -
> On 15/08/2017 14:00:45, Asanka Gunasekara <as...@nimbus.lk> wrote:
> Hi Dag, restart did not work but updating the tables initiate the
> recreation of the system VMs. But it does not give me the chance to restart
> cloudstack server, as soon as destroy the VMs it starts the VM recreation.
> Is there a way to stop this behaviour
>
> Thanks and Regards
>
> Asanka
>
> On 15 August 2017 at 14:19, Asanka Gunasekara wrote:
>
> > Thank you Dag
> >
> > Best Regards
> >
> > Asanka
> >
> > On 15 August 2017 at 13:18, Dag Sonstebo
> > wrote:
> >
> >> Hi Asanka,
> >>
> >> Maybe give you management server a reboot first of all.
> >>
> >> If this fails then yes we sometimes set status to stopped or destroyed
> in
> >> the DB – you also need to set the removed date and last update date.
> >>
> >> Regards,
> >> Dag Sonstebo
> >> Cloud Architect
> >> ShapeBlue
> >>
> >> On 15/08/2017, 07:07, "Asanka Gunasekara" wrote:
> >>
> >> Hi Guys, what would happen if i change the column in the table
> >> VM_instance,
> >> to Destroyed or running
> >>
> >> :(
> >>
> >> On 15 Aug 2017 8:28 am, "Asanka Gunasekara" wrote:
> >>
> >> > Hi Guys, when a system VM is in start state in ui, it does not give
> >> any
> >> > option to delete stop start etc. What if it to change db entry of
> >> the
> >> > system VMS to running state. Will it give me the option to destroy?
> >> If so
> >> > what would be the database relation?
> >> >
> >> > Thanks and regards
> >> >
> >> > Asanka
> >> >
> >> > On 15 Aug 2017 6:42 am, "Asanka Gunasekara"
> >> wrote:
> >> >
> >> >> Hi Dag, I deleted both the system VMs and from the cloudstack it
> >> says
> >> >> starting but I dont see the the VM been generated, now its since
> >> more than
> >> >> 12 houres
> >> >>
> >> >> Thanks and Regards
> >> >>
> >> >> Asanka
> >> >>
> >> >
> >> Dag.Sonstebo@shapeblue.com
> >> www.shapeblue.com
> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> @shapeblue
> >>
> >>
> >>
> >> > On 10 August 2017 at 21:47, Asanka Gunasekara wrote:
> >> >>
> >> >>> Thank you Dag,
> >> >>>
> >> >>>
> >> >>> On 10 Aug 2017 3:09 am, "Dag Sonstebo"
> >> Dag.Sonstebo@shapeblue.com>
> >> >>> wrote:
> >> >>>
> >> >>> Sure, let us know how you get on. The fact that the previous ssvm
> >> check
> >> >>> showed up with 172.17.101.1 was probably down to the wrong “host”
> >> global
> >> >>> setting – since the SSVM didn’t know where to contact management
> >> I would
> >> >>> guess it used a default override.
> >> >>>
> >> >>> Regards,
> >> >>> Dag Sonstebo
> >> >>> Cloud Architect
> >> >>> ShapeBlue
> >> >>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
> >> >>> http://www.shapeblue.com |
> >> >>> Twitter:@ShapeBlue
> >> >>>
> >> >>>
> >> >>> On 09/08/2017, 17:54, "Asanka Gunasekara"
> >> wrote:
> >> >>>
> >> >>> Hi Dag, pleas give me few days as I am on an implementation
> >> visit to
> >> >>> a
> >> >>> remote site. But below are some of the test I performed
> >> before.
> >> >>>
> >> >>> 1. Ping from ssvm to NFS is possible
> >> >>> 2. Manually mounting NFS to /tmp/secondary is possible
> >> without any
> >> >>> Issy
> >> >>>
> >> >>> From the previous run of the ssvm check it is looking for a
> >> serve IP
> >> >>> 172.17.101.1. Where registered NFS share is 172.17.101.253
> >> >>>
> >> >>> I will run the check again on the first chance I get
> >> >>>
> >> >>> Thank you and best regards
> >> >>>
> >> >>> Asanka
> >> >>>
> >> >>>
> >> >>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo"
> >> Dag.Sonstebo@shapeblue.com>
> >> >>> wrote:
> >> >>>
> >> >>> OK , can you post up the results of the ssvm check again?
> >> >>>
> >> >>> As suggested previously on this thread – can you try to
> >> >>> 1) Ping the NFS server from the SSVM (SSVM check does this as
> >> well)
> >> >>> – if
> >> >>> this doesn’t work then you have a networking issue.
> >> >>> 2) Depending on ping - manually mount the secondary NFS share
> >> on
> >> >>> your SSVM.
> >> >>> If this doesn’t work then you need to investigate the logs at
> >> the
> >> >>> NFS end
> >> >>> to see why the NFS handshake fails.
> >> >>>
> >> >>> Regards,
> >> >>> Dag Sonstebo
> >> >>> Cloud Architect
> >> >>> ShapeBlue
> >> >>>
> >> >>> On 08/08/2017, 19:14, "Asanka Gunasekara"
> >> wrote:
> >> >>>
> >> >>> 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
> >> >>>
> >> >>>
> >> >>> Dag.Sonstebo@shapeblue.com
> >> >>> www.shapeblue.com
> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> >>> @shapeblue
> >> >>>
> >> >>>
> >> >>>
> >> >>>
> >> >>> Dag.Sonstebo@shapeblue.com
> >> >>> www.shapeblue.com
> >> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> >>> @shapeblue
> >> >>>
> >> >>>
> >> >>>
> >> >>> On 8 August 2017 at 23:33, Asanka Gunasekara
> >> wrote:
> >> >>>
> >> >>> > 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_s
> >> >>> ubtree_check)
> >> >>> > [root@share ~]#
> >> >>> >
> >> >>> >
> >> >>> > On 8 August 2017 at 17:06, Dag Sonstebo
> >> >>> Dag.Sonstebo@shapeblue.com>
> >> >>> > 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"
> >> asanka@nimbus.lk>
> >> >>> 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.Sonstebo@shapeblue.com
> >> >>> >> www.shapeblue.com
> >> >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> >>> >> @shapeblue
> >> >>> >>
> >> >>> >>
> >> >>> >>
> >> >>> >> On 8 August 2017 at 14:48, Asanka Gunasekara
> >> >>> asanka@nimbus.lk>
> >> >>> wrote:
> >> >>> >>
> >> >>> >> > Thanks Makrand
> >> >>> >> >
> >> >>> >> > On 8 August 2017 at 14:42, Makrand
> >> >>> makrandsanap@gmail.com>
> >> >>> 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
> >> >>> >> asanka@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.Sonstebo@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"
> >> >>> 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.Sonstebo@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.green@gmail.com
> >> >>> >>
> >> >>> >> >> to:
> >> >>> >> >> >> eric.lee.green@gmail.com>> wrote:
> >> >>> >> >> >>
> >> >>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka
> >> Gunasekara
> >> >>> asanka@nimbus.lk
> >> >>> >> >>
> >> >>> >> >> >> asanka@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
Posted by Rodrigo Baldasso <ro...@loophost.com.br>.
Put the zone in maitenance mode, that will not auto create the ssvm's.
- - - - - - - - - - - - - - - - - - -
Rodrigo Baldasso - LHOST
(51) 9 8419-9861
- - - - - - - - - - - - - - - - - - -
On 15/08/2017 14:00:45, Asanka Gunasekara <as...@nimbus.lk> wrote:
Hi Dag, restart did not work but updating the tables initiate the
recreation of the system VMs. But it does not give me the chance to restart
cloudstack server, as soon as destroy the VMs it starts the VM recreation.
Is there a way to stop this behaviour
Thanks and Regards
Asanka
On 15 August 2017 at 14:19, Asanka Gunasekara wrote:
> Thank you Dag
>
> Best Regards
>
> Asanka
>
> On 15 August 2017 at 13:18, Dag Sonstebo
> wrote:
>
>> Hi Asanka,
>>
>> Maybe give you management server a reboot first of all.
>>
>> If this fails then yes we sometimes set status to stopped or destroyed in
>> the DB – you also need to set the removed date and last update date.
>>
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>>
>> On 15/08/2017, 07:07, "Asanka Gunasekara" wrote:
>>
>> Hi Guys, what would happen if i change the column in the table
>> VM_instance,
>> to Destroyed or running
>>
>> :(
>>
>> On 15 Aug 2017 8:28 am, "Asanka Gunasekara" wrote:
>>
>> > Hi Guys, when a system VM is in start state in ui, it does not give
>> any
>> > option to delete stop start etc. What if it to change db entry of
>> the
>> > system VMS to running state. Will it give me the option to destroy?
>> If so
>> > what would be the database relation?
>> >
>> > Thanks and regards
>> >
>> > Asanka
>> >
>> > On 15 Aug 2017 6:42 am, "Asanka Gunasekara"
>> wrote:
>> >
>> >> Hi Dag, I deleted both the system VMs and from the cloudstack it
>> says
>> >> starting but I dont see the the VM been generated, now its since
>> more than
>> >> 12 houres
>> >>
>> >> Thanks and Regards
>> >>
>> >> Asanka
>> >>
>> >
>> Dag.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> > On 10 August 2017 at 21:47, Asanka Gunasekara wrote:
>> >>
>> >>> Thank you Dag,
>> >>>
>> >>>
>> >>> On 10 Aug 2017 3:09 am, "Dag Sonstebo"
>> Dag.Sonstebo@shapeblue.com>
>> >>> wrote:
>> >>>
>> >>> Sure, let us know how you get on. The fact that the previous ssvm
>> check
>> >>> showed up with 172.17.101.1 was probably down to the wrong “host”
>> global
>> >>> setting – since the SSVM didn’t know where to contact management
>> I would
>> >>> guess it used a default override.
>> >>>
>> >>> Regards,
>> >>> Dag Sonstebo
>> >>> Cloud Architect
>> >>> ShapeBlue
>> >>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
>> >>> http://www.shapeblue.com |
>> >>> Twitter:@ShapeBlue
>> >>>
>> >>>
>> >>> On 09/08/2017, 17:54, "Asanka Gunasekara"
>> wrote:
>> >>>
>> >>> Hi Dag, pleas give me few days as I am on an implementation
>> visit to
>> >>> a
>> >>> remote site. But below are some of the test I performed
>> before.
>> >>>
>> >>> 1. Ping from ssvm to NFS is possible
>> >>> 2. Manually mounting NFS to /tmp/secondary is possible
>> without any
>> >>> Issy
>> >>>
>> >>> From the previous run of the ssvm check it is looking for a
>> serve IP
>> >>> 172.17.101.1. Where registered NFS share is 172.17.101.253
>> >>>
>> >>> I will run the check again on the first chance I get
>> >>>
>> >>> Thank you and best regards
>> >>>
>> >>> Asanka
>> >>>
>> >>>
>> >>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo"
>> Dag.Sonstebo@shapeblue.com>
>> >>> wrote:
>> >>>
>> >>> OK , can you post up the results of the ssvm check again?
>> >>>
>> >>> As suggested previously on this thread – can you try to
>> >>> 1) Ping the NFS server from the SSVM (SSVM check does this as
>> well)
>> >>> – if
>> >>> this doesn’t work then you have a networking issue.
>> >>> 2) Depending on ping - manually mount the secondary NFS share
>> on
>> >>> your SSVM.
>> >>> If this doesn’t work then you need to investigate the logs at
>> the
>> >>> NFS end
>> >>> to see why the NFS handshake fails.
>> >>>
>> >>> Regards,
>> >>> Dag Sonstebo
>> >>> Cloud Architect
>> >>> ShapeBlue
>> >>>
>> >>> On 08/08/2017, 19:14, "Asanka Gunasekara"
>> wrote:
>> >>>
>> >>> 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
>> >>>
>> >>>
>> >>> Dag.Sonstebo@shapeblue.com
>> >>> www.shapeblue.com
>> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >>> @shapeblue
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> Dag.Sonstebo@shapeblue.com
>> >>> www.shapeblue.com
>> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >>> @shapeblue
>> >>>
>> >>>
>> >>>
>> >>> On 8 August 2017 at 23:33, Asanka Gunasekara
>> wrote:
>> >>>
>> >>> > 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_s
>> >>> ubtree_check)
>> >>> > [root@share ~]#
>> >>> >
>> >>> >
>> >>> > On 8 August 2017 at 17:06, Dag Sonstebo
>> >>> Dag.Sonstebo@shapeblue.com>
>> >>> > 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"
>> asanka@nimbus.lk>
>> >>> 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.Sonstebo@shapeblue.com
>> >>> >> www.shapeblue.com
>> >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >>> >> @shapeblue
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On 8 August 2017 at 14:48, Asanka Gunasekara
>> >>> asanka@nimbus.lk>
>> >>> wrote:
>> >>> >>
>> >>> >> > Thanks Makrand
>> >>> >> >
>> >>> >> > On 8 August 2017 at 14:42, Makrand
>> >>> makrandsanap@gmail.com>
>> >>> 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
>> >>> >> asanka@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.Sonstebo@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"
>> >>> 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.Sonstebo@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.green@gmail.com
>> >>> >>
>> >>> >> >> to:
>> >>> >> >> >> eric.lee.green@gmail.com>> wrote:
>> >>> >> >> >>
>> >>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka
>> Gunasekara
>> >>> asanka@nimbus.lk
>> >>> >> >>
>> >>> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Dag, restart did not work but updating the tables initiate the
recreation of the system VMs. But it does not give me the chance to restart
cloudstack server, as soon as destroy the VMs it starts the VM recreation.
Is there a way to stop this behaviour
Thanks and Regards
Asanka
On 15 August 2017 at 14:19, Asanka Gunasekara <as...@nimbus.lk> wrote:
> Thank you Dag
>
> Best Regards
>
> Asanka
>
> On 15 August 2017 at 13:18, Dag Sonstebo <Da...@shapeblue.com>
> wrote:
>
>> Hi Asanka,
>>
>> Maybe give you management server a reboot first of all.
>>
>> If this fails then yes we sometimes set status to stopped or destroyed in
>> the DB – you also need to set the removed date and last update date.
>>
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>>
>> On 15/08/2017, 07:07, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>
>> Hi Guys, what would happen if i change the column in the table
>> VM_instance,
>> to Destroyed or running
>>
>> :(
>>
>> On 15 Aug 2017 8:28 am, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>
>> > Hi Guys, when a system VM is in start state in ui, it does not give
>> any
>> > option to delete stop start etc. What if it to change db entry of
>> the
>> > system VMS to running state. Will it give me the option to destroy?
>> If so
>> > what would be the database relation?
>> >
>> > Thanks and regards
>> >
>> > Asanka
>> >
>> > On 15 Aug 2017 6:42 am, "Asanka Gunasekara" <as...@nimbus.lk>
>> wrote:
>> >
>> >> Hi Dag, I deleted both the system VMs and from the cloudstack it
>> says
>> >> starting but I dont see the the VM been generated, now its since
>> more than
>> >> 12 houres
>> >>
>> >> Thanks and Regards
>> >>
>> >> Asanka
>> >>
>> >
>> Dag.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> > On 10 August 2017 at 21:47, Asanka Gunasekara <as...@nimbus.lk> wrote:
>> >>
>> >>> Thank you Dag,
>> >>>
>> >>>
>> >>> On 10 Aug 2017 3:09 am, "Dag Sonstebo" <
>> Dag.Sonstebo@shapeblue.com>
>> >>> wrote:
>> >>>
>> >>> Sure, let us know how you get on. The fact that the previous ssvm
>> check
>> >>> showed up with 172.17.101.1 was probably down to the wrong “host”
>> global
>> >>> setting – since the SSVM didn’t know where to contact management
>> I would
>> >>> guess it used a default override.
>> >>>
>> >>> Regards,
>> >>> Dag Sonstebo
>> >>> Cloud Architect
>> >>> ShapeBlue
>> >>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
>> >>> http://www.shapeblue.com <http://www.shapeblue.com/> |
>> >>> Twitter:@ShapeBlue <https://twitter.com/#!/shapeblue>
>> >>>
>> >>>
>> >>> On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk>
>> wrote:
>> >>>
>> >>> Hi Dag, pleas give me few days as I am on an implementation
>> visit to
>> >>> a
>> >>> remote site. But below are some of the test I performed
>> before.
>> >>>
>> >>> 1. Ping from ssvm to NFS is possible
>> >>> 2. Manually mounting NFS to /tmp/secondary is possible
>> without any
>> >>> Issy
>> >>>
>> >>> From the previous run of the ssvm check it is looking for a
>> serve IP
>> >>> 172.17.101.1. Where registered NFS share is 172.17.101.253
>> >>>
>> >>> I will run the check again on the first chance I get
>> >>>
>> >>> Thank you and best regards
>> >>>
>> >>> Asanka
>> >>>
>> >>>
>> >>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <
>> Dag.Sonstebo@shapeblue.com>
>> >>> wrote:
>> >>>
>> >>> OK , can you post up the results of the ssvm check again?
>> >>>
>> >>> As suggested previously on this thread – can you try to
>> >>> 1) Ping the NFS server from the SSVM (SSVM check does this as
>> well)
>> >>> – if
>> >>> this doesn’t work then you have a networking issue.
>> >>> 2) Depending on ping - manually mount the secondary NFS share
>> on
>> >>> your SSVM.
>> >>> If this doesn’t work then you need to investigate the logs at
>> the
>> >>> NFS end
>> >>> to see why the NFS handshake fails.
>> >>>
>> >>> Regards,
>> >>> Dag Sonstebo
>> >>> Cloud Architect
>> >>> ShapeBlue
>> >>>
>> >>> On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk>
>> wrote:
>> >>>
>> >>> 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
>> >>>
>> >>>
>> >>> Dag.Sonstebo@shapeblue.com
>> >>> www.shapeblue.com
>> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >>> @shapeblue
>> >>>
>> >>>
>> >>>
>> >>>
>> >>> Dag.Sonstebo@shapeblue.com
>> >>> www.shapeblue.com
>> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >>> @shapeblue
>> >>>
>> >>>
>> >>>
>> >>> On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk>
>> wrote:
>> >>>
>> >>> > 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_s
>> >>> ubtree_check)
>> >>> > [root@share ~]#
>> >>> >
>> >>> >
>> >>> > On 8 August 2017 at 17:06, Dag Sonstebo <
>> >>> Dag.Sonstebo@shapeblue.com>
>> >>> > 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" <
>> asanka@nimbus.lk>
>> >>> 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.Sonstebo@shapeblue.com
>> >>> >> www.shapeblue.com
>> >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >>> >> @shapeblue
>> >>> >>
>> >>> >>
>> >>> >>
>> >>> >> On 8 August 2017 at 14:48, Asanka Gunasekara <
>> >>> asanka@nimbus.lk>
>> >>> wrote:
>> >>> >>
>> >>> >> > Thanks Makrand
>> >>> >> >
>> >>> >> > On 8 August 2017 at 14:42, Makrand <
>> >>> makrandsanap@gmail.com>
>> >>> 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 <
>> >>> >> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>> >>> >> >> >> Reply-To: "users@cloudstack.apache.org" <
>> >>> >> users@cloudstack.apache.org>
>> >>> >> >> >> Date: Tuesday, 8 August 2017 at 09:27
>> >>> >> >> >> To: "users@cloudstack.apache.org" <
>> >>> 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.Sonstebo@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.green@gmail.com
>> >>> >> <mail
>> >>> >> >> to:
>> >>> >> >> >> eric.lee.green@gmail.com>> wrote:
>> >>> >> >> >>
>> >>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka
>> Gunasekara <
>> >>> asanka@nimbus.lk
>> >>> >> >> <mailto:
>> >>> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Thank you Dag
Best Regards
Asanka
On 15 August 2017 at 13:18, Dag Sonstebo <Da...@shapeblue.com> wrote:
> Hi Asanka,
>
> Maybe give you management server a reboot first of all.
>
> If this fails then yes we sometimes set status to stopped or destroyed in
> the DB – you also need to set the removed date and last update date.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 15/08/2017, 07:07, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>
> Hi Guys, what would happen if i change the column in the table
> VM_instance,
> to Destroyed or running
>
> :(
>
> On 15 Aug 2017 8:28 am, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>
> > Hi Guys, when a system VM is in start state in ui, it does not give
> any
> > option to delete stop start etc. What if it to change db entry of the
> > system VMS to running state. Will it give me the option to destroy?
> If so
> > what would be the database relation?
> >
> > Thanks and regards
> >
> > Asanka
> >
> > On 15 Aug 2017 6:42 am, "Asanka Gunasekara" <as...@nimbus.lk>
> wrote:
> >
> >> Hi Dag, I deleted both the system VMs and from the cloudstack it
> says
> >> starting but I dont see the the VM been generated, now its since
> more than
> >> 12 houres
> >>
> >> Thanks and Regards
> >>
> >> Asanka
> >>
> >
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> > On 10 August 2017 at 21:47, Asanka Gunasekara <as...@nimbus.lk> wrote:
> >>
> >>> Thank you Dag,
> >>>
> >>>
> >>> On 10 Aug 2017 3:09 am, "Dag Sonstebo" <Dag.Sonstebo@shapeblue.com
> >
> >>> wrote:
> >>>
> >>> Sure, let us know how you get on. The fact that the previous ssvm
> check
> >>> showed up with 172.17.101.1 was probably down to the wrong “host”
> global
> >>> setting – since the SSVM didn’t know where to contact management I
> would
> >>> guess it used a default override.
> >>>
> >>> Regards,
> >>> Dag Sonstebo
> >>> Cloud Architect
> >>> ShapeBlue
> >>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
> >>> http://www.shapeblue.com <http://www.shapeblue.com/> |
> >>> Twitter:@ShapeBlue <https://twitter.com/#!/shapeblue>
> >>>
> >>>
> >>> On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk>
> wrote:
> >>>
> >>> Hi Dag, pleas give me few days as I am on an implementation
> visit to
> >>> a
> >>> remote site. But below are some of the test I performed before.
> >>>
> >>> 1. Ping from ssvm to NFS is possible
> >>> 2. Manually mounting NFS to /tmp/secondary is possible without
> any
> >>> Issy
> >>>
> >>> From the previous run of the ssvm check it is looking for a
> serve IP
> >>> 172.17.101.1. Where registered NFS share is 172.17.101.253
> >>>
> >>> I will run the check again on the first chance I get
> >>>
> >>> Thank you and best regards
> >>>
> >>> Asanka
> >>>
> >>>
> >>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <
> Dag.Sonstebo@shapeblue.com>
> >>> wrote:
> >>>
> >>> OK , can you post up the results of the ssvm check again?
> >>>
> >>> As suggested previously on this thread – can you try to
> >>> 1) Ping the NFS server from the SSVM (SSVM check does this as
> well)
> >>> – if
> >>> this doesn’t work then you have a networking issue.
> >>> 2) Depending on ping - manually mount the secondary NFS share
> on
> >>> your SSVM.
> >>> If this doesn’t work then you need to investigate the logs at
> the
> >>> NFS end
> >>> to see why the NFS handshake fails.
> >>>
> >>> Regards,
> >>> Dag Sonstebo
> >>> Cloud Architect
> >>> ShapeBlue
> >>>
> >>> On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk>
> wrote:
> >>>
> >>> 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
> >>>
> >>>
> >>> Dag.Sonstebo@shapeblue.com
> >>> www.shapeblue.com
> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >>> @shapeblue
> >>>
> >>>
> >>>
> >>>
> >>> Dag.Sonstebo@shapeblue.com
> >>> www.shapeblue.com
> >>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >>> @shapeblue
> >>>
> >>>
> >>>
> >>> On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk>
> wrote:
> >>>
> >>> > 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_s
> >>> ubtree_check)
> >>> > [root@share ~]#
> >>> >
> >>> >
> >>> > On 8 August 2017 at 17:06, Dag Sonstebo <
> >>> Dag.Sonstebo@shapeblue.com>
> >>> > 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" <
> asanka@nimbus.lk>
> >>> 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.Sonstebo@shapeblue.com
> >>> >> www.shapeblue.com
> >>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >>> >> @shapeblue
> >>> >>
> >>> >>
> >>> >>
> >>> >> On 8 August 2017 at 14:48, Asanka Gunasekara <
> >>> asanka@nimbus.lk>
> >>> wrote:
> >>> >>
> >>> >> > Thanks Makrand
> >>> >> >
> >>> >> > On 8 August 2017 at 14:42, Makrand <
> >>> makrandsanap@gmail.com>
> >>> 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 <
> >>> >> asanka@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.Sonstebo@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 <as...@nimbus.lk>
> >>> >> >> >> Reply-To: "users@cloudstack.apache.org" <
> >>> >> users@cloudstack.apache.org>
> >>> >> >> >> Date: Tuesday, 8 August 2017 at 09:27
> >>> >> >> >> To: "users@cloudstack.apache.org" <
> >>> 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.Sonstebo@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.green@gmail.com
> >>> >> <mail
> >>> >> >> to:
> >>> >> >> >> eric.lee.green@gmail.com>> wrote:
> >>> >> >> >>
> >>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara
> <
> >>> asanka@nimbus.lk
> >>> >> >> <mailto:
> >>> >> >> >> asanka@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
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Hi Asanka,
Maybe give you management server a reboot first of all.
If this fails then yes we sometimes set status to stopped or destroyed in the DB – you also need to set the removed date and last update date.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 15/08/2017, 07:07, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
Hi Guys, what would happen if i change the column in the table VM_instance,
to Destroyed or running
:(
On 15 Aug 2017 8:28 am, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
> Hi Guys, when a system VM is in start state in ui, it does not give any
> option to delete stop start etc. What if it to change db entry of the
> system VMS to running state. Will it give me the option to destroy? If so
> what would be the database relation?
>
> Thanks and regards
>
> Asanka
>
> On 15 Aug 2017 6:42 am, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>
>> Hi Dag, I deleted both the system VMs and from the cloudstack it says
>> starting but I dont see the the VM been generated, now its since more than
>> 12 houres
>>
>> Thanks and Regards
>>
>> Asanka
>>
>
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
> On 10 August 2017 at 21:47, Asanka Gunasekara <as...@nimbus.lk> wrote:
>>
>>> Thank you Dag,
>>>
>>>
>>> On 10 Aug 2017 3:09 am, "Dag Sonstebo" <Da...@shapeblue.com>
>>> wrote:
>>>
>>> Sure, let us know how you get on. The fact that the previous ssvm check
>>> showed up with 172.17.101.1 was probably down to the wrong “host” global
>>> setting – since the SSVM didn’t know where to contact management I would
>>> guess it used a default override.
>>>
>>> Regards,
>>> Dag Sonstebo
>>> Cloud Architect
>>> ShapeBlue
>>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
>>> http://www.shapeblue.com <http://www.shapeblue.com/> |
>>> Twitter:@ShapeBlue <https://twitter.com/#!/shapeblue>
>>>
>>>
>>> On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>>
>>> Hi Dag, pleas give me few days as I am on an implementation visit to
>>> a
>>> remote site. But below are some of the test I performed before.
>>>
>>> 1. Ping from ssvm to NFS is possible
>>> 2. Manually mounting NFS to /tmp/secondary is possible without any
>>> Issy
>>>
>>> From the previous run of the ssvm check it is looking for a serve IP
>>> 172.17.101.1. Where registered NFS share is 172.17.101.253
>>>
>>> I will run the check again on the first chance I get
>>>
>>> Thank you and best regards
>>>
>>> Asanka
>>>
>>>
>>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <Da...@shapeblue.com>
>>> wrote:
>>>
>>> OK , can you post up the results of the ssvm check again?
>>>
>>> As suggested previously on this thread – can you try to
>>> 1) Ping the NFS server from the SSVM (SSVM check does this as well)
>>> – if
>>> this doesn’t work then you have a networking issue.
>>> 2) Depending on ping - manually mount the secondary NFS share on
>>> your SSVM.
>>> If this doesn’t work then you need to investigate the logs at the
>>> NFS end
>>> to see why the NFS handshake fails.
>>>
>>> Regards,
>>> Dag Sonstebo
>>> Cloud Architect
>>> ShapeBlue
>>>
>>> On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>>
>>> 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
>>>
>>>
>>> Dag.Sonstebo@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> @shapeblue
>>>
>>>
>>>
>>>
>>> Dag.Sonstebo@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> @shapeblue
>>>
>>>
>>>
>>> On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
>>>
>>> > 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_s
>>> ubtree_check)
>>> > [root@share ~]#
>>> >
>>> >
>>> > On 8 August 2017 at 17:06, Dag Sonstebo <
>>> Dag.Sonstebo@shapeblue.com>
>>> > 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" <as...@nimbus.lk>
>>> 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.Sonstebo@shapeblue.com
>>> >> www.shapeblue.com
>>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> >> @shapeblue
>>> >>
>>> >>
>>> >>
>>> >> On 8 August 2017 at 14:48, Asanka Gunasekara <
>>> asanka@nimbus.lk>
>>> wrote:
>>> >>
>>> >> > Thanks Makrand
>>> >> >
>>> >> > On 8 August 2017 at 14:42, Makrand <
>>> makrandsanap@gmail.com>
>>> 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 <
>>> >> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>>> >> >> >> Reply-To: "users@cloudstack.apache.org" <
>>> >> users@cloudstack.apache.org>
>>> >> >> >> Date: Tuesday, 8 August 2017 at 09:27
>>> >> >> >> To: "users@cloudstack.apache.org" <
>>> 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.Sonstebo@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.green@gmail.com
>>> >> <mail
>>> >> >> to:
>>> >> >> >> eric.lee.green@gmail.com>> wrote:
>>> >> >> >>
>>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <
>>> asanka@nimbus.lk
>>> >> >> <mailto:
>>> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Guys, what would happen if i change the column in the table VM_instance,
to Destroyed or running
:(
On 15 Aug 2017 8:28 am, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
> Hi Guys, when a system VM is in start state in ui, it does not give any
> option to delete stop start etc. What if it to change db entry of the
> system VMS to running state. Will it give me the option to destroy? If so
> what would be the database relation?
>
> Thanks and regards
>
> Asanka
>
> On 15 Aug 2017 6:42 am, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>
>> Hi Dag, I deleted both the system VMs and from the cloudstack it says
>> starting but I dont see the the VM been generated, now its since more than
>> 12 houres
>>
>> Thanks and Regards
>>
>> Asanka
>>
>> On 10 August 2017 at 21:47, Asanka Gunasekara <as...@nimbus.lk> wrote:
>>
>>> Thank you Dag,
>>>
>>>
>>> On 10 Aug 2017 3:09 am, "Dag Sonstebo" <Da...@shapeblue.com>
>>> wrote:
>>>
>>> Sure, let us know how you get on. The fact that the previous ssvm check
>>> showed up with 172.17.101.1 was probably down to the wrong “host” global
>>> setting – since the SSVM didn’t know where to contact management I would
>>> guess it used a default override.
>>>
>>> Regards,
>>> Dag Sonstebo
>>> Cloud Architect
>>> ShapeBlue
>>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
>>> http://www.shapeblue.com <http://www.shapeblue.com/> |
>>> Twitter:@ShapeBlue <https://twitter.com/#!/shapeblue>
>>>
>>>
>>> On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>>
>>> Hi Dag, pleas give me few days as I am on an implementation visit to
>>> a
>>> remote site. But below are some of the test I performed before.
>>>
>>> 1. Ping from ssvm to NFS is possible
>>> 2. Manually mounting NFS to /tmp/secondary is possible without any
>>> Issy
>>>
>>> From the previous run of the ssvm check it is looking for a serve IP
>>> 172.17.101.1. Where registered NFS share is 172.17.101.253
>>>
>>> I will run the check again on the first chance I get
>>>
>>> Thank you and best regards
>>>
>>> Asanka
>>>
>>>
>>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <Da...@shapeblue.com>
>>> wrote:
>>>
>>> OK , can you post up the results of the ssvm check again?
>>>
>>> As suggested previously on this thread – can you try to
>>> 1) Ping the NFS server from the SSVM (SSVM check does this as well)
>>> – if
>>> this doesn’t work then you have a networking issue.
>>> 2) Depending on ping - manually mount the secondary NFS share on
>>> your SSVM.
>>> If this doesn’t work then you need to investigate the logs at the
>>> NFS end
>>> to see why the NFS handshake fails.
>>>
>>> Regards,
>>> Dag Sonstebo
>>> Cloud Architect
>>> ShapeBlue
>>>
>>> On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>>
>>> 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
>>>
>>>
>>> Dag.Sonstebo@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> @shapeblue
>>>
>>>
>>>
>>>
>>> Dag.Sonstebo@shapeblue.com
>>> www.shapeblue.com
>>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> @shapeblue
>>>
>>>
>>>
>>> On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
>>>
>>> > 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_s
>>> ubtree_check)
>>> > [root@share ~]#
>>> >
>>> >
>>> > On 8 August 2017 at 17:06, Dag Sonstebo <
>>> Dag.Sonstebo@shapeblue.com>
>>> > 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" <as...@nimbus.lk>
>>> 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.Sonstebo@shapeblue.com
>>> >> www.shapeblue.com
>>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>>> >> @shapeblue
>>> >>
>>> >>
>>> >>
>>> >> On 8 August 2017 at 14:48, Asanka Gunasekara <
>>> asanka@nimbus.lk>
>>> wrote:
>>> >>
>>> >> > Thanks Makrand
>>> >> >
>>> >> > On 8 August 2017 at 14:42, Makrand <
>>> makrandsanap@gmail.com>
>>> 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 <
>>> >> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>>> >> >> >> Reply-To: "users@cloudstack.apache.org" <
>>> >> users@cloudstack.apache.org>
>>> >> >> >> Date: Tuesday, 8 August 2017 at 09:27
>>> >> >> >> To: "users@cloudstack.apache.org" <
>>> 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.Sonstebo@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.green@gmail.com
>>> >> <mail
>>> >> >> to:
>>> >> >> >> eric.lee.green@gmail.com>> wrote:
>>> >> >> >>
>>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <
>>> asanka@nimbus.lk
>>> >> >> <mailto:
>>> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Guys, when a system VM is in start state in ui, it does not give any
option to delete stop start etc. What if it to change db entry of the
system VMS to running state. Will it give me the option to destroy? If so
what would be the database relation?
Thanks and regards
Asanka
On 15 Aug 2017 6:42 am, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
> Hi Dag, I deleted both the system VMs and from the cloudstack it says
> starting but I dont see the the VM been generated, now its since more than
> 12 houres
>
> Thanks and Regards
>
> Asanka
>
> On 10 August 2017 at 21:47, Asanka Gunasekara <as...@nimbus.lk> wrote:
>
>> Thank you Dag,
>>
>>
>> On 10 Aug 2017 3:09 am, "Dag Sonstebo" <Da...@shapeblue.com>
>> wrote:
>>
>> Sure, let us know how you get on. The fact that the previous ssvm check
>> showed up with 172.17.101.1 was probably down to the wrong “host” global
>> setting – since the SSVM didn’t know where to contact management I would
>> guess it used a default override.
>>
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
>> http://www.shapeblue.com <http://www.shapeblue.com/> | Twitter:@ShapeBlue
>> <https://twitter.com/#!/shapeblue>
>>
>>
>> On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>
>> Hi Dag, pleas give me few days as I am on an implementation visit to a
>> remote site. But below are some of the test I performed before.
>>
>> 1. Ping from ssvm to NFS is possible
>> 2. Manually mounting NFS to /tmp/secondary is possible without any
>> Issy
>>
>> From the previous run of the ssvm check it is looking for a serve IP
>> 172.17.101.1. Where registered NFS share is 172.17.101.253
>>
>> I will run the check again on the first chance I get
>>
>> Thank you and best regards
>>
>> Asanka
>>
>>
>> On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <Da...@shapeblue.com>
>> wrote:
>>
>> OK , can you post up the results of the ssvm check again?
>>
>> As suggested previously on this thread – can you try to
>> 1) Ping the NFS server from the SSVM (SSVM check does this as well) –
>> if
>> this doesn’t work then you have a networking issue.
>> 2) Depending on ping - manually mount the secondary NFS share on your
>> SSVM.
>> If this doesn’t work then you need to investigate the logs at the NFS
>> end
>> to see why the NFS handshake fails.
>>
>> Regards,
>> Dag Sonstebo
>> Cloud Architect
>> ShapeBlue
>>
>> On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>>
>> 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
>>
>>
>> Dag.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>>
>> Dag.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
>>
>> > 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_s
>> ubtree_check)
>> > [root@share ~]#
>> >
>> >
>> > On 8 August 2017 at 17:06, Dag Sonstebo <
>> Dag.Sonstebo@shapeblue.com>
>> > 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" <as...@nimbus.lk>
>> 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.Sonstebo@shapeblue.com
>> >> www.shapeblue.com
>> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> >> @shapeblue
>> >>
>> >>
>> >>
>> >> On 8 August 2017 at 14:48, Asanka Gunasekara <asanka@nimbus.lk
>> >
>> wrote:
>> >>
>> >> > Thanks Makrand
>> >> >
>> >> > On 8 August 2017 at 14:42, Makrand <
>> makrandsanap@gmail.com>
>> 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 <
>> >> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>> >> >> >> Reply-To: "users@cloudstack.apache.org" <
>> >> users@cloudstack.apache.org>
>> >> >> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> >> >> To: "users@cloudstack.apache.org" <
>> 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.Sonstebo@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.green@gmail.com
>> >> <mail
>> >> >> to:
>> >> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >> >>
>> >> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <
>> asanka@nimbus.lk
>> >> >> <mailto:
>> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Dag, I deleted both the system VMs and from the cloudstack it says
starting but I dont see the the VM been generated, now its since more than
12 houres
Thanks and Regards
Asanka
On 10 August 2017 at 21:47, Asanka Gunasekara <as...@nimbus.lk> wrote:
> Thank you Dag,
>
>
> On 10 Aug 2017 3:09 am, "Dag Sonstebo" <Da...@shapeblue.com> wrote:
>
> Sure, let us know how you get on. The fact that the previous ssvm check
> showed up with 172.17.101.1 was probably down to the wrong “host” global
> setting – since the SSVM didn’t know where to contact management I would
> guess it used a default override.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
> S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
> http://www.shapeblue.com <http://www.shapeblue.com/> | Twitter:@ShapeBlue
> <https://twitter.com/#!/shapeblue>
>
>
> On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>
> Hi Dag, pleas give me few days as I am on an implementation visit to a
> remote site. But below are some of the test I performed before.
>
> 1. Ping from ssvm to NFS is possible
> 2. Manually mounting NFS to /tmp/secondary is possible without any Issy
>
> From the previous run of the ssvm check it is looking for a serve IP
> 172.17.101.1. Where registered NFS share is 172.17.101.253
>
> I will run the check again on the first chance I get
>
> Thank you and best regards
>
> Asanka
>
>
> On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <Da...@shapeblue.com>
> wrote:
>
> OK , can you post up the results of the ssvm check again?
>
> As suggested previously on this thread – can you try to
> 1) Ping the NFS server from the SSVM (SSVM check does this as well) –
> if
> this doesn’t work then you have a networking issue.
> 2) Depending on ping - manually mount the secondary NFS share on your
> SSVM.
> If this doesn’t work then you need to investigate the logs at the NFS
> end
> to see why the NFS handshake fails.
>
> Regards,
> Dag Sonstebo
> Cloud Architect
> ShapeBlue
>
> On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
>
> 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
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
>
> Dag.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
>
> > 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_s
> ubtree_check)
> > [root@share ~]#
> >
> >
> > On 8 August 2017 at 17:06, Dag Sonstebo <
> Dag.Sonstebo@shapeblue.com>
> > 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" <as...@nimbus.lk>
> 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.Sonstebo@shapeblue.com
> >> www.shapeblue.com
> >> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> >> @shapeblue
> >>
> >>
> >>
> >> On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk>
> wrote:
> >>
> >> > Thanks Makrand
> >> >
> >> > On 8 August 2017 at 14:42, Makrand <
> makrandsanap@gmail.com>
> 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 <
> >> asanka@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.Sonstebo@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 <as...@nimbus.lk>
> >> >> >> Reply-To: "users@cloudstack.apache.org" <
> >> users@cloudstack.apache.org>
> >> >> >> Date: Tuesday, 8 August 2017 at 09:27
> >> >> >> To: "users@cloudstack.apache.org" <
> 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.Sonstebo@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.green@gmail.com
> >> <mail
> >> >> to:
> >> >> >> eric.lee.green@gmail.com>> wrote:
> >> >> >>
> >> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <
> asanka@nimbus.lk
> >> >> <mailto:
> >> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Thank you Dag,
On 10 Aug 2017 3:09 am, "Dag Sonstebo" <Da...@shapeblue.com> wrote:
Sure, let us know how you get on. The fact that the previous ssvm check
showed up with 172.17.101.1 was probably down to the wrong “host” global
setting – since the SSVM didn’t know where to contact management I would
guess it used a default override.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com |
http://www.shapeblue.com <http://www.shapeblue.com/> | Twitter:@ShapeBlue <
https://twitter.com/#!/shapeblue>
On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
Hi Dag, pleas give me few days as I am on an implementation visit to a
remote site. But below are some of the test I performed before.
1. Ping from ssvm to NFS is possible
2. Manually mounting NFS to /tmp/secondary is possible without any Issy
From the previous run of the ssvm check it is looking for a serve IP
172.17.101.1. Where registered NFS share is 172.17.101.253
I will run the check again on the first chance I get
Thank you and best regards
Asanka
On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <Da...@shapeblue.com>
wrote:
OK , can you post up the results of the ssvm check again?
As suggested previously on this thread – can you try to
1) Ping the NFS server from the SSVM (SSVM check does this as well) – if
this doesn’t work then you have a networking issue.
2) Depending on ping - manually mount the secondary NFS share on your
SSVM.
If this doesn’t work then you need to investigate the logs at the NFS
end
to see why the NFS handshake fails.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
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
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
> 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 <
Dag.Sonstebo@shapeblue.com>
> 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" <as...@nimbus.lk>
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.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk>
wrote:
>>
>> > Thanks Makrand
>> >
>> > On 8 August 2017 at 14:42, Makrand <ma...@gmail.com>
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 <
>> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>> >> >> Reply-To: "users@cloudstack.apache.org" <
>> users@cloudstack.apache.org>
>> >> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> >> To: "users@cloudstack.apache.org" <
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.Sonstebo@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.green@gmail.com
>> <mail
>> >> to:
>> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >>
>> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <
asanka@nimbus.lk
>> >> <mailto:
>> >> >> asanka@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
Posted by Dag Sonstebo <Da...@shapeblue.com>.
Sure, let us know how you get on. The fact that the previous ssvm check showed up with 172.17.101.1 was probably down to the wrong “host” global setting – since the SSVM didn’t know where to contact management I would guess it used a default override.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
S: +44 20 3603 0540 | dag.sonstebo@shapeblue.com | http://www.shapeblue.com <http://www.shapeblue.com/> | Twitter:@ShapeBlue <https://twitter.com/#!/shapeblue>
On 09/08/2017, 17:54, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
Hi Dag, pleas give me few days as I am on an implementation visit to a
remote site. But below are some of the test I performed before.
1. Ping from ssvm to NFS is possible
2. Manually mounting NFS to /tmp/secondary is possible without any Issy
From the previous run of the ssvm check it is looking for a serve IP
172.17.101.1. Where registered NFS share is 172.17.101.253
I will run the check again on the first chance I get
Thank you and best regards
Asanka
On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <Da...@shapeblue.com> wrote:
OK , can you post up the results of the ssvm check again?
As suggested previously on this thread – can you try to
1) Ping the NFS server from the SSVM (SSVM check does this as well) – if
this doesn’t work then you have a networking issue.
2) Depending on ping - manually mount the secondary NFS share on your SSVM.
If this doesn’t work then you need to investigate the logs at the NFS end
to see why the NFS handshake fails.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
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
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
> 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 <Da...@shapeblue.com>
> 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" <as...@nimbus.lk> 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.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk>
wrote:
>>
>> > Thanks Makrand
>> >
>> > On 8 August 2017 at 14:42, Makrand <ma...@gmail.com>
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 <
>> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>> >> >> Reply-To: "users@cloudstack.apache.org" <
>> users@cloudstack.apache.org>
>> >> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> >> To: "users@cloudstack.apache.org" <
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.Sonstebo@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.green@gmail.com
>> <mail
>> >> to:
>> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >>
>> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <
asanka@nimbus.lk
>> >> <mailto:
>> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Hi Dag, pleas give me few days as I am on an implementation visit to a
remote site. But below are some of the test I performed before.
1. Ping from ssvm to NFS is possible
2. Manually mounting NFS to /tmp/secondary is possible without any Issy
From the previous run of the ssvm check it is looking for a serve IP
172.17.101.1. Where registered NFS share is 172.17.101.253
I will run the check again on the first chance I get
Thank you and best regards
Asanka
On 9 Aug 2017 12:55 pm, "Dag Sonstebo" <Da...@shapeblue.com> wrote:
OK , can you post up the results of the ssvm check again?
As suggested previously on this thread – can you try to
1) Ping the NFS server from the SSVM (SSVM check does this as well) – if
this doesn’t work then you have a networking issue.
2) Depending on ping - manually mount the secondary NFS share on your SSVM.
If this doesn’t work then you need to investigate the logs at the NFS end
to see why the NFS handshake fails.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
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
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
> 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 <Da...@shapeblue.com>
> 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" <as...@nimbus.lk> 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.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk>
wrote:
>>
>> > Thanks Makrand
>> >
>> > On 8 August 2017 at 14:42, Makrand <ma...@gmail.com>
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 <
>> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>> >> >> Reply-To: "users@cloudstack.apache.org" <
>> users@cloudstack.apache.org>
>> >> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> >> To: "users@cloudstack.apache.org" <
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.Sonstebo@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.green@gmail.com
>> <mail
>> >> to:
>> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >>
>> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <
asanka@nimbus.lk
>> >> <mailto:
>> >> >> asanka@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
Posted by Dag Sonstebo <Da...@shapeblue.com>.
OK , can you post up the results of the ssvm check again?
As suggested previously on this thread – can you try to
1) Ping the NFS server from the SSVM (SSVM check does this as well) – if this doesn’t work then you have a networking issue.
2) Depending on ping - manually mount the secondary NFS share on your SSVM. If this doesn’t work then you need to investigate the logs at the NFS end to see why the NFS handshake fails.
Regards,
Dag Sonstebo
Cloud Architect
ShapeBlue
On 08/08/2017, 19:14, "Asanka Gunasekara" <as...@nimbus.lk> wrote:
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
Dag.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 8 August 2017 at 23:33, Asanka Gunasekara <as...@nimbus.lk> wrote:
> 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 <Da...@shapeblue.com>
> 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" <as...@nimbus.lk> 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.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk> wrote:
>>
>> > Thanks Makrand
>> >
>> > On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <
>> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>> >> >> Reply-To: "users@cloudstack.apache.org" <
>> users@cloudstack.apache.org>
>> >> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com
>> <mail
>> >> to:
>> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >>
>> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk
>> >> <mailto:
>> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 Gunasekara <as...@nimbus.lk> wrote:
> 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 <Da...@shapeblue.com>
> 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" <as...@nimbus.lk> 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.Sonstebo@shapeblue.com
>> www.shapeblue.com
>> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
>> @shapeblue
>>
>>
>>
>> On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk> wrote:
>>
>> > Thanks Makrand
>> >
>> > On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <
>> asanka@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.Sonstebo@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 <as...@nimbus.lk>
>> >> >> Reply-To: "users@cloudstack.apache.org" <
>> users@cloudstack.apache.org>
>> >> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com
>> <mail
>> >> to:
>> >> >> eric.lee.green@gmail.com>> wrote:
>> >> >>
>> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk
>> >> <mailto:
>> >> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 <Da...@shapeblue.com> 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" <as...@nimbus.lk> 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.Sonstebo@shapeblue.com
> www.shapeblue.com
> 53 Chandos Place, Covent Garden, London WC2N 4HSUK
> @shapeblue
>
>
>
> On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk> wrote:
>
> > Thanks Makrand
> >
> > On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <asanka@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.Sonstebo@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 <as...@nimbus.lk>
> >> >> Reply-To: "users@cloudstack.apache.org" <
> users@cloudstack.apache.org>
> >> >> Date: Tuesday, 8 August 2017 at 09:27
> >> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com
> <mail
> >> to:
> >> >> eric.lee.green@gmail.com>> wrote:
> >> >>
> >> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk
> >> <mailto:
> >> >> asanka@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
Posted by Dag Sonstebo <Da...@shapeblue.com>.
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" <as...@nimbus.lk> 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.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 8 August 2017 at 14:48, Asanka Gunasekara <as...@nimbus.lk> wrote:
> Thanks Makrand
>
> On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <as...@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 <Da...@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 <as...@nimbus.lk>
>> >> Reply-To: "users@cloudstack.apache.org" <us...@cloudstack.apache.org>
>> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com<mail
>> to:
>> >> eric.lee.green@gmail.com>> wrote:
>> >>
>> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk
>> <mailto:
>> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 Gunasekara <as...@nimbus.lk> wrote:
> 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 <as...@nimbus.lk> 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 <as...@nimbus.lk> wrote:
>>
>>> Thanks Makrand
>>>
>>> On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <as...@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 <Da...@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 <as...@nimbus.lk>
>>>> >> Reply-To: "users@cloudstack.apache.org" <users@cloudstack.apache.org
>>>> >
>>>> >> Date: Tuesday, 8 August 2017 at 09:27
>>>> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com<mail
>>>> to:
>>>> >> eric.lee.green@gmail.com>> wrote:
>>>> >>
>>>> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk
>>>> <mailto:
>>>> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 <as...@nimbus.lk> 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 <as...@nimbus.lk> wrote:
>
>> Thanks Makrand
>>
>> On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <as...@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 <Da...@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 <as...@nimbus.lk>
>>> >> Reply-To: "users@cloudstack.apache.org" <us...@cloudstack.apache.org>
>>> >> Date: Tuesday, 8 August 2017 at 09:27
>>> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com<mail
>>> to:
>>> >> eric.lee.green@gmail.com>> wrote:
>>> >>
>>> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk
>>> <mailto:
>>> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 <as...@nimbus.lk> wrote:
> Thanks Makrand
>
> On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <as...@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 <Da...@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 <as...@nimbus.lk>
>> >> Reply-To: "users@cloudstack.apache.org" <us...@cloudstack.apache.org>
>> >> Date: Tuesday, 8 August 2017 at 09:27
>> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com<mail
>> to:
>> >> eric.lee.green@gmail.com>> wrote:
>> >>
>> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk
>> <mailto:
>> >> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
Thanks Makrand
On 8 August 2017 at 14:42, Makrand <ma...@gmail.com> 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 <as...@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 <Da...@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 <as...@nimbus.lk>
> >> Reply-To: "users@cloudstack.apache.org" <us...@cloudstack.apache.org>
> >> Date: Tuesday, 8 August 2017 at 09:27
> >> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com<mailto:
> >> eric.lee.green@gmail.com>> wrote:
> >>
> >> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk<mailto:
> >> asanka@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
Posted by Makrand <ma...@gmail.com>.
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 <as...@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 <Da...@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 <as...@nimbus.lk>
>> Reply-To: "users@cloudstack.apache.org" <us...@cloudstack.apache.org>
>> Date: Tuesday, 8 August 2017 at 09:27
>> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com<mailto:
>> eric.lee.green@gmail.com>> wrote:
>>
>> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk<mailto:
>> asanka@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 <Da...@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 <as...@nimbus.lk>
> Reply-To: "users@cloudstack.apache.org" <us...@cloudstack.apache.org>
> Date: Tuesday, 8 August 2017 at 09:27
> To: "users@cloudstack.apache.org" <us...@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.Sonstebo@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.green@gmail.com<mailto:
> eric.lee.green@gmail.com>> wrote:
>
> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <asanka@nimbus.lk<mailto:
> asanka@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
Posted by Dag Sonstebo <Da...@shapeblue.com>.
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 <as...@nimbus.lk>
Reply-To: "users@cloudstack.apache.org" <us...@cloudstack.apache.org>
Date: Tuesday, 8 August 2017 at 09:27
To: "users@cloudstack.apache.org" <us...@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.Sonstebo@shapeblue.com
www.shapeblue.com
53 Chandos Place, Covent Garden, London WC2N 4HSUK
@shapeblue
On 8 August 2017 at 12:54, Eric Green <er...@gmail.com>> wrote:
> On Aug 7, 2017, at 23:44, Asanka Gunasekara <as...@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
Posted by Asanka Gunasekara <as...@nimbus.lk>.
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 Green <er...@gmail.com> wrote:
>
> > On Aug 7, 2017, at 23:44, Asanka Gunasekara <as...@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
Posted by Eric Green <er...@gmail.com>.
> On Aug 7, 2017, at 23:44, Asanka Gunasekara <as...@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?