Re: Portupgrade problem, possible pkgdb problem?
Thanks, guess it's time to use the work around, the env setting worked fine. -- "Ethernet (n): something used to catch the etherbunny" John Mire: [EMAIL PROTECTED]Network Administration 318-675-5434 LSU Health Sciences Center - Shreveport -Original Message- From: Matthew Seaman <[EMAIL PROTECTED]> To: Mire, John <[EMAIL PROTECTED]> CC: Matt Navarre <[EMAIL PROTECTED]>; [EMAIL PROTECTED] <[EMAIL PROTECTED]> Sent: Thu Oct 07 12:41:17 2004 Subject: Re: Portupgrade problem, possible pkgdb problem? On Thu, Oct 07, 2004 at 10:45:46AM -0500, Mire, John wrote: > I'm still getting this error after a cvsup+buildworld, a make fetchindex and > I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?: > > test# uname -v > FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct 6 17:13:13 CDT 2004 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST > test# cd /usr/ports > test# make fetchindex > Receiving INDEX-5 (5881230 bytes): 100% > 5881230 bytes transferred in 16.9 seconds (339.01 kBps) > test# portupgrade -R sudo > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 11735 port entries found > .1000.2000.3000.4000.5000.60 > 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb > :587: [BUG] Bus Error > ruby 1.8.2 (2004-07-29) [i386-freebsd5] > > Abort (core dumped) > test# rm /var/db/pkg/pkgdb.db > test# portupgrade -R sudo > [Rebuilding the pkgdb in /var/db/pkg ... - 54 packages > found (-0 +54) .. done] > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 11735 port entries found > .1000.2000.3000.4000.5000.60 > 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb > :587: [BUG] Bus Error > ruby 1.8.2 (2004-07-29) [i386-freebsd5] > > Abort (core dumped) > test# The patch was only applied to RELENG_4, RELENG_5 and HEAD -- not RELENG_5_2. However, you can extract it from cvs and apply it yourself by hand if you aren't in a position to upgrade right now -- see: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff? r1=1.5&r2=1.7 (Remember that you'll have to re-apply that patch each time you cvsup(1) your src) Otherwise just use one of the variations on: setenv PORTS_DBDRIVER=bdb1_hash as a workaround. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade problem, possible pkgdb problem?
On Thu, Oct 07, 2004 at 10:45:46AM -0500, Mire, John wrote: > I'm still getting this error after a cvsup+buildworld, a make fetchindex and > I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?: > > test# uname -v > FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct 6 17:13:13 CDT 2004 > [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST > test# cd /usr/ports > test# make fetchindex > Receiving INDEX-5 (5881230 bytes): 100% > 5881230 bytes transferred in 16.9 seconds (339.01 kBps) > test# portupgrade -R sudo > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 11735 port entries found > .1000.2000.3000.4000.5000.60 > 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb > :587: [BUG] Bus Error > ruby 1.8.2 (2004-07-29) [i386-freebsd5] > > Abort (core dumped) > test# rm /var/db/pkg/pkgdb.db > test# portupgrade -R sudo > [Rebuilding the pkgdb in /var/db/pkg ... - 54 packages > found (-0 +54) .. done] > [Failed `Inappropriate file type or format'] [Updating the portsdb > in /usr/ports ... - 11735 port entries found > .1000.2000.3000.4000.5000.60 > 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb > :587: [BUG] Bus Error > ruby 1.8.2 (2004-07-29) [i386-freebsd5] > > Abort (core dumped) > test# The patch was only applied to RELENG_4, RELENG_5 and HEAD -- not RELENG_5_2. However, you can extract it from cvs and apply it yourself by hand if you aren't in a position to upgrade right now -- see: http://www.freebsd.org/cgi/cvsweb.cgi/src/lib/libc/db/btree/bt_split.c.diff?r1=1.5&r2=1.7 (Remember that you'll have to re-apply that patch each time you cvsup(1) your src) Otherwise just use one of the variations on: setenv PORTS_DBDRIVER=bdb1_hash as a workaround. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpRm4klv3Ptz.pgp Description: PGP signature
RE: Portupgrade problem, possible pkgdb problem?
I'm still getting this error after a cvsup+buildworld, a make fetchindex and I have deleted /var/db/pkg/pkgdb.db and rebuilt it, what's the patch?: test# uname -v FreeBSD 5.2.1-RELEASE-p11 #12: Wed Oct 6 17:13:13 CDT 2004 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/TEST test# cd /usr/ports test# make fetchindex Receiving INDEX-5 (5881230 bytes): 100% 5881230 bytes transferred in 16.9 seconds (339.01 kBps) test# portupgrade -R sudo [Failed `Inappropriate file type or format'] [Updating the portsdb in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# rm /var/db/pkg/pkgdb.db test# portupgrade -R sudo [Rebuilding the pkgdb in /var/db/pkg ... - 54 packages found (-0 +54) .. done] [Failed `Inappropriate file type or format'] [Updating the portsdb in /usr/ports ... - 11735 port entries found .1000.2000.3000.4000.5000.60 00.7000.8000/usr/local/lib/ruby/site_ruby/1.8/portsdb.rb :587: [BUG] Bus Error ruby 1.8.2 (2004-07-29) [i386-freebsd5] Abort (core dumped) test# -- "Ethernet (n): something used to catch the etherbunny" John Mire: [EMAIL PROTECTED]Network Administration 318-675-5434 LSU Health Sciences Center - Shreveport The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Matthew Seaman > Sent: Sunday, September 26, 2004 4:14 AM > To: Matt Navarre > Cc: [EMAIL PROTECTED] > Subject: Re: Portupgrade problem, possible pkgdb problem? > > On Sat, Sep 25, 2004 at 06:14:18PM -0700, Matt Navarre wrote: > > On Saturday 25 September 2004 05:13, Alex de Kruijff wrote: > > > > It could be a problem with the DBDriver. You could try this: > > > Edit /root/.cs... > > > and add > > > PORTS_DBDRIVER=bdb1_hash > > > PKG_DBDRIVER=bdb1_hash > > > Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz > it isn't in this > > case, it fails gracefully. > > The core dump is seen with portsdb(1) trying to create > /usr/ports/INDEX.db -- however, the underlying bug can affect anywhere > that ruby uses bdb1_btree files. pkgdb(1) occasionally going a bit > funny is a problem that's been known about for some time; usually just > deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out. > However, I don't think anyone had ever tracked down the root cause of > the problem. Then the portsdb coredumping thing came along, and it > seems an obvious conclusion that the same thing might be affecting > both programs. > > Note that a fix for the bdb1_btree problem has been in HEAD for a few > weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago. > So an alternative fix could be cvsup+buildworld. Unfortunately, I > don't think the fix will be applied to any of the existing 4.x-RELEASE > or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when > that comes out, and it's pretty easy to do if you want to patch things > yourself. > > > I'll go ahead and try this, but I suspect that the > /var/db/pkg info for > > gnucash or one of it's dependancies got horked up. We'll see. > > > > > Then execute this in your shell also. Then do: > > > pkgdb -u && portsdb -u && portupgrade -R gnucash > > Yup. That should ensure you get a clean install of gnucash and all of > its dependencies. > > Cheers, > > Matthew > > -- > Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks > Savill Way > PGP: http://www.infracaninophile.co.uk/pgpkey Marlow > Tel: +44 1628 476614 Bucks., > SL7 1TH UK > ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade problem, possible pkgdb problem?
On Sat, Sep 25, 2004 at 06:14:18PM -0700, Matt Navarre wrote: > On Saturday 25 September 2004 05:13, Alex de Kruijff wrote: > > It could be a problem with the DBDriver. You could try this: > > Edit /root/.cs... > > and add > > PORTS_DBDRIVER=bdb1_hash > > PKG_DBDRIVER=bdb1_hash > Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this > case, it fails gracefully. The core dump is seen with portsdb(1) trying to create /usr/ports/INDEX.db -- however, the underlying bug can affect anywhere that ruby uses bdb1_btree files. pkgdb(1) occasionally going a bit funny is a problem that's been known about for some time; usually just deleting and rebuilding /var/db/pkg/pkgdb.db will sort things out. However, I don't think anyone had ever tracked down the root cause of the problem. Then the portsdb coredumping thing came along, and it seems an obvious conclusion that the same thing might be affecting both programs. Note that a fix for the bdb1_btree problem has been in HEAD for a few weeks, and was MFC'd to both RELENG_4 and RELENG_5 a week or so ago. So an alternative fix could be cvsup+buildworld. Unfortunately, I don't think the fix will be applied to any of the existing 4.x-RELEASE or 5.x-RELEASE branches -- it will of course be in 5.3-RELEASE when that comes out, and it's pretty easy to do if you want to patch things yourself. > I'll go ahead and try this, but I suspect that the /var/db/pkg info for > gnucash or one of it's dependancies got horked up. We'll see. > > > Then execute this in your shell also. Then do: > > pkgdb -u && portsdb -u && portupgrade -R gnucash Yup. That should ensure you get a clean install of gnucash and all of its dependencies. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgpVii1Bm2YMS.pgp Description: PGP signature
Re: Portupgrade problem, possible pkgdb problem?
On Saturday 25 September 2004 05:13, Alex de Kruijff wrote: > On Sat, Sep 25, 2004 at 04:18:47PM -0700, Matt Navarre wrote: > > On Saturday 25 September 2004 02:35, Matt Navarre wrote: > > > I'm trying to upgrade gnucash, but portupgrade is choking: > > > <*snip*> > > > > > > It looks like the pkgdb has something wrong with it, but pkgdb -Fu > > > doesn't report anything that seems like it would cause portupgrade to > > > bomb. There's a duplicate origin for cdrtools, but that doesn't seem to > > > pertain. > > > > > > Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? > > > Will pkgdb -u recreate pkgdb.db? > > > > Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the > > same problem. Odd thing is that so far gnucash is the only installed > > package that generates this error. I suppose I can pkg_delete it and try > > reinstalling. > > It could be a problem with the DBDriver. You could try this: > Edit /root/.cs... > and add > PORTS_DBDRIVER=bdb1_hash > PKG_DBDRIVER=bdb1_hash Doesn't the DBDRIVER bug result in ruby dumping core? 'Cuz it isn't in this case, it fails gracefully. I'll go ahead and try this, but I suspect that the /var/db/pkg info for gnucash or one of it's dependancies got horked up. We'll see. > Then execute this in your shell also. Then do: > pkgdb -u && portsdb -u && portupgrade -R gnucash -- "We all enter this world in the same way: naked, screaming, and soaked in blood. But if you live your life right, that kind of thing doesn't have to stop there." -- Dana Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade problem, possible pkgdb problem?
On Sat, Sep 25, 2004 at 04:18:47PM -0700, Matt Navarre wrote: > On Saturday 25 September 2004 02:35, Matt Navarre wrote: > > I'm trying to upgrade gnucash, but portupgrade is choking: > > > > reichlieu# portupgrade -R gnucash > > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot > > convert nil into String (PkgDB::DBError) > > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in > > `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' > > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from > > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from > > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from > > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from > > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from > > /usr/local/sbin/portupgrade:674:in `main' > > from /usr/local/sbin/portupgrade:207:in `initialize' > > from /usr/local/sbin/portupgrade:207:in `new' > > from /usr/local/sbin/portupgrade:207:in `main' > > from /usr/local/sbin/portupgrade:1845 > > > > It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't > > report anything that seems like it would cause portupgrade to bomb. There's > > a duplicate origin for cdrtools, but that doesn't seem to pertain. > > > > Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will > > pkgdb -u recreate pkgdb.db? > > Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the same > problem. Odd thing is that so far gnucash is the only installed package that > generates this error. I suppose I can pkg_delete it and try reinstalling. It could be a problem with the DBDriver. You could try this: Edit /root/.cs... and add PORTS_DBDRIVER=bdb1_hash PKG_DBDRIVER=bdb1_hash Then execute this in your shell also. Then do: pkgdb -u && portsdb -u && portupgrade -R gnucash -- Alex Articles based on solutions that I use: http://www.kruijff.org/alex/FreeBSD/ ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: Portupgrade problem, possible pkgdb problem?
On Saturday 25 September 2004 02:35, Matt Navarre wrote: > I'm trying to upgrade gnucash, but portupgrade is choking: > > reichlieu# portupgrade -R gnucash > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:323:in `deorigin': cannot > convert nil into String (PkgDB::DBError) > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:916:in > `tsort_build' from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `each' > from /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:915:in `tsort_build' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `each' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:907:in `tsort_build' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:929:in `sort_build' from > /usr/local/lib/ruby/site_ruby/1.8/pkgdb.rb:933:in `sort_build!' from > /usr/local/sbin/portupgrade:674:in `main' > from /usr/local/sbin/portupgrade:207:in `initialize' > from /usr/local/sbin/portupgrade:207:in `new' > from /usr/local/sbin/portupgrade:207:in `main' > from /usr/local/sbin/portupgrade:1845 > > It looks like the pkgdb has something wrong with it, but pkgdb -Fu doesn't > report anything that seems like it would cause portupgrade to bomb. There's > a duplicate origin for cdrtools, but that doesn't seem to pertain. > > Should I move /var/db/pkg/pkgdb.db out of the way and regenerate it? Will > pkgdb -u recreate pkgdb.db? Ok, that didn't work. I regenerated pkgdb.db using pkgdb -u and got the same problem. Odd thing is that so far gnucash is the only installed package that generates this error. I suppose I can pkg_delete it and try reinstalling. > > Thanks, > Matt -- "We all enter this world in the same way: naked, screaming, and soaked in blood. But if you live your life right, that kind of thing doesn't have to stop there." -- Dana Gould ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
