On Di 13 Jan 2015 15:59:06 CET, Michael DePaulo wrote:
On Tue, Jan 13, 2015 at 12:41 AM, Michael DePaulo
<mikedep333@gmail.com> wrote:On Mon, Jan 12, 2015 at 12:33 AM, Michael DePaulo
<mikedep333@gmail.com> wrote:On Sun, Jan 11, 2015 at 11:58 PM, Mike Gabriel <mike.gabriel@das-netzwerkteam.de> wrote:
Hi Alex, hi Heinz, hi Michael,
the build system on jenkins.x2go.org seems to have some troubles at the moment.
Can either of you take a look? I any help is needed I will be happy to provide it during this week.
Greets, Mike [...]
I will take a look tomorrow evening.
Sorry, I'll look at it either tomorrow morning or tomorrow evening.
several builds were failing but hung indefinitely. You can see 2 of the logs here: http://jenkins.x2go.org:8080/view/All/job/x2gobroker+nightly+debian-sid/163/... http://jenkins.x2go.org:8080/view/All/job/x2gobroker+nightly+debian-jessie/1...
I fixed the problem in the short term by killing those qemubuilder processes.
Builds are now working. But there is a build queue of 85 right now.
However, we do not want the problem to happen again. Mike#1 thinks that it is because we ran into the limit of 8 loop devices on the host (japsand.) However, the limit has been set to 64 since before the machine was last rebooted: mikedep333@japsand:/etc/modprobe.d$ cat /etc/modprobe.d/loop.conf options loop max_loop=64
I'll look into this later. Maybe we specified the limit on loop devices incorrectly.
-Mike#2
The deeper cause of the problem is that if qemubuilder finishes
uncleanly, it leaves stale mounts behind that block one loop device
each.
Maybe using a signal trap in x2go-build-deb-package might help with a
good portion of post-build-cleanup code.
Mike
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...