ejabberd - Comments for "mod_http_fileserver crash aften first view page"

i'm enable module in config,

evadim — Fri, 26 Sep 2008 19:23:01 +0000

i'm enable module in config, after we migrate to ejabberd 2.0.0
int work & work & work... but after i upgrade to 2.0.2 it crash.

install - gentoo linux, Erlang/OTP R12B-3.

i'm try view logs

Another possibility

mfoss — Fri, 26 Sep 2008 10:02:21 +0000

The error means that the ETS table with the module configuration cannot be read because it doesn't exist. That table doesn't exist because the module is not running: either it was not enabled (you have explained that you enabled it correctly), or it crashed previously (maybe a bug in the module code).

Maybe this is what happens in your case?

You enable the module correctly in ejabberd.cfg
Start ejabberd correctly
You browse a file correctly
Then, for some reason (a bug?), mod_http_fileserver crashes. The table is automatically deleted.
When you request another object, ejabberd complains with the error messages you showed: the table doesn't exist.

Can you check if there is any error message (in ejabberd.log or sasl.log) before the two error messages you showed? Maybe the reason of the real crash is reported before.

I tried with ejabberd 2.0.2 (compiled from official source code package) with Erlang/OTP R12B-3 and with the configuration you showed, and I don't see the problem. How did you install ejabberd: binary installer in linux, or windows, or some OS package...?

BTW, do you enable the module using ejabberd.cfg, or in Web Admin?

all configured

evadim — Thu, 25 Sep 2008 05:09:23 +0000

module configured correctly, and in ejabberd 2.0.0 & 2.0.1 works fine.
Now, i can view only one page - after i open page in browser - module crash in few seconds with message i posted above.
my settings:

in listen section

  {5280, ejabberd_http, [
                         http_poll,
                        {request_handlers, [
                                            {["pub", "archive"], mod_http_fileserver}
                                          ]
                         }
                        ]},

in modules section

  {mod_http_fileserver, [
                    {docroot, "/var/www/jabber.example.com/htdocs"},
                    {accesslog, "/var/log/jabber/muc-access.log"}
                    ]
  },

Make sure the module is enabled before requesting an URL

mfoss — Wed, 24 Sep 2008 22:11:11 +0000

You defined the request_handlers in the 'listen' section of ejabberdl.cfg

But are you sure you also enabled mod_http_fileserver in the 'modules' section?

Remember that you need to enable the module, for example:

{modules,
 [
  ...
  {mod_http_fileserver, [
                         {docroot, "/var/www"}, 
                         {accesslog, "/var/log/ejabberd/access.log"}
                        ]
  },
  ...
]}.

In the Web Admin, is the module shown before you try to browse pub/archive ?

When you fix this problem, you will probably notice that mod_http_fileserver does not list content of directories: you need to provide the exact name of files.