Hi,
I have a VPS on a FreeBSD 4.1 server w/Direct Admin
this week, on three seperate cases, I had my httpd service stop and I couldn't get it up again.
on the last time I had help from a friend, which I can't reach right now.
he told me he found out some other process is using the apache ports and he located it and killed it.
my questions are :
1. Does anyone know anything about this problem and why it occures ?
2. Is there a solution ?
3. How can I get the PID of the process holding the port ?
I tried :
210# netstat -na -S -f inet | grep .80 | grep LISTEN
tcp4 0 0 212.143.230.210.80 *.* LISTEN
this only gave me the fact that there is a process but not the PID, in my version of FreeBSD there seem to be no way for netstat to tell me what is the PID
I also tried:
210# sockstat -4l
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
but got an empty list...
please help
thank you.
I have a VPS on a FreeBSD 4.1 server w/Direct Admin
this week, on three seperate cases, I had my httpd service stop and I couldn't get it up again.
on the last time I had help from a friend, which I can't reach right now.
he told me he found out some other process is using the apache ports and he located it and killed it.
my questions are :
1. Does anyone know anything about this problem and why it occures ?
2. Is there a solution ?
3. How can I get the PID of the process holding the port ?
I tried :
210# netstat -na -S -f inet | grep .80 | grep LISTEN
tcp4 0 0 212.143.230.210.80 *.* LISTEN
this only gave me the fact that there is a process but not the PID, in my version of FreeBSD there seem to be no way for netstat to tell me what is the PID
I also tried:
210# sockstat -4l
USER COMMAND PID FD PROTO LOCAL ADDRESS FOREIGN ADDRESS
but got an empty list...
please help
thank you.