Issues after upgrade from jessie to stretch

From	Marco DE BOOIJ <marco.maillist@debooy.eu>
Newsgroups	linux.debian.user
Subject	Issues after upgrade from jessie to stretch
Date	2017-10-16 22:20 +0200
Message-ID	<uBk1H-fp-3@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

Since I did the upgrade from jessie to stretch I have a few issues. They 
both relate to services that start before services on which they rely 
upon are not available yet.

I have iscsi that uses a LUN from a SAN. This LUN is used by LVM. On 1 
LV there are the files for PostgreSQL. When PostgreSQL starts the LV is 
not yet available and PostgreSQL does not start. Same for 2 other LVs 
(for TomEE and Sonar).

I use autofs to automount NFS shares. The configuration is stored in 
LDAP that runs on the same server. Autofs starts when slapd is starting 
up. As a result there is nothing to automount.

I use cron as a (ugly) solution: @reboot /bin/sleep 60; /bin/systemctl 
restart autofs; /bin/systemctl restart postgresql

Since I created the systemd scripts for Sonar and Tomee 'myself' I added 
'Requires=postgresql.service' to the [Unit] section of both scripts. For 
postgres and autofs I used 'systemctl edit' with '[Unit]' and 
'Required=open-iscsi.service' or 'Required.slapd.service'. This did not 
solve my issues.

Before on jessie it ran without a problem. How can I fix/debug these issues?

Back to linux.debian.user | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Issues after upgrade from jessie to stretch Marco DE BOOIJ <marco.maillist@debooy.eu> - 2017-10-16 22:20 +0200
  Re: Issues after upgrade from jessie to stretch deloptes <deloptes@gmail.com> - 2017-10-16 22:40 +0200
    Re: Issues after upgrade from jessie to stretch Marco <marco.maillist@debooy.eu> - 2017-10-17 10:20 +0200

csiph-web