By: Doug Huang user 05 Feb 2018 at 4:34 p.m. CST

14 Responses
Doug Huang gravatar

I just installed 3.1.2 and want to config cluster.

The instruction have code as following:

scp /opt/gluu-server-3.1.2/install/community-edition-setup/setup.properties.last root@idp2.example.org:/opt/gluu-server-3.1.2/install/community-edition-setup/setup.propertie

However, I don't see setup.properties.last in /opt/gluu-server-3.1.2/install/community-edition-setup/ folder.

[root@ip-172-31-10-12 ~]# cd /opt/gluu-server-3.1.2/
[root@ip-172-31-10-12 gluu-server-3.1.2]# cd install/
[root@ip-172-31-10-12 install]# ls
community-edition-setup
[root@ip-172-31-10-12 install]# cd community-edition-setup/
[root@ip-172-31-10-12 community-edition-setup]# ls -l
total 200
-rw-r--r--.  1 root root  13662 Jan 18 09:11 ldif.py
-rw-r--r--.  1 root root   1071 Jan 18 09:11 LICENSE
drwxr-xr-x.  2 root root     98 Feb  5 21:40 openldap_migration
drwxr-xr-x.  2 root root     20 Feb  5 21:40 output
-rw-r--r--.  1 root root  10045 Jan 18 09:11 Properties.py
-rw-r--r--.  1 root root    149 Jan 18 09:11 README.md
-rw-r--r--.  1 root root     63 Jan 18 09:11 requirements.txt
drwxr-xr-x.  2 root root    135 Feb  5 21:40 schema
-rw-r--r--.  1 root root   1600 Jan 18 09:11 setup.properties.sample
-rwxr-xr-x.  1 root root 151844 Jan 18 09:11 setup.py
drwxr-xr-x. 12 root root    155 Feb  5 21:40 static
drwxr-xr-x.  5 root root   4096 Feb  5 21:40 templates
drwxr-xr-x.  2 root root    165 Feb  5 21:40 tests
[root@ip-172-31-10-12 community-edition-setup]# 

Is the file missing?

By Chris Blanton staff 07 Feb 2018 at 9:33 a.m. CST

Chris Blanton gravatar

It doesn't look like you have a setup.log either. Have you run setup.py yet?

By Doug Huang user 07 Feb 2018 at 3:18 p.m. CST

Doug Huang gravatar

There is specific instruction as following.

Now for the rest of the servers in the cluster, download the Gluu packages but don't run setup.py yet.

Before following command:

scp /opt/gluu-server-3.1.2/install/community-edition-setup/setup.properties.last root@idp2.example.org:/opt/gluu-server-3.1.2/install/community-edition-setup/setup.propertie

So, I have not run setup.py.

By Chris Blanton staff 07 Feb 2018 at 3:23 p.m. CST

Chris Blanton gravatar

I think maybe that portion of my instructions is misleading:

Now for the rest of the servers in the cluster..

My intention is that the first server is installed, by following the hyperlink header:

https://gluu.org/docs/ce/3.1.2/installation-guide/cluster/#1-install-gluu

I'll change that to a normal header and adjust the instructions to make sure you install the first server, then continue the instructions.

By Chris Blanton staff 08 Feb 2018 at 10:36 a.m. CST

Chris Blanton gravatar

Doug,

Did that work for you?

By Doug Huang user 08 Feb 2018 at 7:37 p.m. CST

Doug Huang gravatar

I install 3.1.2, however, after login I no longer find /install

root@ip-172-31-21-21 ~]# ls /opt
gluu-server-3.1.2
[root@ip-172-31-21-21 ~]# ls /opt/gluu-server-3.1.2/
bin   dev  home     lib    media  opt   root  sbin  sys  usr
boot  etc  install  lib64  mnt    proc  run   srv   tmp  var
[root@ip-172-31-21-21 ~]# /sbin/gluu-serverd-3.1.2 enable
Created symlink from /etc/systemd/system/machines.target.wants/systemd-nspawn@gluu_server_3.1.2.service to /usr/lib/systemd/system/systemd-nspawn@gluu_server_3.1.2.service.
[root@ip-172-31-21-21 ~]# /sbin/gluu-serverd-3.1.2 start
[root@ip-172-31-21-21 ~]# /sbin/gluu-serverd-3.1.2 login
[root@ip-172-31-21-21 ~]# ls /
bin   data  etc   lib    media  opt   root  sbin  sys  usr
boot  dev   home  lib64  mnt    proc  run   srv   tmp  var

By Doug Huang user 09 Feb 2018 at 12:01 p.m. CST

Doug Huang gravatar

