Hi,

If I forgot to stop collector before start a collector. Then I will get
message the Collector.pid file can not be written.
Then I can not stop collector by the command "sudo bin/chukwa collector
stop".  Because start twice will assign new PID and new port to collector.
And the new PID is not written into the Collector.pid file.
And I can not find the PID by the port because the port is not 8080.
Does anyone meet the same problem ? And how to stop collector/agent in this
situation?

Thanks

Yes, this is a known problem.  In bin/chukwa script, there should be some
logic to check for pid file before starting another instance of the
process.  This would prevent the overwriting pid file problem.  Patches are
welcome.

regards,
Eric

On Tue, Dec 18, 2012 at 4:57 PM, GuoWei <[EMAIL PROTECTED]> wrote:

> Hi,
>
> If I forgot to stop collector before start a collector. Then I will get
> message the Collector.pid file can not be written.
> Then I can not stop collector by the command "sudo bin/chukwa collector
> stop".  Because start twice will assign new PID and new port to collector.
> And the new PID is not written into the Collector.pid file.
> And I can not find the PID by the port because the port is not 8080.
> Does anyone meet the same problem ? And how to stop collector/agent in
> this situation?
>
> Thanks
>
>

Is there a Jira issue to capture this problem?  Just curious.  :)

Regards,
Alan

On Dec 18, 2012, at 7:32 PM, Eric Yang wrote:

> Yes, this is a known problem.  In bin/chukwa script, there should be some logic to check for pid file before starting another instance of the process.  This would prevent the overwriting pid file problem.  Patches are welcome.
>
> regards,
> Eric
>
> On Tue, Dec 18, 2012 at 4:57 PM, GuoWei <[EMAIL PROTECTED]> wrote:
> Hi,
>
> If I forgot to stop collector before start a collector. Then I will get message the Collector.pid file can not be written.
> Then I can not stop collector by the command "sudo bin/chukwa collector stop".  Because start twice will assign new PID and new port to collector.
> And the new PID is not written into the Collector.pid file.
> And I can not find the PID by the port because the port is not 8080.
> Does anyone meet the same problem ? And how to stop collector/agent in this situation?
>
> Thanks
>
>

The patch was being worked on. Chukwa-677 captures this.

On Tuesday, December 18, 2012, Alan Cabrera wrote:

> Is there a Jira issue to capture this problem?  Just curious.  :)
>
> Regards,
> Alan
>
> On Dec 18, 2012, at 7:32 PM, Eric Yang wrote:
>
> Yes, this is a known problem.  In bin/chukwa script, there should be some
> logic to check for pid file before starting another instance of the
> process.  This would prevent the overwriting pid file problem.  Patches are
> welcome.
>
> regards,
> Eric
>
> On Tue, Dec 18, 2012 at 4:57 PM, GuoWei <[EMAIL PROTECTED]<javascript:_e({}, 'cvml', '[EMAIL PROTECTED]');>
> > wrote:
>
>> Hi,
>>
>> If I forgot to stop collector before start a collector. Then I will get
>> message the Collector.pid file can not be written.
>> Then I can not stop collector by the command "sudo bin/chukwa collector
>> stop".  Because start twice will assign new PID and new port to collector.
>> And the new PID is not written into the Collector.pid file.
>> And I can not find the PID by the port because the port is not 8080.
>> Does anyone meet the same problem ? And how to stop collector/agent in
>> this situation?
>>
>> Thanks
>>
>>
>
>