You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@storm.apache.org by Abhishek Raj <ab...@outlook.com> on 2015/06/01 07:38:21 UTC

RE: No logs directory in apache storm on Mavericks

The find command doesn't return anything either. :(

> Date: Sat, 30 May 2015 22:59:07 +0530
> Subject: Re: No logs directory in apache storm on Mavericks
> From: skgadalay@gmail.com
> To: user@storm.apache.org
> 
> Is there any cd command in storm script.
> 
> Anyway login as root user and do a find of nimbus and supervisor logs files.
> find / -name nimbus*log*
> find / -name supervisor*log*
> 
> On 5/30/15, Abhishek Raj <ab...@outlook.com> wrote:
> > @skgadalay by "./logs" I meant logs directory in apache storm.
> > @Jeffery Maass, I tried that, the log files don't appear inside the folder
> > even if I manually create it. Any other suggestions?
> > Thanks.Abhishek
> >
> >> Date: Fri, 29 May 2015 22:44:22 +0530
> >> Subject: Re: No logs directory in apache storm on Mavericks
> >> From: skgadalay@gmail.com
> >> To: user@storm.apache.org
> >>
> >> You mentioned the storm script is having the logs directory as "./logs".
> >> Then it will create the logs directory in the current working
> >> directory where you run the storm command.
> >>
> >>
> >> On 5/29/15, Jeffery Maass <ma...@gmail.com> wrote:
> >> > Maybe if you create the logs directory, then restart the processes?
> >> >
> >> > Thank you for your time!
> >> >
> >> > +++++++++++++++++++++
> >> > Jeff Maass <ma...@gmail.com>
> >> > linkedin.com/in/jeffmaass
> >> > stackoverflow.com/users/373418/maassql
> >> > +++++++++++++++++++++
> >> >
> >> >
> >> > On Fri, May 29, 2015 at 12:42 AM, Abhishek Raj
> >> > <ab...@outlook.com>
> >> > wrote:
> >> >
> >> >>  With nimbus the values are
> >> >>
> >> >>
> >> >> -Dstorm.log.dir=/usr/local/apache-storm-0.9.4/logs
> >> >>
> >> >> -Dlogfile.name=nimbus.log
> >> >>
> >> >>
> >> >> -Dlogback.configurationFile=/usr/local/apache-storm-0.9.4/logback/cluster.xml
> >> >>
> >> >>
> >> >> With supervisor, the values are again the same
> >> >>
> >> >>
> >> >> -Dstorm.log.dir=/usr/local/apache-storm-0.9.4/logs
> >> >>
> >> >> -Dlogfile.name=supervisor.log
> >> >>
> >> >>
> >> >> -Dlogback.configurationFile=/usr/local/apache-storm-0.9.4/logback/cluster.xml
> >> >>
> >> >>
> >> >> But the logs directory doesn't appear in
> >> >> /usr/local/apache-storm-0.9.4/
> >> >>
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Abhishek.
> >> >>
> >> >> ------------------------------
> >> >> Date: Thu, 28 May 2015 10:23:27 -0500
> >> >>
> >> >> Subject: Re: No logs directory in apache storm on Mavericks
> >> >> From: maassql@gmail.com
> >> >> To: user@storm.apache.org
> >> >>
> >> >> When the workers and supervisor are run, what are the values for:
> >> >> -Dstorm.log.dir=
> >> >> -Dlogfile.name=
> >> >> -Dlogback.configurationFile=
> >> >>
> >> >> Thank you for your time!
> >> >>
> >> >> +++++++++++++++++++++
> >> >> Jeff Maass <ma...@gmail.com>
> >> >> linkedin.com/in/jeffmaass
> >> >> stackoverflow.com/users/373418/maassql
> >> >> +++++++++++++++++++++
> >> >>
> >> >>
> >> >> On Thu, May 28, 2015 at 10:17 AM, Abhishek Raj
> >> >> <ab...@outlook.com>
> >> >> wrote:
> >> >>
> >> >> Hi Jeff. Thanks for the response.
> >> >>
> >> >> I've checked ${storm.log.dir} and it seems to be set correctly. I
> >> >> verified
> >> >> the logs directory in the startup script (bin/storm) as well. It is
> >> >> set
> >> >> to "./logs". But when I run the daemons, the logs directory doesn't
> >> >> seem
> >> >> to
> >> >> be created at all. I think it might have something to do with
> >> >> java.library.path on Mac OS X. Not so sure though. Any more
> >> >> suggestions?
> >> >>
> >> >> ------------------------------
> >> >> Date: Thu, 28 May 2015 08:47:48 -0500
> >> >> Subject: Re: No logs directory in apache storm on Mavericks
> >> >> From: maassql@gmail.com
> >> >> To: user@storm.apache.org
> >> >>
> >> >>
> >> >> Couple of items to get you going:
> >> >> When you run a topology, you will see that your supervisor and workers
> >> >> both have System Variables set at the command line:
> >> >> -Dstorm.log.dir=/opt/apache-storm-0.9.4/logs
> >> >> -Dlogfile.name=supervisor.log
> >> >> -Dlogback.configurationFile=/opt/apache-storm-0.9.4/logback/cluster.xml
> >> >>
> >> >> in the Storm directory ( wherever you uncompressed Storm ), look at
> >> >> ./logback/cluster.xml
> >> >> You will see that logs write to a variable, ${storm.log.dir}
> >> >>
> >> >>
> >> >> Thank you for your time!
> >> >>
> >> >> +++++++++++++++++++++
> >> >> Jeff Maass <ma...@gmail.com>
> >> >> linkedin.com/in/jeffmaass
> >> >> stackoverflow.com/users/373418/maassql
> >> >> +++++++++++++++++++++
> >> >>
> >> >>
> >> >> On Thu, May 28, 2015 at 3:52 AM, Abhishek Raj
> >> >> <ab...@outlook.com>
> >> >> wrote:
> >> >>
> >> >> I am using apache-storm 0.9.4 on OS X Mavericks. Here's my storm.yaml
> >> >>
> >> >> storm.zookeeper.servers:
> >> >>     - "localhost"
> >> >> storm.zookeeper.port: 2181
> >> >>
> >> >> storm.local.dir: "/var/lib/storm"
> >> >> storm.local.hostname: "localhost"
> >> >>
> >> >> nimbus.host: "localhost"
> >> >> nimbus.childopts: "-Xmx512m"
> >> >>
> >> >> supervisor.childopts: "-Xmx256m"
> >> >> supervisor.slots.ports:
> >> >>     - 6700
> >> >>     - 6701
> >> >>     - 6702
> >> >>     - 6703
> >> >>
> >> >> java.library.path:
> >> >> "/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:/usr/local/lib"
> >> >>
> >> >> ui.port: 8080
> >> >>
> >> >> worker.childopts: "-Xmx768m"
> >> >>
> >> >> I can run nimbus and supervisor fine and can submit topologies as
> >> >> well.
> >> >> But the logs directory doesn't appear in storm's folder. I have
> >> >> already
> >> >> verified that the folder has apt permissions.
> >> >>
> >> >>
> >> >> Please help.
> >> >>
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Abhishek.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >
 		 	   		  

