Great, thanks. I've stopped graylog2 and here's what I got:
2014-04-18 09:45:53 ERROR om_udp apr_socket_send failed;Connection refused
2014-04-18 09:45:55 ERROR last message repeated 2 times
2014-04-18 09:45:56 ERROR om_udp apr_socket_send failed;Connection refused
2014-04-18 09:45:58 ERROR last message repeated 2 times
2014-04-18 09:45:59 ERROR om_udp apr_socket_send failed;Connection refused
2014-04-18 09:46:01 ERROR last message repeated 2 times
2014-04-18 09:46:02 ERROR om_udp apr_socket_send failed;Connection refused
2014-04-18 09:45:46 ERROR om_udp apr_socket_send failed;Connection refused
2014-04-18 09:46:31 INFO got SIGUSR1, dumping debug information
2014-04-18 09:46:31 INFO event queue has 6 events;jobgroup with priority
10;job of module nginx_access/im_file, events: 0;job of module
nginx_error/im_file, events: 0;job of module httpd_access/im_file, events:
0;job of module httpd_error/im_file, events: 0;job of module
graylog2/om_udp, events: 0;non-module job, events: 0;jobgroup with priority
99;non-module job, events: 0;non-module job, events: 0;[route 1]; -
nginx_access: type INPUT, status: RUNNING queuesize: 0; - graylog2: type
OUTPUT, status: RUNNING queuesize: 107;[route 2]; - nginx_error: type
INPUT, status: RUNNING queuesize: 0; - graylog2: type OUTPUT, status:
RUNNING queuesize: 107;[route 3]; - httpd_access: type INPUT, status:
PAUSED queuesize: 0; - graylog2: type OUTPUT, status: RUNNING queuesize:
107;[route 4]; - httpd_error: type INPUT, status: PAUSED queuesize: 0; -
graylog2: type OUTPUT, status: RUNNING queuesize: 107;
As you can see, I have 4 inputs: apache access logs, apache error logs,
nginx access logs and nginx error logs.
I hope this helps. Thanks!
On 18 April 2014 16:28, Botond Botyanszki <b...@nxlog.org> wrote:
> Hi,
>
> Can you send a SIGUSR1 to the nxlog process and check what it prints?
> If the output module's status is STOPPED, then this is probably a bug
> since it should retry sending the datagram(s).
>
> Regards,
> Botond
>
> On Fri, 18 Apr 2014 16:05:47 +0300
> Silvian Cretu <silvian.cr...@gmail.com> wrote:
>
> > Hi guys,
> > I have several nxlog instances parsing Apache logs (module im_file and
> > xm_gelf) and then forwarding them to a graylog2 server that listens on
> UDP
> > (module om_udp)
> >
> > Whenever I have to restart the graylog2 server (for configuration
> changes),
> > the nxlog instances stop sending logs and show this in the log:
> >
> > 2014-04-18 08:33:44 ERROR om_udp apr_socket_send failed;Connection
> refused
> >
> > And I have to restart nxlog on all machines... Do you have any idea on
> how
> > to work around this?
> >
> > Thanks!
> >
> > --
> > Silvian Cretu
>
>
> ------------------------------------------------------------------------------
> Learn Graph Databases - Download FREE O'Reilly Book
> "Graph Databases" is the definitive new guide to graph databases and their
> applications. Written by three acclaimed leaders in the field,
> this first edition is now available. Download your free book today!
> http://p.sf.net/sfu/NeoTech
> _______________________________________________
> nxlog-ce-users mailing list
> nxlog-ce-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
>
--
Silvian Cretu,
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
nxlog-ce-users mailing list
nxlog-ce-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
