You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@slider.apache.org by Krishna Kishore Bonagiri <wr...@gmail.com> on 2015/03/24 11:52:48 UTC
Output from Execute command not appearing in Container's log files
Hi,
I have the following command in my start function in the python script,
but the output from the daemon_cmd is not appearing in the container log
files.
Execute(daemon_cmd,
logoutput=True,
wait_for_finish=False)
But if I run the same command via os.system() as below, the output comes
into the container logs.
os.system(daemon_cmd)
Why is it not happening with Execute command, is there anything missing in
my call? Please help.
Thanks,
Kishore
Re: Output from Execute command not appearing in Container's log files
Posted by Sumit Mohanty <su...@gmail.com>.
Sure, pls. go ahead and open a bug. Thanks.
On Tue, Mar 24, 2015 at 10:25 PM, Krishna Kishore Bonagiri <
write2kishore@gmail.com> wrote:
> Ohhh, ok. I am using incubator-slider-releases-slider-0.60
>
> Please let me know if you want me raise a bug for this.
>
> Thanks,
> Kishore
>
> On Tue, Mar 24, 2015 at 11:58 PM, Sumit Mohanty <sm...@hortonworks.com>
> wrote:
>
> > That sounds like a bug then. I looked at the piece of code but it needs
> > some more investigation.
> >
> > What version are you using?
> > ________________________________________
> > From: Krishna Kishore Bonagiri <wr...@gmail.com>
> > Sent: Tuesday, March 24, 2015 11:10 AM
> > To: dev@slider.incubator.apache.org
> > Subject: Re: Output from Execute command not appearing in Container's log
> > files
> >
> > Hi Sumit,
> > I see the output from the start function in PYTHON code in output-3.txt
> > but the output from the command executed through Execute(command, ....)
> > call inside the start function is missing, which as I was saying is
> showing
> > the output properly in ouptut-3.txt if the same command is executed
> through
> > os.system() call inside the start function.
> >
> > Thanks,
> > Kishore
> >
> > On Tue, Mar 24, 2015 at 11:23 PM, Sumit Mohanty <
> smohanty@hortonworks.com>
> > wrote:
> >
> > > Thats the part in the documentation that we need to update.
> > >
> > > Anyway, the logs are in the following files:
> > >
> > > INSTALL command inputs and logs
> > > command-1.json
> > > errors-1.txt
> > > output-1.txt
> > >
> > > The agent logs for the container
> > > slider-agent.log
> > > slider-agent.out
> > >
> > > START command inputs and logs
> > > command-3.json
> > > errors-3.txt
> > > output-3.txt
> > > ________________________________________
> > > From: Krishna Kishore Bonagiri <wr...@gmail.com>
> > > Sent: Tuesday, March 24, 2015 10:49 AM
> > > To: dev@slider.incubator.apache.org
> > > Subject: Re: Output from Execute command not appearing in Container's
> log
> > > files
> > >
> > > Hi Sumit,
> > >
> > > Thanks for the reply. There is no directory with name command-log
> under
> > > the container directory. This is what is in my yarn-site.xml
> > >
> > > <property>
> > > <name>yarn.nodemanager.log-dirs</name>
> > > <value>/hadoop/yarn/log</value>
> > > </property>
> > >
> > > And, there is a directory with container name in two places, but there
> is
> > > nothing with name command-log, please see below.
> > >
> > > $ ls
> > >
> > >
> >
> /hadoop/yarn/local/usercache/bigsql/appcache/application_1426808752321_0094/container_1426808752321_0094_01_000002/app/
> > > definition install run
> > >
> > > $ ls
> > >
> > >
> >
> /hadoop/yarn/log/application_1426808752321_0094/container_1426808752321_0094_01_000002
> > > command-1.json errors-1.txt output-1.txt slider-agent.log
> > > status_command.json status_command_stdout.txt
> > > command-3.json errors-3.txt output-3.txt slider-agent.out
> > > status_command_stderr.txt
> > >
> > > Also, I am not sure where is "${AGENT_LOG_ROOT}" defined. Are we
> missing
> > > something on that front? Or where else could be the problem.
> > >
> > > Thanks,
> > > Kishore
> > >
> > >
> > > On Tue, Mar 24, 2015 at 7:50 PM, Sumit Mohanty <
> sumit.mohanty@gmail.com>
> > > wrote:
> > >
> > > > The operations log are in per command log files -
> > > > http://slider.incubator.apache.org/developing/debugging.html
> > > >
> > > > Look at the section "
> > > >
> > > > *agent operations log"*
> > > > The doc needs updating in the sense all logs are at the top level log
> > > > folder (e.g. - @
> > > >
> > > >
> > >
> >
> ./log/application_1398098639743_0024/container_1398098639743_0024_01_000003)
> > > >
> > > > On Tue, Mar 24, 2015 at 3:52 AM, Krishna Kishore Bonagiri <
> > > > write2kishore@gmail.com> wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > I have the following command in my start function in the python
> > > script,
> > > > > but the output from the daemon_cmd is not appearing in the
> container
> > > log
> > > > > files.
> > > > >
> > > > > Execute(daemon_cmd,
> > > > > logoutput=True,
> > > > > wait_for_finish=False)
> > > > >
> > > > > But if I run the same command via os.system() as below, the output
> > > comes
> > > > > into the container logs.
> > > > >
> > > > > os.system(daemon_cmd)
> > > > >
> > > > > Why is it not happening with Execute command, is there anything
> > missing
> > > > in
> > > > > my call? Please help.
> > > > >
> > > > > Thanks,
> > > > > Kishore
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > thanks
> > > > Sumit
> > > >
> > >
> >
>
--
thanks
Sumit
Re: Output from Execute command not appearing in Container's log files
Posted by Krishna Kishore Bonagiri <wr...@gmail.com>.
Ohhh, ok. I am using incubator-slider-releases-slider-0.60
Please let me know if you want me raise a bug for this.
Thanks,
Kishore
On Tue, Mar 24, 2015 at 11:58 PM, Sumit Mohanty <sm...@hortonworks.com>
wrote:
> That sounds like a bug then. I looked at the piece of code but it needs
> some more investigation.
>
> What version are you using?
> ________________________________________
> From: Krishna Kishore Bonagiri <wr...@gmail.com>
> Sent: Tuesday, March 24, 2015 11:10 AM
> To: dev@slider.incubator.apache.org
> Subject: Re: Output from Execute command not appearing in Container's log
> files
>
> Hi Sumit,
> I see the output from the start function in PYTHON code in output-3.txt
> but the output from the command executed through Execute(command, ....)
> call inside the start function is missing, which as I was saying is showing
> the output properly in ouptut-3.txt if the same command is executed through
> os.system() call inside the start function.
>
> Thanks,
> Kishore
>
> On Tue, Mar 24, 2015 at 11:23 PM, Sumit Mohanty <sm...@hortonworks.com>
> wrote:
>
> > Thats the part in the documentation that we need to update.
> >
> > Anyway, the logs are in the following files:
> >
> > INSTALL command inputs and logs
> > command-1.json
> > errors-1.txt
> > output-1.txt
> >
> > The agent logs for the container
> > slider-agent.log
> > slider-agent.out
> >
> > START command inputs and logs
> > command-3.json
> > errors-3.txt
> > output-3.txt
> > ________________________________________
> > From: Krishna Kishore Bonagiri <wr...@gmail.com>
> > Sent: Tuesday, March 24, 2015 10:49 AM
> > To: dev@slider.incubator.apache.org
> > Subject: Re: Output from Execute command not appearing in Container's log
> > files
> >
> > Hi Sumit,
> >
> > Thanks for the reply. There is no directory with name command-log under
> > the container directory. This is what is in my yarn-site.xml
> >
> > <property>
> > <name>yarn.nodemanager.log-dirs</name>
> > <value>/hadoop/yarn/log</value>
> > </property>
> >
> > And, there is a directory with container name in two places, but there is
> > nothing with name command-log, please see below.
> >
> > $ ls
> >
> >
> /hadoop/yarn/local/usercache/bigsql/appcache/application_1426808752321_0094/container_1426808752321_0094_01_000002/app/
> > definition install run
> >
> > $ ls
> >
> >
> /hadoop/yarn/log/application_1426808752321_0094/container_1426808752321_0094_01_000002
> > command-1.json errors-1.txt output-1.txt slider-agent.log
> > status_command.json status_command_stdout.txt
> > command-3.json errors-3.txt output-3.txt slider-agent.out
> > status_command_stderr.txt
> >
> > Also, I am not sure where is "${AGENT_LOG_ROOT}" defined. Are we missing
> > something on that front? Or where else could be the problem.
> >
> > Thanks,
> > Kishore
> >
> >
> > On Tue, Mar 24, 2015 at 7:50 PM, Sumit Mohanty <su...@gmail.com>
> > wrote:
> >
> > > The operations log are in per command log files -
> > > http://slider.incubator.apache.org/developing/debugging.html
> > >
> > > Look at the section "
> > >
> > > *agent operations log"*
> > > The doc needs updating in the sense all logs are at the top level log
> > > folder (e.g. - @
> > >
> > >
> >
> ./log/application_1398098639743_0024/container_1398098639743_0024_01_000003)
> > >
> > > On Tue, Mar 24, 2015 at 3:52 AM, Krishna Kishore Bonagiri <
> > > write2kishore@gmail.com> wrote:
> > >
> > > > Hi,
> > > >
> > > > I have the following command in my start function in the python
> > script,
> > > > but the output from the daemon_cmd is not appearing in the container
> > log
> > > > files.
> > > >
> > > > Execute(daemon_cmd,
> > > > logoutput=True,
> > > > wait_for_finish=False)
> > > >
> > > > But if I run the same command via os.system() as below, the output
> > comes
> > > > into the container logs.
> > > >
> > > > os.system(daemon_cmd)
> > > >
> > > > Why is it not happening with Execute command, is there anything
> missing
> > > in
> > > > my call? Please help.
> > > >
> > > > Thanks,
> > > > Kishore
> > > >
> > >
> > >
> > >
> > > --
> > > thanks
> > > Sumit
> > >
> >
>
Re: Output from Execute command not appearing in Container's log
files
Posted by Sumit Mohanty <sm...@hortonworks.com>.
That sounds like a bug then. I looked at the piece of code but it needs some more investigation.
What version are you using?
________________________________________
From: Krishna Kishore Bonagiri <wr...@gmail.com>
Sent: Tuesday, March 24, 2015 11:10 AM
To: dev@slider.incubator.apache.org
Subject: Re: Output from Execute command not appearing in Container's log files
Hi Sumit,
I see the output from the start function in PYTHON code in output-3.txt
but the output from the command executed through Execute(command, ....)
call inside the start function is missing, which as I was saying is showing
the output properly in ouptut-3.txt if the same command is executed through
os.system() call inside the start function.
Thanks,
Kishore
On Tue, Mar 24, 2015 at 11:23 PM, Sumit Mohanty <sm...@hortonworks.com>
wrote:
> Thats the part in the documentation that we need to update.
>
> Anyway, the logs are in the following files:
>
> INSTALL command inputs and logs
> command-1.json
> errors-1.txt
> output-1.txt
>
> The agent logs for the container
> slider-agent.log
> slider-agent.out
>
> START command inputs and logs
> command-3.json
> errors-3.txt
> output-3.txt
> ________________________________________
> From: Krishna Kishore Bonagiri <wr...@gmail.com>
> Sent: Tuesday, March 24, 2015 10:49 AM
> To: dev@slider.incubator.apache.org
> Subject: Re: Output from Execute command not appearing in Container's log
> files
>
> Hi Sumit,
>
> Thanks for the reply. There is no directory with name command-log under
> the container directory. This is what is in my yarn-site.xml
>
> <property>
> <name>yarn.nodemanager.log-dirs</name>
> <value>/hadoop/yarn/log</value>
> </property>
>
> And, there is a directory with container name in two places, but there is
> nothing with name command-log, please see below.
>
> $ ls
>
> /hadoop/yarn/local/usercache/bigsql/appcache/application_1426808752321_0094/container_1426808752321_0094_01_000002/app/
> definition install run
>
> $ ls
>
> /hadoop/yarn/log/application_1426808752321_0094/container_1426808752321_0094_01_000002
> command-1.json errors-1.txt output-1.txt slider-agent.log
> status_command.json status_command_stdout.txt
> command-3.json errors-3.txt output-3.txt slider-agent.out
> status_command_stderr.txt
>
> Also, I am not sure where is "${AGENT_LOG_ROOT}" defined. Are we missing
> something on that front? Or where else could be the problem.
>
> Thanks,
> Kishore
>
>
> On Tue, Mar 24, 2015 at 7:50 PM, Sumit Mohanty <su...@gmail.com>
> wrote:
>
> > The operations log are in per command log files -
> > http://slider.incubator.apache.org/developing/debugging.html
> >
> > Look at the section "
> >
> > *agent operations log"*
> > The doc needs updating in the sense all logs are at the top level log
> > folder (e.g. - @
> >
> >
> ./log/application_1398098639743_0024/container_1398098639743_0024_01_000003)
> >
> > On Tue, Mar 24, 2015 at 3:52 AM, Krishna Kishore Bonagiri <
> > write2kishore@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I have the following command in my start function in the python
> script,
> > > but the output from the daemon_cmd is not appearing in the container
> log
> > > files.
> > >
> > > Execute(daemon_cmd,
> > > logoutput=True,
> > > wait_for_finish=False)
> > >
> > > But if I run the same command via os.system() as below, the output
> comes
> > > into the container logs.
> > >
> > > os.system(daemon_cmd)
> > >
> > > Why is it not happening with Execute command, is there anything missing
> > in
> > > my call? Please help.
> > >
> > > Thanks,
> > > Kishore
> > >
> >
> >
> >
> > --
> > thanks
> > Sumit
> >
>
Re: Output from Execute command not appearing in Container's log files
Posted by Krishna Kishore Bonagiri <wr...@gmail.com>.
Hi Sumit,
I see the output from the start function in PYTHON code in output-3.txt
but the output from the command executed through Execute(command, ....)
call inside the start function is missing, which as I was saying is showing
the output properly in ouptut-3.txt if the same command is executed through
os.system() call inside the start function.
Thanks,
Kishore
On Tue, Mar 24, 2015 at 11:23 PM, Sumit Mohanty <sm...@hortonworks.com>
wrote:
> Thats the part in the documentation that we need to update.
>
> Anyway, the logs are in the following files:
>
> INSTALL command inputs and logs
> command-1.json
> errors-1.txt
> output-1.txt
>
> The agent logs for the container
> slider-agent.log
> slider-agent.out
>
> START command inputs and logs
> command-3.json
> errors-3.txt
> output-3.txt
> ________________________________________
> From: Krishna Kishore Bonagiri <wr...@gmail.com>
> Sent: Tuesday, March 24, 2015 10:49 AM
> To: dev@slider.incubator.apache.org
> Subject: Re: Output from Execute command not appearing in Container's log
> files
>
> Hi Sumit,
>
> Thanks for the reply. There is no directory with name command-log under
> the container directory. This is what is in my yarn-site.xml
>
> <property>
> <name>yarn.nodemanager.log-dirs</name>
> <value>/hadoop/yarn/log</value>
> </property>
>
> And, there is a directory with container name in two places, but there is
> nothing with name command-log, please see below.
>
> $ ls
>
> /hadoop/yarn/local/usercache/bigsql/appcache/application_1426808752321_0094/container_1426808752321_0094_01_000002/app/
> definition install run
>
> $ ls
>
> /hadoop/yarn/log/application_1426808752321_0094/container_1426808752321_0094_01_000002
> command-1.json errors-1.txt output-1.txt slider-agent.log
> status_command.json status_command_stdout.txt
> command-3.json errors-3.txt output-3.txt slider-agent.out
> status_command_stderr.txt
>
> Also, I am not sure where is "${AGENT_LOG_ROOT}" defined. Are we missing
> something on that front? Or where else could be the problem.
>
> Thanks,
> Kishore
>
>
> On Tue, Mar 24, 2015 at 7:50 PM, Sumit Mohanty <su...@gmail.com>
> wrote:
>
> > The operations log are in per command log files -
> > http://slider.incubator.apache.org/developing/debugging.html
> >
> > Look at the section "
> >
> > *agent operations log"*
> > The doc needs updating in the sense all logs are at the top level log
> > folder (e.g. - @
> >
> >
> ./log/application_1398098639743_0024/container_1398098639743_0024_01_000003)
> >
> > On Tue, Mar 24, 2015 at 3:52 AM, Krishna Kishore Bonagiri <
> > write2kishore@gmail.com> wrote:
> >
> > > Hi,
> > >
> > > I have the following command in my start function in the python
> script,
> > > but the output from the daemon_cmd is not appearing in the container
> log
> > > files.
> > >
> > > Execute(daemon_cmd,
> > > logoutput=True,
> > > wait_for_finish=False)
> > >
> > > But if I run the same command via os.system() as below, the output
> comes
> > > into the container logs.
> > >
> > > os.system(daemon_cmd)
> > >
> > > Why is it not happening with Execute command, is there anything missing
> > in
> > > my call? Please help.
> > >
> > > Thanks,
> > > Kishore
> > >
> >
> >
> >
> > --
> > thanks
> > Sumit
> >
>
Re: Output from Execute command not appearing in Container's log
files
Posted by Sumit Mohanty <sm...@hortonworks.com>.
Thats the part in the documentation that we need to update.
Anyway, the logs are in the following files:
INSTALL command inputs and logs
command-1.json
errors-1.txt
output-1.txt
The agent logs for the container
slider-agent.log
slider-agent.out
START command inputs and logs
command-3.json
errors-3.txt
output-3.txt
________________________________________
From: Krishna Kishore Bonagiri <wr...@gmail.com>
Sent: Tuesday, March 24, 2015 10:49 AM
To: dev@slider.incubator.apache.org
Subject: Re: Output from Execute command not appearing in Container's log files
Hi Sumit,
Thanks for the reply. There is no directory with name command-log under
the container directory. This is what is in my yarn-site.xml
<property>
<name>yarn.nodemanager.log-dirs</name>
<value>/hadoop/yarn/log</value>
</property>
And, there is a directory with container name in two places, but there is
nothing with name command-log, please see below.
$ ls
/hadoop/yarn/local/usercache/bigsql/appcache/application_1426808752321_0094/container_1426808752321_0094_01_000002/app/
definition install run
$ ls
/hadoop/yarn/log/application_1426808752321_0094/container_1426808752321_0094_01_000002
command-1.json errors-1.txt output-1.txt slider-agent.log
status_command.json status_command_stdout.txt
command-3.json errors-3.txt output-3.txt slider-agent.out
status_command_stderr.txt
Also, I am not sure where is "${AGENT_LOG_ROOT}" defined. Are we missing
something on that front? Or where else could be the problem.
Thanks,
Kishore
On Tue, Mar 24, 2015 at 7:50 PM, Sumit Mohanty <su...@gmail.com>
wrote:
> The operations log are in per command log files -
> http://slider.incubator.apache.org/developing/debugging.html
>
> Look at the section "
>
> *agent operations log"*
> The doc needs updating in the sense all logs are at the top level log
> folder (e.g. - @
>
> ./log/application_1398098639743_0024/container_1398098639743_0024_01_000003)
>
> On Tue, Mar 24, 2015 at 3:52 AM, Krishna Kishore Bonagiri <
> write2kishore@gmail.com> wrote:
>
> > Hi,
> >
> > I have the following command in my start function in the python script,
> > but the output from the daemon_cmd is not appearing in the container log
> > files.
> >
> > Execute(daemon_cmd,
> > logoutput=True,
> > wait_for_finish=False)
> >
> > But if I run the same command via os.system() as below, the output comes
> > into the container logs.
> >
> > os.system(daemon_cmd)
> >
> > Why is it not happening with Execute command, is there anything missing
> in
> > my call? Please help.
> >
> > Thanks,
> > Kishore
> >
>
>
>
> --
> thanks
> Sumit
>
Re: Output from Execute command not appearing in Container's log files
Posted by Krishna Kishore Bonagiri <wr...@gmail.com>.
Hi Sumit,
Thanks for the reply. There is no directory with name command-log under
the container directory. This is what is in my yarn-site.xml
<property>
<name>yarn.nodemanager.log-dirs</name>
<value>/hadoop/yarn/log</value>
</property>
And, there is a directory with container name in two places, but there is
nothing with name command-log, please see below.
$ ls
/hadoop/yarn/local/usercache/bigsql/appcache/application_1426808752321_0094/container_1426808752321_0094_01_000002/app/
definition install run
$ ls
/hadoop/yarn/log/application_1426808752321_0094/container_1426808752321_0094_01_000002
command-1.json errors-1.txt output-1.txt slider-agent.log
status_command.json status_command_stdout.txt
command-3.json errors-3.txt output-3.txt slider-agent.out
status_command_stderr.txt
Also, I am not sure where is "${AGENT_LOG_ROOT}" defined. Are we missing
something on that front? Or where else could be the problem.
Thanks,
Kishore
On Tue, Mar 24, 2015 at 7:50 PM, Sumit Mohanty <su...@gmail.com>
wrote:
> The operations log are in per command log files -
> http://slider.incubator.apache.org/developing/debugging.html
>
> Look at the section "
>
> *agent operations log"*
> The doc needs updating in the sense all logs are at the top level log
> folder (e.g. - @
>
> ./log/application_1398098639743_0024/container_1398098639743_0024_01_000003)
>
> On Tue, Mar 24, 2015 at 3:52 AM, Krishna Kishore Bonagiri <
> write2kishore@gmail.com> wrote:
>
> > Hi,
> >
> > I have the following command in my start function in the python script,
> > but the output from the daemon_cmd is not appearing in the container log
> > files.
> >
> > Execute(daemon_cmd,
> > logoutput=True,
> > wait_for_finish=False)
> >
> > But if I run the same command via os.system() as below, the output comes
> > into the container logs.
> >
> > os.system(daemon_cmd)
> >
> > Why is it not happening with Execute command, is there anything missing
> in
> > my call? Please help.
> >
> > Thanks,
> > Kishore
> >
>
>
>
> --
> thanks
> Sumit
>
Re: Output from Execute command not appearing in Container's log files
Posted by Sumit Mohanty <su...@gmail.com>.
The operations log are in per command log files -
http://slider.incubator.apache.org/developing/debugging.html
Look at the section "
*agent operations log"*
The doc needs updating in the sense all logs are at the top level log
folder (e.g. - @
./log/application_1398098639743_0024/container_1398098639743_0024_01_000003)
On Tue, Mar 24, 2015 at 3:52 AM, Krishna Kishore Bonagiri <
write2kishore@gmail.com> wrote:
> Hi,
>
> I have the following command in my start function in the python script,
> but the output from the daemon_cmd is not appearing in the container log
> files.
>
> Execute(daemon_cmd,
> logoutput=True,
> wait_for_finish=False)
>
> But if I run the same command via os.system() as below, the output comes
> into the container logs.
>
> os.system(daemon_cmd)
>
> Why is it not happening with Execute command, is there anything missing in
> my call? Please help.
>
> Thanks,
> Kishore
>
--
thanks
Sumit