Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ejabberd crashes with mod_http_upload enabled #1451

Closed
mbirth opened this issue Jan 7, 2017 · 5 comments
Closed

ejabberd crashes with mod_http_upload enabled #1451

mbirth opened this issue Jan 7, 2017 · 5 comments
Assignees

Comments

@mbirth
Copy link

mbirth commented Jan 7, 2017

What version of ejabberd are you using?

16.12-beta1 (from the official Docker image)

What operating system (version) are you using?

Whatever you used in that Docker image

How did you install ejabberd (source, package, distribution)?

Docker

What did not work as expected? Are there error messages in the log? What
was the unexpected behavior? What was the expected result?

As soon as I enable mod_http_upload in settings like this:

-
  port: 5280
  module: ejabberd_http
  ...
  request_handlers:
    "/oauth": ejabberd_oauth
    "/api": mod_http_api
    "/upload": mod_http_upload

....

  mod_http_upload:
    docroot: "/home/p1/cfg/upload"

ejabberd crashes on startup:

2017-01-07 20:24:35.458 [critical] <0.1003.0>@gen_mod:start_module:162 Problem starting the module mod_http_upload for host <<"localhost">>
 options: [{docroot,<<"/home/p1/cfg/upload">>}]
 error: undef
[{http_uri,parse,["http://localhost"],[]},
 {mod_http_upload,get_proc_name,2,
                  [{file,"src/mod_http_upload.erl"},{line,511}]},
 {mod_http_upload,start,2,[{file,"src/mod_http_upload.erl"},{line,148}]},
 {gen_mod,start_module,3,[{file,"src/gen_mod.erl"},{line,154}]},
 {lists,foreach,2,[{file,"lists.erl"},{line,1338}]},
 {ejabberd_app,start,2,[{file,"src/ejabberd_app.erl"},{line,77}]},
 {application_master,start_it_old,4,
                     [{file,"application_master.erl"},{line,273}]}]
2017-01-07 20:24:35.459 [critical] <0.1003.0>@gen_mod:maybe_halt_ejabberd:170 ejabberd initialization was aborted because a module start failed.

Setting put_url didn't make a difference.

@zinid
Copy link
Contributor

zinid commented Jan 7, 2017

This looks like an image issue. It doesn't include http_uri module or something.

@mbirth
Copy link
Author

mbirth commented Jan 7, 2017

The OS seems to be Alpine Linux (https://github.com/processone/docker-ejabberd), so the package would be erlang-inets - but it seems you didn't use Alpine's erlang packages but included erts-8.1 in that ejabberd.tar.gz that was installed to /home/p1/ejabberd.

@cromain cromain self-assigned this Jan 10, 2017
@cromain
Copy link
Contributor

cromain commented Jan 10, 2017

right, thanks pointing that out

@cromain cromain added this to the ejabberd 17.x milestone Jan 10, 2017
@cromain cromain modified the milestones: ejabberd 17.03, ejabberd 17.x Feb 28, 2017
@cromain
Copy link
Contributor

cromain commented Mar 23, 2017

fixed by e56c654
our official 17.03 docker images will be published after ejabberd release.

@cromain cromain closed this as completed Mar 23, 2017
@lock
Copy link

lock bot commented Jun 11, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Jun 11, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants