Logging?

[Chris Mckenzie]

My problem is the unknown. I won't be installing the boxes so I'm trying to
automate as much as possible. If I don't know how much completed
successfully, then depending on how far the kickstart install got, I might
not be able to check.

If I can check, as in the post fails for instance because the NFS isn't
available (or something like that) I only have the TTY3 screen dump that's
not logged anywhere and doesn't remain on screen. (or the box is installed
headless, just plugin, pop the CD in, and go for coffee, when the CD ejects,
power down and add it to the pile)

If it was, I could write a post install script that the installer would run
manually or auto run and report to another server, etc... It could check a
bunch of stuff, including a RH KS install log for expected results. (or
known failures, like NFS unavailable, etc...)

Thanks.

- Chris

-----Original Message-----
From: kickstart-list-bounces at redhat.com
[mailto:kickstart-list-bounces at redhat.com] On Behalf Of Oden, James
Sent: November 22, 2004 11:25 AM
To: Discussion list about Kickstart
Subject: RE: Logging?


 
> On Mon, 22 Nov 2004, Chris Mckenzie wrote:
> 
> >Does anyone have any suggestions on handling kickstart installation 
> >failure logging? If a kickstart succeeds in installing, I
> know because
> >my post script runs. If it fails, either within the middle of the ks 
> >process or fails to run my post script, the system will
> reboot without
> >pausing to let me know what the problem was.
> 
> It will? If anaconda terminates abnormally the system usually
> will print
> something to the screen then prompt to reboot, I thought.
>
Yeah, but an error in %post will not cause anaconda to stop.  I wrote a
bugzilla report about this a while back.  Don't know if it was ever fixed.
 
Cheers...james

_______________________________________________
Kickstart-list mailing list
Kickstart-list at redhat.com
https://www.redhat.com/mailman/listinfo/kickstart-list