https://bugzilla.novell.com/show_bug.cgi?id=388088
User kssingvo@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=388088#c12
--- Comment #12 from Klaus Singvogel 2008-05-14 04:42:31 MST ---
Sorry, but at the moment I'm unable to reproduce it.
Currently I've got the feeling that the old squid isn't dying fast enough and
therefore hanging a bit to long in the system, locking the port.
So, you've to do some more debugging for me.
Next time when this happens do (as root) in a command line terminal the
following command. This might be time critical, so please don't wait.
- Identify the processes which are listening on the 3128 port:
lsof -i | egrep '(ndl-aas|3128).*LISTEN'
==> This will report you the process name (1st column) and the process id (2nd
column).
==> If there is only one process reported, you're too late. Try again.
- Check whether both processes have the same process ids (pid) or at least
parent pids. ==> read the output.
- If not, identify the process ids and check when both processes were
started:
ps -Flp <<pid1>> <<pid2>>
Tell me the result.
==> still NEEDINFO
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.