[utah-devel] New Stable Version

Daniel Manrique daniel.manrique at canonical.com
Wed Jan 30 14:49:20 UTC 2013


On 13-01-30 09:14 AM, Jean-Baptiste Lallement wrote:
> Le 30/01/2013 15:01, Max Brustkern a écrit :
>> On 01/29/2013 04:26 PM, Jean-Baptiste Lallement wrote:
>>> Le 29/01/2013 20:20, Max Brustkern a écrit :
>>>> Various logging improvements: Database, SSH, and cobbler logs can now
>>>> be gathered and easily separated
>>> Does it include remote log gathering during installation on HW?
>>> 
>> Unfortunately it does not.  If you have a working rsyslogd in the lab, you
>> can pass in the needed boot arguments for that, i.e. -b "log_host 10.97.0.1
>> log_port 514"
> There is a working rsyslog on magners and I tried log_host and log_port but
> I don't think it works with desktop images which is what is used by autopilot
> jobs.

Hi,

I spoke to Max a few days ago about this, and I forgot to mention (sorry!) that
while d-i knows about remote syslogging which works out of the box,
ubiquity/casper do not; therefore, to get this working with checkbox-satellite
we had to make a tiny modification to the initrd file, to properly configure
casper's syslog to log remotely. This is compatible with the kernel paramater
syntax described above.

1- Unpack the initrd.lz
2- Add a couple of lines need to added to scripts/init-bottom/ORDER, and a small
script needs to be copied to scripts/init-bottom
3- repack the initrd.lz
4- use that initrd.lz to boot the system, it should automagically pick up
log_host and log_port.

These modifications are described in lp:checkbox-satellite, look in initrd/lz,
the "patch" file is a script that automatically does step 2 above, and the
'rsyslog' is the script that needs to be dropped in scripts/init-bottom.

There's also a scripts/initrd_patch script, which takes care of applying these
patches to initrd. It's used like this:

scripts/initrd_patch <path_to_initrd.lz> <path_to_rsyslog.patch>

These scripts are pretty much independent from the rest of checkbox_satellite.
You can potentially just take initrd_patch, rsyslog.patch and rsyslog, and put
them somewhere in utah where they make sense.

Let me know if I can help further with this.

Cheers!
- Daniel

> 
>> but so far, the automated addition of that and retrieval of those logs 
>> hasn't worked consistently.  It's still high on the list of what we're 
>> working on, and I expect it to be in the next stable release.
>> 
>> Max
>> 
> 
> 

ss



More information about the Ubuntu-utah-devel mailing list