storm-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From sara smith <qdani...@gmail.com>
Subject Re: Help me with this issue
Date Tue, 16 Jan 2018 14:12:08 GMT
I will try strace, but a frind of mine told me to edit Storm.yaml, and
check disabled ACL for blob. I tried from /tmp but I still get the same
error .

On Tue, Jan 16, 2018 at 3:50 PM, Øystein Larsen <oysteila@ifi.uio.no> wrote:

> On 16/01/2018 11:30, sara smith wrote:
> > Which directories should the user running Apache Storm be granted
> > access? Storm path is /opt/storm user/group: storm:storm Storm 1.0.3
> > on Red Hat Enterprise Linux 7.3. Already did: sudo chown -R
> > storm:storm /opt/storm/ sudo chmod -R  775 /opt/storm 3 machines ..
> > 1 running nimbus and 2 running supervisors. all services start fine
> > without errors on logs.. the error described on the previous
> > messages happens specifically when trying to submit the topology jar.
> >  Unfortunately, this error continues for days)  even after
> > terminating the instances and rebuilding instances from scratch and
> > it is now preventing from going live with the MVP in production. Any
> > help will be appreciated.
> >
>
> - The storm home directory, recursively
> - The storm log directory
> - The directory structure holding the topology code
>
> Do you use Streamparse for deploying the topology?
>
> Are you running the topology on hosts where a MAC like SElinux or
> AppArmor may block processes from accessing the required files and
> directories?
>
> If you try running the topology on the Nimbus host alone (which is in
> any case an excellent way for error-checking) you could try to pass it
> through strace, tracing specifically file-related syscalls. That trick
> will usually give a failing process away, when you search for DENIED in
> the trace output. Yes, it is crude, but so is existence.
>



-- 
Dani
+1-9493428085
Business Information Network
Co-Founder
https://www.binmy.com

Mime
View raw message