Hi Vash, Yes the System VMs are able to start and I can SSH into both of them,
That NFS error is in the console proxy SSVM, thus the Web Console is timing out But in there is no error in Secondary Storage VM : ssvm-check.sh root@s-1-VM:~# 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=113 time=30.151 ms 64 bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=29.075 ms --- 8.8.8.8 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 29.075/29.613/30.151/0.538 ms Good: Can ping DNS server ================================================ Good: DNS resolves cloudstack.apache.org ================================================ nfs is currently mounted Mount point is /mnt/SecStorage/3636e78b-77d4-3562-995e-deb81e266bce Good: Can write to mount point ================================================ Management server is 192.168.1.8. Checking connectivity. Good: Can connect to management server 192.168.1.8 port 8250 ================================================ Good: Java process is running ================================================ Tests Complete. Look for ERROR or WARNING above. Why does it say this in console proxy SSVM ? Do I have to redo the whole set up? ================================================ ERROR: NFS is not currently mounted Try manually mounting from inside the VM NFS server is 255.255.255.0 PING 255.255.255.0 (255.255.255.0): 56 data bytes --- 255.255.255.0 ping statistics --- 2 packets transmitted, 0 packets received, 100% packet loss WARNING: cannot ping nfs server Regards, On Sun, May 23, 2021 at 4:41 PM [email protected] <[email protected]> wrote: > Hi Serge, > > to be honest, it's hard for me to understand you current network setup > / deployment at the moment. > Taking a look at the log you've provided, there seems to be an > adressing issue with the nfs-server-address (as long as 255.255.255.0 > isn't the correct address of your nfs server ;-) ). > Regarding the questioned connectivitiy: > The connection of the ssvm to the management server seems to be > working. I am kind of troubled if the console proxy is able to start / > work correctly as long as the ssvm is having trouble with the provided > nfs-shares. > > with regards, > chris > > Am So., 23. Mai 2021 um 15:01 Uhr schrieb Serge Byishimo > <[email protected]>: > > > > Management Server can not ping System VM Console Proxy IP address > > > > root@v-2-VM:~# > > root@v-2-VM:~# > > root@v-2-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=113 time=29.581 ms > > 64 bytes from 8.8.8.8: icmp_seq=1 ttl=113 time=30.140 ms > > --- 8.8.8.8 ping statistics --- > > 2 packets transmitted, 2 packets received, 0% packet loss > > round-trip min/avg/max/stddev = 29.581/29.861/30.140/0.280 ms > > Good: Can ping DNS server > > ================================================ > > Good: DNS resolves cloudstack.apache.org > > ================================================ > > ERROR: NFS is not currently mounted > > Try manually mounting from inside the VM > > NFS server is 255.255.255.0 > > PING 255.255.255.0 (255.255.255.0): 56 data bytes > > --- 255.255.255.0 ping statistics --- > > 2 packets transmitted, 0 packets received, 100% packet loss > > WARNING: cannot ping nfs server > > routing table follows > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use > > Iface > > 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 > eth2 > > 8.8.4.4 192.168.1.1 255.255.255.255 UGH 0 0 0 > eth1 > > 8.8.8.8 192.168.1.1 255.255.255.255 UGH 0 0 0 > eth1 > > 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 > eth0 > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 > eth1 > > 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 > eth2 > > ================================================ > > Management server is 192.168.1.8. Checking connectivity. > > Good: Can connect to management server 192.168.1.8 port 8250 > > ================================================ > > Good: Java process is running > > ================================================ > > Tests Complete. Look for ERROR or WARNING above. > > root@v-2-VM:~# > -- Byishimo Shema Serge Kigali, Rwanda Tel: +250 786 076 106 www.serge.works
