From user-return-14453-archive-asf-public=cust-asf.ponee.io@storm.apache.org Fri Jun 7 08:25:05 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 7EF3018067E for ; Fri, 7 Jun 2019 10:25:04 +0200 (CEST) Received: (qmail 6958 invoked by uid 500); 7 Jun 2019 08:25:02 -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 6948 invoked by uid 99); 7 Jun 2019 08:25:02 -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 08:25:02 +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 8A5E4180D0A for ; Fri, 7 Jun 2019 08:25:01 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 2.851 X-Spam-Level: ** X-Spam-Status: No, score=2.851 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, 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 M6CfIBBMbyuX for ; Fri, 7 Jun 2019 08:24:58 +0000 (UTC) Received: from mail-io1-f45.google.com (mail-io1-f45.google.com [209.85.166.45]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id 5B25A5F180 for ; Fri, 7 Jun 2019 08:24:58 +0000 (UTC) Received: by mail-io1-f45.google.com with SMTP id k20so757818ios.10 for ; Fri, 07 Jun 2019 01:24:58 -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=gmV9aing/AWhlaCGLkRRzcCh1qyYjvJ3H8kzTLeR9QQ=; b=vKB3caopFQudIwIEMbT6K7JwKlJnH46IKM1ZN/fIr1Rch3naoYSVM7hvkr/oZ/KVzd ynfCJP9uMels/Wm2/bK9FxXgKNmZ7PRmqFmCoDPgc6+ggiGm8WAYuA4jf2EEbJe/yO6t +SSyHBeeOhmwukGCNtQTlBQuboCeCnXvR4U9+d9u0jeTfSYopSkQI/MM2B07Anz9JKaj pMxb+Bt10RK02h6BUpHVfFIZT++qS2lW7XiAzv7q9bL8I4Nmot2lT17SF+o1x4Cj2c86 eF+DdjgatTmNbbOM4OrBlgOAnJumidZyo83X8Gmr0CpF9IHQSnTE+QAINB/c8HUmEorg nsdg== 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=gmV9aing/AWhlaCGLkRRzcCh1qyYjvJ3H8kzTLeR9QQ=; b=S2YXmz2tFcbsteSVrLsjiyoBjN/GLk3QRGTVEMH6tI9d6n4ZP/VtHibqf8gKPeRkZa QvpjQF0JlBZeTemtSmMWUAVoWLidceBY+z2q/jgoMu3BDkocMKpPsP7w/7Ho9ivYZgrJ YO8Y51PxaaxcYbMJLXXdToND9uqlVQFfRofcRfdL5YEFuAdpnmRDkYNQCj0yHLUtfSfc fiu/Y0MXZqdAGqWwonJmHL2ymGbI+03p/Sfty4/+lfK8d69zOeXNTrslKG1Kfij14U+y Cvj/vXPw71XIXlt1pnyud0yGZkPf6xMHrbHKWT4ojht08eDfU4L8QKKtsXOZAvwCFW7P pkZw== X-Gm-Message-State: APjAAAV9R4xauaEURDIhoLsd40zQWgVq7l40ZleAGKIdujFx5rBxXhMW JKaYnNTeXcgiW6ajvvEkUzhbadTeIIKx/JteeZvrfzvi X-Google-Smtp-Source: APXvYqyZ3ztbzLTh2zgiPrbN9ANlDHtXlVk3vvgH9O2HyC+U3Vb03A7CmLcwBjWuqUqfw07cgVpgsczPfGOcaQpMsT4= X-Received: by 2002:a5d:8447:: with SMTP id w7mr18177665ior.197.1559895897626; Fri, 07 Jun 2019 01:24:57 -0700 (PDT) MIME-Version: 1.0 References: <7329dbc3bc4542308a9d000641090a99.squirrel@simplewebmail.uom.gr> In-Reply-To: From: Peter Chamberlain Date: Fri, 7 Jun 2019 09:24:46 +0100 Message-ID: Subject: Re: Restart Nimbus Issues To: user@storm.apache.org Content-Type: multipart/alternative; boundary="000000000000dd732d058ab79038" --000000000000dd732d058ab79038 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable It sounds to me, like the command to start nimbus in the supervisord configuration is launching it via another process. And the other process 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=C3=B8ssing wrote: > Hi Nicole, > > No, this is the right place. > > Your question is a little unclear to me since it is hard to tell whether > 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 waitin= g > state where supervisord will wait a bit, before trying to start Nimbus > again. Nimbus may or may not be running when in this state. Supervisord m= ay > 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 readin= g > 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. 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 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 topology a= nd >> 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 >> >> --=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. --000000000000dd732d058ab79038 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
It sounds to me, like the command to start nimbus in the s= upervisord configuration is launching it via another process. And the other= process is what is getting it's PID tracked by supervisord.
What i= s the supervisord configuration like for nimbus?

On Thu, 6 Jun 2019 a= t 15:36, Stig Rohde D=C3=B8ssing <stigdoessing@gmail.com> wrote:
Hi Nicole,

No, this is the right place.

Your questio= n is a little unclear to me since it is hard to tell whether you're tal= king 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 th= e BACKOFF state, and whether it is still running.

= Going by the supervisord docs (http://supervisord.org/subprocess.html), it so= unds like supervisord tried to start Nimbus, decided it didn't succeed,= and placed it into the BACKOFF state. This is a temporary waiting state wh= ere supervisord will wait a bit, before trying to start Nimbus again. Nimbu= s may or may not be running when in this state. Supervisord may have assume= d wrong, and Nimbus actually managed to start. In your case, Nimbus is clea= rly running since you can submit topologies.

Y= ou can most likely figure out whether Nimbus crashed, and why, by reading t= he 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<= br> 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. 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 quickly (process l= og may have details)
storm-ui=C2=A0 =C2=A0 =C2=A0 =C2=A0 RUNNING=C2=A0 =C2=A0pid 4024, uptime 15= :43:28

Nevertheless, Nimbus seems to run normally as I can run a new topology and<= br> 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



--

=C2=A0
=C2=A0
Peter Chamberlain<= span style=3D"color:rgb(6,169,235)">=C2=A0|<= /font>=C2=A0Senior Software Eng= ineer=C2=A0|=C2=A0HTK=C2=A0
T:=C2=A0+44(0)870 600 2311
Connect with me:=C2=A0Email
= =C2=A0
=C2=A0
3D"htk
=C2=A0
Connect with HTK:=C2=A0htk.co.uk=C2=A0|=C2=A0LinkedIn=C2= =A0|=C2=A0Twitter<= /span>
=C2=A0
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 BE= FORE PRINTING THIS EMAIL.
This email is only for the use of the in= tended recipients and may contain 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 r= epresent those of the sender and not necessarily of HTK.=C2=A0
=
--000000000000dd732d058ab79038--