[rsyslog] rsyslog status ABRT or SEGV

2017-11-07 Thread Войнович Андрей Александрович via rsyslog
Hi all! I see the following messages in my syslog: Nov 8 08:42:56 dc-zbx rsyslogd: [origin software="rsyslogd" swVersion="8.4.2" x-pid="13223" x-info="http://www.rsyslog.com";] start Nov 8 08:42:56 dc-zbx systemd[1]: rsyslog.service: main process exited, code=killed, status=11/SEGV Nov 8 08:4

Re: [rsyslog] Legacy FWD Failes on startup (v8)

2017-11-07 Thread deoren
On 11/7/2017 12:25 PM, deoren wrote: On 11/7/2017 10:31 AM, matthew.gaetano wrote: With the exception of the relation to storage, yes, for the most part. We encountered the issue on a physical server using SCSI/SATA drives. Our secondary tester were in vmware. I initially emphasized the boot s

Re: [rsyslog] ommysql database queue bottleneck

2017-11-07 Thread Steven Libby via rsyslog
We had configured large batches (8192) for the main queue, action queue, and udp input module. However, after a brief debugging session, it appears that at least two of these settings are not being honored... The database action queue seems to be deleting maximum batch sizes of 8 at a time: 7968

Re: [rsyslog] Legacy FWD Failes on startup (v8)

2017-11-07 Thread deoren
On 11/7/2017 10:31 AM, matthew.gaetano wrote: With the exception of the relation to storage, yes, for the most part. We encountered the issue on a physical server using SCSI/SATA drives. Our secondary tester were in vmware. I initially emphasized the boot speed from running the Ubuntu 16.04 VM

Re: [rsyslog] Legacy FWD Failes on startup (v8)

2017-11-07 Thread matthew.gaetano
With the exception of the relation to storage, yes, for the most part. We encountered the issue on a physical server using SCSI/SATA drives. Our secondary tester were in vmware. It appears someone else has posted a similar issue already as well @ https://github.com/rsyslog/rsyslog/issues/1694 ~Re

Re: [rsyslog] Legacy FWD Failes on startup (v8)

2017-11-07 Thread deoren
https://github.com/rsyslog/rsyslog/issues/1656 See if that matches what you are fighting with. On November 7, 2017 9:51:51 AM CST, "matthew.gaetano" wrote: >Queue's aside, regardless of the order rsyslog loads (before or after >network) its retry function should not stall. As it currently stand

Re: [rsyslog] Legacy FWD Failes on startup (v8)

2017-11-07 Thread matthew.gaetano
Queue's aside, regardless of the order rsyslog loads (before or after network) its retry function should not stall. As it currently stands under CentOS 7.x and Rsyslog v8.x if a configuration uses FQDNs rather than IPs and the rsyslog server starts prior to the network forwarding actions suspend an