Your message dated Fri, 26 Jan 2007 16:24:54 -0800
with message-id <[EMAIL PROTECTED]>
and subject line jetty: Jetty init fails with 'No such file or directory'
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: jetty
Version: 5.1.5rc1-6
Severity: grave
Tags: patch sid etch
Justification: renders package unusable
Upon both system startup and attempted manual startup of jetty, Jetty
fails (lines wrapped for clarity):
[EMAIL PROTECTED]:~$ sudo /etc/init.d/jetty restart
Password:
Stopping Jetty servlet engine: (not running).
/var/run/jetty.pid exists, but jetty was not running. Ignoring
/var/run/jetty.pid
Starting Jetty servlet engine: -su: /usr/lib/j2sdk1.5-sun/bin/java
-Xmx256m
-Djava.awt.headless=true -Djava.io.tmpdir="/var/cache/jetty"
-Djava.library.path=/usr/lib -DSTART=/etc/jetty/start.config
-Djetty.home=/usr/share/jetty
-jar /usr/share/jetty/lib/start.jar /etc/jetty/jetty.xml >>
/var/log/jetty/out.log 2>&1 & echo $!: No such file or directory
I have identified the problem as a missing -c that should be passed to
the shell spawned by su. Here's the one-liner patch that solves the
problem.
--- /etc/init.d/jetty 2006-05-16 04:19:40.000000000 -0700
+++ /etc/init.d/jetty 2006-05-16 04:19:52.000000000 -0700
@@ -113,7 +113,7 @@
su -p -s /bin/sh "$JETTY_USER" \
-c "$ROTATELOGS \"$LOGDIR/out.log\" 86400" \
< "$LOGDIR/out.log" &
- su -p -s /bin/sh - "$JETTY_USER" \
+ su -p -s /bin/sh - "$JETTY_USER" -c \
"$JAVA $ARGUMENTS >> $LOGDIR/out.log 2>&1 & \
echo \$!" > "$PIDFILE"
echo "$NAME."
Thanks,
Elizabeth Fong
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15.4
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages jetty depends on:
ii adduser 3.87 Add and remove users and groups
ii ant 1.6.5-5 Java based build tool like make
ii gij [java-virtual-machine 4:4.1.0-2 The GNU Java bytecode interpreter
ii gij-4.0 [java-virtual-mac 4.0.3-2 The GNU Java bytecode interpreter
ii gij-4.1 [java-virtual-mac 4.1.0-2j1 The GNU Java bytecode interpreter
ii jikes 1:1.22-4 Fast Java compiler adhering to lan
ii kaffe 2:1.1.7-2 A JVM to run Java bytecode
ii kaffe-pthreads [kaffe] 2:1.1.7-2 A POSIX threads enabled version of
ii libcommons-logging-java 1.0.4-5 commmon wrapper interface for seve
ii libmx4j-java 2.1.1-4 An open source implementation of t
ii libservlet2.4-java 5.0.30-3 Servlet 2.4 and JSP 2.0 Java class
ii libtomcat5-java 5.0.30-9 Java Servlet engine -- core librar
ii libxerces2-java 2.6.2-4 Validating XML parser for Java wit
ii sun-j2sdk1.4 [j2re1.4] 1.4.2+11 Java(TM) 2 SDK, Standard Edition,
ii sun-j2sdk1.5 [j2re1.5] 1.5.0+update06 Java(TM) 2 SDK, Standard Edition,
jetty recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 5.1.10-2
Apparently this was fixed in the changelog for jetty (5.1.10-2), but for
some reason it didn't take in the BTS. Manually closing, as I am the
submitter of the bug.
Elizabeth Fong
--- End Message ---
