Date: Fri, 31 May 2013 15:03:59 +0100 From: Chris Rees <crees@FreeBSD.org> To: Steve Wills <swills@freebsd.org> Cc: "bw.mail.lists" <bw.mail.lists@gmail.com>, FreeBSD Mailing List <freebsd-ports@freebsd.org> Subject: Re: ruby 1.9 upgrade and puppet Message-ID: <CADLo83-rpHAw8BhtbFq6CFa4TBVPVSOZf6T=UjuzHDhY7WupYQ@mail.gmail.com> In-Reply-To: <f7a63bad37b9ef7e3917521a14146ab7.squirrel@mouf.net> References: <51A88F42.5010503@gmail.com> <f7a63bad37b9ef7e3917521a14146ab7.squirrel@mouf.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 31 May 2013 14:27, Steve Wills <swills@freebsd.org> wrote: >> Moving to ruby 1.9 by following the instructions in UPDATING breaks >> puppet. >> >> When updating with portmaster, at install time it says 'could not load >> facter; cannot install' and exits. I had to manually run 'gem install >> facter', then puppet installed. > > It's better to install via the port so that the package management knows > it's there. This could be causing the later problems. > >> However, 'service puppetmaster status' >> was reporting puppet as not running even though it was, so I had to kill >> the running process before 'service puppetmaster start'. I assume this >> is related to $command_interpreter in the rc script being changed from >> ruby18 to ruby19? Although, /usr/local/bin/ruby and >> /usr/local/bin/ruby19 are identical, can't the script use plain ruby >> instead of ruby19? >> > > It would probably be best to kill puppet before the upgrade. This is definitely the problem here. I'm afraid you'll have to manually kill it here, since the old rc script has been deinstalled. You'll only have to do it this once. Chris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CADLo83-rpHAw8BhtbFq6CFa4TBVPVSOZf6T=UjuzHDhY7WupYQ>