Centos8
Cloudstack 4.15
Here is my scenario
I have two servers, one for the host and another for the management server
I used Advanced Networking Configuration and I can SSH Inside the System
VMs,
Inside console proxy VM I can Ping the Management Server
but the problem is I can not ping the co
Thank you Rohit, the issue was resolved,
I have another issue where when you open the console proxy on the instance,
it times out !!
and the management server is not able to ping the console proxy VM
I can SSH inside it and It has this error :
root@v-2-VM:~#
root@v-2-VM:~#
root@v-2-VM:~# /usr/l
...
https://docs.cloudstack.apache.org/en/4.14.1.0/adminguide/accounts.html#using-a-saml-2-0-identity-provider-for-user-authentication
Related blog: https://www.shapeblue.com/saml2-cloudstack/
Regards.
From: Rohit Yadav
Sent: Sunday, May 23, 2021 21:39
To: user
Hi Mike,
Have you setup the SAML IDP server and the CloudStack SP properly? Please refer
to:
Regards.
From: Andrija Panic
Sent: Friday, May 21, 2021 03:22
To: users
Subject: Re: SAML SSO Error
HI Mike,
are you having issues on 4.15 now or on which release
Hi Serge,
Have you added the public IP range with a VLAN (say while deploying the zone)?
You can ping your CPVM IP and use tcpdump on protocol icmp for example "tcpdump
-i icmp" across all hosts (start with the KVM/CentOS host
where the cpvm is running) and debug where the packet is being drop
Hi Rakesh,
Per the error "protocol is disabled or cipher suites are inappropriate", there
is some issue with the client/server JDK allowed TLS protocols. Please check
jdk.tls.disabledAlgorithms or related settings of your JRE.
Regards.
From: Rakesh Venkatesh
I can Ping NFS Server from Console Proxy SSVM
root@v-2-VM:~#
root@v-2-VM:~#
root@v-2-VM:~# ping 192.168.1.7
PING 192.168.1.7 (192.168.1.7): 56 data bytes
64 bytes from 192.168.1.7: icmp_seq=0 ttl=64 time=0.215 ms
64 bytes from 192.168.1.7: icmp_seq=1 ttl=64 time=0.207 ms
64 bytes from 192.168.1.7:
Route Table
root@v-2-VM:~# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric RefUse
Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG0 00 eth2
8.8.4.4 192.168.1.1 255.255.255.255 UGH 0 00 eth1
8.8.8.
Here are some log files
/var/log/cloud.log
root@v-2-VM:/var/log# cat cloud.log
Sun 23 May 2021 03:17:36 PM UTC Executing cloud-early-config
Sun 23 May 2021 03:17:36 PM UTC Scripts checksum detected:
oldmd5=4fc9a03fc8f196d863d30885e9a0c50a
newmd5=032ab7551bf9db6662808252305f4ddf
Sun 23 May 2021 0
Cloudstack 4.15
Console Proxy SSVM check has NFS error trying to reach 255.255.255.0, which
is not the configured secondary storage IP address
I re installed the set up and still the problem is there
root@v-2-VM:~#
root@v-2-VM:~#
root@v-2-VM:~# /usr/local/cloud/systemvm/ssvm-check.sh
===
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
=
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 ;-) ).
Rega
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
wrote:
> The error is right here in the log. SSVM is supposed to h
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
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
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
Centos8
Cloudstack 4.15
My console IP address 192.168.1.86 is unreachable from anywhere
But it’s Private IP 192.168.1.68 is reachable EVERYWHERE
The console also has access to the Internet.
Network Setup :
2 servers : they are on a home Local Network router with internet
Home Router Gateway : 1
17 matches
Mail list logo
