Regify provider appliance tech

From regify WIKI
Jump to navigation Jump to search

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. Re-run your regify web administration wizard (provider maintenance dialogue) to change your SMS gateway settings.

Change of clearing password

Beginning with regify provider V4.1, the hash-codes of the users passwords are encrypted using the SHA256 of the clearing password. Thus, if your clearing password has changed, it will need re-calculation of all encrypted passwords in the database. Luckily, there is a function in your provider maintenance dialogue to do this automatically. If you run a redundant system with some master-master or master-slave configuration, you need to update the clearing password on both systems. Follow this guide to do a clearing update:

  1. Create a backup of your provider database (refer to #Backup_and_recovery).
  2. Enter the provider maintenance dialogue of your regify provider web administration.
  3. If you run a redundant system, please use a second webbrowser instance now(!) and also login to the second one.
  4. Make sure your system(s) are in maintenance mode. This prevents user from registering and log-in during your work. Normally, if clearing has changed the password, this happened automatically.
  5. Enter the provider maintenance dialogue of your regify provider web administration.
  6. Click "Change clearing password now" and activate the function.
  7. Enter the old (current) clearing password and enter the new one (twice).
  8. Click on "Change clearing password now" and start the recalculation.
  9. If you do not run a redundant system, jump to the last step now.
  10. Switch to the already open web administration of the second system.
  11. Click "Change clearing password now" and activate the function.
  12. Enter the old (current) clearing password and enter the new one (twice).
  13. Click on "Change clearing password now" and start the recalculation.
  14. Done. Validate all your login functions.

Database hints

Direct access using SSH

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!

Backup and recovery

Sometimes we encounter problems with character encoding during export and (re)import. This solution managed it to export on a regify-provider and import the data on another machine with no problems:

Export:

mysqldump -uroot --opt --quote-names --skip-set-charset --default-character-set=latin1 regify > backup_dump.sql

Import:

mysql -uroot -ppassword
mysql> create database regify;
mysql> quit

mysql -uroot -pregify --default_character_set utf8 regify < backup_dump.sql

Try using these options to fix your problem. The above values fixed the problem of double encoded UTF8 characters (the characters have been double encoded in the exported dump file).

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