I have been using squid for several weeks now without any problems. However, earlier today I rebooted my computer and had to restart squid. Ever since then, I can't get it to run for more than a few seconds before it terminates. I've checked the logs, but they haven't been written to since I rebooted. The number in the pid file doesn't even change when I restart squid. Does anyone know why this is happening? I've even tried reinstalling squid, but that doesn't work either. Thanks a lot!

I'm having a similar problem on my test squid box at work. I installed the latest squid stable (don't remember version...stable 6 maybe...) on Suse 9.0 and pulled the config file off of the working squid box at work...

problem is when running it...just kills itself (disappears from ps) after a few seconds...any ideas would be apprecieated.

I managed to fix my problem. I hope this works for you as well. This solution was somewhat time-consuming, but it seems to have worked. I first made backups of my important files, then completely deleted the squid directory. I reinstalled squid, but it still wouldn't work. I temporarily changed the permissions on the var folder and its contents to allow anyone to read, write and execute. I then ran squid with the -z switch and it everything seemed to be working. I went through the new conf file and, using my backup of the old one as a reference, changed all the parameters back to the way they had been. Every time I changed a setting I restarted squid just to make sure it was working. I expected that after changing some setting in the conf file squid would stop working and I would know what was causing the trouble. However, this never happened. The only thing different in my new conf file is the disk space used by the cache. I wonder if I could have been running low on space or something. I also changed the cache_effective_user to 'nobody' and set the var folder and its contents to only allow write access to 'nobody,' whereas in my original configuration I didn't even use the directive. I'm not really sure why it works, but it does, and I hope it does for you.

maybe it has something to do with the /var permissions...did you re-set them back once squid was running again?

dunno...maybe I'll look at it when I get to work on monday...right now I really do not care

Once squid was working I set the permissions so it is only accessible to the cache_effective_user, which is 'nobody,' and it still works.