Hi,
I have just installed ejabberd-2.0.0 on a debian ("testing") machine with MySQL as backend. Registering a user at the server works fine. But when I try to register a further user I get the following error message:
The server definitely has enough resources to handle two users ... :) Any ideas?
Thanks in advance.
Matthias Stiller
Erm ... this is the error
Erm ... this is the error message I get:
<error code='500' type='wait'><resource-constraint xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error>It always happens after one registration. Ideas?
Bye.
Are you using ejabberd 2.0.0
Are you using ejabberd 2.0.0 source package, or ejabberd from 2.0.x SVN branch?
In ejabberd 2.0.x (the incoming 2.0.1 and newer ones), there is a new feature that restricts account registrations by a specific IP to 1 registration every 10 minutes.
Any solutions?
Were you able to turn this feature off or is there a way to exclude specific IP addresses from the 1/10 minute limit?
All of my registrations will happen through my website - it's a social networking site and every person who registers will receive an account so I will need to register far more than 1/10 minutes ... and all registrations will come from the same ip address - the ip of the server.
Try the option {registration_timeout, Timeout} in ejabberd.cfg
Were you able to turn this feature off or is there a way to exclude specific IP addresses from the 1/10 minute limit?
Yes, the documentation of mod_register has been recently updated with this explanation:
This module reads also another option defined globably for the server: {registration_timeout, Timeout}. This option limits the frequency of registration from a given IP or username. So, a user can’t register a new account from the same IP address or JID during this number of seconds after previous registration. Timeout is expressed in seconds, and must be an integer. To disable this limitation, instead of an integer put a word like: infinity. Default value: 600 seconds.
{registration_timeout, Timeout}
Thanks for the tip badlop I think that option is exactly what I'm looking for but when I put that option into my config file the server refuses to start whether I put "infinity" or an integer (like 600)
I'm running ejabberd version 2.0.1
Here's what's in my sasl.log file
=CRASH REPORT==== 2-Jun-2008::08:21:57 ===
crasher:
pid: <0.2438.0>
registered_name: []
error_info: {bad_return,{{ejabberd_app,start,[normal,[]]},
{'EXIT',[47,
47,
101,
116,
99,
47,
101,
106,
97,
98,
98,
101,
114,
100,
47,
101,
106,
97,
98,
98,
101,
114,
100,
46,
99,
102,
103,
58,
32,
"514",
58,
32,
"premature end"]}}}
initial_call: {application_master,init,
[<0.2409.0>,
<0.2437.0>,
{appl_data,
ejabberd,
[ejabberd,
ejabberd_sup,
ejabberd_auth,
ejabberd_router,
ejabberd_sm,
ejabberd_s2s,
ejabberd_local,
ejabberd_listeners,
ejabberd_iq_sup,
ejabberd_service_sup,
ejabberd_s2s_out_sup,
ejabberd_s2s_in_sup,
ejabberd_c2s_sup,
ejabberd_mod_roster,
ejabberd_mod_echo,
ejabberd_mod_pubsub,
ejabberd_mod_irc,
ejabberd_mod_muc,
ejabberd_offline,
random_generator],
undefined,
{ejabberd_app,[]},
[acl,
adhoc,
configure,
cyrsasl_anonymous,
cyrsasl,
cyrsasl_digest,
cyrsasl_plain,
ejabberd_admin,
ejabberd_app,
ejabberd_auth_anonymous,
ejabberd_auth,
ejabberd_auth_external,
ejabberd_auth_internal,
ejabberd_auth_ldap,
ejabberd_auth_odbc,
ejabberd_auth_pam,
ejabberd,
ejabberd_c2s,
ejabberd_c2s_config,
ejabberd_config,
ejabberd_ctl,
ejabberd_frontend_socket,
ejabberd_hooks,
ejabberd_http,
ejabberd_http_bind,
ejabberd_http_poll,
ejabberd_listener,
ejabberd_local,
ejabberd_logger_h,
ejabberd_loglevel,
ejabberd_node_groups,
ejabberd_rdbms,
ejabberd_receiver,
ejabberd_router,
ejabberd_s2s,
ejabberd_s2s_in,
ejabberd_s2s_out,
ejabberd_service,
ejabberd_sm,
ejabberd_socket,
ejabberd_sup,
ejabberd_system_monitor,
ejabberd_tmp_sup,
ejabberd_update,
ejabberd_web_admin,
ejabberd_web,
ejabberd_zlib,
ejd2odbc,
eldap,
eldap_filter,
eldap_pool,
eldap_utils,
'ELDAPv3',
extauth,
gen_iq_handler,
gen_mod,
gen_pubsub_node,
gen_pubsub_nodetree,
iconv,
idna,
jd2ejd,
jlib,
mod_adhoc,
mod_announce,
mod_caps,
mod_configure2,
mod_configure,
mod_disco,
mod_echo,
mod_http_bind,
mod_http_fileserver,
mod_irc,
mod_irc_connection,
mod_last,
mod_last_odbc,
mod_muc,
mod_muc_log,
mod_muc_room,
mod_offline,
mod_offline_odbc,
mod_privacy,
mod_privacy_odbc,
mod_private,
mod_private_odbc,
mod_proxy65,
mod_proxy65_lib,
mod_proxy65_service,
mod_proxy65_sm,
mod_proxy65_stream,
mod_pubsub,
mod_register,
mod_roster,
mod_roster_odbc,
mod_service_log,
mod_shared_roster,
mod_stats,
mod_time,
mod_vcard,
mod_vcard_ldap,
mod_vcard_odbc,
mod_version,
node_buddy,
node_club,
node_default,
node_dispatch,
node_pep,
node_private,
node_public,
nodetree_default,
nodetree_virtual,
p1_fsm,
p1_mnesia,
ram_file_io_server,
randoms,
sha,
shaper,
stringprep,
stringprep_sup,
tls,
translate,
xml,
xml_stream,
'XmppAddr'],
[],
infinity,
infinity},
normal]}
ancestors: [<0.2437.0>]
messages: []
links: [<0.2437.0>,<0.2439.0>,<0.2409.0>]
dictionary: []
trap_exit: true
status: running
heap_size: 987
stack_size: 21
reductions: 118
neighbours:
Disregard previous comment, it works!
It works fine!
I forgot to add the period after the config option :P
Thanks for your help