Hi, >> [EMAIL PROTECTED] /var/log/squid# fuser -vun tcp 8080 >> here: 8080 >> USER PID ACCESS COMMAND >> 8080/tcp squid 23790 f.... squid > > > Same occurs if you reboot or do a 'service squid restart'?
Same after 'service squid restart', but diferent PID (as expected). > Is there any refernce to squid in /etc/rc.local? No. No reference to squid. > Another squid process is running, no doubt about it. Check crontabs too. Nothing unexpected in crontabs. Nothing with referance to squid here. > Are you able to reproduce it? I'm not sure. It's strange. Even after restarting squid and dansguardian services and waiting for what's going to happen I found out that this error shows up in logs again (after random time period - in hours...). Other TSL 3.0 box with nearly identical configuration works without any sign of a any problem. I use bit of an older kernel version on this TSL 2.2 machine (2.4.30-3tr), but everything worked fine in the same configuration for months untill now... Because of not latest version of ClamAV there were some viruses I've found in squids cache (Exploit.WMF.A, Trojan.Downloader.Small-356) so I'm starting to think if it's not some kind of DoS from some "bad" LAN machine. Or if the amount of installed RAM (128MB) is sufficient... (only a wild gues ;-)) I'll try to upgrade my dansguardian version to the latest one and see what will happen then. For times when I'm not able to connect to the server and restart the service manually a run script from crontab that will restart dansguardian service every hour (this seems to help for a while). But this is definitely not the right (and permanent) solution to this problem :-( Cheers -- Jaroslav Vrbicky _______________________________________________ tsl-discuss mailing list [email protected] http://lists.trustix.org/mailman/listinfo/tsl-discuss
