Hi, The port 8250 should be open on the management server (10.0.33.1) , and accessible from mgmt server, kvm host and system vms. >From what you said, the port 8250 is accessible from mgmt server and kvm host, but not from system vms. Can you confirm if ping and port 8080 (of 10.0.33.1) work or not?
Kind regards, Wei On Mon, 9 Oct 2023 at 10:44, jaejong <cb...@naver.com> wrote: > Hi Wei > thanks for your reply! > > From server nc to > server itself: connected > host: connection refused > sVm : No route to host or Connection timed out > > From host nc to > host itself: Connection refused > server : onnected > svm: No route to host > > port 9090 is same status with 8250 > > host status > getenforce : Permissive > firewalld : disabled > /etc/sysconfig/iptables : created when added to cluster > there are no entry for 8250 and 9090 > > thanks > -----Original Message----- > From: "Wei ZHOU"<ustcweiz...@gmail.com> > To: <users@cloudstack.apache.org>; > Cc: > Sent: 2023-10-09 (월) 16:14:57 (GMT+09:00) > Subject: Re: server listen ipv6 not ipv4 > > Hi, > > Can you check if port 8250 is open for Ipv4 addresses (from the management > server itself, a kvm host and system vms) ? If not, can you restart > cloudstack-management service ? > > You can use netcat or telnet, see examples below > > [root@kvm1 ~]# nc -vz 10.0.32.105 8250 > Connection to 10.0.32.105 8250 port [tcp/*] succeeded! > [root@kvm1 ~]# telnet 10.0.32.105 8250 > Trying 10.0.32.105... > Connected to 10.0.32.105. > Escape character is '^]'. > ^] > > telnet> > > > -Wei > > > On Mon, 9 Oct 2023 at 04:44, jaejong <cb...@naver.com> wrote: > > > Hi Wei and Wido > > > > You are right about The netstat output looks ok. > > > > So I check more about this problem. > > > > Java uses IPv6 preferentially when both IPv4 and IPv6 are available in > the > > OS. > > > > So, when looking at network port information used with netstat or lsof, > > etc. > > the address is displayed as IPv6. > > > > However, if the server is IPv6-only and does not have an IPv4 address, > > then attempting to connect using an IPv4 address from client, > > will likely result in an error, > > as there will be no corresponding IPv4 endpoint to connect to. > > > > In such cases, you would need to ensure that the server can accept IPv4 > > connections or > > adjust your code to handle IPv6. > > > > with only "tcp6 0 0 :::8080 :::* LISTEN 1454/java' > > I can connect to management server by "http://10.0.33.1:8080/client/"; > > > > With both tcp 0 0 0.0.0.0:22 0.0.0.0:* and tcp6 0 0 :::22 :::* LISTEN > > Ican connect to server from SSVM and SPVM. > > > > So I think my server has no problem. > > > > If you're upgrading an older version, > > sometimes it may work because the upgrade doesn't change the > configuration > > file. > > > > I did a fresh install of OS and ACS. > > > > Would you check more please? > > > > -----Original Message----- > > From: "jaejong"<cb...@naver.com> > > To: <users@cloudstack.apache.org>; > > Cc: > > Sent: 2023-10-04 (수) 18:36:38 (GMT+09:00) > > Subject: Re: server listen ipv6 not ipv4 > > > > Hi Wei ZHOU > > > > There are no problem with ping. > > > > I connect to management server by ssh with no problems. > > > > Thanks > > > > -----Original Message----- > > From: "Wei ZHOU"<ustcweiz...@gmail.com> > > To: <users@cloudstack.apache.org>; > > Cc: > > Sent: 2023-10-04 (수) 18:04:47 (GMT+09:00) > > Subject: Re: server listen ipv6 not ipv4 > > > > Hi, > > > > The route should be good. But the TCP packets might be dropped somewhere > > (ping uses ICMP packets not TCP) > > > > -Wei > > > > On Wed, 4 Oct 2023 at 11:01, jaejong <cb...@naver.com> wrote: > > > > > Yes, eth1 IPs of system vms are in the same subnet as 10.0.33.1 > > > there is no dropped packets during ping. > > > > > > thanks a lot! > > > > > > > > > -----Original Message----- > > > From: "Wei ZHOU"<ustcweiz...@gmail.com> > > > To: <users@cloudstack.apache.org>; > > > Cc: > > > Sent: 2023-10-04 (수) 17:35:56 (GMT+09:00) > > > Subject: Re: server listen ipv6 not ipv4 > > > > > > Hi, > > > > > > +1 with what Wido said. > > > > > > The packet is probably dropped/blocked at a point between SSVM and the > > > management server (if it is running fine). > > > > > > Are the eth1 IPs of system vms in the same subnet as 10.0.33.1 ? > > > > > > -Wei > > > > > > > > > On Wed, 4 Oct 2023 at 09:25, jaejong <cb...@naver.com> wrote: > > > > > > > Hi Wei ZHOU! > > > > > > > > Yes, I can ping to server ip(10.0.33.1) from SSVM and SPVM. > > > > > > > > netstat does not report about 0.0.0.0:8250. > > > > > > > > Is it right? > > > > > > > > Oh, then what is the problems!! > > > > > > > > > > > > -----Original Message----- > > > > From: "Wei ZHOU"<ustcweiz...@gmail.com> > > > > To: <users@cloudstack.apache.org>; > > > > Cc: > > > > Sent: 2023-10-04 (수) 15:31:50 (GMT+09:00) > > > > Subject: Re: server listen ipv6 not ipv4 > > > > > > > > Hi, > > > > > > > > The netstat output looks ok. > > > > > > > > Can you check the IP 10.0.33.1 is reachable from system vm ? > > > > > > > > -Wei > > > > > > > > > > > > > > > > On Wed, 4 Oct 2023 at 03:30, jaejong <cb...@naver.com> wrote: > > > > > > > > > OS : Rocky 8.8 > > > > > ACS : 4.18.1 > > > > > > > > > > ACS management server listem 8250 port only from ipv6(tcp6) > > > > > So SystemVMs can not connect to server. > > > > > > > > > > How to Fix to listen on ipv4? > > > > > > > > > > 2023-10-04 00:18:10,281 INFO [cloud.agent.Agent] (main:null) Agent > > > [id = > > > > > 2 : type = PremiumSecondaryStorageResource : zone = 1 : pod = 1 : > > > > workers = > > > > > 5 : host = 10.0.33.1 : port = 8250 > > > > > 2023-10-04 00:18:10,300 INFO [utils.nio.NioClient] (main:null) > > > > Connecting > > > > > to 10.0.33.1:8250 > > > > > 2023-10-04 00:18:13,358 ERROR [utils.nio.NioConnection] (main:null) > > > > Unable > > > > > to initialize the threads. > > > > > java.net.NoRouteToHostException: No route to host > > > > > at java.base/sun.nio.ch.Net.connect0(Native Method) > > > > > at java.base/sun.nio.ch.Net.connect(Net.java:483) > > > > > at java.base/sun.nio.ch.Net.connect(Net.java:472) > > > > > at java.base/sun.nio.ch > > > > > .SocketChannelImpl.connect(SocketChannelImpl.java:692) > > > > > at com.cloud.utils.nio.NioClient.init(NioClient.java:56) > > > > > at > > > com.cloud.utils.nio.NioConnection.start(NioConnection.java:95) > > > > > at com.cloud.agent.Agent.start(Agent.java:283) > > > > > at > > > com.cloud.agent.AgentShell.launchNewAgent(AgentShell.java:454) > > > > > at > > > > > > > > > com.cloud.agent.AgentShell.launchAgentFromClassInfo(AgentShell.java:431) > > > > > at > > com.cloud.agent.AgentShell.launchAgent(AgentShell.java:415) > > > > > at com.cloud.agent.AgentShell.start(AgentShell.java:511) > > > > > at com.cloud.agent.AgentShell.main(AgentShell.java:541) > > > > > > > > > > $ netstat -tulpn > > > > > Active Internet connections (only servers) > > > > > Proto Recv-Q Send-Q Local Address Foreign Address > > > State > > > > > PID/Program name > > > > > tcp 0 0 0.0.0.0:892 0.0.0.0:* > > > > > LISTEN 1533/rpc.mountd > > > > > tcp 0 0 0.0.0.0:2049 0.0.0.0:* > > > > > LISTEN - > > > > > tcp 0 0 0.0.0.0:32803 0.0.0.0:* > > > > > LISTEN - > > > > > tcp 0 0 0.0.0.0:3306 0.0.0.0:* > > > > > LISTEN 1127/mysqld > > > > > tcp 0 0 0.0.0.0:111 0.0.0.0:* > > > > > LISTEN 1/systemd > > > > > tcp 0 0 0.0.0.0:662 0.0.0.0:* > > > > > LISTEN 1532/rpc.statd > > > > > tcp 0 0 0.0.0.0:22 0.0.0.0:* > > > > > LISTEN 1036/sshd > > > > > tcp6 0 0 :::8250 :::* > > > > > LISTEN 1454/java > > > > > tcp6 0 0 :::36667 :::* > > > > > LISTEN 1454/java > > > > > tcp6 0 0 :::892 :::* > > > > > LISTEN 1533/rpc.mountd > > > > > tcp6 0 0 :::41533 :::* > > > > > LISTEN 1454/java > > > > > tcp6 0 0 :::2049 :::* > > > > > LISTEN - > > > > > tcp6 0 0 :::9090 :::* > > > > > LISTEN 1454/java > > > > > tcp6 0 0 :::32803 :::* > > > > > LISTEN - > > > > > tcp6 0 0 :::33060 :::* > > > > > LISTEN 1127/mysqld > > > > > tcp6 0 0 :::111 :::* > > > > > LISTEN 1/systemd > > > > > tcp6 0 0 :::8080 :::* > > > > > LISTEN 1454/java > > > > > tcp6 0 0 :::662 :::* > > > > > LISTEN 1532/rpc.statd > > > > > tcp6 0 0 :::22 :::* > > > > > LISTEN 1036/sshd > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >
