Registered users, logfiles and some other questions

I am using ejabberd-0.7.5 with the CVS version of JWChat. It was remarkably easy to install, and seems far more stable than jabberd-1.4. I have a few remaining questions on how to configure the services, though.

I don't want just anybody to register as a user. How do I turn off the auto-register functionality? What I would really like is to have a user request an ID, but require an admin to approve it before the ID is actually created. Is this possible?

The logfiles are incredibly verbose. How do I control the verbosity?

I have set the host parameter to the machine's FQDN ( jabber.foo.com, for example ). I was a little surprised when I ran ejabberdctl ejabberd@jabber.foo.com status and was told:
Can't get node 'ejabberd@jabber.foo.com' status: nodedown

=ERROR REPORT==== 9-Apr-2005::12:15:21 ===
** System NOT running to use fully qualified hostnames **
** Hostname jabber.foo.com is illegal **
What is this error message really trying to tell me?

Thanks for any help you can provide.

Mik

config

To turn off the auto-register functionality check ejabber.cfg for the mod_register section. You can prevent registrations of certain usernames, but I'm not sure if there is any ability to manually "vet" them.

As for the FQDN problem, how did you start ejabberd? Did you use:-

erl -pa /var/lib/ejabberd/ebin -name ejabberd -s ejabberd

As I believe that would be the correct way to do it if your hostname is externally resolvable.

I am also havin this

I start ejabberd with:

erl -pa /var/lib/ejabberd/ebin -sname ejabberd -s ejabberd -ejabberd config \"/etc/ejabberd/ejabberd.cfg\"

...and get some progress reports in the shell ending with:

application: ejabberd
started at: ejabberd@USBOU1-DADAUGHT2 (that is the hostname...)

when I then try to use ejabberdctl I type the command:

ejabberdctl ejabberd@USBOU1-DADAUGHT2 status (or any other argument like register...) and I get this error:

Cant get node ejabberd@USBOU1-DADAUGHT2 status: nodedown.

What can I do to rectify this issue?

Syndicate content