LISTSERV mailing list manager LISTSERV 16.5

Help for CODE4LIB Archives


CODE4LIB Archives

CODE4LIB Archives


CODE4LIB@LISTS.CLIR.ORG


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

CODE4LIB Home

CODE4LIB Home

CODE4LIB  February 2012

CODE4LIB February 2012

Subject:

Re: Berkeley DB and NOID

From:

Joshua Gomez <[log in to unmask]>

Reply-To:

[log in to unmask]

Date:

Tue, 14 Feb 2012 13:50:05 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (128 lines)

That didn't work either. I started with a fresh copy of the NOID directory
from before I tried the upgrade command:

gomez@gwnma:/var/www/nd/t1$ ls NOID
__db.001  __db.003  __db.005  lock  log.0000000001  noid.bdb
__db.002  __db.004  __db.006  log   logbdb          README

gomez@gwnma:/var/www/nd/t1$ sudo rm NOID/__*

gomez@gwnma:/var/www/nd/t1$ sudo db4.8_upgrade -v -h NOID noid.bdb
db4.8_upgrade: noid.bdb upgraded successfully

gomez@gwnma:/var/www/nd/t1$ curl localhost/nd/noidu_t1?mint+1
no "Env" object (No such file or directory)

I have been binding the IDs for the production NOID db (t1 is just the test
NOID), but I have also been storing them in a mysql DB on our dspace server
that I use to keep track of where things are in the workflow. So I suppose
I could try what you suggested: setup a new production NOID, mint as many
IDs as we have used so far, then rebind them all using the data in the
mysql DB. Redundant data is a good thing.

-Joshua

On Tue, Feb 14, 2012 at 1:07 PM, John A. Kunze <[log in to unmask]> wrote:

> Try removing the environment files before you upgrade (or after if
> you didn't save the old file).  When I released that version of NOID
> I have since regretted leaving in code that created a stub environment
> (that actually isn't used by NOID) because it just creates upgrade
> problems that I never figured out properly.
>
> If all else fails and you're just using NOID to mint (eg, no binding),
> it's quite easy to start a new minter from scratch and mint until you see
> the last id you minted prior to conversion.  The order of minting is
> deterministic, so in the end you'll have a new minter that's in the same
> "state" as the old minter (again, provided you haven't been doing holds
> and binds -- that's more complicated).
>
> -John
>
>
> --- On Tue, 14 Feb 2012, Joshua Gomez wrote:
>
>> Thanks John!  I tried running db_upgrade, but apparently the utilities
>> were
>> not included in my setup. So I ran the following:
>>
>> gomez@gwnma:/var/www/nd/t1$ sudo apt-get install db4.8-util
>>
>> That installed the utilities, but I'm still having some trouble:
>>
>> gomez@gwnma:/var/www/nd/t1$ sudo db4.8_upgrade -v -h NOID NOID/noid.bdb
>> db4.8_upgrade: Program version 4.8 doesn't match environment version 4.7
>> db4.8_upgrade: DB_ENV->open: DB_VERSION_MISMATCH: Database environment
>> version mismatch
>>
>> I tried leaving off the environment home flag
>>
>> gomez@gwnma:/var/www/nd/t1$ sudo db4.8_upgrade -v NOID/noid.bdb
>> db4.8_upgrade: NOID/noid.bdb upgraded successfully
>>
>> That looks like it worked. However, when I try making a call to the
>> service
>> I get the old error:
>>
>> gomez@gwnma:/var/www/nd/t1$ curl localhost/nd/noidu_t1?mint+1
>> no "Env" object (DB_VERSION_MISMATCH: Database environment version
>> mismatch)
>>
>> -Josh
>>
>>
>> On Mon, Feb 13, 2012 at 5:42 PM, John A. Kunze <[log in to unmask]> wrote:
>>
>>  The standard BerkeleyDB library probably changed when you upgraded
>>> Ubuntu, and it complains that the NOID database (written with the old
>>> library) is incompatible.
>>>
>>> You should be able to use db_upgrade to convert the NOID database
>>> (NOID/noid.bdb).  db_upgrade is a command line utility that comes with
>>> BerkeleyDB.
>>>
>>> -John
>>>
>>>
>>> --- On Mon, 13 Feb 2012, Joshua Gomez wrote:
>>>
>>>  Does anyone here have expertise with Berkeley DB?
>>>>
>>>> I was running an instance of NOID (which uses Berkeley DB) to mint and
>>>> resolve ARKs.  I updated the OS for the server it was running on from
>>>> Ubuntu 9 to Ubuntu 10.  Now NOID has stopped working and complains that
>>>> the
>>>> db version doesn't match: "Program version 4.8 doesn't match environment
>>>> version 4.7"
>>>>
>>>> I have no experience at all with Berkeley DB and could use some advice.
>>>>
>>>> Thanks,
>>>> Josh
>>>>
>>>> --
>>>> Joshua Gomez
>>>> Digital Library Programmer Analyst
>>>> George Washington University Libraries
>>>> 2130 H St, NW Washington, DC 20052
>>>> (202) 994-8267
>>>>
>>>>
>>>>
>>
>> --
>> Joshua Gomez
>> Digital Library Programmer Analyst
>> George Washington University Libraries
>> 2130 H St, NW Washington, DC 20052
>> (202) 994-8267
>>
>>


-- 
Joshua Gomez
Digital Library Programmer Analyst
George Washington University Libraries
2130 H St, NW Washington, DC 20052
(202) 994-8267

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
December 2008
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
March 2008
February 2008
January 2008
December 2007
November 2007
October 2007
September 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003

ATOM RSS1 RSS2



LISTS.CLIR.ORG

CataList Email List Search Powered by the LISTSERV Email List Manager