[00:03] uchimata: no, it won't be possible to log in via ssh when the root file system hasn't been mounted [00:12] meme (~quassel@dslb-088-064-148-030.pools.arcor-ip.net) left irc: Remote host closed the connection [03:07] ErKa (~keryell@68-245-173-61.pools.spcsdns.net) left irc: Ping timeout: 480 seconds [04:58] ErKa (~keryell@static-64-22-43-58.albyny.csvoip.net) joined #fai. [06:31] ErKa (~keryell@static-64-22-43-58.albyny.csvoip.net) left irc: Ping timeout: 480 seconds [09:26] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) joined #fai. [09:43] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) left irc: Quit: Leaving. [10:39] Mrfai (~lange@suenner.informatik.uni-koeln.de) joined #fai. [10:49] verwilst (~verwilst@router.begen1.office.netnoc.eu) joined #fai. [12:53] ErKa (~keryell@static-64-22-43-58.albyny.csvoip.net) joined #fai. [13:46] ErKa (~keryell@static-64-22-43-58.albyny.csvoip.net) left irc: Ping timeout: 480 seconds [15:00] allee-k__ (~allee-k@alleehol.mpe.mpg.de) joined #fai. [15:30] allee-k__ (~allee-k@alleehol.mpe.mpg.de) left irc: Ping timeout: 480 seconds [15:35] meme (~quassel@dslb-088-065-169-048.pools.arcor-ip.net) joined #fai. [15:36] Hi [15:36] Kann man denn die einzelnen Teilschritte, die die faimond-gui anzeigt auch ändern? [15:36] z.B. möchte ich gern einen Installationsstatus der einzelnen Pakete sehen [15:36] um herauszufinden wie lange es dauert Paket XYZ zu installieren [16:03] siggg (~jean@tra78-5-88-172-128-32.fbx.proxad.net) joined #fai. [16:08] allee-k__ (~allee-k@alleehol.mpe.mpg.de) joined #fai. [16:13] verwilst (~verwilst@router.begen1.office.netnoc.eu) left irc: Quit: Ex-Chat [16:15] meme (~quassel@dslb-088-065-169-048.pools.arcor-ip.net) left irc: Ping timeout: 480 seconds [16:43] ErKa (keryell@ted.dyn.cs.rpi.edu) joined #fai. [17:02] allee-k__ (~allee-k@alleehol.mpe.mpg.de) left irc: Remote host closed the connection [17:02] allee-k__ (~allee-k@alleehol.mpe.mpg.de) joined #fai. [17:12] W: Failed to fetch http://www.informatik.uni-koeln.de/fai/download/dists/lenny/Release Unable to find expected entry koeln/binary-armel/Packages in Meta-index file (malformed Release file?) [17:12] meme (~quassel@pD9E4F9CE.dip.t-dialin.net) joined #fai. [17:13] Hallo [17:13] Mrfai: do i really need binary-armel for fai? [17:13] binary-anything, rather [17:21] allee-k__ (~allee-k@alleehol.mpe.mpg.de) left irc: Ping timeout: 480 seconds [18:00] ErKa (keryell@ted.dyn.cs.rpi.edu) left irc: Ping timeout: 480 seconds [18:05] stockholm: there's no strings "armel" in my Release or package file [18:06] Mrfai: i could ignore the warning, everything seems to work [18:29] Mrfai (~lange@suenner.informatik.uni-koeln.de) left irc: Quit: leaving [18:53] Hi there [18:54] I am trying to get more detailed timing information about the installation progress [18:55] Where shoul I start if I want to get the time after each single software package was installed? [19:11] meme: how accurate do you need to be? do you want to time individual packages or just get a better rough idea about the overall progress of an installation? [19:11] it should be detailed how long every software package need. [19:11] I get the overall time with faimond [19:12] but I am interested in which package of my installation needs how long [19:13] I was thinking about the following: running a script after each package that loggs the time to an nfs share [19:13] meme: do you install packages via FAI's and aptitude? [19:14] I think so. [19:16] I created a class file and a package config file with the packages inside [19:17] meme: a first solvable problem is that aptitude installs packages in stages [19:18] meme: so it first downloads all, then selects all, then unpacks all, then configures all [19:18] oh I see [19:18] meme: so it's kind of hard to say how long it took to install one particular package [19:19] I could ignore the downloading part because I am using a local network mges [19:19] so this is only local network traffic [19:19] meme: of course, you could tell FAI to install one pkg at a time but that's rather inefficient [19:22] meme: so I'm still not sure whether you just want to know the time at which a pkg was eventually installed without really learning how long it took all in all to install it or whether it's the latter part you really need to figure out? [19:28] it would be enough to know a timestamp after a single packet was installed [19:31] I would likt to kno the following times: [19:31] a) Start of Installation (I get this from start of a custom script) [19:31] b) Start of FAI Env. on client (I get this from dhcpd.log) [19:31] c) Package Installation [19:31] c1) Package A installed [19:31] c2) Package B installed [19:31] c3).... [19:31] d) End of Client installation ( (I get this from dhcpd.log) [19:32] meme: okay, my personal hack would be to pipe the aptitude progress into a little script which greps the input and when it sees from the aptitude output that a pkg is fully installed, write a timestamp and the package name somewhere [19:33] meme: the aptitude output you get either from /tmp/fai/software.log on the install client or via faimond [19:34] the rest is just a bit of grep and sed magic [19:34] I get this from faimond? [19:34] meme: it'd be a bit of scripting work though [19:35] meme: I personally never used faimond but I would guess so... but don't nail me on that one [19:38] here is a sample faimond output of a machine which installs debian with only the apache package: [19:38] Mon Feb 8 16:34:22 2010 - deb_a_test3 check [19:38] Mon Feb 8 16:34:22 2010 - deb_a_test3 TASKEND confdir 0 [19:38] Mon Feb 8 16:34:22 2010 - deb_a_test3 TASKBEGIN setup [19:38] Mon Feb 8 16:34:23 2010 - deb_a_test3 TASKEND setup 0 [19:38] Mon Feb 8 16:34:23 2010 - deb_a_test3 TASKBEGIN defclass [19:38] Mon Feb 8 16:34:25 2010 - deb_a_test3 TASKEND defclass 0 [19:38] Mon Feb 8 16:34:25 2010 - deb_a_test3 TASKBEGIN defvar [19:38] Mon Feb 8 16:34:25 2010 - deb_a_test3 TASKEND defvar 0 [19:38] Mon Feb 8 16:34:27 2010 - deb_a_test3 TASKBEGIN action [19:38] Mon Feb 8 16:34:34 2010 - deb_a_test3 TASKBEGIN install [19:38] Mon Feb 8 16:34:34 2010 - deb_a_test3 TASKBEGIN partition [19:38] Mon Feb 8 16:34:40 2010 - deb_a_test3 TASKEND partition 0 [19:38] Mon Feb 8 16:34:40 2010 - deb_a_test3 TASKBEGIN mountdisks [19:38] Mon Feb 8 16:34:40 2010 - deb_a_test3 TASKEND mountdisks 0 [19:38] Mon Feb 8 16:34:40 2010 - deb_a_test3 TASKBEGIN extrbase [19:38] Mon Feb 8 16:34:56 2010 - deb_a_test3 TASKEND extrbase 0 [19:38] Mon Feb 8 16:34:56 2010 - deb_a_test3 TASKBEGIN mirror [19:38] Mon Feb 8 16:34:56 2010 - deb_a_test3 TASKEND mirror 0 [19:38] Mon Feb 8 16:34:56 2010 - deb_a_test3 TASKBEGIN debconf [19:38] Mon Feb 8 16:34:56 2010 - deb_a_test3 TASKEND debconf 0 [19:39] Mon Feb 8 16:34:56 2010 - deb_a_test3 TASKBEGIN prepareapt [19:39] Mon Feb 8 16:34:57 2010 - deb_a_test3 TASKEND prepareapt 0 [19:39] Mon Feb 8 16:34:57 2010 - deb_a_test3 TASKBEGIN updatebase [19:39] Mon Feb 8 16:35:16 2010 - deb_a_test3 TASKEND updatebase 0 [19:39] Mon Feb 8 16:35:16 2010 - deb_a_test3 HOOK instsoft.FAIBASE [19:39] Mon Feb 8 16:35:17 2010 - deb_a_test3 HOOK instsoft.LAST [19:39] Mon Feb 8 16:35:17 2010 - deb_a_test3 TASKBEGIN instsoft [19:39] Mon Feb 8 16:37:21 2010 - deb_a_test3 TASKEND instsoft 0 [19:39] Mon Feb 8 16:37:21 2010 - deb_a_test3 TASKBEGIN configure [19:39] Mon Feb 8 16:37:37 2010 - deb_a_test3 TASKEND configure 0 [19:39] Mon Feb 8 16:37:37 2010 - deb_a_test3 TASKBEGIN finish [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKEND finish 0 [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKBEGIN chboot [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKEND chboot 2 [19:39] alright, I get the picture :) [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKBEGIN test [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKEND test 0 [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 HOOK savelog.LAST.source [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKBEGIN savelog [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKEND savelog 0 [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKEND install 0 [19:39] Mon Feb 8 16:37:38 2010 - deb_a_test3 TASKBEGIN faiend [19:39] Mon Feb 8 16:37:48 2010 - deb_a_test3 TASKEND REBOOT 0 [19:39] Could I use a hook script to log the time? [19:39] :-) sorry for flooding [19:39] meme: maybe you want to use something like http://pastebin.ca/ for that next time :) [19:40] meme: ok, never mind, I was assuming that the full FAI log was sent to faimond [19:41] meme: so I guess your next best shot is parsing /tmp/fai/software.log on the install client while the installation is running [19:43] can I change the log path to a nfs dir so that I am able to process this information after the installation [19:44] meme: yeah, I guess you could actually because I think that /tmp/fai is not hardcoded, but since the log file itself does not contain time stamps, that is not sufficient [19:44] oh I assumed taht :-( [19:45] software.log is really just the output of aptitude (or rather install_packages) piped into a file [19:47] meme: you could rather easily have a script add timestamps to that or do more heavy processing on that log file as it is being written during the installation - that would be the hack I mentioned. Not pretty but it would get you somewhere [19:56] ok [20:23] ErKa (keryell@ted.dyn.cs.rpi.edu) joined #fai. [21:47] ErKa (keryell@ted.dyn.cs.rpi.edu) left irc: Ping timeout: 480 seconds [22:01] meme (~quassel@pD9E4F9CE.dip.t-dialin.net) left irc: Ping timeout: 480 seconds [22:17] ErKa (keryell@ted.dyn.cs.rpi.edu) joined #fai. [22:32] ErKa (keryell@ted.dyn.cs.rpi.edu) left irc: Ping timeout: 480 seconds [00:00] --- Wed Feb 10 2010