ypbind taking port of imaps on reboot. Please help guys~

ravangrid · 08-20-2009, 10:37 PM

Dear all,

Upon reboot, ypbind takes the port of imaps. Upon reboot, ypbind starts earlier than imaps. Sometimes ypbind takes 993 and sometimes 995, both cause problems for imaps to start on reboot. My system is RHEL 5. I need both the services to be ON. (I have many other services also running which should be ON, like vsftpd, sshd, nfs, cups, ntpd, httpd, etc. And, SE-Linux has to be in "enforcing" mode.)

I tried the following:

Code:

# service dovecot status

(its not running and stopped)

# netstat -tanp | grep 993
# netstat -tanp | grep 995

(these show that ypbind has taken either of these ports)

# service ypbind stop
# service dovecot start
# chkconfig dovecot on
# service ypbind start
# chkconfig ypbind on

(Now, dovecot first takes its appropriate port. Next, ypbind too takes its appropriate port.)

However, upon reboot, sometimes the problem appears again that imaps is not able to start because its ports is taken (mostly by ypbind).

Please help guys.

---------------------------------------------------------------------

jstephens84 · 08-20-2009, 10:45 PM

check you /etc/sysconfig/network and /etc/yp.conf and look to see what YP is binding to? You can also check the /var/log/dmesg log which could give you some more information about boot time.

chrism01 · 08-20-2009, 11:59 PM

Lock down the NIS ports; Section 5.3.4 http://www.linuxtopia.org/online_boo...#s1-server-nis

ravangrid · 08-24-2009, 09:37 PM

Dear Friends,

Thanks a lot for your help.
I am not proficient in port binding. So, I did the following:

# chkconfig ypbind off

and in /etc/rc.local file, I made this entry:

service ypbind start

So the service ypbind does not start upon reboot. Imaps starts earlier and takes appropriate port. Then ypbind starts at last.

Thanks to jstephens84 and chrism01.