From owner-freebsd-questions Tue Oct 1 3:28:37 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0533037B401 for ; Tue, 1 Oct 2002 03:28:35 -0700 (PDT) Received: from web20204.mail.yahoo.com (web20204.mail.yahoo.com [216.136.226.59]) by mx1.FreeBSD.org (Postfix) with SMTP id BCA2F43E3B for ; Tue, 1 Oct 2002 03:28:34 -0700 (PDT) (envelope-from fbsd2@yahoo.com) Message-ID: <20021001102834.74712.qmail@web20204.mail.yahoo.com> Received: from [209.249.182.113] by web20204.mail.yahoo.com via HTTP; Tue, 01 Oct 2002 03:28:34 PDT Date: Tue, 1 Oct 2002 03:28:34 -0700 (PDT) From: A Ling Subject: Re: help with portupgrade portupgrade mess? (Solved) To: freebsd-questions@FreeBSD.org In-Reply-To: <200209301502.47675.danny@ricin.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Sorry to follow-up my own post, and thanks much to everyone who replied, but in case anyone else runs into this, for the archives, I now think the problem had nothing to do with rebuilding the port. The last paragraph of the man page warns: Sometimes a database may get corrupt and the pkgtools commands start to abort due to segmentation fault. In such cases, run ``pkgdb -fu'' to rebuild the database, and the problems will go away. Indeed, pkgdb -fu (but not pkgdb -u as I previously repeatedly tried) seems to have fixed it. I think how this arose is that while waiting for a particularly long time during the compilation of one port, I opened a second xterm to upgrade some much less complex ports. Keeping an eye on both windows, I was sure they never were both updating the package database at the same time. But they must have collided & corrupted the database. On Monday 30 September 2002, A Ling wrote: > If I'd known I'd have troubles, I'd have kept a > careful log of which errors occured under which > conditions. Unfortunately, I tried what seemed > obvious after looking at the man pages and message > archives, so the following is a reconstruction > from > memory. > > After doing 'portupgrade portupgrade', I got > /usr/local/sbin/portupgrade:34:in `require': No > such > file to load -- > optparse (LoadError) > > After cvsup-ing ports, portsdb -uU and various > portupgrade -r ruby portupgrade machinations, I > started getting > [Updating the pkgdb in > /var/db/pkg > ... - 266 > packages found (-1 +2) (...)Cannot allocate > memory: > Cannot update the > pkgdb!] > > After searching the message archives and make > deinstall; make clean; make reinstall of ruby* and > portupgrade, I got memory allocation errors like > this > # pkgdb -u > [Updating the pkgdb in > /var/db/pkg > ... - 187 packages found (-4 +4) > > (...)/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:435:in > `each': tried to allocate too big memory > (NoMemoryError) > from > /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:435:in > `select' > from > /usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:435:in > `update_db' > from /usr/local/sbin/pkgdb:201:in `main' > from /usr/local/sbin/pkgdb:61:in > `initialize' > from /usr/local/sbin/pkgdb:61:in `new' > from /usr/local/sbin/pkgdb:61:in `main' > from /usr/local/sbin/pkgdb:914 > > I also updated to the latest stable world from > yesterday (previously from 4 August) to no avail. > Login.conf limits are untouched by me, and the > current packages include > # pkg_info -aI | egrep 'ruby|portup' | col1 > portupgrade-20020921.1 > ruby-1.6.7.2002.09.12 > ruby-bdb1-0.1.7 > ruby-shim-ruby18-1.7.3.2002.09.20 > > Anyone recognize this or have suggestions? __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message