Summary: | app-benchmarks/bootchart2 - /sbin/bootchartd requires initrd=/sbin/bootchartd | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jesús Guerrero Botella (RETIRED) <i92guboj> |
Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
Status: | IN_PROGRESS --- | ||
Severity: | normal | CC: | gef.kornflakes |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
The graph
The logs from which the graph is born |
Description
Jesús Guerrero Botella (RETIRED)
2012-05-15 21:43:48 UTC
Changing /etc/bootchartd.conf this way: BOOTLOG_DEST=/bootchart.tgz AUTO_RENDER_DIR="/" EXIT_PROC="kdm_greet xterm konsole gnome-terminal metacity mutter compiz ldm icewm-session enlightenment mingetty" ## added mingetty here Seems to aware the thing when I log in, some messages are printed in the terminal and I can see this file being created. However if I use pybootchart on it it generates an empty graph, not strange considering that most log files in the tarball are also empty. It's worth noting that /var is a separate partition. Time to sleep. Enough for today. Er, huh? I am not sure all the problem is it requiring initrd. As I say, I modified the init script to contemplate the non-initrd case, and it starts, but produces empty output. Something is highly broken in this package, or there's some extra configuration needed that's not described in the README file nor in the elogs/ewarns or whatever they are. As weird as it might seem, the previous "doesn't do anything" title was more accurate :P So I played around some time until I got the init script fixed. As far as can remember setting it to only rdinitrd=/sbin/bootchartd was enough, but I cannot remember why. I will look into the issue and see what is wrong here. (In reply to comment #4) > So I played around some time until I got the init script fixed. As far as > can remember setting it to only rdinitrd=/sbin/bootchartd was enough, but I > cannot remember why. I will look into the issue and see what is wrong here. Well, that will match any kernel line that uses an initrd, which surely is ok for a lot of gentoo users since the Gentoo way is genkernel, and that puts an initrd by default (doesn't it?), but I am sure that a very significant user base still installs their kernel by hand and do not use genkernel. In any case, not supporting the non-initrd systems is not only against this user base, but also against what the distributed README file says, which is confusing. In any case, my problem is not the init script failing any longer, since I already took care of that. My problem is that bootchart2 doesn't produce any output. Could it have something to do with the fact that /var is a separate partition that's not mounted when init starts? I tried setting the paths to /, as I told you above, however the output is still a blank graph. I can send you the tgz file later if you think it will help. (In reply to comment #5) > Well, that will match any kernel line that uses an initrd, which surely is > ok for a lot of gentoo users since the Gentoo way is genkernel, and that If I remember correctly, it is only necessary for initrd users. Other users don't need that part of the init script. But I need to investigate it again. I can remember I put in both options, but removed it later. > In any case, my problem is not the init script failing any longer, since I > already took care of that. My problem is that bootchart2 doesn't produce any > output. > Could it have something to do with the fact that /var is a separate > partition that's not mounted when init starts? I tried setting the paths to That might be related. I will look into it. > /, as I told you above, however the output is still a blank graph. I can > send you the tgz file later if you think it will help. I will contact you in case I need more information (In reply to comment #6) > (In reply to comment #5) > > Well, that will match any kernel line that uses an initrd, which surely is > > ok for a lot of gentoo users since the Gentoo way is genkernel, and that > > If I remember correctly, it is only necessary for initrd users. Other users > don't need that part of the init script. But I need to investigate it again. > I can remember I put in both options, but removed it later. That could very well be. I am thinking that maybe the problem is that I don't use any standard login program. I modified the conf file at the same time to put the path in / and to add mingetty to the list of programs to wait for. So, maybe what did the thing was the mingetty addition, and not the change to /. So, is bootchart2 supposed to write the log files when this wait for the login screen ends without the need for the terminator daemon? > > In any case, my problem is not the init script failing any longer, since I > > already took care of that. My problem is that bootchart2 doesn't produce any > > output. > > Could it have something to do with the fact that /var is a separate > > partition that's not mounted when init starts? I tried setting the paths to > > That might be related. I will look into it. I think I can also do some tests remotely. Thanks you. (In reply to comment #7) > So, is bootchart2 supposed to write the log files when this wait for the > login screen ends without the need for the terminator daemon? Please try to add a terminator trigger into /etc/bootchartd.conf: EXIT_PROC="...." For the rest we need to wait until tonight. (In reply to comment #8) > (In reply to comment #7) > > So, is bootchart2 supposed to write the log files when this wait for the > > login screen ends without the need for the terminator daemon? > Please try to add a terminator trigger into > > /etc/bootchartd.conf: > EXIT_PROC="...." > > For the rest we need to wait until tonight. I tried to remotely reboot the machine and something failed, I can ping it but ssh doesn't respond for some reason. So, I won't be able to do anything either until I arrive home tonight. (In reply to comment #8) > (In reply to comment #7) > > So, is bootchart2 supposed to write the log files when this wait for the > > login screen ends without the need for the terminator daemon? > Please try to add a terminator trigger into > > /etc/bootchartd.conf: > EXIT_PROC="...." > > For the rest we need to wait until tonight. agetty should be fine. Should be even default IMHO. (In reply to comment #8) > (In reply to comment #7) > > So, is bootchart2 supposed to write the log files when this wait for the > > login screen ends without the need for the terminator daemon? > Please try to add a terminator trigger into > > /etc/bootchartd.conf: > EXIT_PROC="...." > > For the rest we need to wait until tonight. I added mingetty into there, I also changed the location to /bootchart2/ and created that directory. Then chmoded it 777 just to be sure. I adjusted the conf file accordingly and now it seems to create something in there, however the graph is still useless. If I run pybootchartgui I get this: # pybootchartgui -i bootchart.tgz parsing 'bootchart.tgz' parsing 'header' parsing 'dmesg' parsing 'cmdline2.log' parsing 'paternity.log' parsing 'proc_cpuinfo.log' parsing 'proc_diskstats.log' parsing 'proc_meminfo.log' parsing 'proc_stat.log' parsing 'taskstats.log' merged 0 logger processes pruned 405 process, 0 exploders, 0 threads, and 0 runs merged 0 logger processes degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart degenerate boot chart I'll attach the resulting png file and the tgz. Created attachment 312055 [details]
The graph
Created attachment 312057 [details]
The logs from which the graph is born
|