Re: Cyrus IMAPd 2.3.2 Released

2006-02-28 Thread Ken Murchison

Tuan Van wrote:

Rosenbaum, Larry M. wrote:


We haven't changed anything about the databases.  We are using whatever
the defaults are, and Berkeley 4.4.16.  From testing with the
cvt_cyrusdb program, it looks like the old program will open the old
database, and the new program will open the new database, but the new
program won't open the old database, and the old program won't open the
new database.

# ./cvt_cyrusdb ~lmr/deliver.db.old berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db.old (berkeley-nosync) to
/home/lmr/y.txt (flat)
fatal error: can't open old database

# ./cvt_cyrusdb ~lmr/deliver.db berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db (berkeley-nosync) to

/home/lmr/y.txt (flat)

# ./cvt_cyrusdb.old ~lmr/deliver.db.old berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db.old (berkeley-nosync) to
/home/lmr/y.txt (flat)
Warning: apparently empty database converted.

# ./cvt_cyrusdb.old ~lmr/deliver.db berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db (berkeley-nosync) to

/home/lmr/y.txt (flat)
fatal error: can't open old database

L
 


Could it be a typo in lib/cyrusdb_berkeley.c ?
I try it with patch below and it seem to work.

--- lib/cyrusdb_berkeley.c.orig 2006-02-27 16:56:53.0 -0800
+++ lib/cyrusdb_berkeley.c  2006-02-27 16:57:35.0 -0800
@@ -981,7 +981,7 @@
 mysync,
 myarchive,

-open_hash,
+open_btree,
 myclose,

 fetch,
@@ -1007,7 +1007,7 @@
 mysync,
 myarchive,

-open_hash,
+open_btree,
 myclose,

 fetch,


Yeah, thats it.  A simple cut-n-paste error.  I'll spin a 2.3.3 shortly.

--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Cyrus IMAPd 2.3.2 Released

2006-02-28 Thread Ken Murchison

Andrzej Kwiatkowski wrote:

2006/2/27, Ken Murchison [EMAIL PROTECTED]:


Larry Rosenbaum wrote:


Has something changed in the database format?  I upgraded a test system from
v2.3.1 to v2.3.2 and it didn't seem to like the deliver.db file:




I don't checked in doc/ files but what with bug in murder enviroment
on frontend installation ??


If you mean the bug where you had to use 2.2 proxys, yes this is fixed.


--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


RE: Cyrus IMAPd 2.3.2 Released

2006-02-27 Thread Larry Rosenbaum
Has something changed in the database format?  I upgraded a test system from
v2.3.1 to v2.3.2 and it didn't seem to like the deliver.db file:

Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 866726 local6.warning] DBERROR
db4: /usr/local/cyrus/config/deliver.db: unexpected file type or format
Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 729713 local6.error] DBERROR:
opening /usr/local/cyrus/config/deliver.db: Invalid argument
Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 729713 local6.error] DBERROR:
opening /usr/local/cyrus/config/deliver.db: cyrusdb error
Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 157947 local6.error] FATAL:
lmtpd: unable to init duplicate delivery database
Feb 27 13:38:22 emroute1x master[17669]: [ID 684980 local6.warning] service
lmtpunix pid 20020 in READY state: terminated abnormally

Deleting the file and restarting made it happier.

 -Original Message-
 From: [EMAIL PROTECTED] [mailto:info-cyrus-
 [EMAIL PROTECTED] On Behalf Of Ken Murchison
 Sent: Monday, February 27, 2006 11:42 AM
 To: Cyrus Mailing List; [EMAIL PROTECTED]; cyrus-
 [EMAIL PROTECTED]; [EMAIL PROTECTED]
 Subject: Cyrus IMAPd 2.3.2 Released
 
 I am pleased to announce the release of Cyrus IMAPd 2.3.2.  This is a
 BETA-quality release, reflecting that it has significant numbers of new
 features that have not been tested on a wide-scale basis, although
 earlier versions of this code have been running at two sites for quite
 some time.  This release is primarily a bugfix release.  Changes of note
 are the addition of the berkeley_hash and berkeley_hash_nosync database
 backends.
 
 For full details, please see doc/changes.html and
 doc/install-upgrade.html which are included in the distribution.
 
 URLs for this release:
 ftp://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.2.tar.gz
 or
 http://ftp.andrew.cmu.edu/pub/cyrus/cyrus-imapd-2.3.2.tar.gz
 
 Questions and comments can be directed to
 info-cyrus@lists.andrew.cmu.edu (public list), or [EMAIL PROTECTED]
 
 --
 Kenneth Murchison
 Systems Programmer
 Project Cyrus Developer/Maintainer
 Carnegie Mellon University
 
 
 
 Cyrus Home Page: http://asg.web.cmu.edu/cyrus
 Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
 List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Cyrus IMAPd 2.3.2 Released

2006-02-27 Thread Ken Murchison

Larry Rosenbaum wrote:

Has something changed in the database format?  I upgraded a test system from
v2.3.1 to v2.3.2 and it didn't seem to like the deliver.db file:


Nothing has changed with the format, unless you change backend types or 
BDB versions.




Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 866726 local6.warning] DBERROR
db4: /usr/local/cyrus/config/deliver.db: unexpected file type or format
Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 729713 local6.error] DBERROR:
opening /usr/local/cyrus/config/deliver.db: Invalid argument
Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 729713 local6.error] DBERROR:
opening /usr/local/cyrus/config/deliver.db: cyrusdb error
Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 157947 local6.error] FATAL:
lmtpd: unable to init duplicate delivery database
Feb 27 13:38:22 emroute1x master[17669]: [ID 684980 local6.warning] service
lmtpunix pid 20020 in READY state: terminated abnormally

