Created Inputs ports not listining

Graylog Central (peer support)
1

Hello,
Please need help.

I’ve created inputs in a new graylog installation and it seems to only listen on ipv6 not ipv4.

Can someone please help on making the application listen as well on IPv4?

]$ netstat -anp | grep 12201
(No info could be read for “-p”: geteuid()=1000 but you should be root.)
tcp6 0 0 :::12201 :::* LISTEN -

netstat -anp | grep 65514
(No info could be read for “-p”: geteuid()=1000 but you should be root.)
udp6 0 0 :::65514 :::* -

regards,
AM

2

What OS did you use? Did you have a multi homed setup? Did you checked if the inputs really only listen on the ipv6?

3

Hello,

What OS did you use?
I’m using CentOS.

Did you have a multi homed setup?
NO, single homed.

Did you checked if the inputs really only listen on the ipv6?

netstat -anp | grep 12201
(No info could be read for “-p”: geteuid()=1000 but you should be root.)
tcp6 0 0 :::12201 :::* LISTEN -

netstat -anp | grep 65514
(No info could be read for “-p”: geteuid()=1000 but you should be root.)
udp6 0 0 :::65514 :::* -

Regards,

4

Did you notice the quote from the linked thread?

5

Hello Jan,

Didin’t noticed. Can you please point me out?

I’ve seen in another thread that we need to change some viriable on the system,

GRAYLOG_SERVER_JAVA_OPTS

located at /etc/sysconfig/graylog-server

but don’t know how.

Best regards,

AR

6
7

Hello,

I’m aware of that, but I don’t see any tcp4 LISTEN port while issuing the netstat command.

Is there a way to only activate the application to LISTEN on TCPv4? If so, can you help me out?

Regards,

8

you might find the information in this thread helpful Ipv6 to Ipv4 help me

9

Hello Jan,

Thanks for all your help.

At the end I found that it was related to incompatibility between Elasticsearch 6 and Graylog

Regards,

10

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.