{"action":"created","issue":{"url":"https://api.github.com/repos/balabit/syslog-ng/issues/713","labels_url":"https://api.github.com/repos/balabit/syslog-ng/issues/713/labels{/name}","comments_url":"https://api.github.com/repos/balabit/syslog-ng/issues/713/comments","events_url":"https://api.github.com/repos/balabit/syslog-ng/issues/713/events","html_url":"https://github.com/balabit/syslog-ng/issues/713","id":107963414,"number":713,"title":"syslog-ng reload causes mod-journal to re-read all messages ever since","user":{"login":"zstyblik","id":6183869,"avatar_url":"https://avatars.githubusercontent.com/u/6183869?v=3","gravatar_id":"","url":"https://api.github.com/users/zstyblik","html_url":"https://github.com/zstyblik","followers_url":"https://api.github.com/users/zstyblik/followers","following_url":"https://api.github.com/users/zstyblik/following{/other_user}","gists_url":"https://api.github.com/users/zstyblik/gists{/gist_id}","starred_url":"https://api.github.com/users/zstyblik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zstyblik/subscriptions","organizations_url":"https://api.github.com/users/zstyblik/orgs","repos_url":"https://api.github.com/users/zstyblik/repos","events_url":"https://api.github.com/users/zstyblik/events{/privacy}","received_events_url":"https://api.github.com/users/zstyblik/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":54,"created_at":"2015-09-23T17:02:57Z","updated_at":"2015-10-11T07:51:11Z","closed_at":null,"body":"EDIT: original message removed\r\n\r\nHello,\r\n\r\nwe have syslog-ng 3.6.4-1 with mod-journal. When syslog-ng is reloaded, eg. via `/etc/init.d/syslog-ng reload`, all syslog messages there ever were since syslog-ng 3.6.4 has been installed are read and send/logged again. I get syslog messages as far as Sep 9.\r\nI believe mod-journal is having some problem keeping the track of which messages have been processed and which not. Machine has been rebooted several times since installation of syslog-ng, so that shouldn't be it. Configuration is pretty much stock one as far as local machine goes.\r\n\r\nThank you in advance.\r\n\r\nKnown information so far:\r\n* reproducible on OS Debian 8 Jessie and Ubuntu 15.04 Vivid\r\n* triggered by combination of `rewrite()` in `network()` destination and destinations `/var/log/syslog` and `/var/log/daemon.log` in `/etc/syslog-ng/syslog-ng.conf`\r\n* some `d_console_all` destinations trigger this as well, although these are commented out by default\r\n* if either `rewrite()` or `/var/log/syslog` and `/var/log/daemon.log` are removed, issue is resolved"},"comment":{"url":"https://api.github.com/repos/balabit/syslog-ng/issues/comments/147167215","html_url":"https://github.com/balabit/syslog-ng/issues/713#issuecomment-147167215","issue_url":"https://api.github.com/repos/balabit/syslog-ng/issues/713","id":147167215,"user":{"login":"zstyblik","id":6183869,"avatar_url":"https://avatars.githubusercontent.com/u/6183869?v=3","gravatar_id":"","url":"https://api.github.com/users/zstyblik","html_url":"https://github.com/zstyblik","followers_url":"https://api.github.com/users/zstyblik/followers","following_url":"https://api.github.com/users/zstyblik/following{/other_user}","gists_url":"https://api.github.com/users/zstyblik/gists{/gist_id}","starred_url":"https://api.github.com/users/zstyblik/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zstyblik/subscriptions","organizations_url":"https://api.github.com/users/zstyblik/orgs","repos_url":"https://api.github.com/users/zstyblik/repos","events_url":"https://api.github.com/users/zstyblik/events{/privacy}","received_events_url":"https://api.github.com/users/zstyblik/received_events","type":"User","site_admin":false},"created_at":"2015-10-11T07:51:11Z","updated_at":"2015-10-11T07:51:11Z","body":"> It seems that compiling logmsg.c without optimization resolves the issue, so there's something in that file that when compiled with gcc (Debian 4.9.2-10) 4.9.2 causes the bug.\r\n\r\nAll I have to say about this is ... heh! :-S"}}