On 0, Holger Rauch <Holger.Rauch@heitec.de> wrote: [snip] > So I did a "netstat -avi | grep 443" but that yielded nothing. So there is > no program that opened a socket on port 443 as the apache-ssl logs > suggest. You seem to have made a couple of silly mistakes here. netstat's -i switch is documented as 'display interface table' which is not what you are trying to do. On my system: # netstat -avi Kernel Interface table Iface MTU Met RX-OK RX-ERR RX-DRP RX-OVR TX-OK TX-ERR TX-DRP TX-OVR Flg eth0 1500 022448895 0 0 0 2519734 0 0 0 BMRU lo 16436 0 711339 0 0 0 711339 0 0 0 LRU which is not what you are trying to grep. What you were trying to do is this: # netstat -a | grep 443 which also would not have worked, since you probably have 443 mapped to https in /etc/services. So what you really wanted was this: # netstat -a | grep https tcp 0 0 *:https *:* LISTEN is that what you were looking for? Even more likely what you wanted was this: # lsof -i | grep https apache-ss 444 root 16u IPv4 220292 TCP *:https (LISTEN) apache-ss 30808 root 16u IPv4 220292 TCP *:https (LISTEN) apache-ss 30809 root 16u IPv4 220292 TCP *:https (LISTEN) apache-ss 30810 root 16u IPv4 220292 TCP *:https (LISTEN) apache-ss 30811 root 16u IPv4 220292 TCP *:https (LISTEN) apache-ss 30812 root 16u IPv4 220292 TCP *:https (LISTEN) which tells me that I have apache-ssl listening on this port, but I suspect that it would tell you that you have something else listening... maybe apache was already configured to listen there? Tom -- Tom Cook Information Technology Services, The University of Adelaide "That you're not paranoid does not mean they're not out to get you." - Robert Waldner Get my GPG public key: https://pinky.its.adelaide.edu.au/tom.cook-at-adelaide.edu.au
Attachment:
pgpv7ptYDbpaN.pgp
Description: PGP signature