How to clear "cobbler status"?

[petermity]

The "cobbler status" command is handy to see when builds are
running/finished.  However, the display can be cluttered by units
that finished building (or hung/failed) days/weeks ago, even if
the Cobbler server is rebooted.  Is there a way to start fresh?

Related: is there a wget command or some other method to tell
Cobbler that a failure occurred in the %post section?  Something
analogous to the $kickstart_done, maybe a $kickstart_failed?

[Scott Henson]

On Mon, 07 Mar 2011 22:33:15 -0800, petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote:
>  The "cobbler status" command is handy to see when builds
> are
>  running/finished.  However, the display can be cluttered by units
>  that finished building (or hung/failed) days/weeks ago, even if
>  the Cobbler server is rebooted.  Is there a way to start fresh?
>  
>  Related: is there a wget command or some other method to tell
>  Cobbler that a failure occurred in the %post section?  Something
>  analogous to the $kickstart_done, maybe a $kickstart_failed? 
I believe you would need to rotate /var/log/cobbler/install.log and
restart cobblerd.

-- 
Scott Henson
Red Hat CIS Operator
WVU Alum BSAE/BSME

[petermity]

Scott Henson <shenson(a)redhat.com&gt; wrote:

> On Mon, 07 Mar 2011 22:33:15 -0800, petermity
> <6t12-n6js(a)dea.spamcon.org&gt; wrote:
> > The "cobbler status" command is handy to see when builds are
> > running/finished.  However, the display can be cluttered by units
> > that finished building (or hung/failed) days/weeks ago, even if
> > the Cobbler server is rebooted.  Is there a way to start fresh?
> > 
> > Related: is there a wget command or some other method to tell
> > Cobbler that a failure occurred in the %post section?  Something
> > analogous to the $kickstart_done, maybe a $kickstart_failed?
>
> I believe you would need to rotate /var/log/cobbler/install.log and
> restart cobblerd. 
Thanks, but I renamed install.log and cobbler.log, restarted
cobblerd, no difference, rebooted the machine, no difference. It
must be getting the information from elsewhere.

[petermity]

petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote:

> Scott Henson <shenson(a)redhat.com&gt; wrote:
>
> >On Mon, 07 Mar 2011 22:33:15 -0800, petermity <6t12-n6js(a)dea.spamcon.org&gt;
> wrote:
> >> The "cobbler status" command is handy to see when builds are
> >> running/finished.  However, the display can be cluttered by units
> >> that finished building (or hung/failed) days/weeks ago, even if
> >> the Cobbler server is rebooted.  Is there a way to start fresh?
> >> 
> >> Related: is there a wget command or some other method to tell
> >> Cobbler that a failure occurred in the %post section?  Something
> >> analogous to the $kickstart_done, maybe a $kickstart_failed?
> >
> >I believe you would need to rotate /var/log/cobbler/install.log and
> >restart cobblerd.
>
> Thanks, but I renamed install.log and cobbler.log, restarted
> cobblerd, no difference, rebooted the machine, no difference. It
> must be getting the information from elsewhere. 
I figured this out - it's not just looking in install.log, but in all of
the rotated install.log* it finds, such as install.log-20110327.  Moving
all such logs elsewhere, it now shows the empty list.

[petermity]

petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote:

> petermity <6t12-n6js(a)dea.spamcon.org&gt; wrote:
>
> >Scott Henson <shenson(a)redhat.com&gt; wrote:
> >
> >>On Mon, 07 Mar 2011 22:33:15 -0800, petermity <6t12-n6js(a)dea.spamcon.org&gt;
> wrote:
> >>> The "cobbler status" command is handy to see when builds are
> >>> running/finished.  However, the display can be cluttered by units
> >>> that finished building (or hung/failed) days/weeks ago, even if
> >>> the Cobbler server is rebooted.  Is there a way to start fresh?
> >>> 
> >>> Related: is there a wget command or some other method to tell
> >>> Cobbler that a failure occurred in the %post section?  Something
> >>> analogous to the $kickstart_done, maybe a $kickstart_failed?
> >>
> >>I believe you would need to rotate /var/log/cobbler/install.log and
> >>restart cobblerd.
> >
> >Thanks, but I renamed install.log and cobbler.log, restarted
> >cobblerd, no difference, rebooted the machine, no difference. It
> >must be getting the information from elsewhere.
>
> I figured this out - it's not just looking in install.log, but in all of
> the rotated install.log* it finds, such as install.log-20110327.  Moving
> all such logs elsewhere, it now shows the empty list. 
FYI, I submitted an enhancement request for a default of "today" or
similar for "cobbler status": https://fedorahosted.org/cobbler/ticket/680

And a request for "$kickstart_failed" or similar:
https://fedorahosted.org/cobbler/ticket/681