Error while apt-get upgrade

AAuer · October 31, 2019, 12:59pm

I got privacyIDEA up and running and it works perfectly. Today I did apt-get update && apt-get upgrade and I got this output:

Setting up privacyidea-nginx (3.1.1-2bionic) ...
useradd: user 'privacyidea' already exists
ln: failed to create symbolic link '/etc/ssl/certs/privacyidea-bundle.crt': File exists
ln: failed to create symbolic link '/etc/ssl/private/privacyidea.key': File exists

             _                    _______  _______
   ___  ____(_)  _____ _______ __/  _/ _ \/ __/ _ |
  / _ \/ __/ / |/ / _ `/ __/ // // // // / _// __ |
 / .__/_/ /_/|___/\_,_/\__/\_, /___/____/___/_/ |_|
/_/                       /___/

()
The file
        /etc/privacyidea/enckey
already exist. We do not overwrite it!

             _                    _______  _______
   ___  ____(_)  _____ _______ __/  _/ _ \/ __/ _ |
  / _ \/ __/ / |/ / _ `/ __/ // // // // / _// __ |
 / .__/_/ /_/|___/\_,_/\__/\_, /___/____/___/_/ |_|
/_/                       /___/

<SQLAlchemy engine=sqlite:////mnt/gluster/pi-data.sqlite>

             _                    _______  _______
   ___  ____(_)  _____ _______ __/  _/ _ \/ __/ _ |
  / _ \/ __/ / |/ / _ `/ __/ // // // // / _// __ |
 / .__/_/ /_/|___/\_,_/\__/\_, /___/____/___/_/ |_|
/_/                       /___/

The file
        /etc/privacyidea/private.pem
already exist. We do not overwrite it!
dpkg: error processing package privacyidea-nginx (--configure):
 installed privacyidea-nginx package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 privacyidea-nginx
E: Sub-process /usr/bin/dpkg returned an error code (1)

I think there’s an error in the privacyidea-nginx.postinst script.
Please help me!

cornelinux · October 31, 2019, 1:12pm

I always would recommend running a apt dist-upgrade to also get new dependencies.

You are really running a sqlite database on a gluster share?
You know that sqlite can not handle concurrent access?
I would recommend to run a “real” database

And this could also be the source of the problem, that some schema update fails with your sqlite installation.
You know the privacyidea-nginx meta package assumes you installed privacyidea with MySQL. So I would recommend removing the privacyidea-nginx package and only update the code package privacyidea, but then you also need to run the schema update manually.

See here:

github.com

NetKnights-GmbH/ubuntu/blob/master/debian_server/privacyidea-nginx.postinst#L117


        rm -f /etc/uwsgi/apps-enabled/*
        ln -sf /etc/nginx/sites-available/privacyidea /etc/nginx/sites-enabled/
	ln -sf /etc/uwsgi/apps-available/privacyidea.xml /etc/uwsgi/apps-enabled/


	ln -s /etc/ssl/certs/privacyideaserver.pem /etc/ssl/certs/privacyidea-bundle.crt || true
	ln -s /etc/ssl/private/privacyideaserver.key /etc/ssl/private/privacyidea.key || true
}


update_db() {
        # Upgrade the database
	/opt/privacyidea/bin/privacyidea-schema-upgrade $MIGRATIONSDIR > /dev/null
}




set_path() {
	# Allow pi-manage to be called
	ln -sf /opt/privacyidea/bin/pi-manage /usr/bin/
	ln -sf /opt/privacyidea/bin/privacyidea-diag /usr/bin/
	ln -sf /opt/privacyidea/bin/privacyidea-token-janitor /usr/bin/
}

cornelinux · October 31, 2019, 1:15pm

Your problems might also depend on from which version you are upgrading.
You need to read READ_BEFORE_UPDATE.md in the privacyidea github repo.

github.com

privacyidea/privacyidea/blob/master/READ_BEFORE_UPDATE.md

# Update Notes

## Update from 3.1 to 3.2

* REST API

  The endpoints "GET /event" has been changed to "GET /event/"
  since it returns a list of events.
  The endpoints "GET /smsgateway" has been changed to 
  "GET /smsgateway/"  since it returns a list of events.

## Update from 3.0 to 3.1

* Policies

  In the scope admin a new action "tokenlist" was added. This
  action assures, that admins can only list tokens in certain realms.
  Without this action, and administrator can not view any tokens.
  To allow all administrators to still list tokens, during migration
  from 3.0 to 3.1 a new policy **pi-update-policy-b9131d0686eb** is

This file has been truncated. show original

AAuer · October 31, 2019, 1:57pm

Hi Cornelius,
thanks for your input!
I managed to get the update working: there was a false path in the privacyidea-nginx.postinst script: the path to the migrations-directory for db-upgrade was not set correctly.

We are working on a better implementation, but there is only a small amount of users at the moment…