• Deutsch (DE-CH-AT)
  • English (United Kingdom)

PDF Drucken

Geschrieben von: Bastian Wieczorek
Freitag, den 23. Oktober 2009 um 00:00 Uhr

There are no translations available.

I just started to updated Lotus Domino 8.5 on my Debian Server to Lotus Domino 8.5.1 and during the update from debian itself it shows:

W: GPG error: http://security.debian.org lenny/updates Release: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 9AA38DCD55BE302B
W: There is no public key available for the following key IDs:
9AA38DCD55BE302B
W: You may want to run apt-get update to correct these problems

Even after running apt-get update, it won´t solve the problem.

To fix this “no public key available” problem, follow the steps below:

  1. Go your shell and type (you need to be root):

    apt-get install debian-keyring debian-archive-keyring

  2. Once debian-keyring and debian-archive-keyring are installed/updated, you now could update your debian system without error messages. To update your debian system perform the following steps:
  3. apt-get update

  4. apt-get upgrade


After that the "There is no public key available for the following key IDs" will not be shown again.



 
PDF Drucken

Geschrieben von: Bastian Wieczorek
Montag, den 15. Januar 2007 um 00:00 Uhr

There are no translations available.

If you install a fixpack or a hotfix for a domino server running on Linux/Unix you might see the following message:

You must create the environment variable NUI_NOTESDIR as path of the directory
that contains notes/latest. E.g., for the default path /opt/lotus/notes/latest
NUI_NOTESDIR=/opt/lotus
export NUI_NOTESDIR


To fix this issue on a domino server running on Debian (yes unsupported ;-) ) you could for example edit the:

/etc/profile

via "nano /etc/profile"

and add the line:

export NUI_NOTESDIR=<path_to_lotus>

where <path_to_lotus> is the full path to the 'lotus' directory for the server to receive the hotfix installation

for example

export NUI_NOTESDIR=/opt/ibm/lotus

After that relogin and the issue is solved.