Solved: virtual schema logging.properties filehandler setup

drumcircle
Rising Star

When I configure logging.properties locally, I can log to /tmp/myvs-log-0.log

 

On the server (AWS AMI, BYOL), logs are not being written, even though there are logs in /tmp

handlers = java.util.logging.ConsoleHandler, java.util.logging.FileHandler
.level = INFO
com.exasol.level = FINE
java.util.logging.FileHandler.pattern=/tmp/myvs-log-%g.log
java.util.logging.FileHandler.limit=0
java.util.logging.FileHandler.count=10
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.ConsoleHandler.level = FINE
java.util.logging.ConsoleHandler.formatter = java.util.logging.SimpleFormatter

 

1 ACCEPTED SOLUTION

Accepted Solutions

drumcircle
Rising Star

File logging not available because UDFs run in container that has no local access to server.  We can get logs out using SET SCRIPT_OUTPUT_ADDRESS, remote debugging and ActiveMQ (or any libraries that call out over TCP).

View solution in original post

1 REPLY 1

drumcircle
Rising Star

File logging not available because UDFs run in container that has no local access to server.  We can get logs out using SET SCRIPT_OUTPUT_ADDRESS, remote debugging and ActiveMQ (or any libraries that call out over TCP).

View solution in original post