Hello Sam, Due to security reason the log file need to be chrooted to IGNITE_HOME/log.
Please review this PR for the fix. https://github.com/apache/ignite/pull/420 Regards, Saikat On Sun, Jan 22, 2017 at 12:03 PM, Saikat Maitra <[email protected]> wrote: > Hi Sam, > > You can pass path as query param to get the log details. Please see this > jira ticket below for reference. > > https://issues.apache.org/jira/browse/IGNITE-944 > > Regards > Saikat > > On Thu, Jan 19, 2017 at 2:21 PM, [email protected] < > [email protected]> wrote: > >> Hi, >> >> I find LOG command very useful. Periodic metrics and topology change >> information helps monitoring. >> >> However it does not work with my application, It fails with below message >> - >> "Request parameter 'path' must contain a path to valid log file." >> >> My application already using Log4j, so not using Ignite configuration XML >> to >> configure Ignite logging. Instead application log4j configured to push all >> Ignite INFO logs to a separate rolling file. Logging works fine. But >> >> 1. Ignite configuration does not have logging configuration details. >> 2. Log files can be anywhere, not under IGNITE_HOME >> >> And because of above 2 points LOG command fails. >> >> How can I make it work? >> >> Thanks, >> -Sam >> >> >> >> >> >> >> >> >> >> >> >> -- >> View this message in context: http://apache-ignite-users.705 >> 18.x6.nabble.com/REST-servive-command-LOG-tp10148.html >> Sent from the Apache Ignite Users mailing list archive at Nabble.com. >> > >
