kill -HUP <some-pid> Is an example. Some vendor distros might actively look for flume agents to shutdown as a part of their administrative process.
On Monday, March 24, 2014, lulynn_2008 <[email protected]> wrote: > Thanks. Do you know how to find the things which throw "a SIGHUP" or "a > SIGTERM"? > At the beginning, flume worked normally. After we made some actions, flume > becomes unreliable. There must be something which made flume shut down, > right? Is it possible to do something to make flume work again? Like stop > some kinds of services or kill some kinds of sessions? > > > > At 2014-03-21 19:46:13,"Christopher Shannon" > <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>> > wrote: > > I have also experienced this. A SIGHUP or a SIGTERM will gracefully shut > it down. So look for anything in your system throwing those. Pretty much > any other signal will kill it outright. > > On Friday, March 21, 2014, lulynn_2008 > <[email protected]<javascript:_e(%7B%7D,'cvml','[email protected]');>> > wrote: > >> Hi All, >> >> After flume agent is started at 1:10 and it shut itself down at 2:08. No >> errors, but graceful shutdown. This situation has happened several times. >> My question is what will possibly gracefully shut down flume? Or which >> side of environment should I pay attention to to trace the error or find >> the root cause? >> >> Thanks >> >> >> > >
