Re: JServ logging
On Wed, 29 Mar 2000, Andreas Tille wrote:
> On Wed, 29 Mar 2000, Robert Varga wrote:
>
> > On Tue, 28 Mar 2000, Andreas Tille wrote:
> >
> > > On Mon, 27 Mar 2000, Peter M Kahle wrote:
> > >
> > > > In my /etc/apache/jserv.conf file, I have the following line, which seems
> > > > to be working:
> > > > ApJServLogFile /var/log/apache/jserv.log
> > > From my /etc/apache/jserv.conf:
> Sorry, this was a "cut-n-pasto": The contents is from my
> /etc/jserv/jserv.conf !!
> Since Jserv-1.1 there isn't any /etc/apache/jserv.conf.
>
> > This is for non-standalone jserv environment.
> Hmmm, what's that? Could Jserv run without Apache? I do not intend
> to run Jserv without Apache.
Essentially you are doing that with debian. Standalone mode is when you
start and stop jserv separately from apache. Apache does not even need to
run or even be there for jserv to work. You can replace it with any ajpv12
client. You can even connect to it from apaches from separate machines.
And so on...
The non-standalone mode is mod_jserv, when jserv is running as an apache
module.
> > > # Syntax: ApJServLogFile [filename]
> > > # Default: "./logs/mod_jserv.log"
> > > # Note: when set to "DISABLED", the log will be redirected to Apache error log
> > > # Debian note: DO NOT SET THIS OPTION HERE - use /etc/apache/httpd.conf!
> > > #ApJServLogFile DISABLED
> > >
> > >
> > > Should I really ignore hints printed UPERCASE?
> > > From my /etc/apache/httpd.conf:
> > >
> > > <IfModule mod_jserv.c>
> > > # The following line is for apacheconfig - DO NOT REMOVE!
> > > ApJServLogFile DISABLED
> > > Include /etc/jserv/jserv.conf
> > > </IfModule>
> > >
> > >
> > > OK, mod_jserv package is obsolete since the latest jserv packages,
> > > but *what* is the right way now and where is the right place to
> > > tell Apache/Jserv where to store the logs?
> >
> > In jserv.properties the log.file clause should be used.
> From my /etc/jserv/jserv.properties file:
>
> # Syntax: log.file=[log path and filename] (String)
> # Default: NONE
> # Note: if the file could not be opened, try using absolute paths.
> log.file=/var/log/jserv.log
>
> The file exists and messages like these
>
> [28/03/2000 10:30:50:493 CEST] ehec: started
> [28/03/2000 10:30:50:504 CEST] ehec: started
> [28/03/2000 10:32:05:367 CEST] java.lang.NullPointerException
> at Web.DoWeb(Web.java:178)
> at ehec.service(ehec.java:17)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:309)
> at org.apache.jserv.JServConnection.processRequest(JServConnection.java:314)
> at org.apache.jserv.JServConnection.run(JServConnection.java:188)
> at java.lang.Thread.run(Thread.java)
>
> are filed correctly to it (ehec is the name of one of my servlets).
> But the messages I used to write with the System.err.println()
> are don't stored in this file and also in no other file. Those
> messages simply vanish :-((((.
>
I think there is an option also in this file which determines whether
System.err should be written to the log or not.
> > It may be worth creating a /var/run/jserv and /var/log/jserv directory
> > with non-root ownership, so you don't need to be root to start a jserv
> > instance.
>
> /var/log> ls -l jserv.log
> -rw-rw-r-- 1 www-data www-data 0 Mär 28 20:03 jserv.log
>
> So the file is owned by www-data which should be OK for Jserv and
> Apache, isn't it?
>
Yes, but if you look at the /etc/init.d/jserv script, it becomes this the
following way:
the script touches the file, then chowns it to www-data.www-data, and
afterwards starts jserv. Therefore it needs to be run as root, or else it
cannot write to /var/log.
> I'm really clueless how to track down may debugging and error messages
:-(.
>
Write to Stefan Gybas, the debian maintainer.
He used to provide prompt answers most of the time, in the evenings. :)
> Kind regards
>
> Andreas.
>
>
Robert
Reply to: