I see, sorry for confusion. I though this is a new PR :) — Denis
> On Jan 23, 2017, at 1:13 PM, Saikat Maitra <[email protected]> wrote: > > Hi Denis, > > The changes are already merged long time back and I wanted to share the old > jira ticket and PR for reference. > > Regards > Saikat > > On Mon, Jan 23, 2017 at 1:33 PM, Denis Magda <[email protected] > <mailto:[email protected]>> wrote: > Saikat, > > Could you create a JIRA ticket providing more info why the modifications are > required and paste a link to the pull-request there? > > Otherwise the dev community might miss your changes. > > — > Denis > >> On Jan 22, 2017, at 10:16 AM, Saikat Maitra <[email protected] >> <mailto:[email protected]>> wrote: >> >> 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 >> <https://github.com/apache/ignite/pull/420> >> >> Regards, >> Saikat >> >> >> On Sun, Jan 22, 2017 at 12:03 PM, Saikat Maitra <[email protected] >> <mailto:[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 >> <https://issues.apache.org/jira/browse/IGNITE-944> >> >> Regards >> Saikat >> >> On Thu, Jan 19, 2017 at 2:21 PM, [email protected] >> <mailto:[email protected]> <[email protected] >> <mailto:[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.70518.x6.nabble.com/REST-servive-command-LOG-tp10148.html >> >> <http://apache-ignite-users.70518.x6.nabble.com/REST-servive-command-LOG-tp10148.html> >> Sent from the Apache Ignite Users mailing list archive at Nabble.com >> <http://nabble.com/>. >> >> > >