I start from scratch and re-do the installation process. Here are I have done:

  1. on idp1.example.com, I have finished setup.py and I have setup.properties.last generated and I scp to idp2.example.com as setup.properties.

  2. on idp2.example.com I modify the ip as the instruction said. Then run ./setup.py. AS the instruction said:

The rest of the configurations for the install should be automatically loaded and all you need to do here is press Enter

I hit enter and the installation run successfully. Then screen display:

Gluu Server installation successful! Point your browser to https://idp1.example.com

Then I think there may have something wrong about the instruction.

I think we should modify hostname as well for setup.properties.

Please clerify.

By Chris Blanton staff 09 Feb 2018 at 12:04 p.m. CST

Chris Blanton gravatar

This part of the documentation is important:

Warning

Make sure to use a separate NGINX/Load-balancing server FQDN as hostname. 

You're using idp1.example.com as your hostname as opposed to loadbalancer.example.com, which will be the load balancing/proxy server.

By Chris Blanton staff 09 Feb 2018 at 12:16 p.m. CST

Chris Blanton gravatar

So the manual configuration can be somewhat cumbersome. If you'd like an easier method, we currently have an automated tool for configuring, monitoring and installing clusters. It's under the Gluu Support License, but since it's in Beta, we would appreciate some feedback. The license will possibly be enforced at a later time.

Here are the docs for installation and configuration.

By Doug Huang user 09 Feb 2018 at 10:10 p.m. CST

Doug Huang gravatar

I am at "2. Enable Replication" section and on first server execute following command:

/opt/opendj/bin/dsreplication enable --host1 gluu-idp1.example.org --port1 4444 --bindDN1 "cn=directory manager" --bindPassword1 <password> --replicationPort1 8989 --host2 gluu-idp2.example.org --port2 4444 --bindDN2 "cn=directory manager" --bindPassword2 <password> --replicationPort2 8989 --adminUID admin --adminPassword 
 <password> --baseDN "o=gluu" -X -n
Establishing connections ..... 
The provided credentials are not valid in server
gluu-idp1.example.org:4444.  Details: [LDAP: error code 49 - Invalid
Credentials]

The provided credentials are not valid in server
gluu-idp2.example.org:4444.  Details: [LDAP: error code 49 - Invalid
Credentials]
-bash-4.2# 

I think I am not very clear about following statement:

All <password>'s should be changed to the same password.

Above command I use same value for <password>, and got that error. Am I missing anything, please advise.

By Chris Blanton staff 10 Feb 2018 at 1:56 a.m. CST

Chris Blanton gravatar

<password> here should be your OpenDJ LDAP password you assigned during installation with setup.py

By Doug Huang user 10 Feb 2018 at 8:59 a.m. CST

Doug Huang gravatar

It works now if I use the LDAP password I was assigned during installation with setup.py. However, I can not find the log file.


See /tmp/opendj-replication-2490068697533956206.log for a detailed log of this
operation.

-bash-4.2# 
-bash-4.2# ls /tmp
hsperfdata_jetty
hsperfdata_ldap
hsperfdata_root
opendj-replication-3661599299199184270.log
opendj-replication-851731409032819475.log
opendj-setup-4134152561402396668.log
System1784191353455345895.properties
systemd-private-479a5ef695f14a3781d533859f60b4ae-httpd.service-PkH8TF
-bash-4.2# ls -lt /tmp/open*
-rw-r--r--. 1 root root 6959 Feb 10 14:29 /tmp/opendj-setup-4134152561402396668.log
-rw-r--r--. 1 root root  488 Feb 10 14:25 /tmp/opendj-replication-3661599299199184270.log
-rw-r--r--. 1 root root 1118 Feb 10 03:53 /tmp/opendj-replication-851731409032819475.log

It happens to "/opt/opendj/bin/dsreplication initialize", I can't find the log file either.

Although both enable and initialize run successfully.

By Doug Huang user 10 Feb 2018 at 12:48 p.m. CST

Doug Huang gravatar

Another installation question:

install csync2

Should it run after chroot or outside chroot container. The instruction is not clear.

By Chris Blanton staff 12 Feb 2018 at 11:33 a.m. CST

Chris Blanton gravatar

Doug,

You can install csync2 inside or outside of the chroot, as long as the directory paths to be replicated are correct.

By Chris Blanton staff 13 Feb 2018 at 9:51 a.m. CST

Chris Blanton gravatar
It happens to "/opt/opendj/bin/dsreplication initialize", I can't find the log file either.

Although both enable and initialize run successfully.

I'm not sure where the log file for the replication is saved, it's probably not properly named and is one of those other files in there.

For future reference, the openDJ logs are located at /opt/opendj/logs/