Failing to start hadoop unit on local with juju

[Asif Iqbal]

On Sun, Apr 27, 2014 at 4:07 PM, John Meinel <john at arbash-meinel.com> wrote:

> Known bug, though I thought the fix made it into 1.19.1.
> To work around it, you use
> juju bootstrap --upload-tools --series precise, trusty
>
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04 LTS
Release: 14.04
Codename: trusty

$ juju --version
1.19.1-trusty-amd64

 $ juju bootstrap --upload-tools --series precise, trusty
error: invalid value "precise," for flag --series: invalid series name ""


John
> =:->
> On Apr 25, 2014 9:35 PM, "Asif Iqbal" <vadud3 at gmail.com> wrote:
>
>>  I am using 1.19.1-trusty-amd64, installed from ppa:juju/devel
>>
>> I am failing start hadoop unit, showing pending
>>
>> environment: local
>> machines:
>>   "0":
>>     agent-state: started
>>     agent-version: 1.19.1.1
>>     dns-name: localhost
>>     instance-id: localhost
>>     series: trusty
>>     state-server-member-status: has-vote
>>   "1":
>>     instance-id: pending
>>     series: precise
>>   "2":
>>     instance-id: pending
>>     series: precise
>> services:
>>   hadoop-master:
>>     charm: cs:precise/hadoop-10
>>     exposed: false
>>     relations:
>>       jobtracker:
>>       - hadoop-slave
>>       namenode:
>>       - hadoop-slave
>>     units:
>>       hadoop-master/0:
>>         agent-state: pending
>>         machine: "1"
>>   hadoop-slave:
>>     charm: cs:precise/hadoop-10
>>     exposed: false
>>     relations:
>>       datanode:
>>       - hadoop-master
>>       tasktracker:
>>       - hadoop-master
>>     units:
>>       hadoop-slave/0:
>>         agent-state: pending
>>         machine: "2"
>>
>> Here is log from all-machines.log
>>
>> machine-0: 2014-04-26 04:33:53 ERROR juju.worker.peergrouper
>> worker.go:137 peergrouper loop terminated: cannot get replica set status:
>> cannot get replica set status: not running with --replSet
>> machine-0: 2014-04-26 04:33:53 ERROR juju.worker runner.go:218 exited
>> "peergrouper": cannot get replica set status: cannot get replica set
>> status: not running with --replSet
>> machine-0: 2014-04-26 04:33:56 ERROR juju.worker.peergrouper
>> worker.go:137 peergrouper loop terminated: cannot get replica set status:
>> cannot get replica set status: not running with --replSet
>> machine-0: 2014-04-26 04:33:56 ERROR juju.worker runner.go:218 exited
>> "peergrouper": cannot get replica set status: cannot get replica set
>> status: not running with --replSet
>> machine-0: 2014-04-26 04:34:00 ERROR juju.worker.peergrouper
>> worker.go:137 peergrouper loop terminated: cannot get replica set status:
>> cannot get replica set status: not running with --replSet
>> machine-0: 2014-04-26 04:34:00 ERROR juju.worker runner.go:218 exited
>> "peergrouper": cannot get replica set status: cannot get replica set
>> status: not running with --replSet
>> machine-0: 2014-04-26 04:34:03 ERROR juju.worker.peergrouper
>> worker.go:137 peergrouper loop terminated: cannot get replica set status:
>> cannot get replica set status: not running with --replSet
>> machine-0: 2014-04-26 04:34:03 ERROR juju.worker runner.go:218 exited
>> "peergrouper": cannot get replica set status: cannot get replica set
>> status: not running with --replSet
>>
>>
>> --
>> Asif Iqbal
>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>> A: Because it messes up the order in which people normally read text.
>> Q: Why is top-posting such a bad thing?
>>
>>
>> --
>> Juju mailing list
>> Juju at lists.ubuntu.com
>> Modify settings or unsubscribe at:
>> https://lists.ubuntu.com/mailman/listinfo/juju
>>
>>


-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/juju/attachments/20140427/67273fe4/attachment.html>