Re: yajsw log settings (nsincaglia)

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Re: yajsw log settings (nsincaglia)

Grant MacKenzie
> Message: 1
> Date: Fri, 23 Jun 2017 13:59:27 -0700 (PDT)
> From: nsincaglia <[hidden email]>
> To: [hidden email]
> Subject: [Exist-open] yajsw log settings
> Message-ID: <[hidden email]>
> Content-Type: text/plain; charset=us-ascii
> I just set up an instance of eXist-db 3.3.0 nightly build 2017-06-23 on AWS
> Linux using Java Java(TM) SE Runtime Environment (build 1.8.0_131-b11) Java
> HotSpot(TM) 64-Bit Server VM (build 25.131-b11, mixed mode).

Check what default init service  yajsw uses. Most modern Linux  (
ubuntu, fedora etc ) flavors use
systemd nowadays.  Secondly check the systemd service name yajsw will use.
... so  if we can assume the service is started with systemd then when I use
util:log-system-out( $msg )
then the systemd  journal log will capture the service log output.
last 8 entries
journalctl -u eXist.service -o cat  -n 8
follow the log
journalctl -f -u eXist.service -o cat

Bear in mind, I don't use the yajsw wrapper.
It might be doing other magic.

> When we run eXist-db using the yajsw wrapper and use the
> util:log-system-out() functions, we see a few lines get written to the log
> but then it stops. Is there a settings issue we need to address?
> Here is the setting info from our wrapper.conf file which is what the code
> comes with.
> #********************************************************************
> # Wrapper Logging Properties
> #********************************************************************
> # Format of output for the console.  (See docs for formats)
> # wrapper.console.format=LPTM
> # Log Level for console output.  (See docs for log levels)
> wrapper.console.loglevel=DEBUG
> # Log file to use for wrapper output logging.
> wrapper.logfile=/mnt/data/exist-3.3.0-2017-06-23/tools/yajsw/logs/wrapper.log
> # Format of output for the log file.  (See docs for formats)
> #wrapper.logfile.format=LPTM
> # Log Level for log file output.  (See docs for log levels)
> wrapper.logfile.loglevel=DEBUG
> # Maximum size that the log file will be allowed to grow to before
> #  the log is rolled. Size is specified in bytes.  The default value
> #  of 0, disables log rolling by size.  May abbreviate with the 'k' (kB) or
> #  'm' (mB) suffix.  For example: 10m = 10 megabytes.
> # If wrapper.logfile does not contain the string ROLLNUM it will be
> automatically added as suffix of the file name
> wrapper.logfile.maxsize=10m
> # Maximum number of rolled log files which will be allowed before old
> #  files are deleted.  The default value of 0 implies no limit.
> wrapper.logfile.maxfiles=10
> # Controls the roll mode of the log file
> # possible values: DATE, WRAPPER, JVM
> # If DATE is set wrapper.logfile should contain the string YYYYMMDD
> # If DATE is set and wrapper.logfile.maxsize is set the log file will be
> rolled by size and date
> # If DATE is set and wrapper.logfile.maxfiles older files rolled by size or
> date are deleted
> #wrapper.logfile.rollmode=WRAPPER
> Is there any settings we need to change in order to get the
> util:log-system-out() function to continue writing  data to the wrapper.log
Take Care
Grant Mackenzie

Check out the vibrant tech community on one of the world's most
engaging tech sites,!
Exist-open mailing list
[hidden email]