Well, that depends on what is in -Dlog4j.configuration= If there is an URI (-Dlog4j.configuration=file:/path/to/log4j.configuration) as log4j expects, Accumulo stops file-based logging as soon as it starts log forwarding.
If there is a path (-Dlog4j.configuration=/path/to/log4j.configuration) then Accumulo is happy but log4j blames "Please initialize the log4j system properly" and file-based logging does not start until log forwarding is enabled. It is better not to use -Dlog4j.configuration at all but those tservers are running with -Dlog4j.configuration=file:/path/to/log4j.configuration :( On 1/13/15, Josh Elser <josh.el...@gmail.com> wrote: > Denis wrote: >>> Do you have any warnings/errors in the new server's logs? >> >> On smaller cluster where I try to reproduce the problem - no >> >> On big cluster, unfortunately, there are no local logs as the tserver >> logs were sent to the monitor:( >> At the moment I cannot add a new tserver there to collect new logs as >> clients are using the cluster. > > Huh? Log-forwarding to the monitor doesn't preclude local file-based > logging. You can have both. >
