Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C2268200CDE for ; Tue, 8 Aug 2017 10:24:14 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C0968166DB0; Tue, 8 Aug 2017 08:24:14 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id DFB9A166DAF for ; Tue, 8 Aug 2017 10:24:13 +0200 (CEST) Received: (qmail 66994 invoked by uid 500); 8 Aug 2017 08:24:12 -0000 Mailing-List: contact users-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@cloudstack.apache.org Delivered-To: mailing list users@cloudstack.apache.org Received: (qmail 66982 invoked by uid 99); 8 Aug 2017 08:24:12 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Aug 2017 08:24:12 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id A8C9A1A4D4D for ; Tue, 8 Aug 2017 08:24:11 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.3 X-Spam-Level: X-Spam-Status: No, score=-0.3 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=nimbus-lk.20150623.gappssmtp.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id wYAxIB7AoczM for ; Tue, 8 Aug 2017 08:24:08 +0000 (UTC) Received: from mail-qk0-f172.google.com (mail-qk0-f172.google.com [209.85.220.172]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id B3BA65FBE2 for ; Tue, 8 Aug 2017 08:24:05 +0000 (UTC) Received: by mail-qk0-f172.google.com with SMTP id d136so15875085qkg.3 for ; Tue, 08 Aug 2017 01:24:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nimbus-lk.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=H10p6EDo+JiRpaQZQwoVwdVvL6PBj7oVYGcl6CmIX+A=; b=e89n3h/gjOCYo9kQn68zYvAQw7KzQ8EdwdnQOUlQeXaX2m88D9CNxTFgeu57ryHP+l gobHklrfRG7oG5GiiI+LjesquOBYVZlUOCbRuG/ZWlU5fqpbTGYNoegn5Az+M4nwm4Ay LuAQmH7WQQLHEsnGo6t5gYUS7Q0Si65lg+wVeuEEPol6IuKXxZvp4pEwZrUXbPACYd++ LaZsT/JLlrvnK6/N+1JKAytd9dASnTrHs2kiQLtbZs99OjcIaxTEVi/a7fAaKv6/goRt 69gJ7J2ZIvrWiwy/dqNCAUJXIgD/iwfLxQ+Y1KQ5dPCmdPQnkC1Xlyu2S8VtnsZBDNQd cePg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=H10p6EDo+JiRpaQZQwoVwdVvL6PBj7oVYGcl6CmIX+A=; b=B06KSiaSESSWyeXERQ2Xp14o/5tIxxJHa5peUaimHU7BtarHQfzfJCim2E7fZ6uFih Qr77cfs/WSjQQkp+Mn2Y2WPuq875Q7IJoL443jQkMYsdtzwRtLfhlYBPdQmKLa3STYcl UM66DC4WuiQvtfl6x4k4DSjVZzH/AvQ9FKuXAPSszo0nyt1OvELYV5QMIwo4OKBUFd8Z 8YS2pIlS65/a/i/sgnDeb+rWDt2oASahI6sNUAhcxvSjoFOdFxCT0qQ1B5kC06FmWT2B GHYpplwtqGcFJbg16Zpgg7qnER0JFqW3rLNMUFfs6WYl8BIpDpVdwXhg0qN32bVcaHjc NEeA== X-Gm-Message-State: AHYfb5iNEcil9eB5HHPW004dtllEvk0zxiYzpykXfURMInvHzyzmkb7m mUfAiStMKyZ5y91Ufj4G80b32xs/z7l3LOXZ7077nD7NdBpvmf/7jr2fsXa2Mm5Tpcke51BUtI3 T0inL8R5LBaTw/E9IY8w9ZVqaUeTaiyhOcXk/fVEoRHNFSl3YVyvnjX9Ngwsinsp6n9fUbhv5VS QuxFI7JUj94KJAppBs X-Received: by 10.55.7.7 with SMTP id 7mr4327438qkh.121.1502180638573; Tue, 08 Aug 2017 01:23:58 -0700 (PDT) MIME-Version: 1.0 Received: by 10.200.34.149 with HTTP; Tue, 8 Aug 2017 01:23:57 -0700 (PDT) In-Reply-To: <15F0D2F2-6974-442C-81C3-8D1900097A19@gmail.com> References: <15F0D2F2-6974-442C-81C3-8D1900097A19@gmail.com> From: Asanka Gunasekara Date: Tue, 8 Aug 2017 13:53:57 +0530 Message-ID: Subject: Re: Secondary storage is not secondary properly To: users@cloudstack.apache.org Content-Type: multipart/related; boundary="001a114c88d85a6440055639af1a" archived-at: Tue, 08 Aug 2017 08:24:14 -0000 --001a114c88d85a6440055639af1a Content-Type: multipart/alternative; boundary="001a114c88d85a643e055639af19" --001a114c88d85a643e055639af19 Content-Type: text/plain; charset="UTF-8" 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 wrote: > > > On Aug 7, 2017, at 23:44, Asanka Gunasekara wrote: > > NFS is running on a different server, I can manual mount this share as > NFS > > and SMB > > Cloud stack - 4.9 > > Os is Centos 7 (64) > > * Make sure that it's accessible from the *storage* network (the network > that you configured as storage when you created the zone, assuming you > selected advanced networking). > * Is the secondary storage virtual machine up and running? Check your > Infrastructure tab. > * If the secondary storage virtual machine is up and running, open its > console and log in as root / password. Then check 'ip addr list' to make > sure that it has IP addresses. > * If it has IP addresses, try pinging your secondary storage NFS server > (still within the SSVM). > * If you can ping your secondary storage NFS server, try mounting the NFS > share at some random place in your filesystem to make sure you can mount it > from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/export/secstorage > /tmp/t' > * Make sure you're using the NFS server's *storage* network IP address > when you make this attempt. > > It is possible that your NFS server has a firewall configured? But from my > experiments, the secondary storage VM not providing secondary storage > usually is a networking problem, things not set up properly in your zone's > networking so that the secondary storage VM can't reach the secondary > storage. Are you using advanced networking, or basic networking? > > --001a114c88d85a643e055639af19 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Makrand thank you for replying, please see below for th= e rest results

* Make sure that it's accessible from the *storag= e* network (the network that you configured as storage when you created the= zone, assuming you selected advanced networking).
Asanka > Since thi= s is a test environemt I have just made it all in one subnet (is that the i= ssue)

* Is the secondary storage virtual machine up and running? Che= ck your Infrastructure tab.
Asanka > Yes both system VMs are up and r= unning

* If the secondary storage virtual machine is up and running,= open its console and log in as root / password. Then check 'ip addr li= st' to make sure that it has IP addresses.
Asanka > Yes it IP are= assigned

* If it has IP addresses, try pinging your secondary stora= ge NFS server (still within the SSVM).
Asanka > I can ping secondary = storage

* If you can ping your secondary storage NFS server, try mou= nting the NFS share at some random place in your filesystem to make sure yo= u can mount it from the SSVM. e.g., 'mkdir /tmp/t; mount myserver:/expo= rt/secstorage /tmp/t'
Asanka > I can mount the secondary storage = as below


3D"Inline

On 8 August 2017 at 12:54, Eric Green <eric= .lee.green@gmail.com> wrote:

> On Aug 7, 2017, at 23:44, Asanka Gunasekara <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 Infra= structure tab.
* If the secondary storage virtual machine is up and running, open its cons= ole and log in as root / password. Then check 'ip addr list' to mak= e sure that it has IP addresses.
* If it has IP addresses, try pinging your secondary storage NFS server (st= ill within the SSVM).
* If you can ping your secondary storage NFS server, try mounting the NFS s= hare 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 addr= ess 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 usual= ly is a networking problem, things not set up properly in your zone's n= etworking so that the secondary storage VM can't reach the secondary st= orage. Are you using advanced networking, or basic networking?


--001a114c88d85a643e055639af19-- --001a114c88d85a6440055639af1a--