Differences

This shows you the differences between two versions of the page.

--- wiki:advanced:x2gobroker:loadbalancing [2013/07/02 01:10]
sunweaver [X2Go Session Broker Daemon / WSGI]
+++ wiki:advanced:x2gobroker:loadbalancing [2016/02/23 16:08]
ionic Fix <basepatch> typo and explain that <basepath> is typically empty.
@@ Line 47: / Line 47: @@
 <code bash>
-$ sudo x2gobroker-pubkeyauthorizer --broker-url http(s)://<broker-server>:<port>/<basepatch>/pubkeys/
+$ sudo x2gobroker-pubkeyauthorizer --broker-url http(s)://<broker-server>:<port>/<basepath>/pubkeys/
 </code>
+Note, that ''<basepath>'' typically is empty, unless the front- and backends were moved to a specific subdirectory as part of a WSGI deployment.
@@ Line 66: / Line 68: @@
 </file>
-It may happen that the broker contacts the X2Go servers under a different address compared to the address that the X2Go Clients have to use for connecting the X2Go Servers. For such cases, every hostname can be written in a special format (as seen in the example above):
+It may happen that the broker contacts the X2Go servers under a different address compared to the address that the X2Go Clients have to use for connecting the X2Go Servers. For such cases, every hostname can be written in a special format (as seen in the examples above and below):
 <file>
 host=s-1.works-with-broker.local (s-1.works-with-client.extern), s-2.works-with-broker.local (s-2.works-with-client.extern)
 </file>
+The hostnames (no IP addresses allowed here) that work with the broker should identically match the hostnames of the X2Go Servers as found in ''/etc/hostname'' of each individual machine. The hostname also appear in the output of the ''x2golistsessions'' command. It is important that hostname patterns (FQDN, short hostnames) match here!!!
+The hostnames (or maybe IP addresses) that work with the clients must resolve via DNS. IP addresses are allowed here.

X2Go - everywhere@home

User Tools

Site Tools

Differences

Page Tools