Topic: ejabberd and iRedAPD port conflict

Version: iRedMail 0.7.3 fresh install
OS: Ubuntu 10.04
Host: Amazon EC2

I've installed iRedMail (OpenLDAP backend) with ejabberd integration and run into this same problem twice. The port that iRedAPD uses is 7777 which is also the default port for ejabberd. See below:

root@ip-10-2-1-10:~# tail /var/log/ejabberd/ejabberd.log

=ERROR REPORT==== 2011-09-25 07:55:11 ===
E(<0.314.0>:ejabberd_listener:463) : Failed to open socket:
Reason: IP address and port number already used: 7777

root@ip-10-2-1-10:~# grep 7777 /opt/iredapd/etc/iredapd.ini
listen_port = 7777
root@ip-10-2-1-10:~# grep 7777 /etc/postfix/*
/etc/postfix/main.cf:smtpd_recipient_restrictions = reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unlisted_recipient, check_policy_service inet:, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination, reject_non_fqdn_helo_hostname, reject_invalid_helo_hostname, check_policy_service inet:

When I change the port in main.cf and iredapd.ini and restart everything then ejabberd starts normally.

Please change the default port in iRedMail for this service so it doesn't conflict in future installs.


==== Provide basic information to help troubleshoot ====
- iRedMail version:
- Linux/BSD distribution name and version:
- Any related log? Log is helpful for troubleshooting.


Get fast and professional support from iRedMail developers:


Re: ejabberd and iRedAPD port conflict

Thanks for your feedback, will fix it in next release. smile


Does my reply help a little? How about buying me a cup of coffee ($5) as an encouragement?

buy me a cup of coffee