[Bug 677248] New: syslog-ng causes oom
https://bugzilla.novell.com/show_bug.cgi?id=677248 https://bugzilla.novell.com/show_bug.cgi?id=677248#c0 Summary: syslog-ng causes oom Classification: openSUSE Product: openSUSE 11.4 Version: Factory Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: Basesystem AssignedTo: mt@novell.com ReportedBy: jslaby@novell.com QAContact: qa@suse.de Found By: --- Blocker: --- Created an attachment (id=417723) --> (http://bugzilla.novell.com/attachment.cgi?id=417723) dmesg after OOM I suspended and resumed and then the OOM killer had to kill some process due to OOM. dmesg says afterwards: [ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj name [ 375] 0 375 5308 36 1 -17 -1000 udevd [ 902] 0 902 6059 1 0 0 0 syslog-ng [ 903] 0 903 714564 440516 0 0 0 syslog-ng .. Out of memory: Kill process 903 (syslog-ng) score 746 or sacrifice child Killed process 903 (syslog-ng) total-vm:2858256kB, anon-rss:1761692kB, file-rss:368kB Well, what's in the 440 megs? Perhaps it's a leak. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c1
--- Comment #1 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c2
--- Comment #2 from Jiri Slaby
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c3
Marius Tomaschewski
Next resume, next OOM: # ps aux|grep syslo root 11164 0.1 62.8 2245300 1292228 ? Ds 11:00 0:42 /sbin/syslog-ng
Hmm, 1.2G of mem.
No idea what this could be -- have to take a look and discuss with upstream. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c4
--- Comment #4 from peter czanik
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c5
--- Comment #5 from Jiri Slaby
- how long does it take for syslog-ng to reach this size?
I don't know exactly. I reproduced it twice a day.
- could you post your config (if it is any different from the default one)
Ok, I was using an old config file (attached). It was complaining: Configuration file has no version number, assuming syslog-ng 2.1 format. Please add @version: maj.min to the beginning of the file; WARNING: Configuration file format is too old, please update it to use the 3.2 format as some constructs might operate inefficiently; WARNING: global: the default value of chain_hostnames is changing to 'no' in version 3.0, please update your configuration accordingly; Your configuration file uses an obsoleted keyword, please update your configuration; keyword='sync', change='flush_lines' Your configuration file uses an obsoleted keyword, please update your configuration; keyword='stats', change='stats_freq' WARNING: input: sources do not remove new-line characters from messages by default in version 3.0, please add 'no-multi-line' flag to your configuration if you want to retain this functionality; WARNING: the expected message format is being changed for unix-domain transports to improve syslogd compatibity with syslog-ng 3.2. If you are using custom applications which bypass the syslog() API, you might need the 'expect-hostname' flag to get the old behaviour back; WARNING: filters do not store matches in macros by default in 3.0, please update your configuration by using an explicit 'store-matches' flag to achieve that; WARNING: the match() filter without the use of the value() option is deprecated and hinders performance, please update your configuration; WARNING: template: the default value for template-escape is changing to 'no' in version 3.0, please update your configuration file accordingly; WARNING: Your configuration uses a newly introduced reserved word as identifier, please use a different name or enclose it in quotes; keyword='null', config-version='2.1', version='3.0', filename='/etc/syslog-ng/syslog-ng.conf', line='180:13' WARNING: Your configuration uses a newly introduced reserved word as identifier, please use a different name or enclose it in quotes; keyword='null', config-version='2.1', version='3.0', filename='/etc/syslog-ng/syslog-ng.conf', line='186:54' Maybe this was the reason? I moved syslog-ng.conf.rpmnew to syslog-ng.conf, so let's see what will happen. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c6
--- Comment #6 from peter czanik
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c7
--- Comment #7 from Jiri Slaby
BTW: Why did you have such an old config file?
I don't know. Maybe I did some changes a while ago and now it didn't update. The new one was stored as .rpmnew. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c8
--- Comment #8 from Marius Tomaschewski
https://bugzilla.novell.com/show_bug.cgi?id=677248
https://bugzilla.novell.com/show_bug.cgi?id=677248#c9
--- Comment #9 from Jiri Slaby
are you using systemd or sysvinit?
Now I use systemd with rsyslog (due to other bugs). At the time of the report, I'm not sure. But guessing from dmesg (there are no messages which systemd outputs to klog) sysvinit. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@novell.com