https://pulp.plan.io/https://pulp.plan.io/favicon.ico2015-02-28T23:18:19ZPulpPulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=14672015-02-28T23:18:19Zrbarlow
<ul></ul><p>From Trey Dockendorf on pulp-list:</p>
<p>"I've been using this on EL6</p>
<p>:programname, isequal, "pulp" -/var/log/pulp.log<br>
& ~</p>
<p>I think as long as that comes before the line that sets the /var/log/messages logging then the "& ~" will discard the messages and keep them from making it to /var/log/messages."</p>
<p>+ This comment was cloned from <a href="https://bugzilla.redhat.com/show_bug.cgi?id=1180163#c1" class="external">Bugzilla #1180163 comment 1</a> +</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=23952015-03-19T20:56:40Zbmbouterbmbouter@redhat.com
<ul><li><strong>Category</strong> deleted (<del><i>1</i></del>)</li><li><strong>Tags</strong> <i>Documentation</i> added</li></ul><p>Documentation is now a Tag not a Category.</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=27922015-03-20T19:16:16Zbmbouterbmbouter@redhat.com
<ul><li><strong>Severity</strong> changed from <i>High</i> to <i>3. High</i></li></ul> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=33032015-04-10T16:38:35Zbmbouterbmbouter@redhat.com
<ul></ul><p>wrath0r on #pulp reported that the solution in <a href="https://pulp.plan.io/issues/654#note-1" class="external">comment 1</a> worked for him. This bug is to make that documentation change and send it to QE for testing.</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=33042015-04-10T16:39:51Zbmbouterbmbouter@redhat.com
<ul><li><strong>Priority</strong> changed from <i>Normal</i> to <i>High</i></li></ul><p>A lot of people get caught on this so I'm moving it to high priority. The other day I had 3 different users ask me how to configure rsyslogd on EL6 in one day!</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=33952015-04-14T18:59:23Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>NEW</i> to <i>ASSIGNED</i></li><li><strong>Assignee</strong> set to <i>jortel@redhat.com</i></li></ul> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=34052015-04-14T21:09:17Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>Adding this file: <em>/etc/rsyslog.d/pulp.conf</em></p>
<p>containing:</p>
<pre><code>:programname, startswith, "pulp" -/var/log/pulp.log
& ~
</code></pre>
<p>On RHEL 6.5 worked.</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=34172015-04-15T14:16:19Zrbarlow
<ul></ul><p>On 04/14/2015 05:09 PM, Pulp wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-11 priority-7 priority-high2 closed" title="Issue: Users are reporting that our rsyslog config example does not work (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/654">#654</a> has been updated by <a href="mailto:jortel@redhat.com" class="email">jortel@redhat.com</a>.</p>
<p>Adding this file: //etc/rsyslog.d/pulp.conf/</p>
<p>containing:</p>
<p>:programname, startswith, "pulp" -/var/log/pulp.log<br>
& ~</p>
<p>On RHEL 6.5 worked.</p>
</blockquote>
<p>We were advised with somewhat strong language from the rsyslog<br>
maintainer not to put files into /etc/rsyslog.d/, so we should not<br>
document this method.</p>
<p>--<br>
Randy Barlow</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=34512015-04-15T21:59:43Zjortel@redhat.comjortel@redhat.com
<ul></ul><p>rbarlow wrote:</p>
<blockquote>
<p>On 04/14/2015 05:09 PM, Pulp wrote:</p>
<blockquote>
<p>Issue <a class="issue tracker-1 status-11 priority-7 priority-high2 closed" title="Issue: Users are reporting that our rsyslog config example does not work (CLOSED - CURRENTRELEASE)" href="https://pulp.plan.io/issues/654">#654</a> has been updated by <a href="mailto:jortel@redhat.com" class="email">jortel@redhat.com</a>.</p>
<p>Adding this file: //etc/rsyslog.d/pulp.conf/</p>
<p>containing:</p>
<p>:programname, startswith, "pulp" -/var/log/pulp.log<br>
& ~</p>
<p>On RHEL 6.5 worked.</p>
</blockquote>
<p>We were advised with somewhat strong language from the rsyslog<br>
maintainer not to put files into /etc/rsyslog.d/, so we should not<br>
document this method.</p>
<p>--<br>
Randy Barlow</p>
</blockquote>
<p>"Oh, that's rich!" - <em>Krusty The Clown, 1995</em></p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=34942015-04-20T15:44:27Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>ASSIGNED</i> to <i>POST</i></li></ul><p><a href="https://github.com/pulp/pulp/pull/1802" class="external">https://github.com/pulp/pulp/pull/1802</a></p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=35282015-04-21T20:08:11Zjortel@redhat.comjortel@redhat.com
<ul><li><strong>Status</strong> changed from <i>POST</i> to <i>MODIFIED</i></li></ul> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=38232015-04-29T14:24:39Zrbarlow
<ul></ul><p><a href="mailto:jortel@redhat.com" class="email">jortel@redhat.com</a> wrote:</p>
<blockquote>
<p>"Oh, that's rich!" - <em>Krusty The Clown, 1995</em></p>
</blockquote>
<p>lol</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=38902015-05-02T22:09:18ZBen.StanleyBen.Stanley@exemail.com.au
<ul></ul><p>Could you please post a link to the comments from the rsyslog maintainer? I want to understand why they do not want files in /etc/rsyslog.d . It is my understanding that we create directories of config file fragments so that packages can easily configure their own appropriate settings without having to sed a shared configuration file.</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=41212015-05-05T21:00:25Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>MODIFIED</i> to <i>5</i></li><li><strong>Platform Release</strong> set to <i>2.6.1</i></li></ul> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=41752015-05-06T12:30:46Zbmbouterbmbouter@redhat.com
<ul></ul><p>QE, you can verify with this link: <a href="http://pulp.readthedocs.org/en/latest/user-guide/troubleshooting.html#rsyslogd" class="external">http://pulp.readthedocs.org/en/latest/user-guide/troubleshooting.html#rsyslogd</a></p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=42152015-05-07T12:56:52Zpthomas@redhat.com
<ul><li><strong>Status</strong> changed from <i>5</i> to <i>6</i></li></ul><p>verified</p>
<pre><code>https://pulp.readthedocs.org/en/latest/user-guide/troubleshooting.html#rsyslogd
<\pre>
</code></pre> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=43212015-05-13T15:26:44Ztheinric
<ul></ul><p>Ben.Stanley wrote:</p>
<blockquote>
<p>Could you please post a link to the comments from the rsyslog maintainer? I want to understand why they do not want files in /etc/rsyslog.d . It is my understanding that we create directories of config file fragments so that packages can easily configure their own appropriate settings without having to sed a shared configuration file.</p>
</blockquote>
<p>Here you have it directly from the source (Fedora, RHEL).<br>
The short answer is that rsyslog's configuration is not very well suited for being split into multiple pieces that are not aware of each other. Some options are global and changing them in one piece would affect the other pieces. The different pieces might be having conflicting requirements. The only way to make this work automatically (from users perspective) would be for all the packages shipping config fragments to be aware of all the other packages doing this and keep up with updates. Highway to hell.<br>
I'd prefer for packages to ship config fragments as samples that the user would revise and drop to rsyslog.d manually.</p>
<p>Still, sed-ing config files is probably the greater evil.</p> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=61372015-09-14T12:53:20Zdkliban@redhat.com
<ul><li><strong>Status</strong> changed from <i>6</i> to <i>CLOSED - CURRENTRELEASE</i></li></ul> Pulp - Issue #654: Users are reporting that our rsyslog config example does not workhttps://pulp.plan.io/issues/654?journal_id=401922019-04-15T21:06:50Zbmbouterbmbouter@redhat.com
<ul><li><strong>Tags</strong> <i>Pulp 2</i> added</li></ul>