OpenSuSE Redis

Fri, 18 Oct 2024 00:00:00 +0000

Redis server on openSUSE

Installation

sudo zypper in redis

Configuration

Copy default config file

sudo cp -a /etc/redis/default.conf.example /etc/redis/instancename.conf

We use the cp -a here, so that our permissions are preserved.
In case you copied the file without the -a:

sudo chown root:redis /etc/redis/instancename.conf
sudo chmod u=rw,g=r,o= /etc/redis/instancename.conf

Add user to redis group with YaST, logout and login.

Minimal config

Change at least pidfile, logfile and dir setting the pid file has to match your config filename without the .conf

pidfile /run/redis/instancename.pid
logfile /var/log/redis/instancename.log
dir /var/lib/redis/instancename/

If you want to run more than one instance you also have to change the socket path and/or the ip:port combination.
e.g. /run/redis/instancename.sock
Also make sure if you copy configurations from somewhere, that daemonize should be set to no.

Create the database dir

sudo install -d -o redis -g redis -m 0750 /var/lib/redis/instancename/
sudo systemctl start redis@instancename
sudo systemctl enable redis@instancename

To stop/restart all instances at the same time use:

sudo systemctl restart redis.target
sudo systemctl stop redis.target

Default config

bind 127.0.0.1 -::1
protected-mode yes
port 6379

Use Unix socket

Add this in conf file:

unixsocket /var/run/redis/instancename.sock
unixsocketperm 775

Integration with apache when using unix domain sockets

If you plan to use redis in combination with apache, then you should add redis to apache group and set unixsocketperm 770:

sudo usermod -a -G redis wwwrun
sudo systemctl restart apache2

apache is now able to connect to the redis socket.

OpenSuSE Galera Cluster

Mon, 16 Jul 2018 21:40:04 +0200

Configuring a galera synchronous multi-master database cluster based on openSuSE Leap 15.6

First node

Add server:database repository from OBS and install the necessary packages, this must be done for all the servers in the cluster.

sudo zypper addrepo https://download.opensuse.org/repositories/server:database/openSUSE_Leap_15.0/server:database.repo
sudo zypper refresh
sudo zypper install mysql mariadb-galera galera-3

Start and securing mariadb installation

sudo systemctl start mariadb
sudo mysql_secure_installation

Once you have answered the prompt questions, you can turn off mariadb and edit the galera file configuration in /etc/my.cnf.d/50-galera.cnf changing this way:

# Whether or not wsrep replication is enabled
wsrep_on=ON
# Full path to wsrep provider library or 'none'
wsrep_provider=/usr/lib64/galera-3/libgalera_smm.so
# Logical cluster name. Should be the same for all nodes.
wsrep_cluster_name="my_cluster"
# Group communication system handle
wsrep_cluster_address="gcomm://"
# Human-readable node name (non-unique). Hostname by default.
wsrep_node_name="node1"

once finished editing the file, after saving it, start mariadb in this way:

sudo galera_new_cluster

Now you can log in into mariadb and verify that the cluster (with only one server enabled) is up and running:

MariaDB [(none)]> SHOW STATUS LIKE 'wsrep_cluster_size';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| wsrep_cluster_size | 1 |
+--------------------+-------+
1 row in set (0.00 sec)

This variable tells you the number of nodes that are connected to the cluster. It’s time to open the ports on the firewall to allow other nodes to connect

sudo firewall-cmd --zone=public --add-service=mysql --permanent
sudo firewall-cmd --zone=public --add-port=3306/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4567/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4568/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4444/tcp --permanent
sudo firewall-cmd --reload

Additional nodes

Repeat the same operations performed on node 1 until it is time to edit the /etc/my.cnf.d/50-galera.cnf file.

# Whether or not wsrep replication is enabled
wsrep_on=ON
# Full path to wsrep provider library or 'none'
wsrep_provider=/usr/lib64/galera-3/libgalera_smm.so
# Logical cluster name. Should be the same for all nodes.
wsrep_cluster_name="my_cluster"
# Group communication system handle
wsrep_cluster_address="gcomm://<node1.ip.address>,<node2.io.address>"
# Human-readable node name (non-unique). Hostname by default.
wsrep_node_name="node2"

Set wsrep\_cluster\_address="gcomm://\<node1.ip.address\>,\<node2.ip.address\>" with the correct ip addresses, open firewall ports and start mariadb.

sudo firewall-cmd --zone=public --add-service=mysql --permanent
sudo firewall-cmd --zone=public --add-port=3306/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4567/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4568/tcp --permanent
sudo firewall-cmd --zone=public --add-port=4444/tcp --permanent
sudo firewall-cmd --reload
sudo systemctl start mariadb

You can check the entry of node2 in the cluster in the same way as before:

MariaDB [(none)]> SHOW STATUS LIKE 'wsrep_cluster_size';
+--------------------+-------+
| Variable_name | Value |
+--------------------+-------+
| wsrep_cluster_size | 2 |
+--------------------+-------+
1 row in set (0.00 sec)

Once the nodes are synchronized it is necessary to go back to the node1 to edit wsrep\_cluster\_address="gcomm://\<node1.ip.address\>,\<node2.ip.address\>" with the correct ip addresses.

Repeat the operations performed on node2 to add additional nodes.

Database on Gallochri's Blog