Mailing-List: contact user-help@flume.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@flume.apache.org
Received-SPF: pass (nike.apache.org: domain of ykim@crunchyroll.com designates
 209.85.160.47 as permitted sender)
Date: Tue, 10 Jul 2012 13:59:21 -0700
From: Young Kim <ykim@crunchyroll.com>
To: flume-user@incubator.apache.org
Message-ID: <344947061FA64D53ACF94F2D6F4123A1@crunchyroll.com>
Subject: flume-ng syslogtcp issue
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="4ffc97a9_2443a858_d6"

--4ffc97a9_2443a858_d6
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hey guys, 

I've been trying to use flume-ng (build in trunk) to read syslogs through tcp then write to a flat file, as seen in this configuration:

# Source, sink, and channel name below
syslog-agent.channels = rmc
syslog-agent.sources = syslog
syslog-agent.sinks = flat

# Configure channels
syslog-agent.channels.rmc.type = memory

# Configure sources
syslog-agent.sources.syslog.type = syslogTcp
syslog-agent.sources.syslog.port = 5140
syslog-agent.sources.syslog.host = 172.17.1.92
syslog-agent.sources.syslog.channels = rmc

# Configure sinks
syslog-agent.sinks.flat.type = FILE_ROLL
syslog-agent.sinks.flat.directory = /Users/ykim/Desktop/test
syslog-agent.sinks.flat.rollInterval = 0
syslog-agent.sinks.flat.channels = rmc


After a bit of wrangling with rsyslog configurations, it appeared as if rsyslog wasn't sending any packets. However, I decided to try out flume-og with a simple dump syslogTcp, and it correctly reads the syslog. At this point, I'm a bit lost and not sure what else to look at. Hopefully, someone on here can shed some light on what could be wrong. 

Thanks,
Young Kim


--4ffc97a9_2443a858_d6
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


                <div>
                    Hey guys,
                </div><div><br></div><div>I've been trying to use flume-n=
g (build in trunk) to read syslogs through tcp then write to a flat file,=
 as seen in this configuration:</div><div><br></div><div><div>=23 Source,=
 sink, and channel name below</div><div>syslog-agent.channels =3D rmc</di=
v><div>syslog-agent.sources =3D syslog</div><div>syslog-agent.sinks =3D f=
lat</div><div><br></div><div>=23 Configure channels</div><div>syslog-agen=
t.channels.rmc.type =3D memory</div><div><br></div><div>=23 Configure sou=
rces</div><div>syslog-agent.sources.syslog.type =3D syslogTcp</div><div>s=
yslog-agent.sources.syslog.port =3D 5140</div><div>syslog-agent.sources.s=
yslog.host =3D 172.17.1.92</div><div>syslog-agent.sources.syslog.channels=
 =3D rmc</div><div><br></div><div>=23 Configure sinks</div><div>syslog-ag=
ent.sinks.flat.type =3D =46ILE=5FROLL</div><div>syslog-agent.sinks.flat.d=
irectory =3D /Users/ykim/Desktop/test</div><div>syslog-agent.sinks.flat.r=
ollInterval =3D 0</div><div>syslog-agent.sinks.flat.channels =3D rmc</div=
></div><div><br></div><div>After a bit of wrangling with rsyslog configur=
ations, it appeared as if rsyslog wasn't sending any packets. However, I =
decided to try out flume-og with a simple dump syslogTcp, and it correctl=
y reads the syslog. At this point, I'm a bit lost and not sure what else =
to look at. Hopefully, someone on here can shed some light on what could =
be wrong.</div>
                <div><div><br></div>Thanks,<br>Young Kim<br><div><br></di=
v></div>
            
--4ffc97a9_2443a858_d6--