powered by Jive Software

Running several WildFire servers on the same machine/OS

Hi All

I see that it is possible to say wich ports WildFire is to use for communications. Have anyone tried to run more that on WildFire server on the same machine (different users/ports)? Is it possible, or not recommended?

I could fiddle about and try, but if anyone know the answer …

-no-

Hi,

Yes it would be possible, but only if

  1. you have 2 completely separate installations (including separate databases)

  2. you change the xmpp ports from the defaults (plain/tls) (this can be done via system properties, I think

  3. you change the admin console port port/ss

  4. you have multihomed ip address h/w support, you will have to identify wildfire server by distinct ip or hostname.

Perhaps there are other conditions aswell. I guess in short it would be easier to have a second machine!.

Hope that helps,

Conor.

Hi,

it is possible but one should know what you want to do before one recommends to do this.

  1. you need an independent database (or one database with independent user schemas) and a separate wildfireHome for every instance you want to run. An easy way to do this is to install it two times like Conor did say.

2.*3.*4. You can either change all[/u] the ports (or disable some) like you did ask for or[/b] you can change the IP address Wildfire uses. (eg. 192.168.1.1 for installation one and 192.168.1.2 for installation two) without changeing the ports.

LG

I am also in the midst of doing this…

I will be starting with 5 different Wildfire servers running on the same OS,

I’‘m sure I’'ll be posting more questions over the next week. I will post my progress

Has anyone tried creating virtual IPs and having an instance of Wildfire running on each Virtual IP?

Is there a way to get Wildfire to NOT bind to 127.0.0.1?

Here is my second wildfire instance wildfire.xml

Where *.56 is an aliased IP (eth0:1)

If i goto 192.168.0.56:9090, I end up getting my first wildfire instance admin page

(192.168.0.55)

Has anyone tried creating virtual IPs and having an

instance of Wildfire running on each Virtual IP?[/i]

If you mean IP aliases, yes - actually it was 127.0.0.2 for some tests.

Is there a way to get Wildfire to NOT bind to

127.0.0.1?[/i]

Yes, you did give the example to do this below:

LG

If you pass in the network interface to find to, Wildfire should only bind to that network. If you’‘re having problems making that work, let us know and we’'ll look into it.

Thanks,

Matt

Ok, trying to get 2 wildfire instances running at the same time

and getting this error message in my error.log

org.jivesoftware.wildfire.container.AdminConsolePlugin.initializePlugin(AdminCon solePlugin.java:197) Trouble $

org.mortbay.util.MultiException[java.net.BindException: Address already in use, java.net.BindException: Address already in use]

There are multiple errors like this throughout the error log… one for each port it can’'t bind to I assume.

Here is my network setup

eth0 Link encap:Ethernet HWaddr 00:13:D4:88:44:CA

inet addr:172.23.230.133 Bcast:172.23.230.255 Mask:255.255.255.0

eth0:1 Link encap:Ethernet HWaddr 00:13:D4:88:44:CA

inet addr:172.23.230.134 Bcast:172.23.230.255 Mask:255.255.255.0

My first wildfire conf has

I also noticed in my Properties

1: IP:Port, Security: 127.0.0.1:5269, NORMAL

Domain Name(s): jtest1.njtech.com

even though i specified a 172.* address in my conf file…

any ideas?

Hi,

it seems that the file transfer proxy (port 7777) is ignoring the interface tag, try to run “netstat -an” to verify which ports Wildfire is using.

LG

For me it looks like this with :

$ netstat -an|grep -E ‘‘522|909|7777’’

tcp 0 0 0.0.0.0[/b]:7777 0.0.0.0:* LISTEN

tcp 0 0 127.0.0.1:9090 0.0.0.0:* LISTEN

tcp 0 0 127.0.0.1:9091 0.0.0.0:* LISTEN

tcp 0 0 127.0.0.1:5222 0.0.0.0:* LISTEN

tcp 0 0 127.0.0.1:5223 0.0.0.0:* LISTEN

ok, after rebooting my first Wildfire instance now shows the correct ip in the control panel

1: IP:Port, Security: 172.23.230.133:5269, NORMAL

Domain Name(s): jtest1.njtech.com

However it still seems to bind to all IPs

tcp 0 0 :::7777 :::* LISTEN

tcp 0 0 :::9090 :::* LISTEN

tcp 0 0 :::9091 :::* LISTEN

tcp 0 0 :::5222 :::* LISTEN

tcp 0 0 :::5223 :::* LISTEN

tcp 0 0 :::5269 :::* LISTEN

Hi,

did you remove section?

LG

Ok, I got it working, I am having the same problem you had as before though…

The File transfer port tries to bind to the local address

tcp 0 0 :::7777 :::* LISTEN

so there is a conflict when running more than one server

Hi,

so you may want to change the port within the web admin gui /file-transfer-proxy.jsp to 7778 or something else, then you should be able to run both servers.

Alex did write the file transfer proxy and will hopefully look into this, I did send him an IM.

LG

Hey Guys,

I created an issue to deal with this:

JM-721

I will check in the fix sometime today and it will be available in the nightly builds!

Thanks,

Alex