On Thu, Sep 30, 2010 at 11:35:51AM +0200, Piñeiro wrote: > From: Olav Vitters <[email protected]> > > > On Thu, Sep 30, 2010 at 10:19:33AM +0200, Piñeiro wrote: > >> subject is clear: b.g.o is down. > >> > >> As usual in this cases, I tried to login on fixed.gnome.org (ssh > >> [email protected]) to check if the master and slave were > >> running and restarted again. > >> > >> But, although I get ping response from fixed.gnome.org, I'm not able > >> to enter in the machine. I don't reach the option to enter the > >> password, or any error. Just nothing. > >> > >> So, what we should do? Contact sys-admin? Olav? > > > > Sysadmins. We have multiple people now. > > When I said sys-admin, I was thinking specifically on > [email protected]. I added here your name as you are also > syndicated to build-bridage list in order to ask that. So I will try > it again: > > Olav, should I forward this mail to [email protected]?
I already cc'ed gnome-infrastructure. Basically the same thing (though you need to subscribe and a public list. > > Lately issue is that it just uses too much memory (*many* leftover dbus > > processes) > > So the build process get stuck in the long term due this dbus > processes? It is a fault of dbus or we would need to solve that on the > gnome buildbot itself? jhbuilds results in dbus-* processes being left over. With RHEL6 you could maybe do a cgroup and kill the whole process structure. -- Regards, Olav _______________________________________________ gnome-infrastructure mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-infrastructure
