Well, it looks like I may be a victim of a bad commit (80ad89e384e04bd0835a13f246840f4f71113263 on April 27), that was rolled back about a week ago (9588ecbb8c8e3b628a1187e88d664662b83c97d5 on July 6). I'm updating my vzctl to HEAD. Let's see if that fixes the problem.
[email protected] wrote: ->From: [email protected] ->To: [email protected] ->Date: Thu, 15 Jul 2010 04:34:09 +0000 ->Message-ID: <[email protected]> > >Hi guys, > >When I try to start a container, vzctl exits 131 (unable to set container >name). Now, there are a number of places where it's possible to exit 131, >so I tracked it down to lib/env.c (around line 555), obviously because >get_dist_name() (see lib/dist.c circa line 200) returns NULL. Now, >before I go any further, does anybody happen to know off-hand what's >likely to be wrong? In case it's any help: before my last HN update, >containers always used to give me some silly warning about "no distro >picked, using defaults," before starting the containers successfully. >I'm not quite sure what this has to do with "unable to set container >name," but the source code doesn't seem to be any more sure than I am. >If nothing else, this is definitely a return-code bug at minimum. > >-- >Uncle Cosmo, why do they call this a word processor? >It's simple, Skyler. You've seen what food processors do to food, right? >_______________________________________________ >Users mailing list >[email protected] >https://openvz.org/mailman/listinfo/users _______________________________________________ Users mailing list [email protected] https://openvz.org/mailman/listinfo/users
