...

1. Update postgresql.conf file

   • Location: Depending upon the OS and installation option, the location of this file varies. Do a google search to find the location of this file as per your OS and the installation option used.

   • Configuration to change: This file contains multiple options for PostreSQL database settings but we are only interested in listen_addresses property. This variable controls which IPs the server will answer on, not which IPs the server will permit connections to authenticate from.

     Image RemovedImage Added

   • Updated Value: Update the value of the listen_addresses property by replacing localhost with * and ensure that this line is not commented by removing the # symbol before this line. This is the most common mistake done by first-time users. The updated file should look like the image below.

     

   • Save and restart PostgreSQL This is necessary to apply the changes. The simplest way is to restart the PC or look for the restart command as per your OS and installation option.

2. Update pg_hba.conf file

   • Location: Depending upon the OS and installation option, the location of this file varies. Do a Google search to find the location of this file as per your OS and the installation option used.

   • Configuration to change: This file is used to control access at a finer-grained level for which IPs the server will accept logins from for specific databases and users. We are interested in entries corresponding to IPv4 and IPv6 hosts.

     Image RemovedImage Added

   • Updated Value: We need to specify the addresses of the hosts which must be allowed to accessthe database along with the method for user authentication. Add the following entries:

     Code Block
     host all all 0.0.0.0/0 md5 host all all ::/0 md5

     The updated file should look like the image below. Save and restart PostgreSQL to apply the changes.

     

...

It is recommended to create a new configuration file and add a reference to the httpd.conf file. See attached image where these configurations are added to jira-vhost.conf file inside <APACHE_ROOT>/extra directory and the reference is added in the httpd.conf file

Proxy pass is used to forward requests from a web server to another server, while proxy pass reverse is used to forward responses from the other server back to the web server.

Reverse proxy configuration files

Command to verify the load balancer configuration

apachectl configtest

...

server {
          listen 80;
          server_name jira.example.com;

          #Configuration for JIRA (running on port 8080)
          location / {
                        proxy_set_header X-Forwarded-Host $host;
                        proxy_set_header X-Forwarded-Server $host;
                        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                        proxy_pass http://127.0.0.1:8080; 
                }
}

sdgs

...

asfasfd

...

Configure Jira to work with reverse proxy

Jira server configuration file

...

Sample Jira server configuration file with reverse proxy and context details

...

Re-Configure Jira to work in Cluster

Create a shared home directory

...

Create a cluster.properties

...

fhsdg

...

sdg

sdggsdg

...

sdgsdg

...

sdgsgfile for both nodes which stores the note name and shared drive location

Sample Jira cluster.properties file to be placed in each Jira local home

...

Add reverse proxy configurations for Cluster

Reverse proxy configuration for Jira Cluster

sdgsg

...

wetwet

...

...

<VirtualHost *:80>
    ServerName jira.example.com
     
    ProxyRequests Off
    ProxyVia Off
    ProxyPreserveHost On
     
#    <Proxy *>
#         Require all granted
#    </Proxy>

 	#for JIRA DC Cluster Setup
	<Proxy balancer://jiracluster>
		# JIRA DC node 1
		BalancerMember http://192.168.29.211:8080/jira route=primary
		# The above link refers to Link #2 in Figure 1

		# JIRA DC node 2
		# BalancerMember http://192.168.29.103:8080/jira route=secondary
		# The above link refers to Link #6 in Figure 1

		# Security "we aren't blocking anyone but this the place to make those changes
		Order Deny,Allow
		Deny from none
		Allow from all

		# Load Balancer Settings
		# We are not really balancing anything in this setup, but need to configure this
		ProxySet lbmethod=byrequests
		ProxySet stickysession=JSESSIONID
	</Proxy>

 
    	ProxyPass /rm http://192.168.29.211:3060/rm/
    	ProxyPassReverse /rm http://192.168.29.211:3060/rm/

    	#for JIRA Data Center
    	# Don't reverse-proxy requests to the management UI
	ProxyPass /balancer-manager !

	# Reverse proxy all other requests to the JIRA cluster
	ProxyPass / balancer://jiracluster/

	# Here's how to enable the load balancer's management UI if desired
	<Location /balancer-manager>
		SetHandler balancer-manager

		# You SHOULD CHANGE THIS to only allow trusted ips to use the manager
		Order deny,allow
		Allow from all
	</Location>

	ErrorLog "/private/var/log/apache2/jira.example.com-error_log"
	CustomLog "/private/var/log/apache2/jira.example.com-access_log" common
</VirtualHost>

Re-start Jira and check the node status

...

Node name will appear in the footer

...

Add remaining nodes as per this doc: https://confluence.atlassian.com/adminjiraserver/set-up-a-jira-data-center-cluster-993929600.html

\uD83D\uDCCB Related articles

https://confluence.atlassian.com/adminjiraserver/set-up-a-jira-data-center-cluster-993929600.html