RE: No logs directory in apache storm on Mavericks

Posted by Srividhya Shanmugam <Sr...@fico.com>.
Instead of usr/local...can you specify a different directory for the storm.log.dir startup option and restart the services?



From: Abhishek Raj [mailto:abhishekraj10@outlook.com]
Sent: Monday, June 01, 2015 1:38 AM
To: user@storm.apache.org
Subject: RE: No logs directory in apache storm on Mavericks

The find command doesn't return anything either. :(
> Date: Sat, 30 May 2015 22:59:07 +0530
> Subject: Re: No logs directory in apache storm on Mavericks
> From: skgadalay@gmail.com<ma...@gmail.com>
> To: user@storm.apache.org<ma...@storm.apache.org>
>
> Is there any cd command in storm script.
>
> Anyway login as root user and do a find of nimbus and supervisor logs files.
> find / -name nimbus*log*
> find / -name supervisor*log*
>
> On 5/30/15, Abhishek Raj <ab...@outlook.com>> wrote:
> > @skgadalay by "./logs" I meant logs directory in apache storm.
> > @Jeffery Maass, I tried that, the log files don't appear inside the folder
> > even if I manually create it. Any other suggestions?
> > Thanks.Abhishek
> >
> >> Date: Fri, 29 May 2015 22:44:22 +0530
> >> Subject: Re: No logs directory in apache storm on Mavericks
> >> From: skgadalay@gmail.com<ma...@gmail.com>
> >> To: user@storm.apache.org<ma...@storm.apache.org>
> >>
> >> You mentioned the storm script is having the logs directory as "./logs".
> >> Then it will create the logs directory in the current working
> >> directory where you run the storm command.
> >>
> >>
> >> On 5/29/15, Jeffery Maass <ma...@gmail.com>> wrote:
> >> > Maybe if you create the logs directory, then restart the processes?
> >> >
> >> > Thank you for your time!
> >> >
> >> > +++++++++++++++++++++
> >> > Jeff Maass <ma...@gmail.com>>
> >> > linkedin.com/in/jeffmaass
> >> > stackoverflow.com/users/373418/maassql
> >> > +++++++++++++++++++++
> >> >
> >> >
> >> > On Fri, May 29, 2015 at 12:42 AM, Abhishek Raj
> >> > <ab...@outlook.com>>
> >> > wrote:
> >> >
> >> >> With nimbus the values are
> >> >>
> >> >>
> >> >> -Dstorm.log.dir=/usr/local/apache-storm-0.9.4/logs
> >> >>
> >> >> -Dlogfile.name=nimbus.log
> >> >>
> >> >>
> >> >> -Dlogback.configurationFile=/usr/local/apache-storm-0.9.4/logback/cluster.xml
> >> >>
> >> >>
> >> >> With supervisor, the values are again the same
> >> >>
> >> >>
> >> >> -Dstorm.log.dir=/usr/local/apache-storm-0.9.4/logs
> >> >>
> >> >> -Dlogfile.name=supervisor.log
> >> >>
> >> >>
> >> >> -Dlogback.configurationFile=/usr/local/apache-storm-0.9.4/logback/cluster.xml
> >> >>
> >> >>
> >> >> But the logs directory doesn't appear in
> >> >> /usr/local/apache-storm-0.9.4/
> >> >>
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Abhishek.
> >> >>
> >> >> ------------------------------
> >> >> Date: Thu, 28 May 2015 10:23:27 -0500
> >> >>
> >> >> Subject: Re: No logs directory in apache storm on Mavericks
> >> >> From: maassql@gmail.com<ma...@gmail.com>
> >> >> To: user@storm.apache.org<ma...@storm.apache.org>
> >> >>
> >> >> When the workers and supervisor are run, what are the values for:
> >> >> -Dstorm.log.dir=
> >> >> -Dlogfile.name=
> >> >> -Dlogback.configurationFile=
> >> >>
> >> >> Thank you for your time!
> >> >>
> >> >> +++++++++++++++++++++
> >> >> Jeff Maass <ma...@gmail.com>>
> >> >> linkedin.com/in/jeffmaass
> >> >> stackoverflow.com/users/373418/maassql
> >> >> +++++++++++++++++++++
> >> >>
> >> >>
> >> >> On Thu, May 28, 2015 at 10:17 AM, Abhishek Raj
> >> >> <ab...@outlook.com>>
> >> >> wrote:
> >> >>
> >> >> Hi Jeff. Thanks for the response.
> >> >>
> >> >> I've checked ${storm.log.dir} and it seems to be set correctly. I
> >> >> verified
> >> >> the logs directory in the startup script (bin/storm) as well. It is
> >> >> set
> >> >> to "./logs". But when I run the daemons, the logs directory doesn't
> >> >> seem
> >> >> to
> >> >> be created at all. I think it might have something to do with
> >> >> java.library.path on Mac OS X. Not so sure though. Any more
> >> >> suggestions?
> >> >>
> >> >> ------------------------------
> >> >> Date: Thu, 28 May 2015 08:47:48 -0500
> >> >> Subject: Re: No logs directory in apache storm on Mavericks
> >> >> From: maassql@gmail.com<ma...@gmail.com>
> >> >> To: user@storm.apache.org<ma...@storm.apache.org>
> >> >>
> >> >>
> >> >> Couple of items to get you going:
> >> >> When you run a topology, you will see that your supervisor and workers
> >> >> both have System Variables set at the command line:
> >> >> -Dstorm.log.dir=/opt/apache-storm-0.9.4/logs
> >> >> -Dlogfile.name=supervisor.log
> >> >> -Dlogback.configurationFile=/opt/apache-storm-0.9.4/logback/cluster.xml
> >> >>
> >> >> in the Storm directory ( wherever you uncompressed Storm ), look at
> >> >> ./logback/cluster.xml
> >> >> You will see that logs write to a variable, ${storm.log.dir}
> >> >>
> >> >>
> >> >> Thank you for your time!
> >> >>
> >> >> +++++++++++++++++++++
> >> >> Jeff Maass <ma...@gmail.com>>
> >> >> linkedin.com/in/jeffmaass
> >> >> stackoverflow.com/users/373418/maassql
> >> >> +++++++++++++++++++++
> >> >>
> >> >>
> >> >> On Thu, May 28, 2015 at 3:52 AM, Abhishek Raj
> >> >> <ab...@outlook.com>>
> >> >> wrote:
> >> >>
> >> >> I am using apache-storm 0.9.4 on OS X Mavericks. Here's my storm.yaml
> >> >>
> >> >> storm.zookeeper.servers:
> >> >> - "localhost"
> >> >> storm.zookeeper.port: 2181
> >> >>
> >> >> storm.local.dir: "/var/lib/storm"
> >> >> storm.local.hostname: "localhost"
> >> >>
> >> >> nimbus.host: "localhost"
> >> >> nimbus.childopts: "-Xmx512m"
> >> >>
> >> >> supervisor.childopts: "-Xmx256m"
> >> >> supervisor.slots.ports:
> >> >> - 6700
> >> >> - 6701
> >> >> - 6702
> >> >> - 6703
> >> >>
> >> >> java.library.path:
> >> >> "/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java:/usr/local/lib"
> >> >>
> >> >> ui.port: 8080
> >> >>
> >> >> worker.childopts: "-Xmx768m"
> >> >>
> >> >> I can run nimbus and supervisor fine and can submit topologies as
> >> >> well.
> >> >> But the logs directory doesn't appear in storm's folder. I have
> >> >> already
> >> >> verified that the folder has apt permissions.
> >> >>
> >> >>
> >> >> Please help.
> >> >>
> >> >>
> >> >> Thanks.
> >> >>
> >> >> Abhishek.
> >> >>
> >> >>
> >> >>
> >> >>
> >> >
> >

This email and any files transmitted with it are confidential, proprietary and intended solely for the individual or entity to whom they are addressed. If you have received this email in error please delete it immediately.