ejabberd - Comments for "Little Tricks"

start will not recall??

pernghh — Tue, 20 Mar 2018 02:54:01 +0000

Hi I try the reload module function. I found that new function did work! But the module's load function doesn't re-call the start_link, start and init function. Due to there are some options inside the ejabberd.yml that I need to initial the module. Should I do something more to reload all module's option back? Or it just add it supervisor & init automatically?

Thank you~~

Changing loglevel without restart

wiro — Tue, 05 May 2015 22:39:36 +0000

If you need change loglevel for debug purposes without restart you can use ejabberdctl debug console.

For getting information about loglevel

(ejabberd@utopia)1> ejabberd_logger:get().
{3,warning,"Warning"}

For setting loglevel

(ejabberd@utopia)2> ejabberd_logger:set(4).
{module,lager}

Use ejabberdctl debug to debug Already Running ejabberd Process

alsuren — Mon, 04 Feb 2013 19:40:13 +0000

I can't find an "edit" button for this page, but:

Attach an Erlang Shell to an Already Running ejabberd Process

I couldn't get the suggested erl invocation to work, but I had success with the following command:

$ sudo ejabberdctl debug
--------------------------------------------------------------------

IMPORTANT: we will attempt to attach an INTERACTIVE shell
to an already running ejabberd node.
If an ERROR is printed, it means the connection was not successful.
You can interact with the ejabberd node if you know how to use it.
Please be extremely cautious with your actions,
and exit immediately if you are not completely sure.

To detach this shell from ejabberd, press:
  control+c, control+c

--------------------------------------------------------------------
To bypass permanently this warning, add to ejabberdctl.cfg the line:
  EJABBERD_BYPASS_WARNINGS=true
Press any key to continue

Erlang R14A (erts-5.8) [source] [64-bit] [smp:2:2] [rq:2] [async-threads:0] [kernel-poll:true]

Eshell V5.8  (abort with ^G)
(ejabberd@hostname)1>

ejabberd user or erlang cookie

gvy — Mon, 07 Feb 2011 17:23:42 +0000

If a user attaching the shell differs from a user ejabberd is running as, -setcookie might be needed:

erl -sname node1 -setcookie $(cat /var/lib/ejabberd/.erlang.cookie) -remsh node2@machine2.example.org

When using the eJabberd Web interface

vbarat — Fri, 16 Jan 2009 09:16:56 +0000

When using the eJabberd Web interface, restarting a module do not reload the new code (it only reloads the currently loaded module). Thus, to install a new freshly compiled version of a module, install it manually in eJabberd's ebin directory, use the Erlang console to reload it (i.e. by typing l(mod_version).) and use the Web console to restart the module.

On the reloading of modules

Sean — Thu, 06 Mar 2008 19:36:01 +0000

Note: c(mod_version). will reload the module, but will not call start/2 or stop/2. If you change your module's hooks, you'll need to do the following:

Remove the beam file. Mine was located in /var/lib/ejabberd/ebin/mod_version.beam
cd to the src directory
Relaunch ejabberd

Changes to any other function will get picked up if you run mod_version, so in practice this isn't a very big deal, but know this quirk exists.