Hello!
From the description you gave it is hard to find out what is happening without some more information. Can you share your configuration, please? Do you use the internal source, wildcard file-source?
We also have a tool that can be used to collect environment and information called 'syslog-ng-debun'. It can collect sensitive data, so be sure to replace/remove those before sending the debun, e.g. IP addresses and passwords from config, etc. https://github.com/balabit/syslog-ng/blob/master/contrib/syslog-ng-debun https://github.com/balabit/syslog-ng/blob/master/contrib/README.syslog-ng-de... As you are using Solaris as syslog-ng 3.12.1 have you built it from source or used a package? Best Regards, Gabor On Thu, Feb 15, 2018 at 6:13 PM, Declan White <declanw@is.bbc.co.uk> wrote:
The data in the core dump would need to stay in my hands, so that's no good.
I'm going to have to toss syslog-ng out :( Silencing sources without logging anything, when things went wrong in the most common way, is a complete deal breaker.
- Declan
On Wed, Feb 14, 2018 at 09:52:37PM +0100, Fabien Wernli wrote:
Hi,
this is very unfortunate. I'm sure a core dump of the process would be helpful to the developers. Not sure if gcore or similar is available on Solaris though.
cheers
____________________________________________________________
Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product= syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq
-- Declan White ____________________________________________________________ __________________ Member info: https://lists.balabit.hu/mailman/listinfo/syslog-ng Documentation: http://www.balabit.com/support/documentation/?product= syslog-ng FAQ: http://www.balabit.com/wiki/syslog-ng-faq