From user-return-14454-archive-asf-public=cust-asf.ponee.io@storm.apache.org Fri Jun 7 11:53:08 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id ED6B918067E for ; Fri, 7 Jun 2019 13:53:07 +0200 (CEST) Received: (qmail 85162 invoked by uid 500); 7 Jun 2019 11:53:05 -0000 Mailing-List: contact user-help@storm.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@storm.apache.org Delivered-To: mailing list user@storm.apache.org Received: (qmail 85152 invoked by uid 99); 7 Jun 2019 11:53:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Jun 2019 11:53:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id A1779180B0C for ; Fri, 7 Jun 2019 11:53:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.187 X-Spam-Level: ** X-Spam-Status: No, score=2.187 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=2, KAM_COUK=0.85, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.664, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=htk-co-uk.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id vej9VyBvkp_H for ; Fri, 7 Jun 2019 11:53:01 +0000 (UTC) Received: from mail-it1-f180.google.com (mail-it1-f180.google.com [209.85.166.180]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 710415F175 for ; Fri, 7 Jun 2019 11:53:01 +0000 (UTC) Received: by mail-it1-f180.google.com with SMTP id m187so2240700ite.3 for ; Fri, 07 Jun 2019 04:53:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=htk-co-uk.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=B3NKdup7aNTZ5Sfm2l80hX7wiI5s+Wdha3AzkP9iYR0=; b=X/riMF9eBHjNf0IEqrLt+pXO8sLKu88wB0pBEX3Q5KopYB07GJ8Jc2xLLlDTmxb0GZ g7OFKxJ+JmSYpcDxBeW+x3MslKOG9MwWYm7HvYU5/ZqT2GP6uWViIz1AWt/+jpl5+FJ8 UhlA1i1aAyXUld4SuFsKO9bJbDBmhGOa+R4h8pXPPl2BRx+XXhY1Q0LKNb37GMuOLZ/m vMHICSbqnOdeTDGoPGw6LZjJD8ALQIRfYJ1X7cPFog3I32gTYApWbvldMbfAFDJ5nxOh YWvqbJOX4T1ygR4JJ+o9EQUWjevuSuzRoit34VnO7svAOH/yXPEcl8+ZhSGJ0E5D52fL iViQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=B3NKdup7aNTZ5Sfm2l80hX7wiI5s+Wdha3AzkP9iYR0=; b=EhWV0FoVh6OO5F46SJeAwFIcJKZIdB76qlYFqN+r0ZqmA2/2P9LbX7M3nIHv+/F+aR bef3yJlZIOc1nZMSiB6g09g5NM+ZUgPU4yxfJqQyi9VTry4Mjp3p68hZsKgSbMdg2i0y Z25cWlr1OiYsB8OmI3ogKeBgjCtO8Nq1W3181fIOiVD5IvBDmJbVJeTO78AKpLNzz40e FK7raY4VmEZieLlGTv1KaIYiI4eDdgDtszMkKtRNS5oUL4B4P7FSKoh4mx0ddlGv1VVf /rxL4hFjiCHippdfVHbOZfELStrsTnbBVzRSC+JKJydwhPjMysZpg1eViAFcYcRCWNdF hhlw== X-Gm-Message-State: APjAAAX8mkPP5WnlW9LvA/YnyJbw9O8Yqp0LRB8+swIxpukF9ewt7yOL iU1iC9k2SmqnEnx6SvbgDbJnkZxNZhgG6tNbseopFA== X-Google-Smtp-Source: APXvYqzktO3zcCOfWmf6Ha7CYvcS/jW/FBVhA45DbfEqXC0vaMxWftKk/vMG3tZzsS0Je4Zs67jpryujt+tAYN4Ns/I= X-Received: by 2002:a24:f34a:: with SMTP id t10mr3582399iti.129.1559908380780; Fri, 07 Jun 2019 04:53:00 -0700 (PDT) MIME-Version: 1.0 References: <7329dbc3bc4542308a9d000641090a99.squirrel@simplewebmail.uom.gr> <90088613c37bdcdeb836f306c826456f.squirrel@simplewebmail.uom.gr> In-Reply-To: <90088613c37bdcdeb836f306c826456f.squirrel@simplewebmail.uom.gr> From: Peter Chamberlain Date: Fri, 7 Jun 2019 12:52:49 +0100 Message-ID: Subject: Re: Restart Nimbus Issues To: nicoleta@uom.gr, user@storm.apache.org Content-Type: multipart/alternative; boundary="000000000000eb4f89058aba7880" --000000000000eb4f89058aba7880 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hmm, that supervisord conf has two entries for starting up storm nimbus. One in supervisord.conf, and the other in the supervisor.d/ folder. You should only need one of those. I would tend to use the supervisor.d/storm-nimbus.conf version, and remove the one in supervisord.conf. Although I would also use the code from the supervisord.conf version... If that makes sense. So you just have: supervisor.d/storm-nimbus.conf [program:storm-nimbus] command=3D/usr/local/storm/bin/storm nimbus autostart=3Dtrue autorestart=3Dtrue startsecs=3D10 startretries=3D999 log_stdout=3Dtrue log_stderr=3Dtrue logfile=3D/var/log/storm/nimbus.out logfile_maxbytes=3D20MB logfile_backups=3D10 And no [program:storm-nimbus] in supervisord.conf It's possible supervisord ended up running both of them, and could only track one. I'm not really sure what it does when it sees duplicate sections. (It basically reads all the files in supervisor.d folder and appends them to the end of the supervisord.conf config file to get it's configuration). Either way, it seems likely that you had a nimbus process running on the box, then a new nimbus processes that supervisord was trying to startup was failing because the storm nimbus port(s) were already in use. To start a topology you have to have a nimbus running (unless you are running things in local mode), so it is very unlikely it wasn't running already. On Linux you can check for running nimbus process from a terminal with: ps aux | grep nimbus and kill it using the pid returned in the above command and kill command. Yes you should really of just replied to the storm user group. I read everything on there anyway. I've sent this reply to the group as well as yourself. Regards, Peter On Fri, 7 Jun 2019 at 12:29, wrote: > Hello Peter and thanks for your interest! > > The code in storm-nimbus.conf (located in conf.d folder in supervisor > folder) is as follows: > > > [program:storm-nimbus] > command=3D/usr/local/storm/bin/storm nimbus > autorestart=3Dtrue > > The code in supervisord.conf (located in supervisor folder)is: > > [program:storm-nimbus] > command=3D/usr/local/storm/bin/storm nimbus > autostart=3Dtrue > autorestart=3Dtrue > startsecs=3D10 > startretries=3D999 > log_stdout=3Dtrue > log_stderr=3Dtrue > logfile=3D/var/log/storm/nimbus.out > logfile_maxbytes=3D20MB > logfile_backups=3D10 > > However, I encounter the same problem when running the nimbus deamon > manually (bin/storm nimbus). It tries to start and exits immediately. > Nevertheless, I can run and kill topologies with no problem at all. > > I finally decided to destroy my master node and build it again. Now > everything wokrs fine and the deamon does not exit. It seems to run > properly. Which is the most appropriate way to terminate a deamon and sto= p > its function (for real, not as I did before...)? > > Thank you in advance. > > Regards, > Nicole > > PS. I am sorry for using your personal email address. Should I just answe= r > the original email and send it back to user@storm.apache.org? > > > > > It sounds to me, like the command to start nimbus in the supervisord > > configuration is launching it via another process. And the other proces= s > > is > > what is getting it's PID tracked by supervisord. > > What is the supervisord configuration like for nimbus? > > > > On Thu, 6 Jun 2019 at 15:36, Stig Rohde D?ssing > > wrote: > > > >> Hi Nicole, > >> > >> No, this is the right place. > >> > >> Your question is a little unclear to me since it is hard to tell wheth= er > >> you're talking about the supervisor Storm daemon, or the supervisord > >> tool > >> for running services. I'm going to assume you are asking why > >> storm-nimbus > >> is in the BACKOFF state, and whether it is still running. > >> > >> Going by the supervisord docs (http://supervisord.org/subprocess.html)= , > >> it sounds like supervisord tried to start Nimbus, decided it didn't > >> succeed, and placed it into the BACKOFF state. This is a temporary > >> waiting > >> state where supervisord will wait a bit, before trying to start Nimbus > >> again. Nimbus may or may not be running when in this state. Supervisor= d > >> may > >> have assumed wrong, and Nimbus actually managed to start. In your case= , > >> Nimbus is clearly running since you can submit topologies. > >> > >> You can most likely figure out whether Nimbus crashed, and why, by > >> reading > >> the Nimbus log. The default location is in > >> your-storm-dir/logs/nimbus.log. > >> > >> Den tor. 6. jun. 2019 kl. 12.31 skrev : > >> > >>> Hello, > >>> > >>> I am Nicole and I am a researcher in University of Macedonia, Greece.= I > >>> am > >>> new to Storm and I found this email in the "Getting Help" Section of > >>> Storm's site. > >>> > >>> I started using Storm a few days ago and I have a question on Nimbus.= I > >>> tried to stop (using both ways i.e Ctrl-C and supervisor) the Nimbus, > >>> UI > >>> and Supervisor deamons and start them again and I had some issues. Wh= en > >>> I > >>> tried to restart Nimbus it seems to exit fast on its own (like pressi= ng > >>> Ctrl-C). When I tried to do the same with supervisor I got the > >>> following > >>> results: > >>> > >>> # sudo supervisorctl status > >>> storm-nimbus BACKOFF Exited too quickly (process log may have > >>> details) > >>> storm-ui RUNNING pid 4024, uptime 15:43:28 > >>> > >>> Nevertheless, Nimbus seems to run normally as I can run a new topolog= y > >>> and > >>> kill it with no problem at all. Why does this happen? Is my Nimbus > >>> still > >>> on? > >>> > >>> In case this is not the right place to ask such questions I am sorry > >>> for > >>> the inconvenience. Is there a community to ask questions? Thank you > >>> very > >>> much in advance. > >>> > >>> Regards, > >>> Nicole > >>> > >>> > > > > -- > > > > > > > > *Peter Chamberlain* | Senior Software Engineer | HTK > > > > T: +44(0)870 600 2311 > > Connect with me: Email > > > > > > [image: htk logo] > > > > Connect with HTK: htk.co.uk | LinkedIn > > | Twitter > > > > > > HTK Limited, Chapmans Warehouse, Wherry Quay, Ipswich, IP4 1AS, UK. > > Company Registered in England and Wales as 3191677, VAT Number 675 9467 > 71 > > > > > > PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. > > This email is only for the use of the intended recipients and may conta= in > > privileged information. If you=E2=80=99ve received this email in error,= please > let > > the sender know; then delete the message. The views expressed in this > > email > > represent those of the sender and not necessarily of HTK. > > > > > --=20 *Peter Chamberlain* | Senior Software Engineer | HTK T: +44(0)870 600 2311 Connect with me: Email [image: htk logo] Connect with HTK: htk.co.uk | LinkedIn | Twitter HTK Limited, Chapmans Warehouse, Wherry Quay, Ipswich, IP4 1AS, UK. Company Registered in England and Wales as 3191677, VAT Number 675 9467 71 PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL. This email is only for the use of the intended recipients and may contain privileged information. If you=E2=80=99ve received this email in error, ple= ase let the sender know; then delete the message. The views expressed in this email represent those of the sender and not necessarily of HTK. --000000000000eb4f89058aba7880 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hmm, that supervisord conf has two entries for starti= ng up storm nimbus. One in supervisord.conf, and the other in the superviso= r.d/ folder. You should only need one of those. I would tend to use the sup= ervisor.d/storm-nimbus.conf version, and remove the one in supervisord.conf= . Although I would also use the code from the supervisord.conf version... I= f that makes sense.
So you just have:
supervisor.d/stor= m-nimbus.conf=C2=A0=C2=A0

[program:storm-nimbu= s]
command=3D/usr/local/storm/bin/storm nimbus
autostart=3Dtrue
au= torestart=3Dtrue
startsecs=3D10
startretries=3D999
log_stdout=3Dtr= ue
log_stderr=3Dtrue
logfile=3D/var/log/storm/nimbus.out
logfile_m= axbytes=3D20MB
logfile_backups=3D10=C2=A0

And n= o [program:storm-nimbus] in supervisord.conf

I= t's possible supervisord ended up running both of them, and could only = track one. I'm not really sure what it does when it sees duplicate sect= ions. (It basically reads all the files in supervisor.d folder and appends = them to the end of the supervisord.conf config file to get it's configu= ration).

Either way, it seems likely that you had a nim= bus process running on the box, then a new nimbus processes that supervisor= d was trying to startup was failing because the storm nimbus port(s) were a= lready in use. To start a topology you have to have a nimbus running (unles= s you are running things in local mode), so it is very unlikely it wasn'= ;t running already.

On Linux you can check for= running nimbus process from a terminal with:
ps aux | grep nimbu= s
and kill it using the pid returned in the above command and kil= l command.

Yes you should really of just replied t= o the storm user group. I read everything on there anyway.
I've sent this reply to the group as well as yourself.
=
Regards,

Peter

On Fri, 7 Jun 2019 a= t 12:29, <nicoleta@= uom.gr> wrote:
Hello Peter and thanks for your interest!

The code in storm-nimbus.conf (located in conf.d folder in supervisor
folder) is as follows:


[program:storm-nimbus]
command=3D/usr/local/storm/bin/storm nimbus
autorestart=3Dtrue

The code in supervisord.conf (located in supervisor folder)is:

[program:storm-nimbus]
command=3D/usr/local/storm/bin/storm nimbus
autostart=3Dtrue
autorestart=3Dtrue
startsecs=3D10
startretries=3D999
log_stdout=3Dtrue
log_stderr=3Dtrue
logfile=3D/var/log/storm/nimbus.out
logfile_maxbytes=3D20MB
logfile_backups=3D10

However, I encounter the same problem when running the nimbus deamon
manually (bin/storm nimbus). It tries to start and exits immediately.
Nevertheless, I can run and kill topologies with no problem at all.

I finally decided to destroy my master node and build it again. Now
everything wokrs fine and the deamon does not exit. It seems to run
properly. Which is the most appropriate way to terminate a deamon and stop<= br> its function (for real, not as I did before...)?

Thank you in advance.

Regards,
Nicole

PS. I am sorry for using your personal email address. Should I just answer<= br> the original email and send it back to user@storm.apache.org?



> It sounds to me, like the command to start nimbus in the supervisord > configuration is launching it via another process. And the other proce= ss
> is
> what is getting it's PID tracked by supervisord.
> What is the supervisord configuration like for nimbus?
>
> On Thu, 6 Jun 2019 at 15:36, Stig Rohde D?ssing <stigdoessing@gmail.com> > wrote:
>
>> Hi Nicole,
>>
>> No, this is the right place.
>>
>> Your question is a little unclear to me since it is hard to tell w= hether
>> you're talking about the supervisor Storm daemon, or the super= visord
>> tool
>> for running services. I'm going to assume you are asking why >> storm-nimbus
>> is in the BACKOFF state, and whether it is still running.
>>
>> Going by the supervisord docs (http://supervisord.org= /subprocess.html),
>> it sounds like supervisord tried to start Nimbus, decided it didn&= #39;t
>> succeed, and placed it into the BACKOFF state. This is a temporary=
>> waiting
>> state where supervisord will wait a bit, before trying to start Ni= mbus
>> again. Nimbus may or may not be running when in this state. Superv= isord
>> may
>> have assumed wrong, and Nimbus actually managed to start. In your = case,
>> Nimbus is clearly running since you can submit topologies.
>>
>> You can most likely figure out whether Nimbus crashed, and why, by=
>> reading
>> the Nimbus log. The default location is in
>> your-storm-dir/logs/nimbus.log.
>>
>> Den tor. 6. jun. 2019 kl. 12.31 skrev <nicoleta@uom.gr>:
>>
>>> Hello,
>>>
>>> I am Nicole and I am a researcher in University of Macedonia, = Greece. I
>>> am
>>> new to Storm and I found this email in the "Getting Help&= quot; Section of
>>> Storm's site.
>>>
>>> I started using Storm a few days ago and I have a question on = Nimbus. I
>>> tried to stop (using both ways i.e Ctrl-C and supervisor) the = Nimbus,
>>> UI
>>> and Supervisor deamons and start them again and I had some iss= ues. When
>>> I
>>> tried to restart Nimbus it seems to exit fast on its own (like= pressing
>>> Ctrl-C). When I tried to do the same with supervisor I got the=
>>> following
>>> results:
>>>
>>> # sudo supervisorctl status
>>> storm-nimbus=C2=A0 =C2=A0 BACKOFF=C2=A0 =C2=A0Exited too quick= ly (process log may have
>>> details)
>>> storm-ui=C2=A0 =C2=A0 =C2=A0 =C2=A0 RUNNING=C2=A0 =C2=A0pid 40= 24, uptime 15:43:28
>>>
>>> Nevertheless, Nimbus seems to run normally as I can run a new = topology
>>> and
>>> kill it with no problem at all. Why does this happen? Is my Ni= mbus
>>> still
>>> on?
>>>
>>> In case this is not the right place to ask such questions I am= sorry
>>> for
>>> the inconvenience. Is there a community to ask questions? Than= k you
>>> very
>>> much in advance.
>>>
>>> Regards,
>>> Nicole
>>>
>>>
>
> --
>
>
>
> *Peter Chamberlain* | Senior Software Engineer | HTK
>
> T: +44(0)870 600 2311
> Connect with me: Email <peter.chamberlain@htk.co.uk>
>
>
> [image: htk logo] <http://www.htk.co.uk/>
>
> Connect with HTK: htk.co.uk <http://www.htk.co.uk/> | LinkedIn
> <http://www.linkedin.com/company/htk/> | Twitter<= br> > <http://www.twitter.com/htkhorizon>
>
> HTK Limited, Chapmans Warehouse, Wherry Quay, Ipswich, IP4 1AS, UK. > Company Registered in England and Wales as 3191677, VAT Number 675 946= 7 71
>
>
> PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL.
> This email is only for the use of the intended recipients and may cont= ain
> privileged information. If you=E2=80=99ve received this email in error= , please let
> the sender know; then delete the message. The views expressed in this<= br> > email
> represent those of the sender and not necessarily of HTK.
>




--

=C2=A0
=C2= =A0
Peter= Chamberlain=C2=A0|=C2=A0Senior Software Engineer=C2=A0|=C2= =A0HTK
=C2=A0
T:=C2=A0+44(0)870 600 2311
Conn= ect with me:<= span style=3D"color:rgb(6,169,235)">=C2=A0Email
=C2=A0
=C2=A0
3D"htk
=C2=A0
<= span style=3D"font-family:Helvetica,arial,sans-serif">Connect with HTK:=C2=A0htk.co.uk= =C2=A0|=C2=A0Li= nkedIn=C2=A0|=C2=A0Twitter
=C2=A0
HTK Limited, Chapmans Warehouse, Wherry Qu= ay, Ipswich, IP4 1AS, UK.
Company Registered in England and Wales as 319= 1677, VAT Number 675 9467 71

<= div dir=3D"ltr">
PLEASE CONSIDE= R THE ENVIRONMENT BEFORE PRINTING THIS EMAIL.
=
This email is only f= or the use of the intended recipients and may contain privileged informatio= n. If you=E2=80=99ve received this email in error, please let the sender kn= ow; then delete the message. The views expre= ssed in this email represent those of the sender and not necessarily of HTK= .=C2=A0
--000000000000eb4f89058aba7880--