telephoneorg / docker-kazoo Goto Github PK
View Code? Open in Web Editor NEWKazoo Dockerized, for Kubernetes
Kazoo Dockerized, for Kubernetes
When I'm trying to set up the docker-compose edition with:
docker-compose pull
docker-compose up --abort-on-container-exit
I'm getting this error message:
Creating dockerkazoo_kzutil_1 ...
Starting dockerkazoo_couchdb-data_1 ...
rabbitmq is up-to-date
Starting dockerkazoo_couchdb-data_1
Creating dockerkazoo_kzutil_1 ... error
Starting dockerkazoo_couchdb-data_1 ... done
couchdb is up-to-date
kazoo is up-to-date
ERROR: for kzutil Cannot create container for service kzutil: No command specified
ERROR: Encountered errors while bringing up the project.
I think this might be the result of a rabbitmq node being hardcoded in the bigcouch.
=ERROR REPORT==== 26-Mar-2016::00:34:02 ===
Channel error on connection <0.5422.0> (172.17.16.0:38859 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 101:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-20-24' of durable queue 'BLF-QUEUE-plasma.valuphone.com' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:34:08 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 244:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=INFO REPORT==== 26-Mar-2016::00:34:13 ===
accepting AMQP connection <0.7669.0> (172.17.60.0:59717 -> 172.17.20.58:5672)
=INFO REPORT==== 26-Mar-2016::00:34:13 ===
accepting AMQP connection <0.7799.0> (172.17.60.0:59718 -> 172.17.20.58:5672)
=ERROR REPORT==== 26-Mar-2016::00:34:13 ===
Channel error on connection <0.7669.0> (172.17.60.0:59717 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 101:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-20-24' of durable queue 'BLF-QUEUE-adeno.valuphone.com' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:34:38 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 246:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:35:08 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 247:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:35:38 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 248:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:36:08 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 249:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:36:38 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 250:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:37:08 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 251:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:37:38 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 252:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:38:08 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 253:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:38:38 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 254:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:39:08 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 255:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
=ERROR REPORT==== 26-Mar-2016::00:39:38 ===
Channel error on connection <0.2328.0> (172.17.20.57:35886 -> 172.17.20.58:5672, vhost: '/', user: 'guest'), channel 256:
operation queue.declare caused a channel exception not_found: "home node 'rabbit@172-17-60-115' of durable queue 'smsc_inbound_queue_sms' in vhost '/' is down or inaccessible"
Hello.
Since erlang params are not set in the ConfigMap, the tmpld tries to calculate them relying on nproc info
+P {{ config.get('erlang.processes', shell('nproc') * 3200) }}
+A {{ config.get('erlang.threads', shell('nproc') * 16) }}
On my bare metal node it calculates something like many many 8888888. I guess it's because of permissions of the container. So, I personally set those variables. My offer is to set back this stuff because it's much more clear and works fine.
Hi,
I am trying to deploy this setup but "Kazoo" pod remain stuck in Init:CrashLoopBackOff. I executed command as follow,
kubectl create -f config.yaml
kubectl create -f deployment.yaml
kubectl create -f service.yaml
kubectl create -f templates.yaml
After executing above command, everything creates fine but my kazoo pod remains in Init:CrashLoopBackOff. Kubectl describe log results are attached for reference.
Kindly help me.
Thanks
Regards,
Umar
For apps that use the erlang distribution protocol it's often necessary to have a hostname that can be resolved to it's ip address. Unfortunately Kubernetes doesn't assign the resolvable hostname of the pod as the container hostname to discourage people relying on such a thing. Great for web type environments but not with erlang.
so is possible im a bit confused i ran the docker-compose up -d but i dont see a freeswitch anywhere
also seemingly there are 2 docker-compose.yaml files on with db can you elaborate on these, getting this running under docker i would think pretty straight tforward but something seems not quite right
21:01:38.733 [info] attempting to connect default freeswitch node '[email protected]'
21:01:43.735 [info] attempting to connect default freeswitch node '[email protected]'
21:01:48.737 [info] attempting to connect default freeswitch node '[email protected]'
21:01:53.738 [info] attempting to connect default freeswitch node '[email protected]'
21:01:58.582 [info] port_request crawler completed a full crawl
21:01:58.739 [info] attempting to connect default freeswitch node '[email protected]'
21:02:03.740 [info] attempting to connect default freeswitch node '[email protected]'
21:02:08.742 [info] attempting to connect default freeswitch node '[email protected]'
21:02:13.744 [info] attempting to connect default freeswitch node '[email protected]'
21:02:18.749 [info] attempting to connect default freeswitch node '[email protected]'
Call hang up doesn't work (tested on softphones CSipSimple, MicroSIP). Also calls are autamatically hanged up after 32 sec.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.