* Sergei Golovan <[EMAIL PROTECTED]> [2008-07-21 11:05:46 CEST]:
> On 7/21/08, Gerfried Fuchs <[EMAIL PROTECTED]> wrote:
> > I tried to use postgres through odbc. I did create the database tables
> > through the sql file available in the sources of ejabberd (would be nice
> > to have those in the binary package as example file, too).
>
> I'll add it to examples.
Thanks.
> > All I receive is an erl_crash.dump file in /var/log/ejabberd when I try
> > to start ejabberd after that. As that file isn't that small and I'm not
> > sure what it might contain I rather refrain from attaching it to the
> > bugreport - just give me a call if you could need it and you'll receive
> > it offsite.
>
> Could you show the first few lines of erl_crash.dump (a slogan could
> be helpful) and a content of /var/log/ejabberd/sasl.log and
> /var/log/ejabberd/ejabberd.log?
sasl.log and ejabberd.log only contains stuff from starting previous to
my changes to ejabberd.cfg.
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-
> 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-
> > -- 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.
Could you maybe be so kind to offer the direct postgres modules instead
of requiring people to use odbc for a workaround?
My jabber-ID is btw. [EMAIL PROTECTED] if you want to get in
more direct contact. That is running on a different system using a
different server so it's not affected by the problem. ;)
So long,
Rhonda
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?
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
