Thanks for the explanation.
Victor Pineiro
Sent from my iPad
On Feb 8, 2012, at 4:32 AM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
> On 8/02/2012 9:37 p.m., PS wrote:
>> Hello!
>>
>> I just wanted to share something interesting that just happened on my squid server.
>>
>> I had rebooted my squid server and walked away for a bit. After returning, I noticed that squid wasn't working. I found out because I was not able to browse using the proxy. After looking through the cache.log, it seemed like squid should have been running. The cache.log file said "2012/02/08 00:18:58| Squid is already running! Process ID 1288". I did a "ps -ef | grep squid" and was not able to find anything. I also did a ps -ef | grep 1288 and no process with the number 1288 showed. Next I did a netstat -ntlp and did not see the server listening on port 3128. I wasn't sure where to look to see where this so called process ID 1288 was running.
>>
>> After doing a bit of searching online, I ran into the tool called htop. I ran htop and I was able to see the process 1288. It said that it was mysql. I went ahead and killed that process and attempted to start squid again and it started up fine. Unfortunately I didn't save the info that htop provided to me. I found it kind of weird that this happened.
>
> It is based on the contents of the PID file. Sometimes after a crash an old value is left there.
> It seems mysql was assigned the same ID between when that Squid process crashed and when you restarted.
>
> Amos
Received on Wed Feb 08 2012 - 17:02:51 MST
This archive was generated by hypermail 2.2.0 : Thu Feb 09 2012 - 12:00:02 MST