-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Le 2015-01-19 16:38, Hummer a écrit :
> Thank you for your replies guys. It really steered me in the right
> direction. I have solved the problem and the solution are as
> follows:-
>
> 1. kz_whistle_apps refused to start because there was a mismatch in
> the cookie value. This one is somewhat elusive because it was not
> as a result of not following the installation instructions but
> because erlang creates a file called .erlang.cookie and write an
> abstract value in there is it cannot find a cookie configuration.
> Delete or change the value of its content to the value you have
> configured in the ini file and kz_whistle_apps should start
> consistently without any problems. NOTE- you must follow the
> powerpbx installation instruction to the letter for this to work
> for you.
Please prove how you came to this conclusion, as I think you've
mis-interpreted things a bit.
For the record, the cookie value of the whistle_apps VM doesn't matter
for anything other than compaction of databases. Kazoo does not use
the Distributed Erlang protocol, and thus the cookie value of the VM
is relatively meaningless. Kazoo communicates via HTTP (such as
Crossbar) and AMQP (all the backend services); neither of which
require the Erlang VM's cookie.
I suspect you made the HAProxy change at the same time as the cookie
change and when Kazoo could successfully connect to BigCouch, things
started working. I could also be wrong about that!
However, barring logs that prove to the contrary, the cookie just flat
out doesn't matter for 99% of Kazoo-related communication.
>
> 2. whapps_config was unable to retrieve config data from the
> database because its db connectivity config requirements differs
> from that of the other modules. The haproxy.cfg was changed as
> follows and this problem along with other related or dependent ones
> disappeared:- NOTE:- This is a change to the powerpbx installation
> instruction.
False. All Kazoo modules that want to access the database go through
the couch_mgr/couch_util modules.
The "normal" (but certainly not required) way to set this up is to
have HAProxy configured to listen on 15984 and 15986 on the
client/Kazoo side, and connect on the standard CouchDB ports of
5984/5986 on the backend/BigCouch side.
You then have to ensure /etc/kazoo/config.ini is also configured to
use the 15984 port.
Perhaps you edited the HAProxy config but didn't restart the service
until you added the 5984 section? I don't know, just speculating here.
Also, did you manually anonymize your BigCouch IP addresses above? How
is the admin port (5986) section going to 172.16.0.X and the api
section (5984) going to 172.1.0.X? Perhaps you made this typo in your
config file too? This would explain why Kazoo couldn't connect to
BigCouch and you saw the '$end_of_table' errors in the logs.
>
> 3. There was another side to the database connectivity issue. The
> Bigcouch cluster was struggling to replicate, hence had some impact
> on the ability for kazoo connecting with it. The reason for this
> was because the max_document_size in the default.ini file on the
> bigcouch server must be set above 1GB and the default is set to
> 67MB hence the issue, 1.4GB is what l think the minimum should be.
> Any less and you would have all sorts of connectivity problems.
What document did you create over 1GB? The only documents I can think
of that might even approach this is the voicemail box doc or maybe the
services doc. Or did you try to upload a huge media file? Seriously
confused and curious how this limit was hit for you.
>
> I hope it works for anyone else having these problems.
>
> On Monday, January 19, 2015 at 6:36:23 PM UTC, Hummer wrote:
>>
>> I have just install a 7 server architecture described in the
>>
http://www.powerpbx.org/content/kazoo-v3-single-or-multiple-server-voip-telephony-platform-install-guide-v1#all
>> tutorial. All servers seem to be working fine up till the point
>> where l needed to do the flush {/opt/kazoo/utils/sup/sup
>> whapps_config flush}. The BigCouch cluster seemed to have
>> replicated well but don't know why whistle is having trouble
>> getting config data from the database. Please help, l am sitting
>> in a pool of hair on this one.
>>
>>
>> KAZOO Tail Jan 19 18:22:02 sip01 2600hz[1342]:
>> |kz_buckets|whapps_config:447 (<0.1094.0>) fetch db config for
>> token_buckets Jan 19 18:22:02 sip01 2600hz[1342]:
>> |0000000000|Undefined:Undefined (emulator) Error in process
>> <0.1094.0> on node '
whistl...@sip.mydomain.com
>> <
whistl...@sip01.hummesh.com>' with exit value:
>> {{badmatch,'$end_of_table'},[{wh_couch_connections,get_server,0,[{file,"src/wh_couch_connections.erl"},{line,132}]},{couch_mgr,open_doc,3,[{file,"src/couch_mgr.erl"},{line,575}]},{whapps_config,get_db_config,1,[{file,"src/wh...
>> #012#012
>>
>>
>> BIGCOUCH Tail [Mon, 19 Jan 2015 18:29:30 GMT] [info]
>> [<0.19183.0>] [91bf2cb6] 172.16.0.5 undefined GET / 200 ok 0
>> [Mon, 19 Jan 2015 18:29:31 GMT] [info] [<0.19187.0>] [--------]
>> 172.16.0.12 - - 'GET' / 200 [Mon, 19 Jan 2015 18:29:31 GMT]
>> [info] [<0.19202.0>] [e1338275] undefined - - 'GET' / 200 [Mon,
>> 19 Jan 2015 18:29:31 GMT] [info] [<0.19202.0>] [e1338275]
>> 172.16.0.12 undefined GET / 200 ok 1 [Mon, 19 Jan 2015 18:29:32
>> GMT] [info] [<0.19217.0>] [--------] 172.16.0.5 - - 'GET' / 200
>> [Mon, 19 Jan 2015 18:29:32 GMT] [info] [<0.19219.0>] [07e0da13]
>> undefined - - 'GET' / 200 [Mon, 19 Jan 2015 18:29:32 GMT] [info]
>> [<0.19219.0>] [07e0da13] 172.16.0.5 undefined GET / 200 ok 1
>> [Mon, 19 Jan 2015 18:29:33 GMT] [info] [<0.19223.0>] [--------]
>> 172.16.0.12 - - 'GET' / 200 [Mon, 19 Jan 2015 18:29:33 GMT]
>> [info] [<0.19238.0>] [4bfa01ee] undefined - - 'GET' / 200 [Mon,
>> 19 Jan 2015 18:29:33 GMT] [info] [<0.19238.0>] [4bfa01ee]
>> 172.16.0.12 undefined GET / 200 ok 0
>>
>
iQEcBAEBAgAGBQJUvfMtAAoJENTKa+JPXCVgm0sIAKP2ZdVtKpm4xSbCqLZMcJp3
/Lkodka04Trhf9a0VetOZA+Yn5E2OTci0iHlQuvW95/AMOLeQkNpDXDmibTZvbUV
56Jv3phJvd3tkd1IXTk6URlLZMTX8vR1sOiyg/vo3UDEjTS1cOCQvqOSdWTi6Xju
JM4nAeo2mIV019ztw6uAd/LfNukIyrDUXa3FASi8npxgXY8sXamaguLu2A5bOEJ8
zPv7/5llOOAxp7PKBVqHEzwqWxi/YwZDRpZtcjodycIWm55GFTCUZ4ur1NMe27EY
xw1bjz9oMz9EjpRFYUyrl0/xNvbnsYDPvMHfZfdh8iabaJRA6IEgVHW3vHMvguU=
=jgmG
-----END PGP SIGNATURE-----