You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cloudstack.apache.org by Serge Byishimo <se...@gmail.com> on 2021/05/23 12:29:15 UTC

Web Console Timing Out

Centos8
Cloudstack 4.15

System VMs are running and their Agent is UP,

System VMs can ping the management server but the management server can not
ping any of the IPs of the System VMs, thus the web console is not
accessible,

I’m thinking it is firewall rules on the System VM side that is causing it,

Any reasons why this is happening?


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:~#





root@v-2-VM:~#
root@v-2-VM:~# iptables -nL
Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0            icmptype 8
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
RELATED,ESTABLISHED
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
RELATED,ESTABLISHED
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
RELATED,ESTABLISHED
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:3922
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:8001
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:8001
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:443
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:80
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:8080
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy DROP)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
root@v-2-VM:~#
root@v-2-VM:~#

Thanks

Re: Web Console Timing Out

Posted by Serge Byishimo <se...@gmail.com>.
Thank you Sergey

How am I supposed to delete the secondary storage with running System VMs?
It gives this Error : Cannot delete image store with active templates
backup!

Regards,

On Sun, May 23, 2021 at 4:29 PM Sergey Levitskiy <se...@hotmail.com>
wrote:

> The error is right here in the log. SSVM is supposed to have secondary
> storage mounted over NFS. 255.255.255.0 is not the correct IP. Likely, the
> cause is garbled record for secondary storage. Try to delete it and re-add.
>
> 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
>
>
> From: Serge Byishimo <se...@gmail.com>
> Date: Sunday, May 23, 2021 at 5:29 AM
> To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
> Subject: Web Console Timing Out
> Centos8
> Cloudstack 4.15
>
> System VMs are running and their Agent is UP,
>
> System VMs can ping the management server but the management server can not
> ping any of the IPs of the System VMs, thus the web console is not
> accessible,
>
> I’m thinking it is firewall rules on the System VM side that is causing it,
>
> Any reasons why this is happening?
>
>
> 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:~#
>
>
>
>
>
> root@v-2-VM:~#
> root@v-2-VM:~# iptables -nL
> Chain INPUT (policy DROP)
> target     prot opt source               destination
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
> ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0            icmptype 8
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
> RELATED,ESTABLISHED
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
> RELATED,ESTABLISHED
> ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
> RELATED,ESTABLISHED
> ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW
> tcp
> dpt:3922
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW
> tcp
> dpt:8001
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW
> tcp
> dpt:8001
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW
> tcp
> dpt:443
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW
> tcp
> dpt:80
> ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW
> tcp
> dpt:8080
> ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
>
> Chain FORWARD (policy DROP)
> target     prot opt source               destination
>
> Chain OUTPUT (policy ACCEPT)
> target     prot opt source               destination
> root@v-2-VM:~#
> root@v-2-VM:~#
>
> Thanks
>


-- 
Byishimo Shema Serge
Kigali, Rwanda
Tel: +250 786 076 106
www.serge.works

Re: Web Console Timing Out

Posted by Sergey Levitskiy <se...@hotmail.com>.
The error is right here in the log. SSVM is supposed to have secondary storage mounted over NFS. 255.255.255.0 is not the correct IP. Likely, the cause is garbled record for secondary storage. Try to delete it and re-add.

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


From: Serge Byishimo <se...@gmail.com>
Date: Sunday, May 23, 2021 at 5:29 AM
To: users@cloudstack.apache.org <us...@cloudstack.apache.org>
Subject: Web Console Timing Out
Centos8
Cloudstack 4.15

System VMs are running and their Agent is UP,

System VMs can ping the management server but the management server can not
ping any of the IPs of the System VMs, thus the web console is not
accessible,

I’m thinking it is firewall rules on the System VM side that is causing it,

Any reasons why this is happening?


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:~#





root@v-2-VM:~#
root@v-2-VM:~# iptables -nL
Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0            icmptype 8
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
RELATED,ESTABLISHED
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
RELATED,ESTABLISHED
ACCEPT     all  --  0.0.0.0/0            0.0.0.0/0            state
RELATED,ESTABLISHED
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:3922
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:8001
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:8001
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:443
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:80
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0            state NEW tcp
dpt:8080
ACCEPT     icmp --  0.0.0.0/0            0.0.0.0/0

Chain FORWARD (policy DROP)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
root@v-2-VM:~#
root@v-2-VM:~#

Thanks