1
votes

This question could apply to any Java process that listens on a port on a VM instance on Google Compute Engine.

I'm trying to establish a TCP connection on port 9090, where an Apache Flume-ng process is running on the VM. I've added a firewall rule for 0.0.0.0/0 TCP:9090 on the default network, and I can see the process is listening on that port.

I have tried both the ephemeral host IP, and static host IP when trying to connect. I'm trying to connect via a Flume-ng client on a local Web app, which when configured for local routing works. It is configured like such

<appender name="FlumeAppender" type="DotNetFlumeNG.Client.log4net.FlumeAppender, DotNetFlumeNG.Client.log4net">
  <client>Thrift</client>
  <host>IP Address</host>
  <!--<host>127.0.0.1</host>-->
  <port>9090</port>
</appender>

I'm seeing TCP SocketExceptions from the flume client, does the application that is attempting to make the connection to port 9090 on GCE need to establish its own OAuth credentials? Or is there something else that I may be missing?

1

1 Answers

0
votes

I never used Apache Fume-ng, but wherever you've configured port to 9090 change binding/listening IP from localhost to 0.0.0.0 and it should be resolved.