tomcat9 fails to install in 18.04

Bug #1823125 reported by Balint Reczey on 2019-04-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Undecided
Unassigned
Bionic
Undecided
Unassigned
Cosmic
Undecided
Unassigned
Disco
Undecided
Unassigned
tomcat9 (Ubuntu)
High
Unassigned
Bionic
Undecided
Unassigned
Cosmic
Undecided
Unassigned
Disco
High
Unassigned

Bug Description

# apt install tomcat9
...
Setting up tomcat9 (9.0.16-3~18.04) ...
[/usr/lib/sysusers.d/tomcat9.conf:7] Trailing garbage.

Creating config file /etc/tomcat9/tomcat-users.xml with new version
chown: invalid group: ‘root:tomcat’
dpkg: error processing package tomcat9 (--configure):
 installed tomcat9 package post-installation script subprocess returned error exit status 1
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for systemd (237-3ubuntu10.15) ...
Processing triggers for ca-certificates (20180409) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...

done.
done.
Processing triggers for rsyslog (8.32.0-1ubuntu4) ...
Errors were encountered while processing:
 tomcat9
E: Sub-process /usr/bin/dpkg returned an error code (1)

Balint Reczey (rbalint) on 2019-04-04
Changed in tomcat9 (Ubuntu):
importance: Undecided → High
tags: added: block-proposed
Balint Reczey (rbalint) on 2019-04-04
summary: - tomca9 fails to install in 18.04
+ tomcat9 fails to install in 18.04
Balint Reczey (rbalint) on 2019-04-04
Changed in tomcat9 (Ubuntu):
status: New → Fix Released
Changed in tomcat9 (Ubuntu Cosmic):
status: New → Fix Released
Changed in systemd (Ubuntu Disco):
status: New → Incomplete
status: Incomplete → Fix Released
Changed in systemd (Ubuntu Cosmic):
status: New → Fix Released
Balint Reczey (rbalint) wrote :

The issue seems to be in systemd-sysusers, but to be released to bionic tomcat9 needs to either depend on a fixed systemd or create the user by other means.

Balint Reczey (rbalint) wrote :

Fixed it in tomcat9 only, by not setting shell in sysusers.d/tomcat9.conf .
The slightly ugly part is that systemd sets the default shell to
/sbin/nologin , not /usr/sbin/nologin that exists on Ubuntu.
The effect is the same, user can't log in it is just a little ugly and with mergedusr the problem goes away thus I have not filed a bug for it.

Balint Reczey (rbalint) on 2019-04-04
Changed in systemd (Ubuntu Bionic):
status: New → Won't Fix
Changed in tomcat9 (Ubuntu Bionic):
status: New → In Progress
Changed in tomcat9 (Ubuntu Bionic):
status: In Progress → Fix Committed
Steve Langasek (vorlon) wrote :

This change is included in tomcat9 9.0.16-3~18.04.1 which is published to bionic-proposed. Changelog:

tomcat9 (9.0.16-3~18.04.1) bionic; urgency=medium

  * Don't set nologin shell in sysusers.d/tomcat9.conf
    It is the default anyway and systemd-sysusers in 18.04 can't parse it.
    (LP: #1823125)

Since this was a proposed-only issue, I am marking this resolved for bionic.

Changed in tomcat9 (Ubuntu Bionic):
status: Fix Committed → Fix Released
Balint Reczey (rbalint) on 2019-04-15
Changed in tomcat9 (Ubuntu Cosmic):
status: Fix Released → Invalid
Changed in tomcat9 (Ubuntu Disco):
status: Fix Released → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers