Hi, Thank you for the feedback. Since this is affecting more community edition users, I have raised the priority of the issue and it should be fixed when time permits. I'll let you know when the fix is available. Note that there is also commercial support for the community edition in case this is urgent.
Regards, Botond On Tue, 22 Apr 2014 11:27:16 +0300 Silvian Cretu <silvian.cr...@gmail.com> wrote: > Hi guys, > I was away during the Easter vacation. And unfortunately, graylog2 crashed > during this period. Even after restarting it and waiting for more than 2 > hours, none of the 9 nxlog instances started sending logs to graylog2, > although their queues appear as running: > > 2014-04-22 04:22:06 INFO got SIGUSR1, dumping debug information > 2014-04-22 04:22:06 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: 105;[route 2]; - nginx_error: type > INPUT, status: RUNNING queuesize: 0; - graylog2: type OUTPUT, status: > RUNNING queuesize: 105;[route 3]; - httpd_access: type INPUT, status: > PAUSED queuesize: 0; - graylog2: type OUTPUT, status: RUNNING queuesize: > 105;[route 4]; - httpd_error: type INPUT, status: PAUSED queuesize: 0; - > graylog2: type OUTPUT, status: RUNNING queuesize: 105; > > So, I guess this can be considered a bug... > > Thanks for the help so far, guys! > > > On 18 April 2014 18:22, Javier Barroso <javibarr...@gmail.com> wrote: > > > Hello, > > El 18/04/2014 15:07, "Silvian Cretu" <silvian.cr...@gmail.com> escribió: > > > > > > > > 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? > > > > I hit with that behaviour a tome ago[1]. While it is not solved at nxlog, > > we will use logcheck , monit, or similar (zabbix un our case) to restart > > nxlog when message march with last line in the log file > > > > Thank you > > > > [1] > > https://www.mail-archive.com/nxlog-ce-users@lists.sourceforge.net/msg00465.html > > > > > > -- > Silvian Cretu, > 0743036414 ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ nxlog-ce-users mailing list nxlog-ce-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/nxlog-ce-users
