Your message dated Thu, 22 Feb 2007 08:46:59 +0100
with message-id <[EMAIL PROTECTED]>
and subject line #356066: Errors when starting -- /etc/init.d/jetty: line 113:
/var/log/jetty/out.log: 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: normal
Hi,
Upon the installation of jetty, an attempt is made to start the server,
and produces the following output:
Setting up jetty (5.1.5rc1-6) ...
Adding system user `jetty' with uid 111...
Adding new user `jetty' (111) with group `nogroup'.
Not creating home directory `/usr/share/jetty'.
Starting Jetty servlet engine: /etc/init.d/jetty: line 113:
/var/log/jetty/out.log: No such file or directory
mesg: /dev/pts/9: Operation not permitted
jetty.
It seems the server is running afterwards, but the output is quite
misleading.
The first error is caused by "< "$LOGDIR/out.log"" which isn't found,
adding a touch solves this part of the bug (but is ugly):
113 su -p -s /bin/sh "$JETTY_USER" \
-c "touch \"$LOGDIR/out.log\""
I couldn't find the cause of the second warning, adding a set -x to the
init script showed:
+ echo -n 'Starting Jetty servlet engine: '
Starting Jetty servlet engine: + su -p -s /bin/sh jetty -c 'touch
"/var/log/jetty/out.log"'
+ su -p -s /bin/sh jetty -c '/usr/sbin/rotatelogs "/var/log/jetty/out.log"
86400'
+ su -p -s /bin/sh - jetty '/usr/lib/j2sdk1.4-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 $!'
mesg: /dev/pts/9: Operation not permitted
+ echo jetty.
jetty.
+ exit 0
I'm using a make-jpkg'ed sun-j2sdk1.4, version 1.4.2+08.
Cheers,
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-686
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15)
Versions of packages jetty depends on:
ii adduser 3.85 Add and remove users and groups
ii ant 1.6.5-5 Java based build tool like make
pn jikes | j2sdk1.3 | j2sdk1.4 | <none> (no description available)
ii libcommons-logging-java 1.0.4-4 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+08 Java(TM) 2 SDK, Standard Edition,
jetty recommends no packages.
-- no debconf information
--
Loïc Minier <[EMAIL PROTECTED]>
Current Earth status: NOT DESTROYED
--- End Message ---
--- Begin Message ---
Version: 5.1.10-2
This bug was apparently fixed by the 5.1.10-2 version but the changelog
entry was buggy. Closing it this way.
Cheers,
Michael
--
.''`. | Michael Koch <[EMAIL PROTECTED]>
: :' : | Free Java Developer <http://www.classpath.org>
`. `' |
`- | 1024D/BAC5 4B28 D436 95E6 F2E0 BD11 5923 A008 2763 483B
--- End Message ---
_______________________________________________
pkg-java-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/pkg-java-maintainers
