On 7/29/08, Michael Flaig <[EMAIL PROTECTED]> wrote: > > > I am seeing a problem with ejabberd rpc on lenny. > > > First problem comes up on install (tried with real machine name > "srv-2000" and localhost) > > > > These problems likely comes from incorrectly (from the Erlang point of > > view) networking setup. So, I think it isn't an ejabberd bug (and at > > least its severity is far from grave). > > > could you elaborate a little bit on what you mean by "Erlang point of > view"?
At least the network setum must allow connections to `hostname -s`. > > > > Could you show a last few lines of /var/log/ejabberd/sasl.log after > > ejabberd start? > > > all logs right after install attached > however I don't see any indication to a failure ... > Yes. sasl.log and ejabberd.log are good. But ps_afterinstall.txt is awful. There should be exactly one epmd instance. Could you upgrade erlang-base and erlang-nox from http://ftp.de.debian.org/debian/pool/main/e/erlang/, kill all epmd processes and install ejabberd again? Also, I'd like to see all messages from epmd in /var/log/syslog. And before upgrading erlang packages, please, kill ejabberd, epmd and start epmd -daemon (in command prompt). Will it start multiple epmd processes? If not, start it again. Will it start the second epmd process or just finish? Cheers! -- Sergei Golovan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
