Date: Fri, 31 May 2013 22:57:32 +0200 From: "bw.mail.lists" <bw.mail.lists@gmail.com> To: Steve Wills <swills@FreeBSD.org> Cc: freebsd-ports@FreeBSD.org Subject: Re: ruby 1.9 upgrade and puppet Message-ID: <51A90EBC.9020309@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
>> 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. > You're right. I guess I stupidly assumed that there isn't a separate port because: http://pastebin.com/5zPcqi35 (it's rather... wide and I'm not sure what the list policy on attachments is) There is no facter in the list of packages to be installed. So I'm guessing a dependency is wrong somewhere? I suppose that would explain why puppet is reporting facter as missing at install time, the wrong version is installed. Forcing a facter reinstall/recompile would fix it. >> 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. Not a problem, but maybe UPDATING should be updated? > >> For poudriere, puppet failed, still facter: >> >> =======================<phase: install >>> ============================ >> ===> Installing for puppet-3.1.1_2 >> ===> Generating temporary packing list >> ===> Checking if sysutils/puppet already installed >> ===> Creating users and/or groups. >> Creating group `puppet' with gid `814'. >> Creating user `puppet' with uid `814'. >> ftools not found. Using FileUtils instead.. >> Could not load facter; cannot install >> *** [do-install] Error code 255 >> >> Stop in /usr/ports/sysutils/puppet. >> ===> Cleaning for puppet-3.1.1_2 >> build of /usr/ports/sysutils/puppet ended at Fri May 31 11:37:10 CEST 2013 >> >> Rebuilding everything with 'poudriere bulk -c' worked fine. I'm aware >> that rebuilding everything isn't needed, but it didn't take that long. > > I'm unable to reproduce any build issues. Well, it's not a problem anymore, now that everything has been rebuilt. This happened once before IIRC. Poudriere is running every night, rebuilding updated packages. I remember seeing puppet fail at some point, but I didn't have time to look at it that day. Next night poudriere decided to rebuild everything for some reason and it got fixed, so I didn't bother taking a second look. I think this was the last puppet update. > >> But then, when upgrading with pkg, again I had to 'gem install facter' >> manually and kill the running script before puppet would restart. > > Could you send me a list of installed system packages and the output of > "gem list"? > Sure: ================================== # pkg info | awk '{print $1}' arping-2.09_2 augeas-1.0.0 bash-4.2.42 dmidecode-2.11 emacs-nox11-24.3_8,3 gettext-0.18.1.1_1 libevent-1.4.14b_2 libexecinfo-1.1_3 libffi-3.0.13 libiconv-1.14_1 libnet11-1.1.6_1,1 libxml2-2.8.0_2 libyaml-0.1.4_2 lsof-4.88.d,8 nginx-1.4.1,1 ngrep-1.45 openssl-1.0.1_8 pcre-8.32 pkg-1.0.12_1 pkgconf-0.9.2_1 puppet-3.1.1_2 ruby-1.9.3.429,1 ruby19-gems-1.8.25 ruby19-iconv-1.9.3.429,1 rubygem-bzip2-0.2.7 rubygem-facter-1.6.18_1 rubygem-hiera-1.1.2 rubygem-json_pure-1.7.7 rubygem-ruby-augeas-0.5.0 sudo-1.8.6.p8 tmux-1.8 vim-lite-7.3.669_2 # gem list *** LOCAL GEMS *** bzip2-ruby (0.2.7) facter (1.7.1) hiera (1.1.2) json_pure (1.7.7) ruby-augeas (0.5.0) ================================== There's a difference in version between the facter that pkg knows it's installed and the one ruby knows about, that's because this is one of the systems where I installed facter manually. I still have systems that aren't updated if you need some info from those, but none that are to be updated with portmaster. Puppet is the only reason why ruby is installed at all, everything there is puppet related.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?51A90EBC.9020309>