Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I changed the ports in the listen section (just added a 1 in front of them) in the /etc/ejabberd/ejabberd.cfg, but after a

/etc/init.d/ejabberd restart

The server still listens on the original ports. Am I doing anything wrong here?

Also the server doesn't seem to start up when the firewawall-rules are set. How Is that possible given that the firewall rules affect only eth0, not localhost/127.0.0.1?

share|improve this question
1  
Can you confirm that ejabberd was actually restarted? You can do a ps auxw |grep ejabberd and find the appropriate beam process and see how long it has been running. – cjc Feb 2 '12 at 2:07
    
You are right .. simply calling /etc/init.d/ejabberd restart doesn't seem to restart it. Thanks! – Dexter Feb 2 '12 at 2:27

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.