Dose nodetool tools support ipv6?

[Yang Liyuan]

I want to deploye a scylla cluster with ipv6, and the scylla-server and scylla-jmx was normal, but when i use nodetool status, i got the error:

、、、

[root@node1 ~]# nodetool status
nodetool: Failed to connect to '127.0.0.1:7199' - ConnectException: 'Connectiion refused(Connection refused)'.

、、、

 But the port 7199 was on ipv6 address, so i want to know whether nodetool support the ipv6.？

scylla version is 4.5.0

、、、

[root@node1 ~]# netstat -nlp | grep scylla
tcp6       0      0 fd88:5110:a350:ff0:9180 :::*                    LISTEN      223414/scylla
tcp6       0      0 fd88:5110:a350:ff0:7199 :::*                    LISTEN      231026/scylla-jmx
tcp6       0      0 fd88:5110:a350:ff0:8000 :::*                    LISTEN      223414/scylla
tcp6       0      0 fd88:5110:a350:ff:19042 :::*                    LISTEN      223414/scylla
tcp6       0      0 :::10116                :::*                    LISTEN      231026/scylla-jmx
tcp6       0      0 fd88:5110:a350:ff:10000 :::*                    LISTEN      223414/scylla
tcp6       0      0 fd88:5110:a350:ff0:9042 :::*                    LISTEN      223414/scylla
tcp6       0      0 fd88:5110:a350:ff0:7000 :::*                    LISTEN      223414/scylla

、、、

[Benny Halevy]

Hello Yang Liyuan,

Examining the nodetool code, it uses the 127.0.0.1 host address by default,

but you can pass the `-h ::1` option to denote the ipv6 localhost address.

However, on the Scylla side, we need also to tell scylla-jmx to listen on the ipv6 address.

I was able to achieve that locally by starting scylla-jmx with `./scripts/scylla-jmx -ja 0.0.0.0`

but I'm not sure what is the official way to do that.

Amnon / Vlad, can you please help?

Thanks,

Benny

--
You received this message because you are subscribed to the Google Groups "ScyllaDB users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to scylladb-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/5a4c955e-f0e3-4fbc-a14b-9c60d8e0ebffn%40googlegroups.com.

[Felipe Mendes]

This should be defined at /etc/default/scylla-jmx (or /etc/sysconfig/scylla-jmx for RHEL variants):

SCYLLA_JMX_ADDR="-ja ::1"

Keep in mind that - by default - the RMI hostname will be bound to localhost and it may typically be a IPV4 alias to 127.0.0.1. If you want it to listen only locally and your system configures a different alias for IPV6 addresses (such as ip6-localhost as in Ubuntu), you can also append the following to the same parameter above:

SCYLLA_JMX_ADDR="-ja ::1 -Djava.rmi.server.hostname=ip6-localhost"

To view this discussion on the web visit https://groups.google.com/d/msgid/scylladb-users/3f12568c85fdc306741a851e3e5376fbb66a8d64.camel%40scylladb.com.

--
Felipe Mendes
Solutions Architect
ScyllaDB

[Yang Liyuan]

Thanks for your help, but i tried your method, but unfortunatly, it did not work expectlly.

、、、

[root@node1 /]# ps -ef
UID          PID    PPID  C STIME TTY          TIME CMD
root           1       0  0 12:45 ?        00:00:00 /opt/scylladb/python3/bin/python3 /opt/scylladb/python3/bin/../libexec/python3.9.bin -s /docker-entrypoint.py
root          26       1  0 12:45 ?        00:00:00 /usr/bin/python /usr/bin/supervisord -c /etc/supervisord.conf
root          29      26 37 12:45 ?        00:00:14 /usr/bin/scylla --alternator-timeout-in-ms 20000 --alternator-address fd88:5110:a350:ff02:9999:0:6447:87b --alternator-port 8000 --alternat
root          30      26  0 12:45 ?        00:00:00 /bin/bash /scylla-housekeeping-service.sh
root          32      26  4 12:45 ?        00:00:01 /opt/scylladb/jmx/symlinks/scylla-jmx -Dapiport=10002 -Dapiaddress=fd88:5110:a350:ff02:9999:0:6447:87b -Xmx256m -XX:+UseSerialGC -XX:+HeapD
root          33      26  0 12:45 ?        00:00:00 rsyslogd -n
root         139      30  0 12:45 ?        00:00:00 sleep 1d
root         160       0  0 12:45 pts/0    00:00:00 /bin/bash
root         173     160  0 12:45 pts/0    00:00:00 ps -ef
[root@node1 /]# nodetool -h fd88:5110:a350:ff02:9999:0:6447:87b status
nodetool: Failed to connect to 'fd88:5110:a350:ff02:9999:0:6447:87b:7199' - ConnectException: 'Connection refused (Connection refused)'.

、、、