| *** bjdooks_ [~ben@trinity.fluff.org] has joined #baserock | 00:02 | |
| *** SotK_ [~adamcoldr@access.ducie-dc1.codethink.co.uk] has joined #baserock | 00:02 | |
| *** juergbi` [~juerg@vserver.paldo.org] has joined #baserock | 00:04 | |
| *** juergbi [~juerg@vserver.paldo.org] has quit [Write error: Broken pipe] | 00:07 | |
| *** bjdooks [~ben@trinity.fluff.org] has quit [Write error: Connection reset by peer] | 00:07 | |
| *** persia_ [quassel@ubuntu/member/persia] has quit [Write error: Connection reset by peer] | 00:07 | |
| *** persia_ [quassel@2400:8900::f03c:91ff:feae:3452] has joined #baserock | 00:07 | |
| *** persia_ [quassel@2400:8900::f03c:91ff:feae:3452] has quit [Changing host] | 00:07 | |
| *** persia_ [quassel@ubuntu/member/persia] has joined #baserock | 00:07 | |
| *** SotK [~adamcoldr@access.ducie-dc1.codethink.co.uk] has quit [Ping timeout: 250 seconds] | 00:11 | |
| *** inara [~inara@192.241.198.49] has quit [Remote host closed the connection] | 00:56 | |
| *** inara [~inara@192.241.198.49] has joined #baserock | 01:01 | |
| *** inara [~inara@192.241.198.49] has quit [Remote host closed the connection] | 01:04 | |
| *** inara [~inara@192.241.198.49] has joined #baserock | 01:06 | |
| *** inara [~inara@192.241.198.49] has quit [Remote host closed the connection] | 01:16 | |
| *** inara [~inara@192.241.198.49] has joined #baserock | 01:20 | |
| *** fay_ [~fay@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 06:37 | |
| *** franred [~franred@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 07:49 | |
| *** tiagogomes [~tiagogome@213.15.255.100] has joined #baserock | 07:51 | |
| richard_maw | paulsherwood: also, filesystems tend to reserve a certain % of their disk capacity for the root user, so you can get -ENOSPC with GiBs free. Which is better than the alternative for btrfs where it gets completely stuck when it runs out. | 08:23 |
|---|---|---|
| pedroalvarez | I agree with that, but it seems to me that a 20% of diskspace is too much | 08:24 |
| *** jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 08:29 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:15 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Client Quit] | 09:18 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 09:19 | |
| ssam2 | I'm seeing Git connections dropped due to 'too many children' on git.baserock.org | 09:24 |
| ssam2 | is there a known way to fix this? | 09:24 |
| richard_maw | restart the git daemon | 09:25 |
| richard_maw | there's a couple of ways to mitigate it, but I was hoping we could work out why it was happening first, since the mitigation either involves allowing unbounded git subprocecces on git.baserock.org, or setting a timeout that may break valid connections | 09:26 |
| juergbi` is now known as juergbi | 09:54 | |
| *** franred [~franred@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving] | 10:44 | |
| *** franred [~franred@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 10:52 | |
| franred | ummm, do we use forks or main projects? I've been looking to add procps to baserock to update ps/pstree/kill commands and I've found that there are a mainline called procps: http://procps.sourceforge.net/ and its fork used by Debian, Fedora and openSUSE: procps-ng: http://sourceforge.net/projects/procps-ng/ | 11:42 |
| liw-orc | franred, I'd say it depends on a case by case basis | 11:42 |
| radiofree | franred: if debian, feodra and openSUSE are using it i'd say "use the fork, luke" | 11:42 |
| franred | the lorry file will be like this: http://fpaste.org/130068/14095725/ <-- could someone review it? | 11:56 |
| persia | looks reasonable to me | 11:58 |
| pedroalvarez | looks ok to me, but I'm not sure about the "-ng" | 11:58 |
| pedroalvarez | but if persia likes it, then +1 | 11:59 |
| persia | pedroalvarez: You suggest we ought declare it to be "procps"? | 11:59 |
| * persia tends to stick with upstream naming convensions, or sensible derivatives thereof (ii-esu being the most deviant I've not complained about) | 12:00 | |
| pedroalvarez | I was thinking that maybe some people think that we ought to | 12:00 |
| persia | Hmm, indeed, it seems to be given this name by some projects (e.g. Debian). | 12:02 |
| persia | As long as we never expect original procps to be used, I'm happy with calling it procps. If we want flexibility, I'd prefer procps-ng. Mostly, I'd prefer if the upstreams were collaborating, rather than there being a distros fork. | 12:03 |
| pedroalvarez | franred: then procps-ng is ok | 12:04 |
| franred | pedroalvarez, persia thanks, I will merge it | 12:06 |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 240 seconds] | 12:47 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 12:47 | |
| *** persia_ [quassel@2400:8900::f03c:91ff:feae:3452] has joined #baserock | 13:55 | |
| *** persia_ [quassel@2400:8900::f03c:91ff:feae:3452] has quit [Changing host] | 13:56 | |
| *** persia_ [quassel@ubuntu/member/persia] has joined #baserock | 13:56 | |
| franred | I've try to add procps-ng in the tools morphology but when I deploy the image Im not able to log into it... | 15:17 |
| persia | Interesting. | 15:18 |
| persia | Does systemd's journal have a configuration that lets you spam the console with all the messages? | 15:18 |
| * persia was going to suggest reconfiguring syslog, but realised that's probably not where the errors are put | 15:18 | |
| franred | persia, not sure if Im able to check the journal without log into my VM | 15:19 |
| franred | which is not possible | 15:19 |
| persia | I don't expect you can: rather I thought you might be able to deploy a similar image and use file injection to cause it to configure the journal to print to console, so you can observe it. | 15:20 |
| persia | The alternative is attempting to find some way to mount the virtual disk in some other environment, where you can log in, and inspect it, but getting that working probably involves quite a bit of yak shaving. | 15:21 |
| franred | persia, I was wrong, what is cause the login error is something that I've done in my morphology when I installed java | 15:51 |
| franred | I've removed the java chunk and it works with procps. it still not replace the busybox ps but this is another step. I will continue investigating what Im doing wrong when I install java | 15:53 |
| pedroalvarez | franred: so, after removing the java-gerrit chunk, you can login? | 15:55 |
| franred | pedroalvarez, yes, and I can see the procps-ng version of ps in /usr/bin/ | 15:56 |
| pedroalvarez | right | 15:56 |
| franred | I imagine that I will need to do some configuration extension if I want to /bin/ps to point to /usr/bin/ps, am I wrong? | 15:57 |
| pedroalvarez | franred: so then, yes, the problem is with the java-gerrit chunk, I'd suggest you to look at the content of the artifact, and see if it is installing something strange | 15:57 |
| franred | pedroalvarez, yes, I will do, thanks :) | 15:57 |
| pedroalvarez | franred: can't you install the new ps in /bin? | 15:58 |
| pedroalvarez | so it overrides the previous one? | 15:59 |
| franred | pedroalvarez, ummm, yes. There is a way to tell in chunk that it should use / rather than /usr to install the chunk without rewrite all the autotools commands? | 16:02 |
| pedroalvarez | franred: we do it in build-essentials.morph stratum | 16:05 |
| pedroalvarez | http://pastebin.com/37MQMD4g | 16:05 |
| pedroalvarez | where we put some things under /tool | 16:06 |
| pedroalvarez | It will work, if the autotools commands of the ps chunk use $PREFIX, afaik | 16:06 |
| persia | If it doesn't work perfectly, one can always use mv as part of install-commands | 16:08 |
| franred | testing now | 16:09 |
| franred | pedroalvarez, persia, it works. Also I hava java working. So the only remainig piece where the loggin error can be is in the gerrit configuration-extension. | 16:18 |
| franred | looking at it now | 16:19 |
| persia | \o/ | 16:19 |
| pedroalvarez | heheh, the probem was small, but funny | 16:30 |
| pedroalvarez | the configuration extension was creating a symlink from /bin/sh to nothing | 16:31 |
| persia | And $SHELL was set to /bin/sh? | 16:31 |
| pedroalvarez | or maybe was a symlink from /bin/bash to nothing | 16:32 |
| *** tiagogomes [~tiagogome@213.15.255.100] has quit [Quit: Leaving] | 16:34 | |
| *** jonathanmaw [~jonathanm@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving] | 16:40 | |
| *** ssam2 [~ssam2@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Remote host closed the connection] | 16:56 | |
| franred | :) happy - all chuncks ready to test tomorrow gerrit :) | 17:04 |
| pedroalvarez | franred: well done | 17:04 |
| *** franred [~franred@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Quit: Leaving] | 17:04 | |
| *** fay_ [~fay@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Remote host closed the connection] | 17:19 | |
| paulsherwood | w00t :) | 17:20 |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 240 seconds] | 19:12 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 19:27 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 245 seconds] | 19:39 | |
| jjardon | Hi, I was trying to compile a system some minutes ago but seems there is some problem fetching from g.b.o, is this a known issue? | 19:44 |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 19:51 | |
| paulsherwood | sadly, yes. | 19:58 |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 19:59 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 20:00 | |
| paulsherwood | we are in the process of spinning up new instances. maybe you could try using http://85.199.252.93/cgi-bin/cgit.cgi/ in the meantime? | 20:01 |
| paulsherwood | jjardon: ^^ | 20:01 |
| paulsherwood | actually, that probably doesn't work, now i'm trying it | 20:05 |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 20:13 | |
| * paulsherwood tries g.b.o and finds that it's working for him, but slow | 20:16 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 20:17 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 255 seconds] | 20:21 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 20:29 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 255 seconds] | 20:36 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 20:37 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 255 seconds] | 20:43 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 20:46 | |
| jjardon | paulsherwood: thanks, will check again tomorrow | 20:47 |
| jjardon | Interesting proposal, with some similarities with baserock: http://0pointer.net/blog/revisiting-how-we-put-together-linux-systems.html | 20:48 |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 245 seconds] | 21:00 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 21:06 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 21:17 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 21:20 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 21:27 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 21:31 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 21:38 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 21:43 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 21:54 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 21:58 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 255 seconds] | 22:12 | |
| paulsherwood | sadly he failed to actually mention baserock :/ | 22:17 |
| paulsherwood | but yes, it's interesting | 22:17 |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 22:19 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 255 seconds] | 22:27 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 22:28 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 260 seconds] | 22:33 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 22:36 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 255 seconds] | 22:50 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 22:51 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has quit [Ping timeout: 245 seconds] | 23:14 | |
| *** flatmush [~flatmush@82-70-136-246.dsl.in-addr.zen.co.uk] has joined #baserock | 23:15 | |
Generated by irclog2html.py 2.15.3 by Marius Gedminas - find it at mg.pov.lt!