Hello, today I came to my job and I noticed that apache is not running. When I tried to run it, I learned that port 80 uis already in use. Using netstat -aenpl I tried to learn wha proces is using port 80, but I only leatned this:
tcp 0 0 172.16.0.1:80 172.16.0.1:35664 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:43464 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:33764 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:51384 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:47699 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:47791 SYN_RECV 0 0 - tcp 0 0 my.pub.lic.ip:80 217.81.10.188:61300 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:45716 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:48526 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:45993 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:50785 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:55806 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:57663 SYN_RECV 0 0 - tcp 0 0 my.pub.lic.ip:80 66.249.72.5:50125 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:58561 SYN_RECV 0 0 - tcp 0 0 my.pub.lic.ip:80 217.81.10.188:61301 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:53022 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:55240 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:60697 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:52945 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:33246 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:47257 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:54033 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:55839 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:44242 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:51132 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:48444 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:53611 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:60368 SYN_RECV 0 0 - tcp 0 0 my.pub.lic.ip:80 217.81.10.188:61302 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:59879 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:59621 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:57013 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:40449 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:50700 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:60153 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:43080 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:41124 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:38234 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:57507 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:56755 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:42277 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:49429 SYN_RECV 0 0 - tcp 0 0 my.pub.lic.ip:80 217.81.10.188:61303 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:49392 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:43053 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:43267 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:46651 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:34273 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:36782 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:56613 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:35705 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:50500 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:36750 SYN_RECV 0 0 - tcp 0 0 my.pub.lic.ip:80 217.81.10.188:61298 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:56108 SYN_RECV 0 0 - tcp 0 0 172.16.0.1:80 172.16.0.1:33492 SYN_RECV 0 0 - tcp 0 0 my.pub.lic.ip:40732 194.228.32.13:80 TIME_WAIT 0 0 - It is possible to use shorewall to close these conections? I use apache2 2.0.54 fromdebian sarge a shorewall 3.0.5. Thanks for help. Jiri ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
