<div dir="ltr"><div><div><div>><br>And I think that including<br>
everything from /var/log/messages is too much.<br>><br></div><br></div>only if regression fails we capture messages file, I dont think its a big overhead. <br><br>> But, I also did not check<br>
how big /var/log/messages is on a Jenkins slave<br>><br></div>Capturing last/active messages file should be fine.<br></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature"><div dir="ltr"><div>--Humble<br></div><br></div></div></div>
<br><div class="gmail_quote">On Thu, Dec 11, 2014 at 4:25 PM, Niels de Vos <span dir="ltr"><<a href="mailto:ndevos@redhat.com" target="_blank">ndevos@redhat.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Thu, Dec 11, 2014 at 03:45:28PM +0530, Humble Devassy Chirammal wrote:<br>
> ><br>
><br>
> I suggest to use 'logger -s' to add a marker that a regression test has<br>
> been started in /var/log/messages, and only copy the contents from after<br>
> the last marker into the archive<br>
> ><br>
><br>
> I doubt we need a marker, because its 'not' always we need to look at<br>
> 'messages' file to see whether its a system specific issue.<br>
<br>
</span>But how many lines should get gathered? And I think that including<br>
everything from /var/log/messages is too much. But, I also did not check<br>
how big /var/log/messages is on a Jenkins slave...<br>
<span class="HOEnZb"><font color="#888888"><br>
Niels<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
><br>
> --Humble<br>
><br>
><br>
> On Thu, Dec 11, 2014 at 3:38 PM, Niels de Vos <<a href="mailto:ndevos@redhat.com">ndevos@redhat.com</a>> wrote:<br>
><br>
> > On Thu, Dec 11, 2014 at 11:05:21AM +0530, Humble Devassy Chirammal wrote:<br>
> > > Hi Atin,<br>
> > ><br>
> > > Have a check at current version of regression.sh here:<br>
> > ><br>
> > ><br>
> > <a href="https://forge.gluster.org/gluster-patch-acceptance-tests/gluster-patch-acceptance-tests/blobs/master/regression.sh" target="_blank">https://forge.gluster.org/gluster-patch-acceptance-tests/gluster-patch-acceptance-tests/blobs/master/regression.sh</a><br>
> > ><br>
> > > It should be a small patch near to line 109.<br>
> ><br>
> > I suggest to use 'logger -s' to add a marker that a regression test has<br>
> > been started in /var/log/messages, and only copy the contents from after<br>
> > the last marker into the archive.<br>
> ><br>
> > Would that make sense?<br>
> ><br>
> > Thanks,<br>
> > Niels<br>
> ><br>
> > ><br>
> > > --Humble<br>
> > ><br>
> > > --Humble<br>
> > ><br>
> > ><br>
> > > On Thu, Dec 11, 2014 at 9:32 AM, Atin Mukherjee <<a href="mailto:amukherj@redhat.com">amukherj@redhat.com</a>><br>
> > wrote:<br>
> > ><br>
> > > > Hi Justin,<br>
> > > ><br>
> > > > The current regression.sh code doesn't capture /var/log/messages which<br>
> > > > means whether the system ran out of memory or not can not be justified<br>
> > > > looking at the the log archive. I strongly believe we should capture<br>
> > > > this message as part of archiving the log.<br>
> > > ><br>
> > > > Would you be able to do this change and apply it in Rackspace?<br>
> > > ><br>
> > > > ~Atin<br>
> > > > _______________________________________________<br>
> > > > Gluster-devel mailing list<br>
> > > > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > > > <a href="http://supercolony.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-devel</a><br>
> > > ><br>
> ><br>
> > > _______________________________________________<br>
> > > Gluster-devel mailing list<br>
> > > <a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
> > > <a href="http://supercolony.gluster.org/mailman/listinfo/gluster-devel" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-devel</a><br>
> ><br>
> ><br>
</div></div></blockquote></div></div>