Thanks Lennart for reply :)
So this is what I've done
1. Started rsyslog on machine on 12500.
2. While configuring the graylog2 input mentioned the
ip: 0.0.0.0
port: 12500
3. then the error came.
Another problem I got, I was trying to send my logs from my mac to graylog2
but could not. Iv'e followed this guide
http://support.torch.sh/help/kb/getting-your-logs-into-graylog2/sending-with-osx-syslogd
Any help would be appreciated :)
-suresh
On Fri, Mar 7, 2014 at 6:51 PM, Lennart Koopmann <lenn...@torch.sh> wrote:
> "Address already in use" - Something is already listening on that port.
>
> On Thu, Mar 6, 2014 at 5:02 PM, Suresh Prajapati
> <er.sureshprajap...@gmail.com> wrote:
> > Hi ,
> >
> > I've started rsyslog on 12500 port . Its still saying it can not bind to
> > that port for input
> >
> > An input has failed to start. a few seconds ago
> >
> > Input 53189bb60cf201071467bacd has failed to start on node
> > aaa96817-0fc9-4759-a806-30cea824a926 for this reason: "Could not bind
> syslog
> > TCP input to address /0.0.0.0:12500, Failed to bind to: /0.0.0.0:12500,
> > Address already in use". This means that you are unable to receive any
> > messages from this input. This is mostly an indication for a
> > misconfiguration or an error. You can click here to solve this
> >
> >
> >
> > On Thursday, 13 February 2014 18:48:29 UTC+5:30, lennart wrote:
> >>
> >> Great! Thanks for posting your solution.
> >>
> >> On Thu, Feb 13, 2014 at 1:48 PM, André Coelho <coe...@gmail.com> wrote:
> >> > I'm configuring a switch that does not have the option to set other
> port
> >> > for
> >> > the destination log server, it only sends to port 514.
> >> >
> >> > I have tried authbind but it does not work with port 514
> >> > I have tried setcap 'cap_net_bind_service=+ep' /usr/bin/java but it
> does
> >> > not
> >> > work
> >> >
> >> > Then finally using IPTABLES worked:
> >> >
> >> > iptables -A PREROUTING -t nat -i eth0 -p udp --dport 514 -j REDIRECT
> >> > --to-port 10515
> >> >
> >> > Thanks for you help
> >> >
> >> >
> >> > Em quarta-feira, 12 de fevereiro de 2014 17h14min51s UTC-2, lennart
> >> > escreveu:
> >> >>
> >> >> You need to be root to bind sockets on ports <=1024 on most *NIX
> >> >> systems. Either run graylog2-server as root (not recommended) or use
> a
> >> >> port higher than 1024. You could also try to give the local user
> than
> >> >> runs graylog2-server permission to bind to those restricted ports,
> but
> >> >> usually just choosing a higher port is the easiest solution.
> >> >>
> >> >> On Wed, Feb 12, 2014 at 7:19 PM, André Coelho <coe...@gmail.com>
> wrote:
> >> >> > Hi All
> >> >> > I have this version of graylog installed on ubuntu 12.04:
> >> >> > Graylog2-server (Current: 0.20-rc.1-1)
> >> >> > Graylog2-web (Current: 0.20-rc.2)
> >> >> > Graylog2-radio Current: 0.20-rc.2)
> >> >> >
> >> >> > When I try to add a global Syslog Input to listen on port 514 TCP
> or
> >> >> > UDP
> >> >> > (bind address: 0.0.0.0) the server gives this error:
> >> >> > Input 52fbb0d5e4b0a4cfa9f30f88 has failed to start on node
> >> >> > f728fbee-73f5-4a3a-a0f1-c10511eed089 for this reason: "Could not
> bind
> >> >> > UDP
> >> >> > syslog input to address /0.0.0.0:514, Failed to bind to:
> >> >> > /0.0.0.0:514,
> >> >> > Permission denied". This means that you are unable to receive any
> >> >> > messages
> >> >> > from this input. This is mostly an indication for a
> misconfiguration
> >> >> > or
> >> >> > an
> >> >> > error. You can click here to solve this
> >> >> > And the log looks like this:
> >> >> > 2014-02-12 16:16:39,732 ERROR: org.graylog2.inputs.InputRegistry -
> >> >> > The
> >> >> > [org.graylog2.inputs.syslog.udp.SyslogUDPInput] input with ID
> >> >> > <52fbba87e4b0f89aaac73a29> misfired. Reason: Could not bind UDP
> >> >> > syslog
> >> >> > input
> >> >> > to address /0.0.0.0:514, Failed to bind to: /0.0.0.0:514,
> Permission
> >> >> > denied
> >> >> >
> >> >> >
> >> >> > This looks like the user that graylog runs does not have permission
> >> >> > to
> >> >> > bind
> >> >> > port 514.
> >> >> >
> >> >> > Someone knows how to fix this?
> >> >> >
> >> >> > Thanks
> >> >> >
> >> >> > --
> >> >> > You received this message because you are subscribed to the Google
> >> >> > Groups
> >> >> > "graylog2" group.
> >> >> > To unsubscribe from this group and stop receiving emails from it,
> >> >> > send
> >> >> > an
> >> >> > email to graylog2+u...@googlegroups.com.
> >> >> > For more options, visit https://groups.google.com/groups/opt_out.
> >> >
> >> > --
> >> > You received this message because you are subscribed to the Google
> >> > Groups
> >> > "graylog2" group.
> >> > To unsubscribe from this group and stop receiving emails from it, send
> >> > an
> >> > email to graylog2+u...@googlegroups.com.
> >> > For more options, visit https://groups.google.com/groups/opt_out.
> >
> > --
> > You received this message because you are subscribed to the Google Groups
> > "graylog2" group.
> > To unsubscribe from this group and stop receiving emails from it, send an
> > email to graylog2+unsubscr...@googlegroups.com.
> > For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "graylog2" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/graylog2/5iLepNboyOI/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to
> graylog2+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
--
You received this message because you are subscribed to the Google Groups
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to graylog2+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
