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: [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: [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, 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.
Are there any .core files for squid? find / -name squid.core -print It seems like your cache is crashing for some unknown reason - are you not killing it every few hours somehow? Its highly unlikely that squid is dying after EXACTLY 66 minutes. Also try using the latest version... -Original Message- From: Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Sent: 09 November 2005 02:45 PM To: squid-users@squid-cache.org Subject: 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
RE: [squid-users] Squid unreachable every hour and 6 minutes.
Are there any .core files for squid? find / -name squid.core -print It seems like your cache is crashing for some unknown reason - are you not killing it every few hours somehow? Its highly unlikely that squid is dying after EXACTLY 66 minutes. Also try using the latest version... -Original Message- From: Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Sent: 09 November 2005 02:45 PM To: squid-users@squid-cache.org Subject: 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
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.
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. 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
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. 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
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: [squid-users] Squid unreachable every hour and 6 minutes.
did you check that nothing in cron start every hour ? try : #crontab -l -Message d'origine- De : Gix, Lilian (CI/OSR) * [mailto:[EMAIL PROTECTED] Envoyé : mercredi 9 novembre 2005 16:01 À : [EMAIL PROTECTED] Cc : squid-users@squid-cache.org Objet : RE: [squid-users] Squid unreachable every hour and 6 minutes. 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. But as the server is in production, I wll try tonight to delete folder as you propose, Thanks. L.G. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Mittwoch, 9. November 2005 15:46 To: Gix, Lilian (CI/OSR) *; [EMAIL PROTECTED]; squid-users@squid-cache.org 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. 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
Re: [squid-users] Squid unreachable every hour and 6 minutes.
Hi Lilian, The effect was exactly the same : squid stop every hour. Are you sure that no cron job is running which terminates squid? Could you please check * /etc/crontab * /etc/cron.hourly/ and do a crontab -l as root? If there is anything running, please check what exactly that job is doing. Maybe that's the reason. Regards, Peter -- Peter Albrecht, Novell Training Services, [EMAIL PROTECTED]
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.
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.
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.
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.
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.
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.
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.
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
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
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.
Robert Borkowski wrote: 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. Heh. Haven't had enough coffee this morning. I read that as 1GB, not 100MB. My bad. Still worth checking out the swap setup and ulimits though. -- Robert Borkowski
