Difference between revisions of "Regify provider appliance tech"

From regify WIKI
Jump to navigation Jump to search
Line 67: Line 67:
 
4) Check if the VMWare tools are running:
 
4) Check if the VMWare tools are running:
 
  /etc/init.d/vmware-tools status
 
  /etc/init.d/vmware-tools status
 
== How to fix broken cross-master replication ==
 
 
# login to both systems by using SSH (PuTTY) with user root and the password you set during installation
 
# Make a copy of your databases on both machines by using mysqldump<br>''mysqldump --databases regify > /tmp/mysql_backup.sql''
 
# Enter provider configuration on both systems by typing ''providerConfig''
 
# On both systems, navigate to "Database..." -> "View Database Status"
 
# Determine, which system is the one with most recent data
 
## One of the two systems is showing "Master Status" and "Slave Status". The other one only showing "Master Status".
 
## If it is not like descibed above, this tutorial will not help you! Please contact regify support!
 
## The one with both "Master Status" and "Slave Status" is the one with the most recent data. We call it now '''Origin'''. The other one is called '''Behind''' now.
 
# Navigate to "Database..." -> "Configure Replication..."
 
# Choose "no replication" on both systems ("master" and "slave")
 
# Choose "Cross Master" on the '''Origin''' system
 
# Fill in the data of the master dialogue
 
## Enter Unique Server ID (now 1 for the '''Origin''')
 
## Enter correct number of servers (2 in most cases)
 
## Enter IP address/subnet of the '''Behind''' system
 
## Enter a username like 'providerRep' and a password (note the password!)
 
## Choose 'Next'
 
# In slave dialogue
 
## Enter the IP of the '''Behind''' system (already filled in)
 
## Enter the same credentials as in the dialogue before
 
## Choose 'Next'
 
# Answer the "Replication Synchronisation" question with "Yes"
 
# Fill in the IP address of the '''Behind''' system and enter the root password of the '''Behind''' system.
 
# Choose 'Ok'
 
# Wait
 
# Choose "Cross Master" on the '''Behind''' system.
 
# Fill in the data of the master dialogue
 
## Enter Unique Server ID (now 2 for the '''Behind''')
 
## Enter correct number of servers (like on the '''Origin''')
 
## Enter IP address/subnet of the '''Origin''' system
 
## Enter the same credentials as in the dialogue on the '''Origin'''
 
## Choose 'Next'
 
# In slave dialogue
 
## Enter the IP of the '''Origin''' system (already filled in)
 
## Enter the same credentials as in the dialogue before
 
## Choose 'Next'
 
# Answer the "Replication Synchronisation" question with "No" (important!)
 
# Wait
 
# Done
 
  
 
== Manually run the updates ==
 
== Manually run the updates ==

Revision as of 16:20, 5 June 2014

PostFix

The regify Provider Appliance runs a PostFix server as MTA or SmartHost. You can use the following tricks to get a closer look:

To see the queue status:

> mailq

To flush the mailqueue (maybe, after you changed something)

> postqueue -f

To show mail log (continuously):

> tail -f /var/log/maillog

Logfiles

You can find most logs in

> /var/log/
> /var/log/httpd/

Additionally, the regify-provider does its own daily logging about provider business:

> /opt/provider/REGIFY_LOGS/

Certificates

The installed certificates are located at

/etc/pki/tls/certs
/etc/pki/tls/private

While installing SSL certificates by using the applicance SSH menu, please ensure that you copy the complete certificate chain including the root CA and the private key. The order of the entries does not matter.

Appliance

If you like to turn off the regify Provider Appliance, exit the appliance menu, login as root and enter

> shutdown -h now

It may be you need to use sudo, if you only logged in using 'regify' or you used the 'drop to shell' option.

SMS gateway

You can find information about the SMS gateway at the regify homepage.

Database access

In order to access the regify provider database directly, we recommend the following:

  1. Use PuTTy to access the system (like accessing the provider appliance menu). Please configure your PuTTY connection to create a port forwarding tunnel like in the screenshot. This is to tunnel the remote systems port 3306 to your local client machines port 3306.
  2. Use a tool like HeidiSQL to access the now local available MySQL database.
  3. PLEASE BE CAREFUL! You now have full control over the database!

Install VMWare Tools

1) Please respect the licence and support information about third party software on the regify provider appliance. You can find this information in your regify appliance manual. In short words, you are not allowed to install anything except software that is essentially needed for running the appliance on a virtual environment. No other RPM repositories allowed!

2) Chose to install or update VMWare tools for your virtual machine. This will create a new CD rom device for the regify provider software appliance.

3) Enter in terminal:

mkdir /mnt/cdrom
mount /dev/cdrom /mnt/cdrom
cp /mnt/cdrom/VMwareTools-*.tar.gz /tmp
umount /mnt/cdrom
tar -zxf /tmp/VMwareTools-*.tar.gz -C /tmp
cd /
./tmp/vmware-tools-distrib/vmware-install.pl --default
rm -f /tmp/VMwareTools-*.tar.gz
rm -rf /tmp/vmware-tools-distrib

Sometimes, you might need to mount /dev/sr0 instead of /dev/cdrom.

4) Check if the VMWare tools are running:

/etc/init.d/vmware-tools status

Manually run the updates

In order to manually run the updates for the provider and regigate without SSH GUI, simply execute

yum upgrade