Hi Bertrand,
The first thing to check is that your containers are running. You can do this
by running sudo docker ps. You should see something like:
CONTAINER ID IMAGE COMMAND
CREATED STATUS PORTS NAMES
e506c876cecd clearwaterdocker_bono "/usr/bin/supervisord" 35
minutes ago Up 35 minutes 0.0.0.0:3478->3478/tcp,
0.0.0.0:3478->3478/udp, 0.0.0.0:5060->5060/tcp, 0.0.0.0:5062->5062/tcp,
0.0.0.0:5060->5060/udp, 5058/tcp, 0.0.0.0:32773->22/tcp
clearwaterdocker_bono_1
34005c1236e3 clearwaterdocker_sprout "/usr/bin/supervisord" 35
minutes ago Up 35 minutes 5052/tcp, 5054/tcp, 0.0.0.0:32772->22/tcp
clearwaterdocker_sprout_1
a97a42035b9c clearwaterdocker_ellis "/usr/bin/supervisord" 35
minutes ago Up 35 minutes 0.0.0.0:80->80/tcp, 0.0.0.0:32771->22/tcp
clearwaterdocker_ellis_1
61425b298529 clearwaterdocker_homer "/usr/bin/supervisord" 35
minutes ago Up 35 minutes 7888/tcp, 0.0.0.0:32770->22/tcp
clearwaterdocker_homer_1
b4161df0319c quay.io/coreos/etcd:v2.2.5 "/etcd -name etcd0 -a" 35
minutes ago Up 35 minutes 2379-2380/tcp, 4001/tcp, 7001/tcp
clearwaterdocker_etcd_1
0f4bceba2aa0 clearwaterdocker_ralf "/usr/bin/supervisord" 35
minutes ago Up 35 minutes 10888/tcp, 0.0.0.0:32769->22/tcp
clearwaterdocker_ralf_1
064e124ee549 clearwaterdocker_homestead "/usr/bin/supervisord" 35
minutes ago Up 35 minutes 8888-8889/tcp, 0.0.0.0:32768->22/tcp
clearwaterdocker_homestead_1
The output also shows the port-forwarding that Docker has configured to allow
you to connect to the containers from outside. For example, my Ellis container
has port 80 forwarded to allow HTTP connections (see the bold above).
If your output is similar to this, then you should check that your network is
set up to allow HTTP access to your box. Are all the firewalls in your network
set up to allow connections over tcp on port 80?
http://clearwater.readthedocs.io/en/stable/Clearwater_IP_Port_Usage.html
explains all of the connections that are required to talk to Project Clearwater.
If it’s not a network problem, then can you send the output of running sudo
netstat -lnp on your box? That way we can see for certain whether Ellis is
listening on the right port.
Yours,
Chris
From: Bertrand Bouge [mailto:[email protected]]
Sent: 10 May 2016 21:15
To: Chris Elford (projectclearwater.org) <[email protected]>
Cc: [email protected]
Subject: Re: [Project Clearwater] Error winch Bono an Sproud on lxc (ubuntu
template)
Hi Chris,
I finally used dockers by following this procedure
(https://github.com/Metaswitch/clearwater-docker) . But I can not conect to
Ellis GUI ( Http://ellis.example.com | Http://ellis.example.com:80 |
Http://ellis.example.com:8080 ) .
Could you help me please.
Yours.
2016-05-09 9:07 GMT-04:00 Chris Elford
(projectclearwater.org<http://projectclearwater.org>)
<[email protected]<mailto:[email protected]>>:
Hi Bertrand,
Thanks for letting us know about this.
We have managed to get Project Clearwater running on Linux containers using
Docker. Our clearwater-docker<https://github.com/Metaswitch/clearwater-docker>
repository contains Dockerfiles, and instructions, which you should be able to
follow to make that work for you too. We run these under continuous integration
in EC2, and they are currently working fine.
If you are set on using a different container manager to Docker, then there are
some things that you will need to work around, like the issue with sysctl that
you have seen below. If you look at the Dockerfiles in clearwater-docker, you
will see that we take a range of steps as well as installing the packages on
the images. You should be able to run these commands in your Linux container
environment. The main differences are:
• Replacing sysctl with a dummy script.
• Using supervisord instead of monit to monitor our processes.
• A range of sed scripts to tweak configuration.
When you get this working, please let us know – I’m sure there are people on
the mailing list who may want to try the same thing.
Yours,
Chris
From: Clearwater
[mailto:[email protected]<mailto:[email protected]>]
On Behalf Of Bertrand Bouge
Sent: 04 May 2016 13:07
To:
[email protected]<mailto:[email protected]>
Subject: [Project Clearwater] Error winch Bono an Sproud on lxc (ubuntu
template)
Hi for all,
I'm new with clearwater projet and I'm trying to setup bono,sproud on Linux
containers. I have error when execute these command on containers.
sudo DEBIAN_FRONTEND=noninteractive apt-get install bono restund --yes
sudo DEBIAN_FRONTEND=noninteractive apt-get install clearwater-management --yes
Errors:
Paramétrage de clearwater-tcp-scalability (1.0-160413.154808) ...
sysctl: cannot stat /proc/sys/net/core/rmem_max: Aucun fichier ou dossier de ce
type
sysctl: cannot stat /proc/sys/net/core/wmem_max: Aucun fichier ou dossier de ce
type
sysctl: cannot stat /proc/sys/net/ipv4/tcp_rmem: Aucun fichier ou dossier de ce
type
sysctl: cannot stat /proc/sys/net/ipv4/tcp_wmem: Aucun fichier ou dossier de ce
type
sysctl: cannot stat /proc/sys/net/ipv4/tcp_syncookies: Aucun fichier ou dossier
de ce type
sysctl: cannot stat /proc/sys/net/ipv4/tcp_tw_reuse: Aucun fichier ou dossier
de ce type
sysctl: cannot stat /proc/sys/net/ipv4/tcp_mem: Aucun fichier ou dossier de ce
type
sysctl: cannot stat /proc/sys/net/core/netdev_max_backlog: Aucun fichier ou
dossier de ce type
sysctl: permission denied on key 'fs.file-max'
dpkg: error processing package clearwater-tcp-scalability (--configure):
Place need your help.
Thanks for all
--
Bertrand Bouge
[email protected]<mailto:[email protected]>
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/mailman/listinfo/clearwater_lists.projectclearwater.org
