Hello everyone!
We are running an instant messaging network using ejabberd-2.0.0 installed from the installation binary.
Our issue is that Ad-hoc commands (such as the ability to announce to a group of users using mod_announce) do not show up as a command in the Pidgin menu for at least 20 minutes after logging in.
This happens with multiple users, on multiple machines.
I have the following ejabberd modules installed (copied from ejabberd.ctl. the ones commented out are inactivated):
{mod_adhoc, []},
{mod_announce,
{mod_caps, []},
{mod_configure,[]}, % requires mod_adhoc
{mod_disco, []},
%%{mod_echo, [
{mod_http_bind,[]},
%%{mod_http_fileserver,
{mod_irc, []},
{mod_last, []},
{mod_log_chat,
{mod_muc, } ]},
%%{mod_muc_log,[]},
{mod_offline, []},
{mod_privacy, []},
{mod_private, []},
%%{mod_proxy65,[]},
{mod_pubsub,
{mod_register, [
{mod_service_log,[]},
{mod_shared_roster,[]},
{mod_stats, []}
{mod_time, []}
{mod_vcard, []}
{mod_version, []}
Our jabber client that we are using to connect to the server is pidgin-2.3.1-1.fc8
The client computer is running Fedora 8 x86 kernel kernel-2.6.23.14-115.fc8
The jabber server is running Fedora 8 x86_64 kernel kernel-2.6.24.3-12.fc8
We have the following erlang-related packages installed according to rpm:
erlang-R12B-0.1.fc8
compat-erlang-R10B-11.9.fc8
Is anyone else having this issue? Can anyone shed some light onto fixing the issue?
Any help at all is greatly appreciated!
Thanks again,
apotrebka
I installed Pidgin 2.4.0
I installed Pidgin 2.4.0 (Debian package), and logged in an admin account in a local ejabberd 2.0.0 server.
I am curious: where should the ad-hoc commands appear? I waited 25 minutes, looked in all menus but didn't find anything about the announce commands: in Buddies, in Accounts->my account, Tools ... ?
Anyway, I don't understand how can such a strange problem happen; this is the first time I read about it.
You can also try other Jabber clients for administering the server: Psi, Tkabber or Gajim for example.
Offtopic: if you installed ejabberd using the binary installers from Process-one website, then you don't need to install Erlang/OTP because it is already included. Anyway, I think this isn't related to your problem.
Solution: proxy settings
Thank you badlop for your response, it is much appreciated.
I have come across a solution. I do not understand at this point how it is a solution, however, it is.
The solution is the set the Proxy Type under Proxy Options to No Proxy.
This option is found in Pidgin under Accounts>(username)>Edit Account>Advanced Tab
After changing this option, our ad-hoc commands appear almost instantly.