My goal is to migrate my jabberd 1.4 server. I'm running Red Hat 8.0.
My server is known as jabber.mydomain.com (obviously disguised). But the output of hostname -s is simply "oscar".
In ejabberd.cfg I have,
% Host name:
{hosts, ["jabber.mydomain.com"]}.
Furthermore I need to run muc under conference.mydomain.com, which I've configured as so:
{mod_muc, [{access, muc},
{access_create, muc},
{access_admin, muc_admin}'
{host,"conference.mydomain.com"}]},
Now I'm having problems starting ejabberd. I was able to do it once, but now I can't, and so I think I may be having a conflict with my hostname and node name.
Like other people, I'm not quite sure the best way of starting the server. Do I try
A) erl -pa /var/lib/ejabberd/ebin \
-sname ejabberd \
-s ejabberd \
-ejabberd config \"/etc/ejabberd/ejabberd.cfg\" \
log_path \"/var/log/ejabberd/ejabberd.log\" \
-sasl sasl_error_logger \{file,\"/var/log/ejabberd/sasl.log\"\} \
-mnesia dir \"/var/lib/ejabberd/spool\"
Should -sname be "ejabberd" or "oscar" or "jabber.mydomain.com" or "oscar.mydomain.com" ?
or B)
su ejabberd -c "erl -s ejabberd -name ejabberd
-ejabberd config '\"ejabberd.cfg\"' -detached"
Should this be -sname instead of -name? I am running this as user ejabberd, group jabber, by the way.
or C)
su ejabberd -c "ejabberdctl ejabberd@oscar start"
Re: Configuring hostname or node name
Now I'm having problems starting ejabberd. I was able to do it once, but now I can't
What problems? Any error report?
Working now
I have it working now.
Step 1) log into ejabberd account (home dir same as install dir)
Step 2) cd bin
Step 3) ./ejabberdctl start
my ejabberd.cfg file has
% Host name:
{hosts, ["jabber.mydomain.com"]}.
and
{mod_muc, [{access, muc},
{access_create, muc},
{access_admin, muc_admin},
{host, "conference.mydomain.com"}]},
One thing I noted that may have been causing some of my problems is that the 'stop' command does not kill all the processes. I still have one left over that I have to kill by hand:
ejabberd 1372 0.0 0.0 1820 624 ? S 16:19 0:00 /opt/ejabberd-1.0.0/bin/epmd -daemon
The problems I was experiencing initially was
A) ejabberd would appear to start, but not listen to any ports
B) would take a minute before the "ejabberd has been started on..." message appeared. The correct behavior had that message displaying within a second.