Hello list, Yesterday and today, I've been busy either patching boxes for the BIND advisory that we received on the 23rd (when they were running 8.1 or 8.2-RELEASE), or upgrading them (when running 8.0-RELEASE). Today I've come across 2 boxes running 8.2-STABLE and of course, the BIND patch wouldn't apply correctly. I've decided to cvsup them to 8.2-RELEASE and "upgrade" them to it. I've gone through the following steps: - make buildworld - make buildkernel - make installkernel - nextboot -k my new kernel, to ensure it worked fine - rebooted again with the new kernel, this time correctly installed as /boot/kernel - installed the world - run mergemaster -FiPU - rebuild ports Now, I'm facing this odd situation where, just after booting, I get this on the 2 boxes: root 22 0.0 0.0 8256 1876 v0 Is+ 7:32PM 0:00.03 sh /etc/rc autoboot root 1250 0.0 0.0 18000 2576 v0 I+ 7:32PM 0:00.04 /usr/local/sbin/rsyslogd -a /var/run/log -a /var/named/var/run/log -i /var/run/syslog.pid -f /usr/local/etc/rsyslog.conf root 1790 0.0 0.0 8256 1952 v0 I+ 7:32PM 0:00.00 sh /etc/rc autoboot root 1793 0.0 0.0 8256 1952 v0 I+ 7:32PM 0:00.00 sh /etc/rc autoboot Does anybody have an idea why I get these stuck "sh /etc/rc autoboot" processes ? Any pointers as to where I should look ? /var/run/dmesg.boot doesn't give much useful info. They're backup firewalls so I can run complementary tests on them as required.
On Tue, Dec 27, 2011 at 07:46:52PM +0100, Damien Fleuriot wrote:> Hello list, > > Yesterday and today, I've been busy either patching boxes for the BIND > advisory that we received on the 23rd (when they were running 8.1 or > 8.2-RELEASE), or upgrading them (when running 8.0-RELEASE). > > > Today I've come across 2 boxes running 8.2-STABLE and of course, the > BIND patch wouldn't apply correctly. > > I've decided to cvsup them to 8.2-RELEASE and "upgrade" them to it.Why cvsup and not csup? Secondly, and more importantly, when upgrading to a different tag (e.g. you were using RELENG_8_0 before, moving to RELENG_8 or RELENG_8_2 -- you don't really explain in a coherent way what you did, you've mentioned 4 different FreeBSD versions above :-) ), I tend to do the following: rm -fr /usr/obj/* rm -fr /var/db/sup/src-all rm -fr /usr/src/* csup ... The problem I've seen is that "some" source bits manage to figure out that they need to be updated to a different version based on the release tag in the cvsup/csup configuration file, but sometimes this doesn't work quite right and the underlying source files in /usr/src end up getting "mix-matched" between two versions. You may want to do this for ports as well, e.g.: rm -fr /var/db/sup/ports-all rm -fr /usr/ports/* csup ... It gets more tricky assuming during your original FreeBSD installation you chose to install src and ports. The below is the cvsup FAQ, but it applies to csup too. Read items 11, 12, and 13. http://www.cvsup.org/faq.html#caniadopt Welcome to why I never bother to install src or ports from CD/DVD, I simply use csup once the system is up. And for changing tags/releases, I do what's described above.> I've gone through the following steps: > - make buildworld > - make buildkernel > - make installkernel > - nextboot -k my new kernel, to ensure it worked fine > - rebooted again with the new kernel, this time correctly installed as > /boot/kernel > - installed the world > - run mergemaster -FiPU > - rebuild portsThis doesn't look correct. The process you should be following is documented plainly in /usr/src/Makefile. You're missing some steps. Try doing what I recommended above, and following what's in /usr/src/Makefile, and then see if things improve. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB |
On 27 December 2011 22:46, Damien Fleuriot <ml@my.gd> wrote:> Hello list, > > > > Yesterday and today, I've been busy either patching boxes for the BIND > advisory that we received on the 23rd (when they were running 8.1 or > 8.2-RELEASE), or upgrading them (when running 8.0-RELEASE). > > > Today I've come across 2 boxes running 8.2-STABLE and of course, the > BIND patch wouldn't apply correctly. > > I've decided to cvsup them to 8.2-RELEASE and "upgrade" them to it. > > > I've gone through the following steps: > - make buildworld > - make buildkernel > - make installkernel > - nextboot -k my new kernel, to ensure it worked fine > - rebooted again with the new kernel, this time correctly installed as > /boot/kernel > - installed the world > - run mergemaster -FiPU > - rebuild ports > > > Now, I'm facing this odd situation where, just after booting, I get this > on the 2 boxes: > > > root ? ? ? ? 22 ?0.0 ?0.0 ?8256 ?1876 ?v0 ?Is+ ? 7:32PM ? 0:00.03 sh > /etc/rc autoboot > root ? ? ? 1250 ?0.0 ?0.0 18000 ?2576 ?v0 ?I+ ? ?7:32PM ? 0:00.04 > /usr/local/sbin/rsyslogd -a /var/run/log -a /var/named/var/run/log -i > /var/run/syslog.pid -f /usr/local/etc/rsyslog.conf > root ? ? ? 1790 ?0.0 ?0.0 ?8256 ?1952 ?v0 ?I+ ? ?7:32PM ? 0:00.00 sh > /etc/rc autoboot > root ? ? ? 1793 ?0.0 ?0.0 ?8256 ?1952 ?v0 ?I+ ? ?7:32PM ? 0:00.00 sh > /etc/rc autoboot > > > Does anybody have an idea why I get these stuck "sh /etc/rc autoboot" > processes ? > > Any pointers as to where I should look ?Check if the box has a working resolving during boot. This is a main reason why it may stuck in /etc/rc phase. When on physical console, type ^T. Usually it will get you the name of offending process. You posted output from ps aux. It would be nice if you post ps auxl, so values of MWCHAN ps keyword will be also seen, which can add an additional debugging info. -- wbr, pluknet