Cluster install on Debian 10
Tom Moore
I am trying to install Dsiprouter on two machines running Debian 10 with a
third machine running the Mysql database server.
What command line options do I use to specify the database server name and
login information for this server to have the database created on?
I was not able to find this in the install instructions or the help option
of the dsiprouter.sh script itself.
When I installed the system it seemed to create a Mysql setup on each node
itself instead of asking for the common host to have each node reach out too
for database access.
Thanks for any help you can provide.
Tom
Mack Hendricks
-Mack
> On Oct 22, 2021, at 10:19 AM, Tom Moore <tommy...@gmail.com> wrote:
>
> Hi,
> You received this message because you are subscribed to the Google Groups "dSIPRouter" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to dSIPRouter+...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/msgid/dSIPRouter/036e01d7c74f%24da415ee0%248ec41ca0%24%40gmail.com.
Mack Hendricks
dsiprouter setcredentials -kc kamailio:kamai...@terraform-20210201213031041000000001.foo.us-east-1.rds.amazonaws.com:3306/kamailio -createdbuser -dac dbadmin:foo
The above example will point the dSIPRouter instance to the Remote Database Server and will create the user kamailio in the kamailio database if it doesn’t already exist. The -dac parameter is the username/password of a privileged account for the RDS instance
Hi,
I was able to import the database into the server and have a database user with the proper privileges for managing the database configured on the Mysql server.
Are there any usage examples for the command line options I need to use for configuring the database connector as there doesn't seem to be any way I can do this from the help presented?
When installing the system onto the nodes I noticed the following:
If I use the clusterinstall option I can only specify the node ip addresses I wish to install the system on, I do not seem to be able to specify other option such as -servernat after the hostnames for general install options as the servers I am using are behind nat connections themselves.
Tom
Mack Hendricks
On Oct 27, 2021, at 12:43 PM, Tom Moore <tommy...@gmail.com> wrote:
Hi,
I stared from scratch with the following:
The machine is an Aws t4.small instance with Debian 10.
Forward and reverse dns are configured.
The hostnamectl set-hostname sip01.mycompany.com was set.
The install script was ran:
./dsiprouter.sh install -debug -all -servernat 1>1.txt 2>2.tt 3>3.tt
These messages are attached for your review.
At this point the Mysql install process seems to finish properly, but something is up with the Kamilio install process.
Tom
From: Mack Hendricks <a...@goflyball.com>
Sent: Saturday, October 23, 2021 6:08 PM
To: Tom Moore <tommy...@gmail.com>
Subject: Re: [dSIPRouter - Users] Cluster install on Debian 10
Clusterinstall is only used when mysql replication is used. Not for this configuration.
If you are still having trouble we should get you support so that you can open a support ticket.
Mack Hendricks
Chief Flyball
dOpenSource / DetroitPBX, Flyball Companies
Direct: 313-789-1313 (SMS Enabled)
On Oct 23, 2021, at 5:21 PM, Tom Moore <tommy...@gmail.com> wrote:
Hi,
I am still having trouble connecting the Dsiprouter hosts into a central db server.
Here is the line I used and this did not work for me.
dsiprouter setcredentials -kc kamailio:dsipr...@192.168.5.33:3306/kamailio -createdbuser -dac root:hello
The kamailio user and password are what I want the kamailio user to have on the database server and the root user I defined is the database server admin user.
Before I try this on an rds instance I figured I would try this setup on 3 Vmware machines here locally.
I have the following:
Hostname dsiprouter1.tom.lan 192.168.5.31
Hostname dsiprouter2.tom.lan 192.168.5.32
Hostname mysql.tom.lan 192.168.5.33
All machines are Debian 10 based.
The Mysql server has a basic Mysql server install with a root database administrator that can connect from anywhere on the lan with all privileges on all databases with a password of hello.
It also has the kamailio database copied from dsiprouter1 in as an accessible database with 89 tables.
In addition I have fetched the master branch of Dsiprouter from Github.
On my two Dsiprouter hosts I have the following:
/etc/apt/sources.list file has the cdrom install disk line commented out.
The git and curl packages are installed.
I have valid authorized_keys files on each host to allow the controller to autologin to the hosts for install purposes.
Each host has the Dsiprouter distribution installed onto it via the clusterinstall option from the Mysql node.
On the Mysql node I ran:
dsiprouter.sh clusterinstall ro...@192.168.5.31 ro...@192.168.5.32
Is there something I am missing that I am overlooking or have these systems changed in some way that are causing the dsiprouter management script to fail when doing certain operations?
If needed I would be willing to do a shared screen process to show the steps I am taking that are proving to be unsuccessful.
Thanks,
Tom
<1.txt><2.txt>
Tom Moore
Hi,
I was able to overcome the single instance install issue by using an amd64 t3 instance type.
Currently arm64 instance types are not supported.
Tom