Deleting the file and restarting made it happier.



--
Kenneth Murchison
Systems Programmer
Project Cyrus Developer/Maintainer
Carnegie Mellon University

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Cyrus IMAPd 2.3.2 Released

2006-02-27 Thread Andrzej Kwiatkowski
2006/2/27, Ken Murchison [EMAIL PROTECTED]:
 Larry Rosenbaum wrote:
  Has something changed in the database format?  I upgraded a test system from
  v2.3.1 to v2.3.2 and it didn't seem to like the deliver.db file:


I don't checked in doc/ files but what with bug in murder enviroment
on frontend installation ??

Have you fixed this ? For me this should be as minor bugfix ;-)

Thanks
AK

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


RE: Cyrus IMAPd 2.3.2 Released

2006-02-27 Thread Rosenbaum, Larry M.
We haven't changed anything about the databases.  We are using whatever
the defaults are, and Berkeley 4.4.16.  From testing with the
cvt_cyrusdb program, it looks like the old program will open the old
database, and the new program will open the new database, but the new
program won't open the old database, and the old program won't open the
new database.

# ./cvt_cyrusdb ~lmr/deliver.db.old berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db.old (berkeley-nosync) to
/home/lmr/y.txt (flat)
fatal error: can't open old database

# ./cvt_cyrusdb ~lmr/deliver.db berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db (berkeley-nosync) to
/home/lmr/y.txt (flat)

# ./cvt_cyrusdb.old ~lmr/deliver.db.old berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db.old (berkeley-nosync) to
/home/lmr/y.txt (flat)
Warning: apparently empty database converted.

# ./cvt_cyrusdb.old ~lmr/deliver.db berkeley-nosync ~lmr/y.txt flat
Converting from /home/lmr/deliver.db (berkeley-nosync) to
/home/lmr/y.txt (flat)
fatal error: can't open old database

L

 -Original Message-
 From: Ken Murchison [mailto:[EMAIL PROTECTED]
 Sent: Monday, February 27, 2006 3:12 PM
 To: Rosenbaum, Larry M.
 Cc: info-cyrus@lists.andrew.cmu.edu
 Subject: Re: Cyrus IMAPd 2.3.2 Released
 
 Larry Rosenbaum wrote:
  Has something changed in the database format?  I upgraded a test
system from
  v2.3.1 to v2.3.2 and it didn't seem to like the deliver.db file:
 
 Nothing has changed with the format, unless you change backend types
or
 BDB versions.
 
 
  Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 866726
local6.warning]
 DBERROR
  db4: /usr/local/cyrus/config/deliver.db: unexpected file type or
format
  Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 729713 local6.error]
DBERROR:
  opening /usr/local/cyrus/config/deliver.db: Invalid argument
  Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 729713 local6.error]
DBERROR:
  opening /usr/local/cyrus/config/deliver.db: cyrusdb error
  Feb 27 13:38:22 emroute1x lmtpunix[20020]: [ID 157947 local6.error]
FATAL:
  lmtpd: unable to init duplicate delivery database
  Feb 27 13:38:22 emroute1x master[17669]: [ID 684980 local6.warning]
service
  lmtpunix pid 20020 in READY state: terminated abnormally
 
  Deleting the file and restarting made it happier.
 
 
 --
 Kenneth Murchison
 Systems Programmer
 Project Cyrus Developer/Maintainer
 Carnegie Mellon University

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html


Re: Cyrus IMAPd 2.3.2 Released

2006-02-27 Thread Tuan Van
Rosenbaum, Larry M. wrote:
 We haven't changed anything about the databases.  We are using whatever
 the defaults are, and Berkeley 4.4.16.  From testing with the
 cvt_cyrusdb program, it looks like the old program will open the old
 database, and the new program will open the new database, but the new
 program won't open the old database, and the old program won't open the
 new database.

 # ./cvt_cyrusdb ~lmr/deliver.db.old berkeley-nosync ~lmr/y.txt flat
 Converting from /home/lmr/deliver.db.old (berkeley-nosync) to
 /home/lmr/y.txt (flat)
 fatal error: can't open old database

 # ./cvt_cyrusdb ~lmr/deliver.db berkeley-nosync ~lmr/y.txt flat
 Converting from /home/lmr/deliver.db (berkeley-nosync) to
 /home/lmr/y.txt (flat)

 # ./cvt_cyrusdb.old ~lmr/deliver.db.old berkeley-nosync ~lmr/y.txt flat
 Converting from /home/lmr/deliver.db.old (berkeley-nosync) to
 /home/lmr/y.txt (flat)
 Warning: apparently empty database converted.

 # ./cvt_cyrusdb.old ~lmr/deliver.db berkeley-nosync ~lmr/y.txt flat
 Converting from /home/lmr/deliver.db (berkeley-nosync) to
 /home/lmr/y.txt (flat)
 fatal error: can't open old database

 L
   
Could it be a typo in lib/cyrusdb_berkeley.c ?
I try it with patch below and it seem to work.

--- lib/cyrusdb_berkeley.c.orig 2006-02-27 16:56:53.0 -0800
+++ lib/cyrusdb_berkeley.c  2006-02-27 16:57:35.0 -0800
@@ -981,7 +981,7 @@
 mysync,
 myarchive,

-open_hash,
+open_btree,
 myclose,

 fetch,
@@ -1007,7 +1007,7 @@
 mysync,
 myarchive,

-open_hash,
+open_btree,
 myclose,

 fetch,


HTH

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html