[squid-users] Problem with ipcacheParse
Hello, Since this morning, I have many problem with my proxies (2.5.STABLE6). Just for info, my company has stric rules regarding Intra and Inernet IP resolution : from inside it's not possible to get IP from Outside. So my Proxies know everything in the Intranet but they are not able to resolv Internet IPs. After many tests, I think it was DNS problem So I changed my Resolv.conf file to another one. My problem looks fix. But now I have a lot of : ipcacheParse: No Address records in response to '...' ... : could be www.yahoo.com, www.wikipedia.org, Is it possible that my Proxies do not try to resolve those name ? Or are there another way to stop those messages ? Thanks. Gix Lilian
RE: [squid-users] Problem with ipcacheParse
Thanks for your help . No, I can't resolve Internet names. (this is normal) The only goal of me proxies is to separate Intranet from internet. Internet flow is forward to another proxy. (and the mane resolution for it works fine) Gix Lilian -Original Message- From: Mark Elsen [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 29. März 2006 17:03 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Problem with ipcacheParse Hello, Since this morning, I have many problem with my proxies (2.5.STABLE6). Just for info, my company has stric rules regarding Intra and Inernet IP resolution : from inside it's not possible to get IP from Outside. So my Proxies know everything in the Intranet but they are not able to resolv Internet IPs. After many tests, I think it was DNS problem So I changed my Resolv.conf file to another one. My problem looks fix. But now I have a lot of : ipcacheParse: No Address records in response to '...' ... : could be www.yahoo.com, www.wikipedia.org, Is it possible that my Proxies do not try to resolve those name ? On the contrary, they can no longer resolve these names... Or are there another way to stop those messages ? - Check whether the configured resolvers in /etc/resolv.conf; can resolve internet hostnames. Check them out manually; there are tools for that. M.
RE: [squid-users] Problem with ipcacheParse
Hello, In fact my original problem is: if I use the first DNS, Squid run fine 10-15 minutes then it restart, I can see nothing in Cache.log: 2006/03/29 17:14:16| WARNING: Disk space over limit: 105540 KB 102400 KB 2006/03/29 17:25:44| Starting Squid Cache version 2.5.STABLE6 for i386-debian-linux-gnu... 2006/03/29 17:25:44| Process ID 1115 2006/03/29 17:25:44| With 4096 file descriptors available 2006/03/29 17:25:44| DNS Socket created at 0.0.0.0, port 32774, FD 5 2006/03/29 17:25:44| Adding nameserver 193.108.217.69 from /etc/resolv.conf 2006/03/29 17:25:44| Adding nameserver 193.108.217.70 from /etc/resolv.conf 2006/03/29 17:25:44| User-Agent logging is disabled. 2006/03/29 17:25:44| Referer logging is disabled. 2006/03/29 17:25:44| Unlinkd pipe opened on FD 10 2006/03/29 17:25:44| Swap maxSize 102400 KB, estimated 7876 objects 2006/03/29 17:25:44| Target number of buckets: 393 2006/03/29 17:25:44| Using 8192 Store buckets 2006/03/29 17:25:44| Max Mem size: 102400 KB 2006/03/29 17:25:44| Max Swap size: 102400 KB 2006/03/29 17:25:44| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2006/03/29 17:25:44| Store logging disabled 2006/03/29 17:25:44| Rebuilding storage in /cache (DIRTY) 2006/03/29 17:25:44| Using Least Load store dir selection 2006/03/29 17:25:44| Set Current Directory to /cache_log/ 2006/03/29 17:25:44| Loaded Icons. 2006/03/29 17:25:44| Accepting HTTP connections at 0.0.0.0, port 8080, FD 11. 2006/03/29 17:25:44| Accepting ICP messages at 0.0.0.0, port 3130, FD 12. 2006/03/29 17:25:44| HTCP Disabled. 2006/03/29 17:25:44| WCCP Disabled. 2006/03/29 17:25:44| Ready to serve requests. 2006/03/29 17:25:44| Configuring Parent rb-proxy-ip.company.com/8080/0 2006/03/29 17:25:44| Store rebuilding is 30.1% complete 2006/03/29 17:25:45| WARNING: newer swaplog entry for dirno 0, fileno 0001 ... 2006/03/29 17:25:45| WARNING: newer swaplog entry for dirno 0, fileno 010F 2006/03/29 17:25:45| Done reading /cache swaplog (13998 entries) 2006/03/29 17:25:45| Finished rebuilding storage from disk. 2006/03/29 17:25:45| 11780 Entries scanned 2006/03/29 17:25:45| 0 Invalid entries. 2006/03/29 17:25:45| 0 With invalid flags. 2006/03/29 17:25:45| 11431 Objects loaded. 2006/03/29 17:25:45| 0 Objects expired. 2006/03/29 17:25:45| 2 Objects cancelled. 2006/03/29 17:25:45| 501 Duplicate URLs purged. 2006/03/29 17:25:45| 347 Swapfile clashes avoided. 2006/03/29 17:25:45| Took 0.7 seconds (17536.2 objects/sec). 2006/03/29 17:25:45| Beginning Validation Procedure 2006/03/29 17:25:45| Completed Validation Procedure 2006/03/29 17:25:45| Validated 10930 Entries 2006/03/29 17:25:45| store_swap_size = 105976k 2006/03/29 17:25:45| storeLateRelease: released 0 objects 2006/03/29 17:25:45| WARNING: Disk space over limit: 105000 KB 102400 KB 2006/03/29 17:28:54| Starting Squid Cache version 2.5.STABLE6 for i386-debian-linux-gnu... 2006/03/29 17:28:54| Process ID 1118 2006/03/29 17:28:54| With 4096 file descriptors available 2006/03/29 17:28:54| DNS Socket created at 0.0.0.0, port 32774, FD 5 2006/03/29 17:28:54| Adding nameserver x.x.217.69 from /etc/resolv.conf 2006/03/29 17:28:54| Adding nameserver x.x.217.70 from /etc/resolv.conf 2006/03/29 17:28:54| User-Agent logging is disabled. 2006/03/29 17:28:54| Referer logging is disabled. 2006/03/29 17:28:54| Unlinkd pipe opened on FD 10 2006/03/29 17:28:54| Swap maxSize 102400 KB, estimated 7876 objects 2006/03/29 17:28:54| Target number of buckets: 393 2006/03/29 17:28:54| Using 8192 Store buckets 2006/03/29 17:28:54| Max Mem size: 102400 KB 2006/03/29 17:28:54| Max Swap size: 102400 KB 2006/03/29 17:28:54| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2006/03/29 17:28:54| Store logging disabled 2006/03/29 17:28:54| Rebuilding storage in /cache (DIRTY) 2006/03/29 17:28:54| Using Least Load store dir selection 2006/03/29 17:28:54| Set Current Directory to /cache_log/ 2006/03/29 17:28:54| Loaded Icons. 2006/03/29 17:28:54| Accepting HTTP connections at 0.0.0.0, port 8080, FD 11. 2006/03/29 17:28:54| Accepting ICP messages at 0.0.0.0, port 3130, FD 12. 2006/03/29 17:28:54| HTCP Disabled. 2006/03/29 17:28:54| WCCP Disabled. 2006/03/29 17:28:54| Ready to serve requests. 2006/03/29 17:28:54| Configuring Parent rb-proxy-ip.company.com/8080/0 2006/03/29 17:28:54| Store rebuilding is 31.5% complete 2006/03/29 17:28:54| Done reading /cache swaplog (13390 entries) 2006/03/29 17:28:54| Finished rebuilding storage from disk. 2006/03/29 17:28:54| 11453 Entries scanned 2006/03/29 17:28:54| 0 Invalid entries. 2006/03/29 17:28:54| 0 With invalid flags. 2006/03/29 17:28:54| 11433 Objects loaded. 2006/03/29 17:28:54| 0 Objects expired. 2006/03/29 17:28:54| 0 Objects cancelled. 2006/03/29 17:28:54| 501 Duplicate URLs purged. 2006/03/29 17:28:54|20 Swapfile clashes avoided. 2006/03/29 17:28:54| Took 0.6 seconds (17620.4 objects/sec).
RE: [squid-users] Problem with ipcacheParse
Hi, Thanks For your help. Here is my config regarding this : always_direct allow Company1_Sites always_direct allow Company2_Sites always_direct allow Intern always_direct deny all never_direct allow all Gix Lilian CI/OSA - Application Services -Original Message- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 30. März 2006 00:26 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: RE: [squid-users] Problem with ipcacheParse ons 2006-03-29 klockan 17:07 +0200 skrev Gix, Lilian (CI/OSR) *: Thanks for your help . No, I can't resolve Internet names. (this is normal) The only goal of me proxies is to separate Intranet from internet. Make sure you use never_direct to tell your internal Squid that it is not connected to the Internet, and always_direct giving it the domain names that are internal.. Regards Henrik
RE: [squid-users] Problem with ipcacheParse
Thaose ACL are like this : acl Company1_Sites dstdomain /etc/squid/Company1_sites.conf acl Company2_Sites dstdomain /etc/squid/Company2_sites.conf Gix Lilian -Original Message- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 30. März 2006 08:43 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: RE: [squid-users] Problem with ipcacheParse tor 2006-03-30 klockan 07:43 +0200 skrev Gix, Lilian (CI/OSR) *: Hi, Thanks For your help. Here is my config regarding this : always_direct allow Company1_Sites always_direct allow Company2_Sites always_direct allow Intern And how is the above three acls defined? Regards Henrik
RE: [squid-users] FILE DESCRIPTORS
Hello, I always had some problems with Filedescriptor. One day, U changed my Linux version to a Debian (I don't now if it's the reason) and I update Squid. And since, I got a configuration file under: /etc/default/squid On this file, there is: # # /etc/default/squidConfiguration settings for the Squid proxy server. # # Max. number of filedescriptors to use. You can increase this on abusy # cache to a maximum of (currently) 4096 filedescriptors. Default is 1024. SQUID_MAXFD=4096 I don't know if this can help Gix Lilian -Original Message- From: Mark Elsen [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 23. Februar 2006 09:26 To: Gregori Parker Cc: squid-users@squid-cache.org Subject: Re: [squid-users] FILE DESCRIPTORS Sorry to be pounding the list lately, but I'm about to lose it with these file descriptors... I've done everything I have read about to increase file descriptors on my caching box, and now I just rebuilt a fresh clean squid. Before I ran configure, I did ulimit -HSn 8192, and I noticed that while configuring it said Checking File Descriptors... 8192. I even double-checked autoconf.h and saw #define SQUID_MAXFD 8192. I thought everything was good, even ran a ulimit -n right before starting squid and saw 8192! So I start her up, and in cache.log I see... 2006/02/22 19:05:08| Starting Squid Cache version 2.5.STABLE12 for x86_64-unknown-linux-gnu... 2006/02/22 19:05:08| Process ID 3657 2006/02/22 19:05:08| With 1024 file descriptors available To make sure that this is not bogus w.r.t. the real available amount of FD's : do you still get warnings in cache.log about FD-shortage when reaching the 1024 (bogus-reported ?) limit. The reason I ask is, that I have been playing with the FAQ guidelines too, ultimately getting the same result (stuck?) as you did. M.
[squid-users] Non respect fo Proxy chain
Hello, It's not the first time I ask for this, but I didn't see any answer. I have two proxies. They have Ips 10.105.x.y and 10.105.x.y+1 The outgoing is an upstream proxy. My problem is: They try to reach by themselves URL with: 192.168.*.* instead of forward them to the Upstream proxy. 1139206331.003 179161 10.104.x.* TCP_MISS/504 1490 GET http://192.168.37.10/icons/parent.gif - NONE/- text/html 1139206331.003 179123 10.104.x.* TCP_MISS/504 1492 GET http://192.168.37.10/icons/archive.gif - NONE/- text/html 1139206331.003 179119 10.104.x.* TCP_MISS/504 1486 GET http://192.168.37.10/icons/text.gif - NONE/- text/html 1139206331.003 179119 10.104.x.* TCP_MISS/504 1492 GET http://192.168.37.10/icons/unknown.gif - NONE/- text/html I really need a solution. Thanks. Gix Lilian
RE: [squid-users] Non respect fo Proxy chain
Thanks for your help: Here is my Configuration regarding direct access: always_direct deny Firm1_Sites_Internet always_direct deny Firm2_Sites_Internet always_direct allow Firm1_Sites_Intranet always_direct allow Firm2_Sites_Intranet always_direct allow Intern always_direct deny all never_direct allow all Gix Lilian -Original Message- From: Mark Elsen [mailto:[EMAIL PROTECTED] Sent: Montag, 6. Februar 2006 10:07 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Non respect fo Proxy chain Hello, It's not the first time I ask for this, but I didn't see any answer. I have two proxies. They have Ips 10.105.x.y and 10.105.x.y+1 The outgoing is an upstream proxy. My problem is: They try to reach by themselves URL with: 192.168.*.* instead of forward them to the Upstream proxy. 1139206331.003 179161 10.104.x.* TCP_MISS/504 1490 GET http://192.168.37.10/icons/parent.gif - NONE/- text/html 1139206331.003 179123 10.104.x.* TCP_MISS/504 1492 GET http://192.168.37.10/icons/archive.gif - NONE/- text/html 1139206331.003 179119 10.104.x.* TCP_MISS/504 1486 GET http://192.168.37.10/icons/text.gif - NONE/- text/html 1139206331.003 179119 10.104.x.* TCP_MISS/504 1492 GET http://192.168.37.10/icons/unknown.gif - NONE/- text/html http://www.squid-cache.org/Doc/FAQ/FAQ-4.html#ss4.8 M.
RE: [squid-users] squid uses its own IP address instead client IP Address
Hello, As far as I known your situation is normal. It shows the normal proxy philosophy and I don't think another way would be better (for the cache, for security (firewall,...)). L.G. -Original Message- From: Vijayakumar Perumal [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 15. Dezember 2005 08:37 To: squid-users@squid-cache.org Subject: [squid-users] squid uses its own IP address instead client IP Address Hi, I am T.P.Vijayakumar, I am seting up a web cache to enhance my user experience( Note all my users are having a valid public IP). But It seems the squid uses its own IP address to contact web servers. So that means all the HTTP replies will come for the Squid Machines IP. Is it possible to configure the Squid so that the requesting IP will be of Clients's IP address instead of the Squid's machine. I am running squid/2.5.STABLE12 on a Fedora Core 4. running wccp with my cisco 3660. WCCP other things are working fine. With Regards, T.P.Vijayakumar, +91-9840280030. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
RE: [squid-users] which user is using max bandwidth
Hello Sarg or Webaliser are probably what you are looking for Gix Lilian -Original Message- From: Jason Staudenmayer [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 16. November 2005 15:05 To: squid-users@squid-cache.org Subject: RE: [squid-users] which user is using max bandwidth Take a look at SARG for squid reporting on the access.log -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 15, 2005 11:24 PM To: squid-users@squid-cache.org Subject: [squid-users] which user is using max bandwidth Hi, I am a novice in squid. Can someone please tell me how to find out which of my user is using how much bandwidth . Also how to find out who is visiting which site. Regards Gaurav Duggal.
[squid-users] Log analyser
Hello, I'm looking for a log analyzer witch give me the number of Mbytes a client(s) (IP) took on last days (access.log.0,...) I tried several from squid site, but it never gave this. And it takes many time to test. So if you can give me the name of one you know? Thanks. L.G.
RE: [squid-users] Squid unreachable every hour and 6 minutes.
I don't know if I right saw, but I think Squid leaved the task list of the TOP command. Any Idea ? PS : Cron has been stop. Gix Lilian -Original Message- From: Robert Borkowski [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. November 2005 17:44 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. Gix, Lilian (CI/OSR) * wrote: It's nearly what I already tried. (1) Ok (2) I had : cache_dir ufs /cache 5000 16 256 (3) mke2fs -j -c /dev/cciss/c0d0p6 (/dev/cciss/c0d0p6 is my Cache partition) (3) ok (4) /etc/init.d squid start. The effect was exactly the same : squid stop every hour. So I tried : (2) changed : cache_dir ufs /cache 100 16 256 (4) squid -k reconfigure Same result. Then a last sing I did : (1) Stop Squid (3) cd /cache rm cache.swap (4) Start Squid And again ... Same result. Can you clarify something for me? When you say every hour and 6 minutes, do you mean squid restarts every 66 minutes, or 6 minutes past every hour (1:06, 2:06, 3:06) If it's the second one, then try turning off the cron daemon about 15 minutes before the new hour /etc/init.d/cron stop -- Robert Borkowski
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, So, I confirm, my squid died: it leaved TOP list and get a new PID. What could be the reason? I saw another task running with Squid User: UNLINKD. Could it be the reason ? Gix Lilian -Original Message- From: Robert Borkowski [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. November 2005 17:44 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. Gix, Lilian (CI/OSR) * wrote: It's nearly what I already tried. (1) Ok (2) I had : cache_dir ufs /cache 5000 16 256 (3) mke2fs -j -c /dev/cciss/c0d0p6 (/dev/cciss/c0d0p6 is my Cache partition) (3) ok (4) /etc/init.d squid start. The effect was exactly the same : squid stop every hour. So I tried : (2) changed : cache_dir ufs /cache 100 16 256 (4) squid -k reconfigure Same result. Then a last sing I did : (1) Stop Squid (3) cd /cache rm cache.swap (4) Start Squid And again ... Same result. Can you clarify something for me? When you say every hour and 6 minutes, do you mean squid restarts every 66 minutes, or 6 minutes past every hour (1:06, 2:06, 3:06) If it's the second one, then try turning off the cron daemon about 15 minutes before the new hour /etc/init.d/cron stop -- Robert Borkowski
RE: AW: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Do you have some name for such software ? Thanks Gix Lilian -Original Message- From: Dave Raven [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. November 2005 17:16 To: Gix, Lilian (CI/OSR) *; squid-users@squid-cache.org Subject: RE: AW: [squid-users] Squid unreachable every hour and 6 minutes. Run squid under some sort of trace program - you'll need to see whats causing it to crash... -Original Message- From: Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Sent: 11 November 2005 09:45 AM To: Serassio Guido; Chris Robertson; squid-users@squid-cache.org Subject: RE: AW: [squid-users] Squid unreachable every hour and 6 minutes. Hello, Webalizer is a software to create some statistic on squid Log files. But even if I disable it, I didn't see any difference. Restart continues. L.G. -Original Message- From: Serassio Guido [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. November 2005 08:36 To: Chris Robertson; squid-users@squid-cache.org Subject: RE: AW: [squid-users] Squid unreachable every hour and 6 minutes. Hi, At 19.53 10/11/2005, Chris Robertson wrote: 0 0 * * * /etc/webmin/webalizer/webalizer.pl /cache_log/access.log What is the content of webalizer.pl ? Regards Guido Does it matter? It only runs once per day (at midnight). It's the only custom script related to squid present on crontab, so why don't check it when squid is still doing unexpected things ? It's a work of half minute Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Squid stop 6 minutes past every hour (1:06, 2:06, 3:06) I stopped cron, and the problem still here Gix Lilian -Original Message- From: Robert Borkowski [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. November 2005 17:44 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. Gix, Lilian (CI/OSR) * wrote: It's nearly what I already tried. (1) Ok (2) I had : cache_dir ufs /cache 5000 16 256 (3) mke2fs -j -c /dev/cciss/c0d0p6 (/dev/cciss/c0d0p6 is my Cache partition) (3) ok (4) /etc/init.d squid start. The effect was exactly the same : squid stop every hour. So I tried : (2) changed : cache_dir ufs /cache 100 16 256 (4) squid -k reconfigure Same result. Then a last sing I did : (1) Stop Squid (3) cd /cache rm cache.swap (4) Start Squid And again ... Same result. Can you clarify something for me? When you say every hour and 6 minutes, do you mean squid restarts every 66 minutes, or 6 minutes past every hour (1:06, 2:06, 3:06) If it's the second one, then try turning off the cron daemon about 15 minutes before the new hour /etc/init.d/cron stop -- Robert Borkowski
RE: AW: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Webalizer is a software to create some statistic on squid Log files. But even if I disable it, I didn't see any difference. Restart continues. L.G. -Original Message- From: Serassio Guido [mailto:[EMAIL PROTECTED] Sent: Freitag, 11. November 2005 08:36 To: Chris Robertson; squid-users@squid-cache.org Subject: RE: AW: [squid-users] Squid unreachable every hour and 6 minutes. Hi, At 19.53 10/11/2005, Chris Robertson wrote: 0 0 * * * /etc/webmin/webalizer/webalizer.pl /cache_log/access.log What is the content of webalizer.pl ? Regards Guido Does it matter? It only runs once per day (at midnight). It's the only custom script related to squid present on crontab, so why don't check it when squid is still doing unexpected things ? It's a work of half minute Regards Guido - Guido Serassio Acme Consulting S.r.l. - Microsoft Certified Partner Via Lucia Savarino, 1 10098 - Rivoli (TO) - ITALY Tel. : +39.011.9530135 Fax. : +39.011.9781115 Email: [EMAIL PROTECTED] WWW: http://www.acmeconsulting.it/
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Realy no body have an idea ? :( L.G. -Original Message- From: Gix, Lilian (CI/OSR) * Sent: Mittwoch, 2. November 2005 10:26 To: squid-users@squid-cache.org Subject: [squid-users] Squid unreachable every hour and 6 minutes. Hello, I have a problem with my squid : every hour and 6 minutes, it is unreachable for few second. Here is a part of Cache.log : 2005/11/02 09:44:45| Detected REVIVED Parent: virus2.com/8080/0 2005/11/02 10:07:05| Starting Squid Cache version 2.5.STABLE6 for i386-debian-li nux-gnu... 2005/11/02 10:07:05| Process ID 1430 2005/11/02 10:07:05| With 4096 file descriptors available 2005/11/02 10:07:05| DNS Socket created at 0.0.0.0, port 32772, FD 5 2005/11/02 10:07:05| Adding nameserver 193.108.217.70 from /etc/resolv.conf 2005/11/02 10:07:05| User-Agent logging is disabled. 2005/11/02 10:07:05| Referer logging is disabled. 2005/11/02 10:07:05| Unlinkd pipe opened on FD 10 2005/11/02 10:07:05| Swap maxSize 102400 KB, estimated 7876 objects 2005/11/02 10:07:05| Target number of buckets: 393 2005/11/02 10:07:05| Using 8192 Store buckets 2005/11/02 10:07:05| Max Mem size: 102400 KB 2005/11/02 10:07:05| Max Swap size: 102400 KB 2005/11/02 10:07:05| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2005/11/02 10:07:05| Store logging disabled 2005/11/02 10:07:05| Rebuilding storage in /cache (DIRTY) 2005/11/02 10:07:05| Using Least Load store dir selection 2005/11/02 10:07:05| Set Current Directory to /cache_log/ 2005/11/02 10:07:05| Loaded Icons. 2005/11/02 10:07:15| Accepting HTTP connections at 0.0.0.0, port 8080, FD 11. 2005/11/02 10:07:15| Accepting ICP messages at 0.0.0.0, port 3130, FD 12. 2005/11/02 10:07:15| HTCP Disabled. 2005/11/02 10:07:15| WCCP Disabled. 2005/11/02 10:07:15| Configuring Parent 10.4.13.184/8080/0 2005/11/02 10:07:15| Ready to serve requests. 2005/11/02 10:07:15| Configuring Parent virus1.com/8080/0 2005/11/02 10:07:15| Configuring Parent virus2.com/8080/0 2005/11/02 10:07:15| Store rebuilding is 1.9% complete 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 031F 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 0371 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E4 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E8 2005/11/02 10:07:19| Done reading /cache swaplog (215057 entries) 2005/11/02 10:07:19| Finished rebuilding storage from disk. 2005/11/02 10:07:19|111709 Entries scanned 2005/11/02 10:07:19| 0 Invalid entries. 2005/11/02 10:07:19| 0 With invalid flags. 2005/11/02 10:07:19| 35086 Objects loaded. 2005/11/02 10:07:19| 0 Objects expired. 2005/11/02 10:07:19| 6194 Objects cancelled. 2005/11/02 10:07:19| 3443 Duplicate URLs purged. 2005/11/02 10:07:19| 70406 Swapfile clashes avoided. 2005/11/02 10:07:19| Took 14.5 seconds (2411.4 objects/sec). 2005/11/02 10:07:19| Beginning Validation Procedure 2005/11/02 10:07:19| Completed Validation Procedure 2005/11/02 10:07:19| Validated 31666 Entries 2005/11/02 10:07:19| store_swap_size = 400260k 2005/11/02 10:07:20| WARNING: Disk space over limit: 399480 KB 102400 KB 2005/11/02 10:07:20| storeLateRelease: released 2 objects 2005/11/02 10:07:31| WARNING: Disk space over limit: 384820 KB 102400 KB 2005/11/02 10:07:39| WARNING: 1 swapin MD5 mismatches 2005/11/02 10:07:42| WARNING: Disk space over limit: 377240 KB 102400 KB 2005/11/02 10:07:53| WARNING: Disk space over limit: 369680 KB 102400 KB 2005/11/02 10:08:04| WARNING: Disk space over limit: 351148 KB 102400 KB 2005/11/02 10:08:15| WARNING: Disk space over limit: 340112 KB 102400 KB 2005/11/02 10:08:26| WARNING: Disk space over limit: 320184 KB 102400 KB 2005/11/02 10:08:37| WARNING: Disk space over limit: 309412 KB 102400 KB 2005/11/02 10:08:41| clientProcessHit: Vary object loop! 2005/11/02 10:08:48| WARNING: Disk space over limit: 295500 KB 102400 KB 2005/11/02 10:08:59| WARNING: Disk space over limit: 287596 KB 102400 KB 2005/11/02 10:09:10| WARNING: Disk space over limit: 277460 KB 102400 KB 2005/11/02 10:09:11| WARNING: 10 swapin MD5 mismatches 2005/11/02 10:09:21| WARNING: Disk space over limit: 267808 KB 102400 KB 2005/11/02 10:09:32| WARNING: Disk space over limit: 256848 KB 102400 KB ... I already tried to : - Stop Squid, delete swap.state, restart squid - Stop Squid
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Thanks for support. I suppose WARNING: Disk space over limit come from the fact that squid restart by itself and so corrupt is cache. But I don't know why every time it use more space than I allow it. proxy1:~# cd / proxy1:/# find . -name core -print ./dev/core ./lib/modules/2.4.26-1-686-smp/kernel/net/core ./lib/modules/2.4.26-1-386/kernel/net/core ./proc/sys/net/core proxy1:/# Thnaks. L.G. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 13:57 To: Gix, Lilian (CI/OSR) *; squid-users@squid-cache.org Subject: AW: [squid-users] Squid unreachable every hour and 6 minutes. While squid is unreachable maybe the system writes a core file to the disk? Please search for core files: Login as root cd / find . -name core -print The find command may run some minutes depending of the size of your disks. Furthermore you should find out why WARNING: Disk space over limit. Werner Rost -Ursprüngliche Nachricht- Von: Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 9. November 2005 13:45 An: squid-users@squid-cache.org Betreff: RE: [squid-users] Squid unreachable every hour and 6 minutes. Hello, Realy no body have an idea ? :( L.G. -Original Message- From: Gix, Lilian (CI/OSR) * Sent: Mittwoch, 2. November 2005 10:26 To: squid-users@squid-cache.org Subject: [squid-users] Squid unreachable every hour and 6 minutes. Hello, I have a problem with my squid : every hour and 6 minutes, it is unreachable for few second. Here is a part of Cache.log : 2005/11/02 09:44:45| Detected REVIVED Parent: virus2.com/8080/0 2005/11/02 10:07:05| Starting Squid Cache version 2.5.STABLE6 for i386-debian-li nux-gnu... 2005/11/02 10:07:05| Process ID 1430 2005/11/02 10:07:05| With 4096 file descriptors available 2005/11/02 10:07:05| DNS Socket created at 0.0.0.0, port 32772, FD 5 2005/11/02 10:07:05| Adding nameserver 193.108.217.70 from /etc/resolv.conf 2005/11/02 10:07:05| User-Agent logging is disabled. 2005/11/02 10:07:05| Referer logging is disabled. 2005/11/02 10:07:05| Unlinkd pipe opened on FD 10 2005/11/02 10:07:05| Swap maxSize 102400 KB, estimated 7876 objects 2005/11/02 10:07:05| Target number of buckets: 393 2005/11/02 10:07:05| Using 8192 Store buckets 2005/11/02 10:07:05| Max Mem size: 102400 KB 2005/11/02 10:07:05| Max Swap size: 102400 KB 2005/11/02 10:07:05| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2005/11/02 10:07:05| Store logging disabled 2005/11/02 10:07:05| Rebuilding storage in /cache (DIRTY) 2005/11/02 10:07:05| Using Least Load store dir selection 2005/11/02 10:07:05| Set Current Directory to /cache_log/ 2005/11/02 10:07:05| Loaded Icons. 2005/11/02 10:07:15| Accepting HTTP connections at 0.0.0.0, port 8080, FD 11. 2005/11/02 10:07:15| Accepting ICP messages at 0.0.0.0, port 3130, FD 12. 2005/11/02 10:07:15| HTCP Disabled. 2005/11/02 10:07:15| WCCP Disabled. 2005/11/02 10:07:15| Configuring Parent 10.4.13.184/8080/0 2005/11/02 10:07:15| Ready to serve requests. 2005/11/02 10:07:15| Configuring Parent virus1.com/8080/0 2005/11/02 10:07:15| Configuring Parent virus2.com/8080/0 2005/11/02 10:07:15| Store rebuilding is 1.9% complete 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 031F 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 0371 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E4 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E8 2005/11/02 10:07:19| Done reading /cache swaplog (215057 entries) 2005/11/02 10:07:19| Finished rebuilding storage from disk. 2005/11/02 10:07:19|111709 Entries scanned 2005/11/02 10:07:19| 0 Invalid entries. 2005/11/02 10:07:19| 0 With invalid flags. 2005/11/02 10:07:19| 35086 Objects loaded. 2005/11/02 10:07:19| 0 Objects expired. 2005/11/02 10:07:19| 6194 Objects cancelled. 2005/11/02 10:07:19| 3443 Duplicate URLs purged. 2005/11/02 10:07:19| 70406 Swapfile clashes avoided. 2005/11/02 10:07:19| Took 14.5 seconds (2411.4 objects/sec). 2005/11/02 10:07:19| Beginning Validation Procedure 2005/11/02 10:07:19| Completed Validation Procedure 2005/11/02 10:07:19| Validated 31666 Entries 2005/11/02 10:07:19| store_swap_size = 400260k 2005/11/02 10:07:20| WARNING: Disk space over limit: 399480 KB 102400 KB 2005/11/02 10:07:20| storeLateRelease: released 2 objects 2005/11/02 10:07:31| WARNING: Disk space over limit: 384820 KB 102400 KB 2005/11/02 10:07:39| WARNING: 1 swapin MD5 mismatches 2005/11/02 10:07:42
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Great, thanks for your answer and questions : 1- I have a message form my browser (IE, Firefox) witch says the proxy is unreachable. My MSN, yahoo messengers loose their access. 2- Ping like all other services still work perfectly. (SSH, Apache, Ping,...) 3- Cache.log part is on the previous mail. You can see that there is nothing special between 09:44:45 and 10:07:05 (when squid come back) Thanks for help. L.G. From: Mike Cudmore [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 14:10 To: Gix, Lilian (CI/OSR) * Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. Lilian I may have missed earlier entries in this thread so apologies if I ask you to repeat any info. 1) How do you know squid is unreachable at these times ? 2) try pinging the host squid is running on for a period that covers the time that the squid is unreachable. Does the host become unreachable as well? 3) What does cache.log say for these periods ? I have more thoughts depending on the answers to these Regards Mike Gix, Lilian (CI/OSR) * [EMAIL PROTECTED] 09/11/05 12:44:30 Hello, Realy no body have an idea ? :( L.G. -Original Message- From: Gix, Lilian (CI/OSR) * Sent: Mittwoch, 2. November 2005 10:26 To: squid-users@squid-cache.org Subject: [squid-users] Squid unreachable every hour and 6 minutes. Hello, I have a problem with my squid : every hour and 6 minutes, it is unreachable for few second. Here is a part of Cache.log : 2005/11/02 09:44:45| Detected REVIVED Parent: virus2.com/8080/0 2005/11/02 10:07:05| Starting Squid Cache version 2.5.STABLE6 for i386-debian-li nux-gnu... 2005/11/02 10:07:05| Process ID 1430 2005/11/02 10:07:05| With 4096 file descriptors available 2005/11/02 10:07:05| DNS Socket created at 0.0.0.0, port 32772, FD 5 2005/11/02 10:07:05| Adding nameserver 193.108.217.70 from /etc/resolv.conf 2005/11/02 10:07:05| User-Agent logging is disabled. 2005/11/02 10:07:05| Referer logging is disabled. 2005/11/02 10:07:05| Unlinkd pipe opened on FD 10 2005/11/02 10:07:05| Swap maxSize 102400 KB, estimated 7876 objects 2005/11/02 10:07:05| Target number of buckets: 393 2005/11/02 10:07:05| Using 8192 Store buckets 2005/11/02 10:07:05| Max Mem size: 102400 KB 2005/11/02 10:07:05| Max Swap size: 102400 KB 2005/11/02 10:07:05| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2005/11/02 10:07:05| Store logging disabled 2005/11/02 10:07:05| Rebuilding storage in /cache (DIRTY) 2005/11/02 10:07:05| Using Least Load store dir selection 2005/11/02 10:07:05| Set Current Directory to /cache_log/ 2005/11/02 10:07:05| Loaded Icons. 2005/11/02 10:07:15| Accepting HTTP connections at 0.0.0.0, port 8080, FD 11. 2005/11/02 10:07:15| Accepting ICP messages at 0.0.0.0, port 3130, FD 12. 2005/11/02 10:07:15| HTCP Disabled. 2005/11/02 10:07:15| WCCP Disabled. 2005/11/02 10:07:15| Configuring Parent 10.4.13.184/8080/0 2005/11/02 10:07:15| Ready to serve requests. 2005/11/02 10:07:15| Configuring Parent virus1.com/8080/0 2005/11/02 10:07:15| Configuring Parent virus2.com/8080/0 2005/11/02 10:07:15| Store rebuilding is 1.9% complete 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 031F 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 0371 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E4 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E8 2005/11/02 10:07:19| Done reading /cache swaplog (215057 entries) 2005/11/02 10:07:19| Finished rebuilding storage from disk. 2005/11/02 10:07:19|111709 Entries scanned 2005/11/02 10:07:19| 0 Invalid entries. 2005/11/02 10:07:19| 0 With invalid flags. 2005/11/02 10:07:19| 35086 Objects loaded. 2005/11/02 10:07:19| 0 Objects expired. 2005/11/02 10:07:19| 6194 Objects cancelled. 2005/11/02 10:07:19| 3443 Duplicate URLs purged. 2005/11/02 10:07:19| 70406 Swapfile clashes avoided. 2005/11/02 10:07:19| Took 14.5 seconds (2411.4 objects/sec). 2005/11/02 10:07:19| Beginning Validation Procedure 2005/11/02 10:07:19| Completed Validation Procedure 2005/11/02 10:07:19| Validated 31666 Entries 2005/11/02 10:07:19| store_swap_size = 400260k 2005/11/02 10:07:20| WARNING: Disk space over limit: 399480 KB 102400 KB 2005/11/02 10:07:20| storeLateRelease: released 2 objects 2005/11/02 10:07:31| WARNING: Disk space over limit: 384820 KB 102400 KB 2005/11/02 10:07:39| WARNING: 1 swapin MD5 mismatches 2005/11/02 10:07:42| WARNING: Disk space over limit: 377240 KB 102400 KB 2005/11/02 10:07:53| WARNING: Disk space over limit: 369680 KB 102400 KB 2005/11/02 10:08:04| WARNING: Disk space over limit: 351148 KB
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Here are results: proxy1:/# find / -name squid.core -print proxy1:/# proxy1:/# df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p2 10083964 1606012 7965708 17% / tmpfs 516744 0516744 0% /dev/shm /dev/cciss/c0d0p191747 15993 70859 19% /boot /dev/cciss/c0d0p6 10079868156200 9411632 2% /cache /dev/cciss/c0d0p5 14011356 4575072 8724532 35% /cache_log Again, thanks. L.G. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 14:40 To: Gix, Lilian (CI/OSR) *; squid-users@squid-cache.org Subject: AW: [squid-users] Squid unreachable every hour and 6 minutes. Thanks for support. I suppose WARNING: Disk space over limit come from the fact that squid restart by itself and so corrupt is cache. But I don't know why every time it use more space than I allow it. I think this warning says that one of your disks is full. Check your disk space with df -k. proxy1:~# cd / proxy1:/# find . -name core -print ./dev/core ./lib/modules/2.4.26-1-686-smp/kernel/net/core ./lib/modules/2.4.26-1-386/kernel/net/core ./proc/sys/net/core proxy1:/# These are directories, you have no core files. Werner Rost
RE: [squid-users] Squid unreachable every hour and 6 minutes.
I already tried to : - Stop Squid, delete swap.state, restart squid - Stop Squid, format my cache parition, squid -z, start squid - change cache_dir ufs /cache 5000 16 256 to cache_dir ufs /cache 100 16 256, squid -k restart. - reboot completely the server But nothing worked. -Original Message- From: Dave Raven [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 14:58 To: Gix, Lilian (CI/OSR) *; squid-users@squid-cache.org Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. Try use my method posted earlier to search for code files. The fact that your log suddenly shows squid restarting means it died unexpectedly. If there is a core file it'll be squids problem - if not its probably something else causing the problem. Also, you should try clean out your cache_dir potentially... Remove everything and run squid -z to recreate it -Original Message- From: Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Sent: 09 November 2005 03:32 PM To: Mike Cudmore Cc: squid-users@squid-cache.org Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. Great, thanks for your answer and questions : 1- I have a message form my browser (IE, Firefox) witch says the proxy is unreachable. My MSN, yahoo messengers loose their access. 2- Ping like all other services still work perfectly. (SSH, Apache, Ping,...) 3- Cache.log part is on the previous mail. You can see that there is nothing special between 09:44:45 and 10:07:05 (when squid come back) Thanks for help. L.G. From: Mike Cudmore [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 14:10 To: Gix, Lilian (CI/OSR) * Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. Lilian I may have missed earlier entries in this thread so apologies if I ask you to repeat any info. 1) How do you know squid is unreachable at these times ? 2) try pinging the host squid is running on for a period that covers the time that the squid is unreachable. Does the host become unreachable as well? 3) What does cache.log say for these periods ? I have more thoughts depending on the answers to these Regards Mike Gix, Lilian (CI/OSR) * [EMAIL PROTECTED] 09/11/05 12:44:30 Hello, Realy no body have an idea ? :( L.G. -Original Message- From: Gix, Lilian (CI/OSR) * Sent: Mittwoch, 2. November 2005 10:26 To: squid-users@squid-cache.org Subject: [squid-users] Squid unreachable every hour and 6 minutes. Hello, I have a problem with my squid : every hour and 6 minutes, it is unreachable for few second. Here is a part of Cache.log : 2005/11/02 09:44:45| Detected REVIVED Parent: virus2.com/8080/0 2005/11/02 10:07:05| Starting Squid Cache version 2.5.STABLE6 for i386-debian-li nux-gnu... 2005/11/02 10:07:05| Process ID 1430 2005/11/02 10:07:05| With 4096 file descriptors available 2005/11/02 10:07:05| DNS Socket created at 0.0.0.0, port 32772, FD 5 2005/11/02 10:07:05| Adding nameserver 193.108.217.70 from /etc/resolv.conf 2005/11/02 10:07:05| User-Agent logging is disabled. 2005/11/02 10:07:05| Referer logging is disabled. 2005/11/02 10:07:05| Unlinkd pipe opened on FD 10 2005/11/02 10:07:05| Swap maxSize 102400 KB, estimated 7876 objects 2005/11/02 10:07:05| Target number of buckets: 393 2005/11/02 10:07:05| Using 8192 Store buckets 2005/11/02 10:07:05| Max Mem size: 102400 KB 2005/11/02 10:07:05| Max Swap size: 102400 KB 2005/11/02 10:07:05| Local cache digest enabled; rebuild/rewrite every 3600/3600 sec 2005/11/02 10:07:05| Store logging disabled 2005/11/02 10:07:05| Rebuilding storage in /cache (DIRTY) 2005/11/02 10:07:05| Using Least Load store dir selection 2005/11/02 10:07:05| Set Current Directory to /cache_log/ 2005/11/02 10:07:05| Loaded Icons. 2005/11/02 10:07:15| Accepting HTTP connections at 0.0.0.0, port 8080, FD 11. 2005/11/02 10:07:15| Accepting ICP messages at 0.0.0.0, port 3130, FD 12. 2005/11/02 10:07:15| HTCP Disabled. 2005/11/02 10:07:15| WCCP Disabled. 2005/11/02 10:07:15| Configuring Parent 10.4.13.184/8080/0 2005/11/02 10:07:15| Ready to serve requests. 2005/11/02 10:07:15| Configuring Parent virus1.com/8080/0 2005/11/02 10:07:15| Configuring Parent virus2.com/8080/0 2005/11/02 10:07:15| Store rebuilding is 1.9% complete 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 031F 2005/11/02 10:07:16| WARNING: newer swaplog entry for dirno 0, fileno 0371 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E4 2005/11/02 10:07:19| WARNING: newer swaplog entry for dirno 0, fileno 39E8 2005/11/02 10:07:19| Done reading /cache swaplog (215057 entries) 2005/11/02 10:07:19| Finished rebuilding storage from disk. 2005/11/02 10:07:19|111709 Entries scanned 2005/11/02 10:07:19| 0 Invalid entries
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Here is what I have during the problem : proxy1:/# df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p2 10083964 1606024 7965696 17% / tmpfs 516744 0516744 0% /dev/shm /dev/cciss/c0d0p191747 15993 70859 19% /boot /dev/cciss/c0d0p6 10079868158536 9409296 2% /cache /dev/cciss/c0d0p5 14011356 4586500 8713104 35% /cache_log Nothing wrong I can notice. L.G. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 14:58 To: Gix, Lilian (CI/OSR) *; squid-users@squid-cache.org Subject: AW: [squid-users] Squid unreachable every hour and 6 minutes. Please observe the disk space with df -k in the time when squid is unreachable. Does some value in the column Use% grow over 70 % ? Werner Here are results: proxy1:/# find / -name squid.core -print proxy1:/# proxy1:/# df -k Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p2 10083964 1606012 7965708 17% / tmpfs 516744 0516744 0% /dev/shm /dev/cciss/c0d0p191747 15993 70859 19% /boot /dev/cciss/c0d0p6 10079868156200 9411632 2% /cache /dev/cciss/c0d0p5 14011356 4575072 8724532 35% /cache_log Again, thanks. L.G. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 14:40 To: Gix, Lilian (CI/OSR) *; squid-users@squid-cache.org Subject: AW: [squid-users] Squid unreachable every hour and 6 minutes. Thanks for support. I suppose WARNING: Disk space over limit come from the fact that squid restart by itself and so corrupt is cache. But I don't know why every time it use more space than I allow it. I think this warning says that one of your disks is full. Check your disk space with df -k. proxy1:~# cd / proxy1:/# find . -name core -print ./dev/core ./lib/modules/2.4.26-1-686-smp/kernel/net/core ./lib/modules/2.4.26-1-386/kernel/net/core ./proc/sys/net/core proxy1:/# These are directories, you have no core files. Werner Rost
RE: AW: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Thanks for your help : proxy1:~# crontab -l 0 0 * * * /etc/webmin/webalizer/webalizer.pl /cache_log/access.log proxy1:~# more /etc/crontab SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # m h dom mon dow user command 17 ** * * rootrun-parts --report /etc/cron.hourly 1 0 * * * roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.daily 47 6* * 7 roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.weekly 52 61 * * roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.monthly proxy1:~# ls /etc/cron.hourly/ proxy1:~# The server is a compaq DL580 (2*Xeon700Mhz, 1G of Ram, Raid 5: 32G), working on Debian L.G. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 16:53 To: squid-users@squid-cache.org Subject: Re: AW: [squid-users] Squid unreachable every hour and 6 minutes. The disk space is over limit error is not saying the disk is full. The cache has reached the limit that's been set in the squid.conf file. It could be causing squid to die, but how likely is it that this would be the cause, if squid dies 6 minutes after every hour? My suggestion is to check and see what cron jobs are running: cat /etc/crontab or (as root): crontab -l and then crontab -l any other users that might be running cron jobs If there's a timely pattern to the connectivity issue, the root of the problem probably has something to do with a schedule for something. Cron would be a good place to start. On the disk space is over limit issue... You really shouldn't have to tend to this. Squid should use whatever replacement policy was specified at compile time (forget which one is default if none is specified) To remove old/unused cache objects in an effort to free up space. However, if squid is trying to do this, and is actively handling proxy requests at the same time, squid could be running out of resources. What specs do you have on this machine? CPU/Ram/etc. Tim Rainier Information Services, Kalsec, INC [EMAIL PROTECTED] [EMAIL PROTECTED] 11/09/2005 09:45 AM To [EMAIL PROTECTED], [EMAIL PROTECTED], squid-users@squid-cache.org cc Subject AW: [squid-users] Squid unreachable every hour and 6 minutes. Please repeat that again. (1) stop squid (2) find out wht are the cache directories squid uses, for example # grep cache_dir squid.conf cache_dir ufs /data1/squid_cache 6000 32 512 cache_dir ufs /data2/squid_cache 1 32 512 # In this example /data1/squid_cache and /data2/squid_cache are the cache dirs. (3) Clean all cache dirs - in this example: cd /data1/squid_cache rm -f * cd /data2/squid_cache rm -f * (3) create the cache structures again: squid -z (4) Start squid. What happens? Is squid running? ps -ef | grep squid What does cache.log say since starting of squid? Is squid reachable? (5) What happens after 1 hour an 6 minutes? Werner Rost -Ursprüngliche Nachricht- Von: Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Gesendet: Mittwoch, 9. November 2005 15:10 An: Dave Raven; squid-users@squid-cache.org Betreff: RE: [squid-users] Squid unreachable every hour and 6 minutes. I already tried to : - Stop Squid, delete swap.state, restart squid - Stop Squid, format my cache parition, squid -z, start squid - change cache_dir ufs /cache 5000 16 256 to cache_dir ufs /cache 100 16 256, squid -k restart. - reboot completely the server But nothing worked. -Original Message- From: Dave Raven [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 14:58 To: Gix, Lilian (CI/OSR) *; squid-users@squid-cache.org Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. Try use my method posted earlier to search for code files. The fact that your log suddenly shows squid restarting means it died unexpectedly. If there is a core file it'll be squids problem - if not its probably something else causing the problem. Also, you should try clean out your cache_dir potentially... Remove everything and run squid -z to recreate it -Original Message- From: Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Sent: 09 November 2005 03:32 PM To: Mike Cudmore Cc: squid-users@squid-cache.org Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. Great, thanks for your answer and questions : 1- I have a message form my browser (IE, Firefox) witch says the proxy is unreachable. My MSN, yahoo messengers loose their access. 2- Ping like all other services still work perfectly. (SSH, Apache, Ping,...) 3- Cache.log part is on the previous mail. You can see that there is nothing special between 09:44:45 and 10:07:05 (when squid come back) Thanks for help. L.G
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Any body else have an idea ? Sorry, I relay don't know where could be the problem and I'm open to all hint. Thanks. L.G. -Original Message- From: Gix, Lilian (CI/OSR) * Sent: Montag, 7. November 2005 11:26 To: 'Robert Borkowski' Cc: Henrik Nordstrom; squid-users@squid-cache.org Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. Hello, Here is : /proc/meminfo: [EMAIL PROTECTED]:/root$ more /proc/meminfo total:used:free: shared: buffers: cached: Mem: 1058295808 1040723968 175718400 125198336 713523200 Swap: 1048645632 12443648 1036201984 MemTotal: 1033492 kB MemFree: 17160 kB MemShared: 0 kB Buffers:122264 kB Cached: 696028 kB SwapCached:772 kB Active: 137096 kB Inactive: 829072 kB HighTotal: 131056 kB HighFree: 2044 kB LowTotal: 902436 kB LowFree: 15116 kB SwapTotal: 1024068 kB SwapFree: 1011916 kB Here is /etc/profile : [EMAIL PROTECTED]:/root$ more /etc/profile # /etc/profile: system-wide .profile file for the Bourne shell (sh(1)) # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...). PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games if [ $PS1 ]; then if [ $BASH ]; then PS1='[EMAIL PROTECTED]:\w\$ ' else if [ `id -u` -eq 0 ]; then PS1='# ' else PS1='$ ' fi fi fi export PATH umask 022 proxy1:~# su squid [EMAIL PROTECTED]:/root$ ulimit unlimited and : [EMAIL PROTECTED]:/root$ more /etc/default/squid # # /etc/default/squidConfiguration settings for the Squid proxy server. # # Max. number of filedescriptors to use. You can increase this on a busy # cache to a maximum of (currently) 4096 filedescriptors. Default is 1024. SQUID_MAXFD=4096 I can't realy find where could be the mistake. L.G. -Original Message- From: Robert Borkowski [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 3. November 2005 16:38 To: Gix, Lilian (CI/OSR) * Cc: Henrik Nordstrom; squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. Gix, Lilian (CI/OSR) * wrote: The server has 1G of RAM (only 100M for squid) 2005/11/02 10:07:05| Max Mem size: 102400 KB ^^ I asked about memory because of this line... Two possibilities 1) The kernel is killing off squid because there's no VM left. What's in /proc/meminfo ? 2) There's a process ulimit that squid hits and it gets killed off that way. Check for ulimit in /etc/profile or the squid startup script In either case, you need to lower the amount of memory used by squid to below whatever the limit is. I was hoping for some 'out of memory', or 'OOM killer', or 'zero order allocation' errors in the dmesg output. If they're not there then the second (ulimit) possibility is most likely. -- Robert Borkowski
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Here is : /proc/meminfo: [EMAIL PROTECTED]:/root$ more /proc/meminfo total:used:free: shared: buffers: cached: Mem: 1058295808 1040723968 175718400 125198336 713523200 Swap: 1048645632 12443648 1036201984 MemTotal: 1033492 kB MemFree: 17160 kB MemShared: 0 kB Buffers:122264 kB Cached: 696028 kB SwapCached:772 kB Active: 137096 kB Inactive: 829072 kB HighTotal: 131056 kB HighFree: 2044 kB LowTotal: 902436 kB LowFree: 15116 kB SwapTotal: 1024068 kB SwapFree: 1011916 kB Here is /etc/profile : [EMAIL PROTECTED]:/root$ more /etc/profile # /etc/profile: system-wide .profile file for the Bourne shell (sh(1)) # and Bourne compatible shells (bash(1), ksh(1), ash(1), ...). PATH=/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/games if [ $PS1 ]; then if [ $BASH ]; then PS1='[EMAIL PROTECTED]:\w\$ ' else if [ `id -u` -eq 0 ]; then PS1='# ' else PS1='$ ' fi fi fi export PATH umask 022 proxy1:~# su squid [EMAIL PROTECTED]:/root$ ulimit unlimited and : [EMAIL PROTECTED]:/root$ more /etc/default/squid # # /etc/default/squidConfiguration settings for the Squid proxy server. # # Max. number of filedescriptors to use. You can increase this on a busy # cache to a maximum of (currently) 4096 filedescriptors. Default is 1024. SQUID_MAXFD=4096 I can't realy find where could be the mistake. L.G. -Original Message- From: Robert Borkowski [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 3. November 2005 16:38 To: Gix, Lilian (CI/OSR) * Cc: Henrik Nordstrom; squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. Gix, Lilian (CI/OSR) * wrote: The server has 1G of RAM (only 100M for squid) 2005/11/02 10:07:05| Max Mem size: 102400 KB ^^ I asked about memory because of this line... Two possibilities 1) The kernel is killing off squid because there's no VM left. What's in /proc/meminfo ? 2) There's a process ulimit that squid hits and it gets killed off that way. Check for ulimit in /etc/profile or the squid startup script In either case, you need to lower the amount of memory used by squid to below whatever the limit is. I was hoping for some 'out of memory', or 'OOM killer', or 'zero order allocation' errors in the dmesg output. If they're not there then the second (ulimit) possibility is most likely. -- Robert Borkowski
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Hello, Thanks for your support. Unfortunately, my problem happen even if I haven't problem with my upstream. It's right that my extract of the log file is not the best, but as you can see, the time between those two event is very different. Regards. L.G. -Original Message- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 3. November 2005 09:55 To: Gix, Lilian (CI/OSR) * Cc: squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. On Wed, 2 Nov 2005, Gix, Lilian (CI/OSR) * wrote: Hello, I have a problem with my squid : every hour and 6 minutes, it is unreachable for few second. Any crontab entry running at that time? Here is a part of Cache.log : 2005/11/02 09:44:45| Detected REVIVED Parent: virus2.com/8080/0 2005/11/02 10:07:05| Starting Squid Cache version 2.5.STABLE6 for i386-debian-li This indicates something forcibly killed your Squid process. The problem is most likely caused by something external to Squid, not Squid itself. Regards Henrik
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Oh, sorry, miss understood : Here is my cron information : proxy1:/etc/cron.hourly# more /etc/crontab # /etc/crontab: system-wide crontab # Unlike any other crontab you don't have to run the `crontab' # command to install the new version when you edit this file. # This file also has a username field, that none of the other crontabs do. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # m h dom mon dow user command 17 ** * * rootrun-parts --report /etc/cron.hourly 1 0 * * * roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.daily 47 6* * 7 roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.weekly 52 61 * * roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.monthly # proxy1:/etc/cron.hourly# ls /etc/cron.hourly/ proxy1:/etc/cron.hourly# As far as I see, there is nothing special on this. One thing I saw witch start every hour is a Digest generation, So I placed : digest_generation off But this didn't changed anything Thanks, L.G. -Original Message- From: Henrik Nordstrom [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 3. November 2005 15:07 To: Gix, Lilian (CI/OSR) * Cc: Henrik Nordstrom; squid-users@squid-cache.org Subject: RE: [squid-users] Squid unreachable every hour and 6 minutes. On Thu, 3 Nov 2005, Gix, Lilian (CI/OSR) * wrote: Hello, Thanks for your support. Unfortunately, my problem happen even if I haven't problem with my upstream. Didn't ask about your upstream. I asked if you have any crontab entries coinciding with the times your Squid stops responding. It's right that my extract of the log file is not the best, but as you can see, the time between those two event is very different. The important message is that there is no message indicating why your Squid terminates before it starts again. Regards Henrik
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Here is what I have: proxy1:/var/spool/cron/crontabs# ls root proxy1:/var/spool/cron/crontabs# more root # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.zzxZ9g/crontab installed on Tue Aug 24 10:16:27 2004) # (Cron version -- $Id: crontab.c,v 2.13 1994/01/17 03:20:37 vixie Exp $) 0 0 * * * /etc/webmin/webalizer/webalizer.pl /cache_log/access.log Proxy1:/var/spool/cron/crontabs# And the user is a special user : squid Thanks for the support. L.G. -Original Message- From: Robert Borkowski [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 3. November 2005 15:42 To: Gix, Lilian (CI/OSR) * Cc: Henrik Nordstrom; squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. Gix, Lilian (CI/OSR) * wrote: Oh, sorry, miss understood : Here is my cron information : proxy1:/etc/cron.hourly# more /etc/crontab # /etc/crontab: system-wide crontab # Unlike any other crontab you don't have to run the `crontab' # command to install the new version when you edit this file. # This file also has a username field, that none of the other crontabs do. SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin # m h dom mon dow user command 17 ** * * rootrun-parts --report /etc/cron.hourly 1 0 * * * roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.daily 47 6* * 7 roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.weekly 52 61 * * roottest -x /usr/sbin/anacron || run-parts --report /etc/cron.monthly # proxy1:/etc/cron.hourly# ls /etc/cron.hourly/ proxy1:/etc/cron.hourly# As far as I see, there is nothing special on this. One thing I saw witch start every hour is a Digest generation, So I placed : digest_generation off But this didn't changed anything Thanks, L.G. What user does squid run as? Are there any other crontabs installed? Take a look in /var/spool/cron/crontabs -- Robert Borkowski
RE: [squid-users] Squid unreachable every hour and 6 minutes.
The server has 1G of RAM (only 100M for squid) Dmesg give me many things, but I don't know how to interpret this : proxy1:~# dmesg |more eive checksums enabled cpu cycle saver enabled e100: selftest OK. e100: eth1: Intel(R) PRO/100 Network Connection Hardware receive checksums enabled cpu cycle saver enabled ncr53c8xx: at PCI bus 0, device 4, function 0 ncr53c8xx: 53c1510D detected ncr53c8xx: at PCI bus 0, device 4, function 1 ncr53c8xx: 53c1510D detected ncr53c1510D-0: rev 0x2 on pci bus 0 device 4 function 0 irq 10 ncr53c1510D-0: ID 7, Fast-40, Parity Checking ncr53c1510D-1: rev 0x2 on pci bus 0 device 4 function 1 irq 11 ncr53c1510D-1: ID 7, Fast-40, Parity Checking scsi0 : ncr53c8xx-3.4.3b-20010512 scsi1 : ncr53c8xx-3.4.3b-20010512 megaraid: v1.18k (Release Date: Thu Aug 28 10:05:11 EDT 2003) megaraid: no BIOS enabled. scsi2 : SCSI host adapter emulation for IDE ATAPI devices eepro100.c:v1.09j-t 9/29/99 Donald Becker http://www.scyld.com/network/eepro100. html eepro100.c: $Revision: 1.36 $ 2000/11/17 Modified by Andrey V. Savochkin [EMAIL PROTECTED] w.sw.com.sg and others pci_hotplug: PCI Hot Plug PCI Core version: 0.5 cpqphp: Hot Plug Subsystem Device ID: a2f8 cpqphp: Initializing the PCI hot plug controller residing on PCI bus 2 PCI: Using BIOS Interrupt Routing Table PCI: Using BIOS Interrupt Routing Table cpqphp: Hot Plug Subsystem Device ID: a2f9 cpqphp: Initializing the PCI hot plug controller residing on PCI bus 7 PCI: Using BIOS Interrupt Routing Table cpqphp: Compaq Hot Plug PCI Controller Driver version: 0.9.7 usb.c: registered new driver usbdevfs usb.c: registered new driver hub uhci.c: USB Universal Host Controller Interface driver v1.1 usb-uhci.c: $Revision: 1.275 $ time 13:57:34 Aug 24 2004 usb-uhci.c: High bandwidth mode enabled usb-uhci.c: v1.275:USB Universal Host Controller Interface driver hw tcp v4 csum failed hw tcp v4 csum failed hw tcp v4 csum failed hw tcp v4 csum failed hw tcp v4 csum failed hw tcp v4 csum failed hw tcp v4 csum failed regarding the ps | grep, I don't know, I will test on the next problem. L.G. -Original Message- From: Robert Borkowski [mailto:[EMAIL PROTECTED] Sent: Donnerstag, 3. November 2005 16:21 To: Gix, Lilian (CI/OSR) * Cc: Henrik Nordstrom; squid-users@squid-cache.org Subject: Re: [squid-users] Squid unreachable every hour and 6 minutes. How much memory is in your server? What does the command 'dmesg' return? What does 'ps aux|grep squid' return just before a crash? -- Robert Borkowski
