
--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
Has the wiki already been updated? I've just tried installing through chefsolo on centos 6, without any luck. If anyone can provide me with detailed instructions for any OS I'd be more than happy.
Cheers,
Ronald.
These nitty gritty details are crucial to the project's success.
Please file a ticket as a bug or improvement stating that the output of crossbar_maintenance create_account was not useful when the vm.args �name field was invalid.
From: "pawl...@gmail.com" <pawl...@gmail.com>
Reply-To: "2600h...@googlegroups.com" <2600h...@googlegroups.com>
Date: Tuesday, August 27, 2013 7:39 AM
To: "2600h...@googlegroups.com" <2600h...@googlegroups.com>
Cc: "pawl...@gmail.com" <pawl...@gmail.com>
Subject: Re: Kazoo Manual Deployment - wiki documentation
Hi Raj,
thanks for your help, I had a typo in my vm.args�in the -name�field... needless to say that crossbar_maintenance create_account�was not properly creating the account, but because this is my first install and since the output wasn't helpful...�I didn't clue in on that. All seems to work now!
Thanks again, you have saved me a huge amount of trouble!�
Cheers!
A.
On Monday, August 26, 2013 12:32:00 AM UTC-4, Raj Saini wrote:
Hi,
Can you check if Kazoo is connected to CouchDB? I can think of that either Kazoo is not able to connect to CouchDB or database is not created may be due to file system permissions. Make sure your database folder (/var/lib/bigcouch if you have followed the wiki) is owned by couchdb user. Also, check in /opt/bigcouch/etc/vm.args that -name is set to bigcouch@your host ip. It has to be -name and not -sname.
Thanks,
Raj
On Saturday 24 August 2013 11:01 PM, pawl...@gmail.com wrote:
Hi Raj,
I have followed your wiki post, thanks a lot for the instructions, conf files and scripts!�
Everything seemed to have gone well, however I can't for the life of me login using Kazoo UI or authenticate through the 'user_auth' endpoint on the API. I keep getting { ... "message":"invalid credentials","error":"401" ...} �from the API so I'm assuming that something in the setup scripts or the "crossbar_maintenance create_account" script must be missing or buggy... When I turn on debug logging in Erlang and run dev-start-apps.sh I see the following error: [ debug ] failed to find account DB from realm <the.realm.used.to.create.the.account>"
Can you or anyone here please point me in the right direction? I made sure that 'credentials' and 'realm' fields that I supply to the endpoint are correct by copy pasting it from Futon. Any idea what I might be missing?
Thanks in advance!
A.
On Saturday, August 10, 2013 3:14:38 AM UTC-4, Raj Saini wrote:
Hello,
I have updated the Wiki with latest instructions and also provided few
scripts to automate the process. Although, I have used these
instructions on multiple server, I may have missed few points �or there
may be typos. Please report any errors you find and I will update the Wiki.
Thanks,
Raj
On Saturday 20 July 2013 07:16 PM, Joan Jou wrote:
> Hi Raj,
> Please, make me know when your instructions wil be updated to test it.
>
> Enviat des del iPhone
>
> El 20/07/2013, a les 13:07, Darren Schreiber <dar...@2600hz.com> va escriure:
>> Raj,
>> � � There are a number of people who would be thrilled, I imagine, to have
>> those instructions updated. Please feel free. I have enabled edit access
>> for your user, thank you for offering to help!!! We really do appreciate
>> it.
>>
>> --
>> Darren Schreiber
>> CEO / Co-Founder
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> On 7/19/13 3:55 AM, "Raj Saini" <rajs...@gmail.com> wrote:
>>
>>> I have been able to build and install the Kazoo on Ubuntu 13.04. My
>>> deployment is on a single machine and all �components but Kazoo were
>> the vm.args �name field was invalid.
>>
>> http://tickets.2600hz.com/
>>
>>
>> From: "pawl...@gmail.com <javascript:>" <pawl...@gmail.com
>> <javascript:>
>>>
>> Reply-To: "2600h...@googlegroups.com <javascript:>" <
>> 2600h...@googlegroups.com <javascript:>> Date: Tuesday, August
>> 27, 2013 7:39 AM To: "2600h...@googlegroups.com <javascript:>"
>> <2600h...@googlegroups.com<javascript:>
>>>
>> Cc: "pawl...@gmail.com <javascript:>" <pawl...@gmail.com
>> <javascript:>> Subject: Re: Kazoo Manual Deployment - wiki
>> documentation
>>
>> Hi Raj,
>>
>> thanks for your help, I had a typo in my vm.args�in the
>> -name�field... needless to say that crossbar_maintenance
>> create_account�was not properly creating the account, but
>> because this is my first install and since the output wasn't
>> helpful...�I didn't clue in on that. All seems to work now!
>>
>> Thanks again, you have saved me a huge amount of trouble!�
>>
>> Cheers!
>>
>> A.
>>
>> On Monday, August 26, 2013 12:32:00 AM UTC-4, Raj Saini wrote:
>>>
>>> Hi,
>>>
>>> Can you check if Kazoo is connected to CouchDB? I can think of
>>> that either Kazoo is not able to connect to CouchDB or database
>>> is not created may be due to file system permissions. Make sure
>>> your database folder (/var/lib/bigcouch if you have followed
>>> the wiki) is owned by couchdb user. Also, check in
>>> /opt/bigcouch/etc/vm.args that -name is set to bigcouch@your
>>> host ip. It has to be -name and not -sname.
>>>
>>> Thanks,
>>>
>>> Raj
>>>
>>> On Saturday 24 August 2013 11:01 PM, pawl...@gmail.com wrote:
>>>
>>> Hi Raj,
>>>
>>> I have followed your wiki post, thanks a lot for the
>>> instructions, conf files and scripts!�
>>>
>>> Everything seemed to have gone well, however I can't for the
>>> life of me login using Kazoo UI or authenticate through the
>>> 'user_auth' endpoint on the API. I keep getting { ...
>>> "message":"invalid credentials","error":"401" ...} �from the
>>> API so I'm assuming that something in the setup scripts or the
>>> "crossbar_maintenance create_account" script must be missing or
>>> buggy... When I turn on debug logging in Erlang and run
>>> dev-start-apps.sh I see the following error: [ debug ] failed
>>> to find account DB from realm
>>> <the.realm.used.to.create.the.account>"
>>>
>>> Can you or anyone here please point me in the right direction?
>>> I made sure that 'credentials' and 'realm' fields that I supply
>>> to the endpoint are correct by copy pasting it from Futon. Any
>>> idea what I might be missing?
>>>
>>> Thanks in advance!
>>>
>>> A.
>>>
>>> On Saturday, August 10, 2013 3:14:38 AM UTC-4, Raj Saini wrote:
>>>
>>>>
>>>> Hello,
>>>>
>>>> I have updated the Wiki with latest instructions and also
>>>> provided few scripts to automate the process. Although, I
>>>> have used these instructions on multiple server, I may have
>>>> missed few points �or there may be typos. Please report any
>>>> errors you find and I will update the Wiki.
>>>>
>>>> Thanks,
>>>>
>>>> Raj On Saturday 20 July 2013 07:16 PM, Joan Jou wrote:
>>>>> Hi Raj, Please, make me know when your instructions wil be
>>>>> updated to test it.
>>>>>
>>>>> Enviat des del iPhone
>>>>>
>>>>> El 20/07/2013, a les 13:07, Darren Schreiber
>>>>> <dar...@2600hz.com> va
>>>> escriure:
>>>>>> Raj, � � There are a number of people who would be
>>>>>> thrilled, I
>>>> imagine, to have
>>>>>> those instructions updated. Please feel free. I have
>>>>>> enabled edit
>>>> access
>>>>>> for your user, thank you for offering to help!!! We
>>>>>> really do
>>>> appreciate
>>>>>> it.
>>>>>>
>>>>>> -- Darren Schreiber CEO / Co-Founder
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On 7/19/13 3:55 AM, "Raj Saini" <rajs...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>>> I have been able to build and install the Kazoo on
>>>>>>> Ubuntu 13.04. My deployment is on a single machine and
>>>>>>> all �components but Kazoo
I never had such problem and I am running multiple deployments.
Can you paste your Kazoo and FS logs.
Raj
./dev-start-apps.sh, I get the following error messages.
21:54:09.283 [info] failed to connect to BigCouch/HAProxy at 192.168.140.226:15984: {case_clause,{error,{conn_failed,{error,econnrefused}}}}
21:54:09.283 [info] failed to connect to BigCouch/HAProxy at 192.168.140.226:15986: {case_clause,{error,{conn_failed,{error,econnrefused}}}}
21:54:10.285 [info] failed to connect to BigCouch/HAProxy at 192.168.140.226:15984: {case_clause,{error,{conn_failed,{error,econnrefused}}}}
21:54:10.286 [info] failed to connect to BigCouch/HAProxy at 192.168.140.226:15986: {case_clause,{error,{conn_failed,{error,econnrefused}}}}
21:54:11.291 [info] failed to connect to BigCouch/HAProxy at 192.168.140.226:15986: {case_clause,{error,{conn_failed,{error,econnrefused}}}}
21:54:11.291 [info] failed to connect to BigCouch/HAProxy at 192.168.140.226:15984: {case_clause,{error,{conn_failed,{error,econnrefused}}}}
21:54:12.293 [info] failed to connect to BigCouch/HAProxy at 192.168.140.226:15984: {case_clause,{error,{conn_failed,{error,econnrefused}}}}