Rundeck binds to IPv6

[Jae Kim]

Hi

I installed Rundeck on CentOS and launched it but it binds to the IPv6 address based on netstat -na command.

I tried editing rundeck-config.properties. 

I changed http://localhost:4440 to http://185.48.118.52:4440

I ran rundeckd stop and then rundeckd start. But still it still binds to IPv6 address.

How can I get it to bind to IPv4 address.

[Jae Kim]

[Jae Kim]

[Alex Honor]

Try adding this to your RDECK_JVM flags in /etc/rundeck/profile: -Djava.net.preferIPv4Stack=true

On Wed, Apr 19, 2017 at 11:31 AM, Jae Kim <jki...@gmail.com> wrote:

On Thursday, April 20, 2017 at 3:29:32 AM UTC+9, Jae Kim wrote:

On Thursday, April 20, 2017 at 12:09:14 AM UTC+9, Jae Kim wrote:

Hi

I installed Rundeck on CentOS and launched it but it binds to the IPv6 address based on netstat -na command.

I tried editing rundeck-config.properties. 

I changed http://localhost:4440 to http://185.48.118.52:4440

I ran rundeckd stop and then rundeckd start. But still it still binds to IPv6 address.

How can I get it to bind to IPv4 address.

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to rundeck-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/d845f4c7-41c9-4584-bc66-b62c39230e65%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Alex Honor

[Rundeck | a...@rundeck.com ]

[Jae Kim]

[Jae Kim]

I added the argument as below

[Jae Kim]

I then restarted Rundeck

It still bind to the IPv6

[Alex Honor]

Ok, try both: -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to rundeck-discuss@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/567701f8-1a0e-4606-b551-321cb6bfad1d%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Jae Kim]

Still the same

On Thursday, April 20, 2017 at 4:18:31 AM UTC+9, Alex Honor wrote:

Ok, try both: -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true

On Wed, Apr 19, 2017 at 12:12 PM, Jae Kim <jki...@gmail.com> wrote:

I then restarted Rundeck

It still bind to the IPv6

On Thursday, April 20, 2017 at 4:08:11 AM UTC+9, Jae Kim wrote:

I added the argument as below

On Thursday, April 20, 2017 at 3:31:43 AM UTC+9, Jae Kim wrote:

On Thursday, April 20, 2017 at 3:29:32 AM UTC+9, Jae Kim wrote:

On Thursday, April 20, 2017 at 12:09:14 AM UTC+9, Jae Kim wrote:

Hi

I installed Rundeck on CentOS and launched it but it binds to the IPv6 address based on netstat -na command.

I tried editing rundeck-config.properties. 

I changed http://localhost:4440 to http://185.48.118.52:4440

I ran rundeckd stop and then rundeckd start. But still it still binds to IPv6 address.

How can I get it to bind to IPv4 address.

--
You received this message because you are subscribed to the Google Groups "rundeck-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discu...@googlegroups.com.
To post to this group, send email to rundeck...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/567701f8-1a0e-4606-b551-321cb6bfad1d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alex Honor

[Rundeck | a....@rundeck.com ]

[Jae Kim]

Here is my ifconfig

[Jae Kim]

Here is my Java version

[Jae Kim]

Should I try installing Oracle Java?

[Kofi AHIANYO-AKAKPO]

Hi Kim

Netstat might not work as you think. Rundeck might actually bind to the IPv4 address but still netstat could show you something confusing in its output.

Try checking with 'ss' command.

Ex: ss -plt4n | grep 4440

=> will show you rundeck process (-p) if it is listening (-l) in TCP (-t) IPv4 (-4). -n is for showing numbers in ss output, not hostnames or ports names.

This is a common mistake we make when dealing with IPv6 enabled system running in compatibility mode i think (https://www.ietf.org/rfc/rfc3493.txt).

Tell me if that could be the case here.

Kofi.

To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to rundeck-discuss@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/0b149929-d2fd-48e6-8f0a-fd99e00f66ae%40googlegroups.com.

[Jae Kim]

I ran the command

[Kofi]

Kim

I've just noticed a typo in your RDECK_JVM parameter.

It says -Djava.net.perferIPv4Stack=true instead of -Djava.net.preferIPv4Stack=true.

1) Could you double check that the correct parameter name is in place please ?

2) What's in your /etc/hosts file ?

3) Can you run :

nc -4 -v localhost 4440 (replace localhost by whatever you have defined rundeck to listen to).

To unsubscribe from this group and stop receiving emails from it, send an email to rundeck-discuss+unsubscribe@googlegroups.com.
To post to this group, send email to rundeck-discuss@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rundeck-discuss/126d88b3-3e6d-4cd2-b675-2a146d5159d6%40googlegroups.com.

[Jae Kim]

We ended up creating a topology in the cloud with the IPv6 disabled

[Nick Moore]

I got the same output with netstat however when I nmap the ipv4 address I can see the port open.

(base) nmoore@itnet-bastion0:~$ nmap 10.245.75.245 -p 4440
Starting Nmap 7.92 ( https://nmap.org ) at 2022-01-28 20:48 UTC
Nmap scan report for itnet-bastion0 (10.245.75.245)
Host is up (0.00011s latency).

PORT     STATE SERVICE
4440/tcp open  unknown

Nmap done: 1 IP address (1 host up) scanned in 0.08 seconds