Jeff Carreon <[EMAIL PROTECTED]> wrote:
> Thanks! I've passed that obstacle, but I've stumbled upon another
> oddity, though. This is part of the output of the bootstrap command.
>
> *** Creating tables on this Mnesia node ('[EMAIL PROTECTED]')
...
> Bootstrapping complete.
>
>
> When I start incomingproxy again, this error appears:
>
> 2006-10-09 16:00:02.871 error<0.61.0>:Startup problem: Mnesia table
> 'user' does not exist - did you bootstrap Yxa? (see README file)
>
> I checked the database directory, and see the file user.DCD among
> them, so it couldn't have been missing. Should I use a custom
> bootstrap configuration file?
> Thanks again.
It's more of the same problem actually. When you start the incomingproxy
node, it's node name is not '[EMAIL PROTECTED]'. I don't know what
it is, but it is not the one you bootstrapped with. The Mnesia database
files created by the bootstrap contains the name you set, but since that
name does not match the name Erlang decides to use for your
incomingproxy node, the Mnesia database on disk is ignored.
Perhaps the node name is printed somewhere if you start the
incomingproxy node in debug mode :
$ ./incomingproxy -d
If it is not, then I think the easiest way to figure out what name
Erlang uses for your incomingproxy node is to add a log command. If you
look in sipserver.erl, around line 240 you will see the call to
logger:log that results in the log entry you saw. Add this on the line
before that call :
logger:log(error, "This nodes name is '~p'", [node()]),
recompile and try again. Then you should be able to see the node name in
your logfile. You the bootstrap again with the node name of the
incomingproxy as -name.
/Fredrik
_______________________________________________
Yxa-devel mailing list
[email protected]
https://lists.su.se/mailman/listinfo/yxa-devel
