When I start a fresh copy of the Jabber server, it produces a string of warning messages: 20030322T13:06:11: [warn] (io_select): 127.0.0.1(22) is being connection rate limited 20030322T13:06:11: [warn] (io_select): 127.0.0.1(22) is being connection rate limited 20030322T13:06:11: [warn] (io_select): 127.0.0.1(22) is being connection rate limited The only way I have found to prevent these warnings from appearing is to change one of the lines in the multiple.xml file <rate points="10" time="25"/> - I replaced these values with bigger numbers. I am not exactly sure what each of these numbers signify anyway.
The problem I had was that the ebuild did not install a config file in the first place. I had to go into distfiles and fetch it manually. Even after that, the locations the files are installed to does not match the config file: Invalid Configuration in instance 'sessions': <load main='jsm'> <jsm>./jsm/jsm.so</jsm> <mod_echo>./jsm/jsm.so</mod_echo> <mod_roster>./jsm/jsm.so</mod_roster> <mod_time>./jsm/jsm.so</mod_time> <mod_vcard>./jsm/jsm.so</mod_vcard> <mod_last>./jsm/jsm.so</mod_last> <mod_version>./jsm/jsm.so</mod_version> <mod_announce>./jsm/jsm.so</mod_announce> <mod_agents>./jsm/jsm.so</mod_agents> <mod_browse>./jsm/jsm.so</mod_browse> <mod_admin>./jsm/jsm.so</mod_admin> <mod_filter>./jsm/jsm.so</mod_filter> <mod_offline>./jsm/jsm.so</mod_offline> <mod_presence>./jsm/jsm.so</mod_presence> <mod_auth_plain>./jsm/jsm.so</mod_auth_plain> <mod_auth_digest>./jsm/jsm.so</mod_auth_digest> <mod_auth_0k>./jsm/jsm.so</mod_auth_0k> <mod_log>./jsm/jsm.so</mod_log> <mod_register>./jsm/jsm.so</mod_register> <mod_xml>./jsm/jsm.so</mod_xml> </load> So it looks like you have to manually change every one of those lines. This could have been done better.
Okay. I'm new at this, but the way jabberd is set up to start through /etc/init.d/jabber doesn't make sense to me. With the help of the well done Jabberd admin guide at http://www.jabber.org/admin/adminguide.html , I was able to come out with a working basic jabberd server by: 1) pulling the default jabber.xml file out of distfiles/jabber-1.4.2.tar.gz 2) using sed to replace all instances of files referanced by "./path/filename" with the full paths to each file 2) starting up jabberd with the -c flag pointing at /etc/jabber.xml (same jabber.xml from above) 3) watching the errors, and one by one track down each instance of any other "./path/filename" and replace it with the full path the actual file 4) When the admin guide talks about creating a spool dir with the name of your server, make sure that the user AND group "jabber" can write to it, and also the directory below it. You'll need to restart your server after doing that. If you don't get this part right, it will complain about not being able to write. 5) enjoy I don't know how to maintain or create ebuilds, but a better way would have been to provide a jabber.xml modified the way I have done, with the directories set up as well as could be, and a notice at the end of building saying that the directory you create for you server files must be owned and rw / rwx to user jabber group jabber. It would also help if some docs were placed into /usr/doc or similar , or some man pages. I was unable to find ANY after the install. With such changes, installing and configuring jabberd on gentoo would become a much easier task.
To comment on the original bug. The reason for the bug is that the secret for muconference is different in multiple.xml and mctrans.xml. In multiple.xml: <service id="muclinker"> <host>conference.localhost</host> <accept> <ip>127.0.0.1</ip> <port>31518</port> <secret>mymucsecret</secret> </accept> </service> In muctrans.xml: <service id="muclinker"> <uplink/> <connect> <ip>127.0.0.1</ip> <port>31518</port> <secret>secret</secret> </connect> </service> changinc the <secret> tag so they are equal fixes the connection rate warning.
In the /etc/jabber/msntrans.xml file, please add the following: <servers> <ip>127.0.0.1</ip> </servers> Consider adding 'ip' tags for any other IPs you might use to connect the MSN transport to the Jabber server. Regarding some of the replies, please use '/etc/init.d/jabber start/stop/restart' to run your Jabber server. This will cause it to use the configuration file located in /etc/jabber/multiple.xml. The default muclinker secret will match in 1.4.2-r3.
