ejabberd - Comments for "Clustering over internet." https://www.ejabberd.im/node/1300 en Re: Clustering over internet. https://www.ejabberd.im/node/1300#comment-2948 <div class="quote-msg"> <div class="quote-author"><em>sarfaraz</em> wrote:</div> <p>Is it possible to cluster ejabberd running on different windows machine which is geographically separated but connected through internet.</p></div> <p>You can just use <noindex><a href="http://en.wikipedia.org/wiki/IP_Security" rel="nofollow" >IPsec</a></noindex>. This is the simplest solution of your problem.</p> Sat, 27 Jan 2007 06:05:52 +0000 xram@jabber.ru comment 2948 at https://www.ejabberd.im setcookie https://www.ejabberd.im/node/1300#comment-2899 <p>We will use .erlang.cookie, thank you.</p> Fri, 19 Jan 2007 08:05:56 +0000 Tarick comment 2899 at https://www.ejabberd.im setcookie https://www.ejabberd.im/node/1300#comment-2894 <div class="quote-msg"> <div class="quote-author"><em>Tarick</em> wrote:</div> <p>Is there any better way to do it right? Some caveats or advices? Howto or success story would be appreciated.</p></div> <p>I do not have any experience, though I've some advice: do not use the -setcookie option. It's dangereous: when someone has access to an account on your server, he can see the cookie using ps, and this is a security risk.</p> <p>--<br /> sander</p> Thu, 18 Jan 2007 19:31:24 +0000 sander comment 2894 at https://www.ejabberd.im When using clustered https://www.ejabberd.im/node/1300#comment-2893 <p>I'm deploying the same configuratioon and have some problems on which I'd like to get comments.</p> <p>Authentification, vcard storage, offline and roster were moved to Postgres DB with corresponding *_odbc modules, we want to move to Postgres as much as possible as this info will be used on web pages and to avoid problems with mnesia in future.<br /> Nodes started with:<br /> Node 1) erl -pa /usr/local/ejabberd/var/lib/ejabberd/ebin -name <noindex><a href="mailto:ejabberd@node1.domain.com" rel="nofollow" >ejabberd@node1.domain.com</a></noindex> -s ejabberd -ejabberd config \"/usr/local/ejabberd/etc/ejabberd/ejabberd.cfg\" log_path \"/usr/local/ejabberd/var/log/ejabberd/ejabberd.log\" -sasl sasl_error_logger \{file,\"/usr/local/ejabberd/var/log/ejabberd/sasl.log\"\} -mnesia dir \"/usr/local/ejabberd/var/lib/ejabberd/spool\" -setcookie XWDMRXPCDJPLPKZIEWJJ</p> <p>Node 2) erl -setcookie XWDMRXPCDJPLPKZIEWJJ -pa /usr/local/ejabberd/var/lib/ejabberd/ebin -nam<br /> e <noindex><a href="mailto:ejabberd1@node2.domain.com" rel="nofollow" >ejabberd1@node2.domain.com</a></noindex> -s ejabberd -ejabberd config \"/usr/local/ejabberd/etc/ejab<br /> berd/ejabberd.cfg\" log_path \"/usr/local/ejabberd/var/log/ejabberd/ejabberd.log\" -sas<br /> l sasl_error_logger \{file,\"/usr/local/ejabberd/var/log/ejabberd/sasl.log\"\} -mnesia<br /> dir \"/usr/local/ejabberd/var/lib/ejabberd/spool\" extra_db_nodes "['ejabberd@node1.domain.com']"</p> <p>Nodes are connected and pinged succesfully, on Node2 mnesia tables are set to ram+disk or ram (none of them is remote in admin db web-page).<br /> What I want is jabber serving one domain with users connected to differen nodes and consistent user namespace. Plus, conference service should run on each of them (with different DNS-names as clustering of muc is not possible in ejabber yet).<br /> So, I guess I must setup Postgres DB replication of some tables (at least users, vcard and roster) between this nodes, because contact presence works only with mod_roster but not with mod_roster_odbc, users with the same names can be created on differents nodes (tkabber tries to kill another session though) and foreign vcard is not found.</p> <p>Also, each node doesn't start if other is offline.</p> <p>Is there any better way to do it right? Some caveats or advices? Howto or success story would be appreciated.</p> Thu, 18 Jan 2007 16:07:08 +0000 Tarick comment 2893 at https://www.ejabberd.im When using clustered https://www.ejabberd.im/node/1300#comment-2892 <p>When using clustered ejabberd, reliability of the link between nodes is more important then the reliability of a node. Every time the link breaks you will end up with inconsistent database, and will have to repair it by hands.</p> Wed, 17 Jan 2007 18:30:10 +0000 teo comment 2892 at https://www.ejabberd.im