Hello,

Yes, we are able to ping  192.168.254.6 . Please find the below details .

==============
PING 192.168.254.6 (192.168.254.6) 56(84) bytes of data.
64 bytes from 192.168.254.6: icmp_seq=1 ttl=64 time=0.030 ms
64 bytes from 192.168.254.6: icmp_seq=2 ttl=64 time=0.036 ms
64 bytes from 192.168.254.6: icmp_seq=3 ttl=64 time=0.034 ms
64 bytes from 192.168.254.6: icmp_seq=4 ttl=64 time=0.034 ms
^C
--- 192.168.254.6 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3278ms
rtt min/avg/max/mdev = 0.030/0.033/0.036/0.006 ms
==============

=============================

rpcinfo -p 192.168.254.6

   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100024    1   udp    662  status
    100024    1   tcp    662  status
    100005    1   udp    892  mountd
    100005    1   tcp    892  mountd
    100005    2   udp    892  mountd
    100005    2   tcp    892  mountd
    100005    3   udp    892  mountd
    100005    3   tcp    892  mountd
    100003    2   tcp   2049  nfs
    100003    3   tcp   2049  nfs
    100003    4   tcp   2049  nfs
    100227    2   tcp   2049  nfs_acl
    100227    3   tcp   2049  nfs_acl
    100003    2   udp   2049  nfs
    100003    3   udp   2049  nfs
    100003    4   udp   2049  nfs
    100227    2   udp   2049  nfs_acl
    100227    3   udp   2049  nfs_acl
    100021    1   udp  32769  nlockmgr
    100021    3   udp  32769  nlockmgr
    100021    4   udp  32769  nlockmgr
    100021    1   tcp  32803  nlockmgr
    100021    3   tcp  32803  nlockmgr
    100021    4   tcp  32803  nlockmgr
=============================




--
Regards,
Adam
SupportPRO.com




On Friday 14 November 2014 02:43 PM, Alerts wrote:
Hi,

We configured Cloudstack 4.4 with a management server and a compute node(management server with nfs shares for primary and secondary). We can manually mount the nfs shares(both primary and secondary), however, the secondary storage is not being detected by the Cloudstack setup. We are receiving the error as below from the server logs.
==================================================================
2014-11-13 19:09:55,012 DEBUG [c.c.a.t.Request] (AgentManager-Handler-14:null) Seq 3-8948089509631754274: Processing: { Ans: , MgmtId: 9474724282990, via: 3, Ver: v1, Flags: 10, [{"com.cloud.agent.api.Answer":{"result":false,"details":"com.cloud.utils.exception.CloudRuntimeException: GetRootDir for nfs://192.168.254.6/export/secondary failed due to com.cloud.utils.exception.CloudRuntimeException: Unable to mount 192.168.254.6:/export/secondary at /mnt/SecStorage/a5d7ce94-f3f1-33c7-891f-280f22ceab5f due to mount.nfs: Network is unreachable\n\tat org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.getRootDir(NfsSecondaryStorageResource.java:1839)\n\tat org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.execute(NfsSecondaryStorageResource.java:1588)\n\tat org.apache.cloudstack.storage.resource.NfsSecondaryStorageResource.executeRequest(NfsSecondaryStorageResource.java:212)\n\tat com.cloud.storage.resource.PremiumSecondaryStorageResource.defaultAction(PremiumSecondaryStorageResource.java:64)\n\tat com.cloud.storage.resource.PremiumSecondaryStorageResource.executeRequest(PremiumSecondaryStorageResource.java:60)\n\tat com.cloud.agent.Agent.processRequest(Agent.java:501)\n\tat com.cloud.agent.Agent$AgentRequestHandler.doTask(Agent.java:808)\n\tat com.cloud.utils.nio.Task.run(Task.java:84)\n\tat java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)\n\tat java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)\n\tat java.lang.Thread.run(Thread.java:745)\n","wait":0}}] }
==================================================================

Any assistance regarding this would be appreciated.

--
Regards,
George
SupportPRO.com


Reply via email to