So it looks like it is the EMAIL parser in patterndb that completely fails Any use of the @EMAIL@ parser causes a segmentation fault. On 09/21/2015 09:31 AM, Evan Rempel wrote:
Has anyone noticed the segmentation fault in patterndb tool when testing some patterns. The pattern database worked fine under syslog-ng 3.6.3 (and earlier).
[xerr@wolverine ~]$ /usr/local/bin/pdbtool --validate test --rule-id ea7cd8ed-0fb7-46d7-8a65-13f42bd8a939 pattern2.xml pattern2.xml validates Testing message: program='ageoutboundquota2' message='Updating S3:walkerh@uvic.ca:24.85.242.83 in (1, 1, 1, 1, 5, 7, 3, 3, 6, 7, 7, 7, 12, 12) -> (0, 0, 1, 1, 5, 7, 3, 3, 6, 7, 7, 7, 12, 12 (Quota 100,1000))' Segmentation fault
I have trimmed the pattern database down to a single program with its patterns and tests.
I have not yet determined exactly what it is that causes this.
Comments welcomed!
Evan Rempel. ______________________________________________________________________________ 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
-- Evan Rempel erempel@uvic.ca Senior Systems Administrator 250.721.7691 Data Centre Services, University Systems, University of Victoria