Bug 165936

Summary: net-im/ejabberd fails when starting odbc.
Product: Ports & Packages Reporter: Andrey Shestakov <ornicum>
Component: Individual Port(s)Assignee: Ashish SHUKLA <ashish>
Status: Closed Feedback Timeout    
Severity: Affects Only Me CC: cs, miwi
Priority: Normal    
Version: Latest   
Hardware: Any   
OS: Any   

Description Andrey Shestakov 2012-03-11 16:40:04 UTC
Goof time of day!

I have installed erlang with odbc support and ejabberd from ports, erlang version is R14B04 and ejabberd version is 2.1.9. When I try to start it in ejabberd.log I see this:

=INFO REPORT==== 2012-03-11 22:43:23 ===
    application: ejabberd
    exited: {bad_return,
        {{ejabberd_app,start,[normal,[]]},
         {'EXIT',
          {noproc,
           {gen_server,call,
            [ejabberd_sup,
             {start_child,
              {'ejabberd_odbc_sup_<my.domain>',
               {ejabberd_odbc_sup,start_link,["<my.domain>"]},
               transient,infinity,supervisor,
               [ejabberd_odbc_sup]}},
             infinity]}}}}}
    type: temporary

And same error in erlang.log.
How can you see there is nothing error name, type of error only. I have searching any information about it. Developers of ejabberd answered that such behavior impossible because it was fixed in more earlier version. And on official site of ejabberd project written in "2.4.1  Requirements" section: "Erlang/OTP R10B-9 or higher. The recommended versions are R12B-5 and R13B04. Dont use R14A or R14B because they have a bug."

What can I do?

Regards,

Andrey Shestakov

How-To-Repeat: 1. Install erlang with odbc support.
2. Install ejabberd.
3. Install ejabberd module for postgresql.
4. My ejabberd.cfg.
override_acls.
{loglevel, 5}.
{hosts, ["<my.domain>"]}.
{listen,
 [
  {5222, ejabberd_c2s, [
   {access, c2s},
   {shaper, c2s_shaper},
   {max_stanza_size, 65536}
  ]},
  {5280, ejabberd_http, [
   captcha,
   http_bind,
   http_poll,
   web_admin
  ]}
 ]}.
{auth_method, odbc}.
{odbc_server, {pgsql, "localhost", "ejabberd", "ejabber", "password"}}.
{pgsql_users_number_estimate, true}.

all other options is in default value.

5. In /etc/rc.conf.
ejabberd_enable="YES"
ejabberd_node="<my0>@<my_domain>"

6. And now starting.
#/usr/local/etc/rc.d/ejabberd start
Comment 1 Edwin Groothuis freebsd_committer freebsd_triage 2012-03-12 00:51:20 UTC
Responsible Changed
From-To: freebsd-ports-bugs->ashish

Over to maintainer (via the GNATS Auto Assign Tool)
Comment 2 Ashish SHUKLA freebsd_committer freebsd_triage 2012-05-18 23:22:33 UTC
Hi,

I updated port net-im/ejabberd to 2.1.11. Could you please check if it solves
your problem?

Thanks
-- 
Ashish SHUKLA      | GPG: F682 CDCC 39DC 0FEA E116  20B6 C746 CFA9 E74F A4B0
freebsd.org!ashish | http://people.freebsd.org/~ashish/

Sent from my Emacs
Comment 3 Carlo Strub freebsd_committer freebsd_triage 2014-09-11 19:58:25 UTC
Is this PR still relevant?