problem with Debian squeeze

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
13 messages Options
Reply | Threaded
Open this post in threaded view
|

problem with Debian squeeze

Gabor Kiss
Hi folks!

After Debian lenny->squeeze upgrade I got this:

/etc/cron.daily/sks:
db4.7_archive: Program version 4.7 doesn't match environment version 4.6
db4.7_archive: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch
run-parts: /etc/cron.daily/sks exited with return code 1

What to do now?
I've little experience with Berkeley DB.
Any hint will be appreciated.

SKS was upgraded from 1.1.0-4 to 1.1.1+dpkgv3-6.

Regards

Gabor
--
A mug of beer, please. Shaken, not stirred.

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Jonathan Wiltshire-4
On Tue, Dec 07, 2010 at 09:22:05AM +0100, Kiss Gabor (Bitman) wrote:
> /etc/cron.daily/sks:
> db4.7_archive: Program version 4.7 doesn't match environment version 4.6
> db4.7_archive: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch
> run-parts: /etc/cron.daily/sks exited with return code 1

This was bug #594103 and there are instructions in
/usr/share/doc/sks/README.Debian

(apt should have given you a news item about it when you upgraded the
package?)

--
Jonathan Wiltshire                                      [hidden email]
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel

signature.asc (853 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Christoph Egger-9
In reply to this post by Gabor Kiss
"Kiss Gabor (Bitman)" <[hidden email]> writes:
> /etc/cron.daily/sks:
> db4.7_archive: Program version 4.7 doesn't match environment version 4.6
> db4.7_archive: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch
> run-parts: /etc/cron.daily/sks exited with return code 1

% gunzip -c /usr/share/doc/sks/NEWS.Debian.gz
sks (1.1.1+dpkgv3-1) unstable; urgency=high

   *** NOTE ***

  sks now uses a different BerkelyDB version.
  You need to upgrade your database prior to starting sks.
  Please read README.Debian for instructions

 -- Christoph Martin <[hidden email]>  Wed, 25 Aug 2010 17:55:07 +0200

/usr/share/doc/sks/README.Debian

If you have an old database from a Berkely DB Version (e.g 4.6) prior to the
current version (at the moment 4.7) you have to do the following in
/var/lib/sks/DB and /var/lib/sks/PTree:

 db4.6_checkpoint -1
 db4.6_recover
 db4.7_recover -e
 db4.7_checkpoint -1
 db4.7_archive | xargs --no-run-if-empty rm -f

 chown -R debian-sks:debian-sks /var/lib/sks /var/log/sks

Regards

    Christoph

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Jonathan Wiltshire-4
In reply to this post by Gabor Kiss
On Tue, Dec 07, 2010 at 09:22:05AM +0100, Kiss Gabor (Bitman) wrote:
> /etc/cron.daily/sks:
> db4.7_archive: Program version 4.7 doesn't match environment version 4.6
> db4.7_archive: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch
> run-parts: /etc/cron.daily/sks exited with return code 1

This was bug #594103 and there are instructions in
/usr/share/doc/sks/README.Debian

(apt should have given you a news item about it when you upgraded the
package?)

--
Jonathan Wiltshire                                      [hidden email]
Debian Developer                         http://people.debian.org/~jmw

4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC  74C3 5394 479D D352 4C51

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel

signature.asc (853 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

John Clizbe-2
In reply to this post by Gabor Kiss
Kiss Gabor (Bitman) wrote:

> Hi folks!
>
> After Debian lenny->squeeze upgrade I got this:
>
> /etc/cron.daily/sks:
> db4.7_archive: Program version 4.7 doesn't match environment version 4.6
> db4.7_archive: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch
> run-parts: /etc/cron.daily/sks exited with return code 1
>
> What to do now?
> I've little experience with Berkeley DB.
> Any hint will be appreciated.
>
> SKS was upgraded from 1.1.0-4 to 1.1.1+dpkgv3-6.
Based on the docs at the BerkelyDB (now Oracle) site, this is the process I've
used each time I have upgraded bdb versions. The only change from mine is to
Debianize the dir and command names.

cd /var/lib/sks
for db in DB PTree
do
  db4.6_checkpoint -1h $db  # make sure everything is committed to the db
  db4.6_recover     -h $db  # remove the old version environment
  db4.7_checkpoint -1h $db  # This converts the log to the new version
  db4.7_archive    -dh $db  # remove old log files
done

The __db.00[1-5] environment files will be recreated when sks restarts.

--
John P. Clizbe                      Inet: John (a) Gingerbear DAWT net
FSF Assoc #995 / FSFE Fellow #1797  hkp://keyserver.gingerbear.net  or
     mailto:[hidden email]?subject=HELP

Q:"Just how do the residents of Haiku, Hawai'i hold conversations?"
A:"An odd melody / island voices on the winds / surplus of vowels"


_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel

signature.asc (510 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Gabor Kiss
> > After Debian lenny->squeeze upgrade I got this:
> >
> > /etc/cron.daily/sks:
> > db4.7_archive: Program version 4.7 doesn't match environment version 4.6
> > db4.7_archive: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch
> > run-parts: /etc/cron.daily/sks exited with return code 1
> >
> > What to do now?
> > I've little experience with Berkeley DB.
> > Any hint will be appreciated.
> >
> > SKS was upgraded from 1.1.0-4 to 1.1.1+dpkgv3-6.
>
> Based on the docs at the BerkelyDB (now Oracle) site, this is the process I've
> used each time I have upgraded bdb versions. The only change from mine is to
> Debianize the dir and command names.
>
> cd /var/lib/sks
> for db in DB PTree
> do
>   db4.6_checkpoint -1h $db  # make sure everything is committed to the db
>   db4.6_recover     -h $db  # remove the old version environment
>   db4.7_checkpoint -1h $db  # This converts the log to the new version
>   db4.7_archive    -dh $db  # remove old log files
> done
>
> The __db.00[1-5] environment files will be recreated when sks restarts.

Thank you, John! :)

Unfortunately after repairing database I got new error messages:

debian-sks@hufu:/etc/sks$ /usr/sbin/sks db
Fatal error: exception Keydb.Unsafe.No_db
debian-sks@hufu:/etc/sks$ /usr/sbin/sks recon
Fatal error: exception Bdb.DBError("unable to join the environment")
debian-sks@hufu:/etc/sks$

According to strace this happens right after opening /var/lib/sks/DB/__db.001:

[...]
open("/var/lib/sks/DB/__db.rep.init", O_RDONLY|O_LARGEFILE) = -1 ENOENT (No such file or directory)
open("/var/lib/sks/DB/__db.001", O_RDWR|O_LARGEFILE) = 7
fcntl64(7, F_GETFD)                     = 0
fcntl64(7, F_SETFD, FD_CLOEXEC)         = 0
fstat64(7, {st_mode=S_IFREG|0600, st_size=24576, ...}) = 0
close(7)                                = 0
open("/var/lib/sks/DB/__db.001", O_RDWR|O_LARGEFILE) = 7
fcntl64(7, F_GETFD)                     = 0
fcntl64(7, F_SETFD, FD_CLOEXEC)         = 0
mmap2(NULL, 24576, PROT_READ|PROT_WRITE, MAP_SHARED, 7, 0) = 0xb7712000
close(7)                                = 0
munmap(0xb7712000, 24576)               = 0
time(NULL)                              = 1291813181
stat64("/etc/localtime", {st_mode=S_IFREG|0644, st_size=866, ...}) = 0
write(4, "2010-12-08 13:59:41 Shutting dow"..., 43) = 43
write(2, "Fatal error: exception Keydb.Uns"..., 42Fatal error: exception Keydb.Unsafe.No_db
) = 42
exit_group(2)                           = ?

(Note that __db.001 was not read but opened only.)

What should I do? :-/

Regards

Gabor
--
A tavalyi bajnok reszvetele nelkul indul a Masodik Nemzetkozi Kamikazeverseny

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Gabor Kiss
In reply to this post by Jonathan Wiltshire-4
Dear Jonathan,

> > /etc/cron.daily/sks:
> > db4.7_archive: Program version 4.7 doesn't match environment version 4.6
> > db4.7_archive: DB_ENV->open: DB_VERSION_MISMATCH: Database environment version mismatch
> > run-parts: /etc/cron.daily/sks exited with return code 1
>
> This was bug #594103 and there are instructions in

Sorry for the duplicated bug report.

> /usr/share/doc/sks/README.Debian

I'm a bit confused.

Do you mean the normal workflow of Debian upgrade is
1. download manually the .deb file
2. read and follow instructions carefully
3. install package manually
for all the thousands of installed packages
instead of simple "aptitude dist-upgrade"? :-)

IMHO its are postrm and postinst scripts that should be do
necessary checks and warn user if manual intervention is required
as well as disabling start of upgraded daemon.

> (apt should have given you a news item about it when you upgraded the
> package?)

I don't know exactly what happens if a NEWS file is provided.
Will it appear on the screen during upgrade?

Regards

Gabor

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Gabor Kiss
> > This was bug #594103 and there are instructions in
>
> Sorry for the duplicated bug report.
>
> > /usr/share/doc/sks/README.Debian
>
> I'm a bit confused.
>
> Do you mean the normal workflow of Debian upgrade is
> 1. download manually the .deb file
> 2. read and follow instructions carefully
> 3. install package manually
> for all the thousands of installed packages
> instead of simple "aptitude dist-upgrade"? :-)
>
> IMHO its are postrm and postinst scripts that should be do
> necessary checks and warn user if manual intervention is required
> as well as disabling start of upgraded daemon.
>
> > (apt should have given you a news item about it when you upgraded the
> > package?)
>
> I don't know exactly what happens if a NEWS file is provided.
> Will it appear on the screen during upgrade?

Meanwhile Christoph Martin (Debian package maintainer) also replied
and it seems that some warning should be displayed during
the upgrade.
Unfortunately I could see nothing like this.
This is the source of confusion.

Regards

Gabor

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Gaudenz Steinlin
Excerpts from Kiss Gabor (Bitman)'s message of Mit Dez 08 14:35:45 +0100 2010:
> Meanwhile Christoph Martin (Debian package maintainer) also replied
> and it seems that some warning should be displayed during
> the upgrade.
> Unfortunately I could see nothing like this.
> This is the source of confusion.

You need to install apt-listchanges for this to work. This package is
installed in a default install nowdays, but you might have installed
your system before it became priority "standard" or you explicitly
deselected the standard task during installation.

Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel

signature.asc (493 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Gabor Kiss
> > Meanwhile Christoph Martin (Debian package maintainer) also replied
> > and it seems that some warning should be displayed during
> > the upgrade.
> > Unfortunately I could see nothing like this.
> > This is the source of confusion.
>
> You need to install apt-listchanges for this to work. This package is
> installed in a default install nowdays, but you might have installed
> your system before it became priority "standard" or you explicitly
> deselected the standard task during installation.

Eeeeer... maybe I misunderstand something but as far as if
somebody installs this as apt plugin he will get a lot of information
displayed for every upgraded package. Then he must press some keys
to go on.
This may be useful on ordinary days when upgrading a few packages only
but seems to be pointless on distribution upgrade. Who will read 1-2
thousands of changelog and NEWS files? :-o

Gabor
--
A mug of beer, please. Shaken, not stirred.

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Gaudenz Steinlin
Excerpts from Gabor Kiss's message of Mit Dez 08 15:22:22 +0100 2010:

> > > Meanwhile Christoph Martin (Debian package maintainer) also replied
> > > and it seems that some warning should be displayed during
> > > the upgrade.
> > > Unfortunately I could see nothing like this.
> > > This is the source of confusion.
> >
> > You need to install apt-listchanges for this to work. This package is
> > installed in a default install nowdays, but you might have installed
> > your system before it became priority "standard" or you explicitly
> > deselected the standard task during installation.
>
> Eeeeer... maybe I misunderstand something but as far as if
> somebody installs this as apt plugin he will get a lot of information
> displayed for every upgraded package. Then he must press some keys
> to go on.
> This may be useful on ordinary days when upgrading a few packages only
> but seems to be pointless on distribution upgrade. Who will read 1-2
> thousands of changelog and NEWS files? :-o
In it's default configuration it will only show NEWS items. But this
is getting a bit off-topic...

Gaudenz
--
Ever tried. Ever failed. No matter.
Try again. Fail again. Fail better.
~ Samuel Beckett ~

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel

signature.asc (493 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Matthew Palmer-2
In reply to this post by Gabor Kiss
On Wed, Dec 08, 2010 at 03:22:22PM +0100, Gabor Kiss wrote:

> > > Meanwhile Christoph Martin (Debian package maintainer) also replied
> > > and it seems that some warning should be displayed during
> > > the upgrade.
> > > Unfortunately I could see nothing like this.
> > > This is the source of confusion.
> >
> > You need to install apt-listchanges for this to work. This package is
> > installed in a default install nowdays, but you might have installed
> > your system before it became priority "standard" or you explicitly
> > deselected the standard task during installation.
>
> Eeeeer... maybe I misunderstand something but as far as if
> somebody installs this as apt plugin he will get a lot of information
> displayed for every upgraded package. Then he must press some keys
> to go on.
> This may be useful on ordinary days when upgrading a few packages only
> but seems to be pointless on distribution upgrade. Who will read 1-2
> thousands of changelog and NEWS files? :-o

Anyone who wants to properly manage their systems.

- Matt

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel
Reply | Threaded
Open this post in threaded view
|

Re: problem with Debian squeeze

Gabor Kiss
In reply to this post by Gabor Kiss
> I'd retry the db4.7 recover and checkpoint commands. Twice.

I ran it in endless loop for a while. :-)
Aaaaaaand.... it works. Synchronisation is in progress.

"Virgil Brigman back on the air" :-)

I've just had to tune IPv6 access a little

Thanks for your support guys.

Gabor

_______________________________________________
Sks-devel mailing list
[hidden email]
http://lists.nongnu.org/mailman/listinfo/sks-devel