Your message dated Mon, 18 Oct 2021 11:09:46 +0200
with message-id <[email protected]>
and subject line Re: Re%3A Bug#826257%3A jetty9%3A Installation fails
"jetty9.pid exists%2C%0A but jetty was not running"
has caused the Debian Bug report #826257,
regarding jetty9: Installation fails "jetty9.pid exists, but jetty was not
running"
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
826257: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=826257
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: jetty9
Version: 9.2.16-1
Severity: important
* What led up to the situation?
Trying to install via "aptitude install jetty9"
* What was the outcome of this action?
Setting up jetty9 (9.2.16-1) ...
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.
systemctl:
jetty9.service - LSB: Start Jetty
Loaded: loaded (/etc/init.d/jetty9; generated; vendor preset: enabled)
Active: failed (Result: exit-code) since Fr 2016-06-03 19:35:16 CEST; 51s ago
Docs: man:systemd-sysv-generator(8)
Process: 22147 ExecStart=/etc/init.d/jetty9 start (code=exited,
status=1/FAILURE)
Jun 03 19:35:11 w530-lx-jpl systemd[1]: Starting LSB: Start Jetty...
Jun 03 19:35:11 w530-lx-jpl jetty9[22147]: Starting Jetty 9 Servlet Engine:
jetty9/var/run/jetty9.pid exists, but jetty was not running. Ignoring
/var/run/jet
Jun 03 19:35:16 w530-lx-jpl jetty9[22147]: failed!
Jun 03 19:35:16 w530-lx-jpl systemd[1]: jetty9.service: Control process exited,
code=exited status=1
Jun 03 19:35:16 w530-lx-jpl systemd[1]: Failed to start LSB: Start Jetty.
Jun 03 19:35:16 w530-lx-jpl systemd[1]: jetty9.service: Unit entered failed
state.
Jun 03 19:35:16 w530-lx-jpl systemd[1]: jetty9.service: Failed with result
'exit-code'.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.6.0-1 (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages jetty9 depends on:
ii adduser 3.114
ii apache2-utils 2.4.20-2
ii default-jre-headless [java7-runtime-headless] 2:1.8-57
ii libjetty9-extra-java 9.2.16-1
ii libjetty9-java 9.2.16-1
ii openjdk-8-jre-headless [java7-runtime-headless] 8u91-b14-2
Versions of packages jetty9 recommends:
ii authbind 2.1.1+nmu1
jetty9 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Tue, 27 Jun 2017 17:44:04 +0200 Kai Michael Hamich <[email protected]> wrote:
> Hi,
>
> I had the same issue! Can you check your jetty log?
>
> In my case jetty could not bind to port 8080, another deamon was running on
> the same port. Does 'netstat -tulpn | grep :8080' show another process bind
to
> the port?
>
> You can switch the port by changing the following line:
>
> /etc/jetty9/start.ini:
> jetty.port=8080
>
> Maybe it solves your problem ....
I cannot reproduce the problem with a fresh installation of Jetty9 in Stretch
hence I am going to close this bug report now. Indeed start up errors are often
caused by another service that runs on the same default port as Jetty, so
disabling the other service or changing the port helps.
Regards,
Markus
signature.asc
Description: This is a digitally signed message part
--- End Message ---
