[ome-users] Blitz log file too big

[Josh Moore]

Hi Carnë,

On Jun 24, 2014, at 6:09 PM, Carnë Draug wrote:
> On 23 June 2014 15:23, Mark Carroll <m.t.b.carroll at dundee.ac.uk> wrote:
>> 
>> The Blitz log levels are set in etc/logback.xml and a running server
>> will soon pick up any changes there, as described at
>> http://www.openmicroscopy.org/site/support/omero5/developers/logging.html#java-servers
> 
> For me, this doesn't apply to the processor.log. This log seems to be
> rotating every 5MB.
> 
> $ ls -sh var/log/Processor-0.log*
> 2.4M .var/log/Processor-0.log
...
> 4.8M var/log/Processor-0.log.9
> 
> I'm guessing it is following the system defaults (set
> "java.util.logging.FileHandler.limit = 50000" at
> /etc/java-7-openjdk/logging.properties). Why is not using
> "etc/logback.xml"?

There are both Java and Python processes, each of which has its own log configuration:

 https://www.openmicroscopy.org/site/support/omero5/developers/logging.html?highlight=logging#java-servers

 https://www.openmicroscopy.org/site/support/omero5/developers/logging.html?highlight=logging#python-servers

Any of the Python logging properties found here:

https://github.com/openmicroscopy/openmicroscopy/blob/develop/etc/grid/templates.xml#L64

can be changed via bin/omero config:

 $ bin/omero config set omero.logging.directory /tmp
 $ ls /tmp/*.log
 /tmp/DropBox.log  /tmp/FileServer.log  /tmp/MonitorServer.log  /tmp/Processor-0.log  /tmp/Tables-0.log


> Carnë

Cheers,
~Josh.

P.S. to go back to one of your original questions:

> Alternatively, if I move the var/log folder to NFS share (our storage)
> and create a soft link at the original place, would OME 5 complain
> anything about it?

Soft-linking should be fine, and OMERO shouldn't inherently complain.