Glusterfs client starts binding from port number 1023 and if any port is not available, then tries to bind to the lower port. (i.e. suppose 1023 is not available because some other process is already using it, then it decrements the port to 1022 and tries to bind.) So in this case it has tried all the ports starting 1023 and found that those ports are not free (used by other processes) and found that port 80 is free and just did bind on it.
Regards, Raghavendra Bhat ----- Original Message ----- From: "Tomasz Chmielewski" <[email protected]> To: "Gluster General Discussion List" <[email protected]> Sent: Monday, June 4, 2012 7:02:55 AM Subject: [Gluster-users] why is glusterfs sometimes listening on port 80? I've noticed that I'm sometimes not able to start a webserver on machines running glusterfs. It turned out that glusterfs, when mounting, is sometimes starting to listen on port 80: root@ca11:~# netstat -tpna|grep :80 tcp 0 0 192.168.20.31:80 192.168.20.34:24010 ESTABLISHED 13843/glusterfs Why does glusterfs do it? Killing glusterfs and mounting again usually fixes the problem. -- Tomasz Chmielewski http://www.ptraveler.com _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users _______________________________________________ Gluster-users mailing list [email protected] http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
