From owner-freebsd-questions Mon Oct 7 23:34:25 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 4CCF637B401 for ; Mon, 7 Oct 2002 23:34:23 -0700 (PDT) Received: from vectors.cx (manifold.vectors.cx [64.163.147.229]) by mx1.FreeBSD.org (Postfix) with ESMTP id D121743E9C for ; Mon, 7 Oct 2002 23:34:22 -0700 (PDT) (envelope-from monkey@vectors.cx) Received: from vectors.cx (a5f1867f90e046ad4ec673e6c8dbbd6c@localhost [127.0.0.1]) by vectors.cx (8.12.6/8.12.4) with ESMTP id g986ZQho083510; Mon, 7 Oct 2002 23:35:26 -0700 (PDT) (envelope-from monkey@vectors.cx) Received: (from monkey@localhost) by vectors.cx (8.12.6/8.12.6/Submit) id g986ZQwo083509; Mon, 7 Oct 2002 23:35:26 -0700 (PDT) (envelope-from monkey) Date: Mon, 7 Oct 2002 23:35:26 -0700 From: Adam Weinberger To: Tom Carrick Cc: freebsd-questions@FreeBSD.ORG Subject: Re: portupgrade problem Message-ID: <20021008063525.GK81796@vectors.cx> References: <1034050523.370.13.camel@knyghtmare.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1034050523.370.13.camel@knyghtmare.com> X-Editor: Vim 6.1 http://www.vim.org X-Mailer: Mutt 1.5 http://www.mutt.org X-URL: http://www.vectors.cx http://www.crackula.com User-Agent: Mutt/1.5.1i 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 try portsdb -fu. the switches are easy enough to remember ::P. portupgrade dies from time to time, and that command can often get you back in business. -Adam >> (10.07.2002 @ 2115 PST): Tom Carrick said, in 2.0K: << > I was using portupgrade happily upgrading my ports, when it barfed in > the middle of something. I don't remember exactly what, I think it could > have been links or libslang. I don't remember the exact error, only that > it had something to do with memory. So I assumed there just wasn't > enough available. I checked with top, and I still had a good 50MB of RAM > available, and most of my swap space (500MB orso) free. > > Fair enough. So I try to continue. It fails on the package upgrade. > Trying to find out what fails, I tried pkgdb -u. Failed. Same error. I > tried deleting portupgrade and installing it again, to no effect. > > It invariably, depending on the phase of the moon, I suppose, gives one > of two errors, either: > > root@knyghtmare:/root# pkgdb -u > [Updating the pkgdb in /var/db/pkg ... - 325 > packages found (-3 +2) > (...)/usr/local/lib/ruby/site_ruby/1.6/pkgdb.rb:435: [BUG] Segmentation > fault > ruby 1.6.7 (2002-09-12) [i386-freebsd4] > Abort (core dumped) > > or... > > root@knyghtmare:/root# pkgdb -u > [Updating the pkgdb in /var/db/pkg ... - 325 > packages found (-3 +2) (...)Cannot allocate memory: Cannot update the > pkgdb!] > > I've tried rebooting. Doesn't seem to help, and it was working fine > until it barfed on me. > > I've tried deleting links and libslang, too, in case it messed the > database somehow. That's still my best theory, though deleting them > didn't help. > > Anyone have any ideas? >> end of "portupgrade problem" from Tom Carrick << -- "Oh good, my dog found the chainsaw." -Lilo, "Lilo & Stitch" Adam Weinberger adam@vectors.cx To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message