On Tue, 2016-11-15 at 11:29 +0100, Emmanuel Bourg wrote:
> Hi,
> Thank you for the report. jetty8 has been removed from stretch and
> replaced by jetty9. The jetty9 package is quite similar, could you
> give
> it a try and see if it's affected by the same issue please?
> Thank you,
> Emmanuel Bourg
Yes, jetty9 is the same.

Selecting previously unselected package jetty9.
(Reading database ... 477197 files and directories currently
Preparing to unpack .../jetty9_9.2.19-2_all.deb ...
Unpacking jetty9 (9.2.19-2) ...
Setting up jetty9 (9.2.19-2) ...
Adding system user `jetty' (UID 131) ...
Adding new group `jetty' (GID 142) ...
Adding new user `jetty' (UID 131) with group `jetty' ...
Not creating home directory `/usr/share/jetty9'.
insserv: warning: script 'K01vpnagentd_init' missing LSB tags and
insserv: warning: script 'vpnagentd_init' missing LSB tags and
Job for jetty9.service failed because the control process exited with
error code.
See "systemctl status jetty9.service" and "journalctl -xe" for details.
invoke-rc.d: initscript jetty9, action "start" failed.
● jetty9.service - LSB: Start Jetty
   Loaded: loaded (/etc/init.d/jetty9; generated; vendor preset:
   Active: failed (Result: exit-code) since Thu 2016-11-17 11:52:26
CST; 5ms ago
     Docs: man:systemd-sysv-generator(8)
  Process: 13934 ExecStart=/etc/init.d/jetty9 start (code=exited,
      CPU: 1.537s

Nov 17 11:52:21 brente systemd[1]: Starting LSB: Start Jetty...
Nov 17 11:52:21 brente jetty9[13934]: Starting Jetty 9 Servlet Engine:
Nov 17 11:52:26 brente jetty9[13934]:  failed!
Nov 17 11:52:26 brente systemd[1]: jetty9.service: Control process
exited, …us=1
Nov 17 11:52:26 brente systemd[1]: Failed to start LSB: Start Jetty.
Nov 17 11:52:26 brente systemd[1]: jetty9.service: Unit entered failed
Nov 17 11:52:26 brente systemd[1]: jetty9.service: Failed with result
Hint: Some lines were ellipsized, use -l to show in full.
dpkg: error processing package jetty9 (--configure):
 subprocess installed post-installation script returned error exit
status 1
Processing triggers for systemd (232-3) ...
Errors were encountered while processing:

Not all changes and updates succeeded. For further details of the
failure, please expand the 'Details' panel below.


This is the maintainer address of Debian's Java team
Please use
debian-j...@lists.debian.org for discussions and questions.

Reply via email to