https://bugzilla.balabit.com/show_bug.cgi?id=219 Summary: log_msg_is_write_protected when a source is used in multiple log statments Product: syslog-ng Version: 3.4.x Platform: PC OS/Version: Linux Status: NEW Severity: critical Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: erempel@uvic.ca Type of the Report: --- Estimated Hours: 0.0 Created an attachment (id=71) --> (https://bugzilla.balabit.com/attachment.cgi?id=71) minimal syslog-ng.conf It appears that if a source is used in two different log statements, all branches use a write protected instance of the log message. Module loaded and initialized successfully; module='syslogformat' Running application hooks; hook='1' Running application hooks; hook='3' syslog-ng starting up; version='3.4.1' Syslog connection accepted; fd='12', client='AF_INET(142.104.141.3:40576)', local='AF_INET(0.0.0.0:514)' Incoming log entry; line='<134>2013-02-04T15:28:46-08:00 pangolin.comp.uvic.ca/pangolin.comp.uvic.ca action-handler[24020]: starting' Initializing destination file writer; template='/var/syslog/archive.log', filename='/var/syslog/archive.log' Filter node evaluation result; result='not-match' Filter node evaluation result; result='not-match', type='filter(f_short_host_at)' ** ERROR:logmsg.c:535:log_msg_set_value_indirect: assertion failed: (!log_msg_is_write_protected(self)) Attached is a very simple config file that reproduces this issue. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.