On 7/21/08, Gerfried Fuchs <[EMAIL PROTECTED]> wrote:
>
> The first linkes from the dump are:
>
> #v+
> =erl_crash_dump:0.1
> Mon Jul 21 10:43:25 2008
> Slogan: Kernel pid terminated (application_controller)
> ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})
> System version: Erlang (BEAM) emulator version 5.6.3 [source]
> [async-threads:0] [kernel-poll:true]
> Compiled: Wed Jun 18 07:45:21 2008
> Atoms: 4118
> #v-
It means that ejabberd failed to even start.
>
> > Also, could you try to start ejabberd attached to the terminal (just
> > run /usr/sbin/ejabberd as ejabberd user) and show the results (if
> > there's something interesting)?
>
> #v+
> [EMAIL PROTECTED]:~$ /usr/sbin/ejabberd
> Erlang (BEAM) emulator version 5.6.3 [source] [async-threads:0]
> [kernel-poll:false]
>
> Eshell V5.6.3 (abort with ^G)
> ([EMAIL PROTECTED])1>
> =INFO REPORT==== 21-Jul-2008::11:38:37 ===
> application: ejabberd
> exited: {bad_return,
> {{ejabberd_app,start,[normal,[]]},
> {'EXIT',
> {badarg,
> [{ejabberd_check,'-get_db_used/0-fun-0-',2},
> {ejabberd_check,get_db_used,0},
> {ejabberd_check,check_database_modules,0},
> {ejabberd_app,start,2},
> {application_master,start_it_old,4}]}}}}
> type: temporary
> #v-
It likely means that you have some invalid {odbc_server, ???} entry in
local_config table. Try to uncomment override_local directive in
ejabberd.cfg and start ejabberd again. If it will not work then I's
likely a bug in ejabberd_check module and I'll try to find it.
>
> > > -- System Information:
> > > Debian Release: lenny/sid
> > > APT prefers testing
> > > APT policy: (500, 'testing')
> > > Architecture: powerpc (ppc)
> >
> > It wouldn't be a big surprise to me if erlang odbc driver fails to
> > work on powerpc architecture. I bet it was never testing on it
> > thorouhly.
>
> That's a pitty then because that's the only way you offer it. Do you
> guess it might be an endianness bug? There are other architectures that
> would also be affected by that.
As far as I can see from your report there's still no evidence which
supports my words about odbc driver. I know definitely that it wasn't
working properly on amd64 before 12.b.3.
Another known issue with erlang odbc driver is a size restriction of
SQL queries. The maximum data size is 8000 bytes, which is
insufficient for vCard data for example.
>
> Could you maybe be so kind to offer the direct postgres modules instead
> of requiring people to use odbc for a workaround?
They aren't included in ejabberd souces by upstream, and I wouldn't
like to deviate from upstream source too much. But if someone will
create an additional package (is ejabberd-pgsql a good name for it?)
I'd be happy to sponsor it for example.
> P.S.: Interesting that your spam system tagged the bugreport as spam.
> Can you investigate what did that and maybe repair it? I am not so
> much worried about my own bugreports but maybe others that might end
> up in your spam box?
It only marks messages and doesn't delete them, so it's mostly harmless.
--
Sergei Golovan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
