Hi Lafferty,
The result is below:
[root@meng cloudstack]# showmount -e 10.244.18.55
Export list for 10.244.18.55:
/primary *
/secondary *
[root@meng cloudstack]# mount
/dev/mapper/vg_meng-lv_root on / type ext4 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
tmpfs on /dev/shm type tmpfs
(rw,rootcontext="system_u:object_r:tmpfs_t:s0")
/dev/sda1 on /boot type ext4 (rw)
/dev/mapper/vg_meng-lv_home on /home type ext4 (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
nfsd on /proc/fs/nfsd type nfsd (rw)
gvfs-fuse-daemon on /root/.gvfs type fuse.gvfs-fuse-daemon
(rw,nosuid,nodev)
/dev/sdb1 on /media/C03A-B0D6 type vfat
(rw,nosuid,nodev,uhelper=udisks,uid=0,gid=0,shortname=mixed,dmask=0077,utf8=1,flush)
10.244.18.55:/primary on /mnt/82df7a6d-6708-3333-877a-1cf1f3f5e945 type
nfs (rw,noac,vers=4,addr=10.244.18.55,clientaddr=10.244.18.55)
root@s-1-VM:~# mount -t nfs -v 10.244.18.55:/secondary test
mount.nfs: timeout set for Tue Aug 13 15:07:57 2013
mount.nfs: trying text-based options
'vers=4,addr=10.244.18.55,clientaddr=10.244.18.46'
mount.nfs: mount(2): Input/output error
mount.nfs: mount system call failed
The firewall rules on the NFS server are as follows:
-A INPUT -p tcp -m tcp --dport 49152:49216 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 53 -j ACCEPT
-A INPUT -i virbr0 -p udp -m udp --dport 67 -j ACCEPT
-A INPUT -i virbr0 -p tcp -m tcp --dport 67 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 5900:6100 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 16509 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 9090 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8250 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 7080 -j ACCEPT
-A INPUT -p tcp -m tcp --dport 8080 -j ACCEPT
-A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT
-A INPUT -p icmp -j ACCEPT
-A INPUT -i lo -j ACCEPT
-A INPUT -p tcp -m state --state NEW -m tcp --dport 22 -j ACCEPT
-A INPUT -j REJECT --reject-with icmp-host-prohibited
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport
111 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
111 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
2049 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
32803 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport
32769 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
892 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport
892 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
875 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport
875 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p tcp -m state --state NEW -m tcp --dport
662 -j ACCEPT
-A INPUT -s 10.244.18.0/24 -p udp -m state --state NEW -m udp --dport
662 -j ACCEPT
On Tue, 13 Aug 2013 14:48:21 +0000, Donal Lafferty wrote:
What is the result of "showmount -e 10.244.18.55" when run on the
SSVM?
What is the result of manually mounting the NFS share?
-----Original Message-----
From: Han,Meng [mailto:meng...@ufl.edu]
Sent: 13 August 2013 15:13
To: dev@cloudstack.apache.org
Subject: [GSOC] SSVM not working
Hi all,
Recently I reinstalled CloudStack 4.1.1 using the quick install
guide.
I found that I can not add instance because the secondary storage vm
is not
working correctly thus I cannot register templates. Below is the
output the
healthy check scripts of ssvm,
root@s-1-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh
================================================
First DNS server is 8.8.8.8
PING 8.8.8.8 (8.8.8.8): 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=47 time=1059.012 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=47 time=58.099 ms
--- 8.8.8.8 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss round-trip
min/avg/max/stddev = 58.099/558.555/1059.012/500.457 ms
Good: Can ping DNS server
================================================
Good: DNS resolves download.cloud.com
================================================
ERROR: NFS is not currently mounted
Try manually mounting from inside the VM NFS server is
169.254.1.111 PING
169.254.1.111 (169.254.1.111): 56 data bytes
64 bytes from 169.254.1.111: icmp_seq=0 ttl=64 time=0.043 ms
64 bytes from 169.254.1.111: icmp_seq=1 ttl=64 time=0.053 ms
--- 169.254.1.111 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss round-trip
min/avg/max/stddev = 0.043/0.048/0.053/0.000 ms
Good: Can ping NFS server
================================================
Management server is 10.244.18.55. Checking connectivity.
Good: Can connect to management server port 8250
================================================
Good: Java process is running
================================================
Tests Complete. Look for ERROR or WARNING above.
The NFS server is not mounted, and the IP address listed above as
the NFS
server is actually the link local address of the ssvm. The NFS
server address
should be 10.244.18.55 which is the same as the management server.
could
someone tell me why the link local address is there?
The following is the content of /var/cache/cloud/cmdline on ssvm.
template=domP type=secstorage host=10.244.18.55 port=8250
name=s-1-
VM
zone=1 pod=1 guid=s-1-VM
resource=com.cloud.storage.resource.NfsSecondaryStorageResource
instance=SecStorage sslcopy=true role=templateProcessor mtu=1500
eth2ip=10.244.18.58 eth2mask=255.255.255.0 gateway=10.244.18.1
eth0ip=169.254.1.111 eth0mask=255.255.0.0 eth1ip=10.244.18.46
eth1mask=255.255.255.0 mgmtcidr=10.244.18.0/24 localgw=10.244.18.1
private.network.device=eth1 eth3ip=10.244.18.52
eth3mask=255.255.255.0
storageip=10.244.18.52 storagenetmask=255.255.255.0
storagegateway=10.244.18.1 internaldns1=8.8.8.8 internaldns2=8.8.4.4
dns1=8.8.8.8 dns2=8.8.4.4
Could someone give me some help?
Cheers,
Meng
