[squid-users] Cache Log Errors
Good day, Is there any way i can use to stop squid store rebuilding process, why is squid rebuilding its store and why does it longer time to conclude? Why are mine seeing some http log in cache log instead of access log? Why are mine getting these errors (see below) in my squid cache log? What can i do to prevent these error from occurrrng? Regards, Yomi 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) 011/04/02 07:13:51| Store rebuilding is 13.9% complete 2011/04/02 07:14:06| Store rebuilding is 14.9% complete 2011/04/02 07:14:21| Store rebuilding is 16.0% complete 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/01 17:14:44| Preparing for shutdown after 18038 requests 2011/04/01 17:14:44| Waiting 0 seconds for active connections to finish 2011/04/01 17:14:44| FD 21 Closing HTTP connection 2011/04/01 17:14:45| Shutting down... 2011/04/01 17:14:45| FD 22 Closing ICP connection 2011/04/01 17:14:45| FD 23 Closing HTCP socket 2011/04/01 17:14:45| FD 24 Closing SNMP socket 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://prod1.rest-notify.msg.yahoo.com/v1/pushchannel/michealomoniyi90?sid=oxsQqevs3BrUSPEmbgkZN8DUms6k5KS3kNONWA--c=t3i2XkVUiKvseq=5cb=ca7u4bqsformat=jsonidle=110cache=1301674432962 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.112 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.145.channel.facebook.com/x/1534213288/1667359870/false/p_11050471985=0 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.110 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.63.channel.facebook.com/x/2878475822/2523481944/false/p_12078361547=44 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.192.channel.facebook.com/x/461011288/1190138722/false/p_11927647801=1 2011/04/01 17:14:45| Closing unlinkd pipe on FD 10 2011/04/01 17:14:45| Not currently OK to rewrite swap log. 2011/04/01 17:14:45| storeDirWriteCleanLogs: Operation aborted. CPU Usage: 7147.781 seconds = 1196.078 user + 5951.703 sys Maximum Resident Size: 113604 KB Page faults with physical i/o: 28549
Re: [squid-users] Cache Log Errors
On 03/04/11 19:55, sq...@sourcesystemsonline.com wrote: Good day, Is there any way i can use to stop squid store rebuilding process, why is squid rebuilding its store and why does it longer time to conclude? Why are mine seeing some http log in cache log instead of access log? http log? cache.log displays details about the problems seen by Squid. Being an HTTP proxy almost all problems are somehow related to HTTP. Why are mine getting these errors (see below) in my squid cache log? What can i do to prevent these error from occurrrng? Regards, Yomi 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) ... Resource temporarily unavailable. unlinkd is the cache file eraser. It looks like a file delete failed due to something moving or double-deleting the file or locking the disk access away from Squid's eraser. 011/04/02 07:13:51| Store rebuilding is 13.9% complete 2011/04/02 07:14:06| Store rebuilding is 14.9% complete 2011/04/02 07:14:21| Store rebuilding is 16.0% complete 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 The Squid meta-data about the file 0/002C3FA8 in the cache is different to the file actually in the cache. Somebody has tampered with the file, or the disk is getting corruption. When store problems are found Squid drops/erases the cache entry for safety. 2011/04/01 17:14:44| Preparing for shutdown after 18038 requests 2011/04/01 17:14:44| Waiting 0 seconds for active connections to finish 2011/04/01 17:14:44| FD 21 Closing HTTP connection 2011/04/01 17:14:45| Shutting down... 2011/04/01 17:14:45| FD 22 Closing ICP connection 2011/04/01 17:14:45| FD 23 Closing HTCP socket 2011/04/01 17:14:45| FD 24 Closing SNMP socket 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://prod1.rest-notify.msg.yahoo.com/v1/pushchannel/michealomoniyi90?sid=oxsQqevs3BrUSPEmbgkZN8DUms6k5KS3kNONWA--c=t3i2XkVUiKvseq=5cb=ca7u4bqsformat=jsonidle=110cache=1301674432962 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.112 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.145.channel.facebook.com/x/1534213288/1667359870/false/p_11050471985=0 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.110 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.63.channel.facebook.com/x/2878475822/2523481944/false/p_12078361547=44 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.192.channel.facebook.com/x/461011288/1190138722/false/p_11927647801=1 2011/04/01 17:14:45| Closing unlinkd pipe on FD 10 So far a normal shutdown process. The WARNING are not errors, just important information that some clients connections are being killed while still in use. channel.facebook uses a HTTP technique they call long-polling apparently, to keep connections open for hours or days. These can be ignored. I'm not sure about the yahoo URL. 2011/04/01 17:14:45| Not currently OK to rewrite swap log. 2011/04/01 17:14:45| storeDirWriteCleanLogs: Operation aborted. Hmm, that may be a problem. COuld be related or from the same cause as the unlinkd problems. Something is preventing Squid from saving its meta data to disk. This will result in your cache rebuilding slowely next startup. CPU Usage: 7147.781 seconds = 1196.078 user + 5951.703 sys Maximum Resident Size: 113604 KB Page faults with physical i/o: 28549 Here is some useful information about how much RAM your Squid needed to run and how much swapping was done. You can use the Resident Size to check that you have enough RAM allocated for Squid to use. That is how much it needed to use since the last restart. The Page faults indicates that there was not enough RAM available (needed 113604 KB) and swapping was done 28,549 times. 0 is best. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.11 Beta testers wanted for 3.2.0.5
Re: [squid-users] Cache Log Errors
Good day, I have 4GB RAM install in my squid server. After increasing the RAM maximum resident size due high page faults and reconfigure squid a WARNING: Very large maximum_object_size_in_memory settings can have negative impact on performance was displayed. What is the implication of this warning, any danger? See below for more information and excerpts from my squid.conf Regards, Yomi. C:\squid\sbinsquid -n squid -k reconfigure 2011/04/03 17:46:15| WARNING: Very large maximum_object_size_in_memory settings can have negative impact on performance Status of squid Service: Service Type: 0x10 Current State: 0x4 Controls Accepted: 0x5 Exit Code: 0 Service Specific Exit Code: 0 Check Point: 0 Wait Hint: 0 # MEMORY CACHE OPTIONS --- #Default: cache_mem 1024 MB #Default: maximum_object_size_in_memory 131072 KB #Default: # memory_replacement_policy lru # DISK CACHE OPTIONS # -- #Default: # cache_replacement_policy lru #Default: cache_dir ufs c:/squid/var/cache 40960 128 512 cache_dir ufs d:/squid/var/cache 20480 128 512 cache_dir ufs e:/squid/var/cache 5120 128 512 cache_dir ufs f:/squid/var/cache 20480 128 512 #Default: # store_dir_select_algorithm least-load #Default: # max_open_disk_fds 0 #Default: # minimum_object_size 0 KB #Default: maximum_object_size 204800 KB #Default: # cache_swap_low 90 # cache_swap_high 95 #Default: # update_headers on On 03/04/11 19:55, sq...@sourcesystemsonline.com wrote: Good day, Is there any way i can use to stop squid store rebuilding process, why is squid rebuilding its store and why does it longer time to conclude? Why are mine seeing some http log in cache log instead of access log? http log? cache.log displays details about the problems seen by Squid. Being an HTTP proxy almost all problems are somehow related to HTTP. Why are mine getting these errors (see below) in my squid cache log? What can i do to prevent these error from occurrrng? Regards, Yomi 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) ... Resource temporarily unavailable. unlinkd is the cache file eraser. It looks like a file delete failed due to something moving or double-deleting the file or locking the disk access away from Squid's eraser. 011/04/02 07:13:51| Store rebuilding is 13.9% complete 2011/04/02 07:14:06| Store rebuilding is 14.9% complete 2011/04/02 07:14:21| Store rebuilding is 16.0% complete 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 The Squid meta-data about the file 0/002C3FA8 in the cache is different to the file actually in the cache. Somebody has tampered with the file, or the disk is getting corruption. When store problems are found Squid drops/erases the cache entry for safety. 2011/04/01 17:14:44| Preparing for shutdown after 18038 requests 2011/04/01 17:14:44| Waiting 0 seconds for active connections to finish 2011/04/01 17:14:44| FD 21 Closing HTTP connection 2011/04/01 17:14:45| Shutting down... 2011/04/01 17:14:45| FD 22 Closing ICP connection 2011/04/01 17:14:45| FD 23 Closing HTCP socket 2011/04/01 17:14:45| FD 24 Closing SNMP socket 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://prod1.rest-notify.msg.yahoo.com/v1/pushchannel/michealomoniyi90?sid=oxsQqevs3BrUSPEmbgkZN8DUms6k5KS3kNONWA--c=t3i2XkVUiKvseq=5cb=ca7u4bqsformat=jsonidle=110cache=1301674432962 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.112 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.145.channel.facebook.com/x/1534213288/1667359870/false/p_11050471985=0 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.110 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.63.channel.facebook.com/x/2878475822/2523481944/false/p_12078361547=44 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.192.channel.facebook.com/x/461011288/1190138722/false/p_11927647801=1 2011/04/01 17:14:45| Closing unlinkd pipe on FD 10 So far a normal shutdown process. The WARNING are not errors, just important information that
Re: [squid-users] Cache Log Errors
On Sun, 3 Apr 2011 13:41:22 -0400, sq...@sourcesystemsonline.com wrote: Good day, I have 4GB RAM install in my squid server. After increasing the RAM maximum resident size due high page faults and reconfigure squid a WARNING: Very large maximum_object_size_in_memory settings can have negative impact on performance was displayed. No, no. That setting does not affect the problem like that. Resident size is not something Squid can easily affect directly. Have a read through http://wiki.squid-cache.org/SquidFaq/SquidMemory to learn how Squid uses memory and what things can be adjusted to affect that. You need to ensure that when squid is not running the operating system says free available memory is a bigger number than the Squid maximum resident size. And that when Squid is running the amount of virtual or swap memory reported by the operating system is zero. More on that below. But please read that wiki page before continuing, the answers below will make a lot more sense when you know the background ideas. What is the implication of this warning, any danger? The setting you changed is the limit on *individual* objects stored in memory. The problems referred to are the swapping ones you are already seeing before the change. The change may make them randomly even worse than before. See below for more information and excerpts from my squid.conf Regards, Yomi. C:\squid\sbinsquid -n squid -k reconfigure 2011/04/03 17:46:15| WARNING: Very large maximum_object_size_in_memory settings can have negative impact on performance Status of squid Service: Service Type: 0x10 Current State: 0x4 Controls Accepted: 0x5 Exit Code: 0 Service Specific Exit Code: 0 Check Point: 0 Wait Hint: 0 # MEMORY CACHE OPTIONS --- #Default: cache_mem 1024 MB Hmm, 4GB of RAM on the system and you are dedicating 25% of it to a RAM cache for Squid. #Default: maximum_object_size_in_memory 131072 KB This can at most be set to the same as cache_mem. Though generally you want many HTTP objects in the RAM cache. #Default: # memory_replacement_policy lru # DISK CACHE OPTIONS # -- #Default: # cache_replacement_policy lru #Default: cache_dir ufs c:/squid/var/cache 40960 128 512 cache_dir ufs d:/squid/var/cache 20480 128 512 cache_dir ufs e:/squid/var/cache 5120 128 512 cache_dir ufs f:/squid/var/cache 20480 128 512 Using the rule-of-thumb 1MB/GB estimate those dir need 880 MB of memory for their indexes. Plus the cache_mem RAM cache. That gives up to 2GB of RAM consumed by Squid before any clients start connecting. More for traffic handling. Also, I believe the aufs scheme uses windows disk IO threading. You could possibly avoid some of the disk speed problems by changing those types to aufs (just a Squid restart needed to switch). Also check that those sizes are leaving at least 10% of the disk space free on each for the cache swap.state journals. If the disk is filled that would result in those unable to save swap.state which your shutdown sees. Also check that the disks are not being put into any kind of standby or hibernate mode underneath Squid. I suspect that would lead to the resource unavailable messages your logs show. #Default: # cache_swap_low 90 # cache_swap_high 95 With caches 20GB I would change that low-threshold 90 to a 94. That minimizes the period when the background garbage collection can drain speed. There is nothing there to indicate a box with 4GB RAM would swap badly. So I conclude there must be other software hogging memory and reducing the amount available to Squid. Removing that other software would be a good thing for performance. Amos
[squid-users] Cache Log Errors
Good day, Is there any way i can use to stop squid store rebuilding process, why is squid rebuilding its store and why does it longer time to conclude? Why are mine seeing some http log in cache log instead of access log? Why are mine getting these errors (see below) in my squid cache log? What can i do to prevent these error from occurrrng? 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) WSAEWOULDBLOCK, Resource temporarily unavailable. 2011/03/31 15:02:01| unlinkdUnlink: write FD 10 failed: (10035) 011/04/02 07:13:51| Store rebuilding is 13.9% complete 2011/04/02 07:14:06| Store rebuilding is 14.9% complete 2011/04/02 07:14:21| Store rebuilding is 16.0% complete 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/02 07:14:26| WARNING: newer swaplog entry for dirno 0, fileno 002C3FA8 2011/04/01 17:14:44| Preparing for shutdown after 18038 requests 2011/04/01 17:14:44| Waiting 0 seconds for active connections to finish 2011/04/01 17:14:44| FD 21 Closing HTTP connection 2011/04/01 17:14:45| Shutting down... 2011/04/01 17:14:45| FD 22 Closing ICP connection 2011/04/01 17:14:45| FD 23 Closing HTCP socket 2011/04/01 17:14:45| FD 24 Closing SNMP socket 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://prod1.rest-notify.msg.yahoo.com/v1/pushchannel/michealomoniyi90?sid=oxsQqevs3BrUSPEmbgkZN8DUms6k5KS3kNONWA--c=t3i2XkVUiKvseq=5cb=ca7u4bqsformat=jsonidle=110cache=1301674432962 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.112 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.145.channel.facebook.com/x/1534213288/1667359870/false/p_11050471985=0 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.110 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.63.channel.facebook.com/x/2878475822/2523481944/false/p_12078361547=44 2011/04/01 17:14:45| WARNING: Closing client 192.168.137.111 connection due to lifetime timeout 2011/04/01 17:14:45| http://0.192.channel.facebook.com/x/461011288/1190138722/false/p_11927647801=1 2011/04/01 17:14:45| Closing unlinkd pipe on FD 10 2011/04/01 17:14:45| Not currently OK to rewrite swap log. 2011/04/01 17:14:45| storeDirWriteCleanLogs: Operation aborted. CPU Usage: 7147.781 seconds = 1196.078 user + 5951.703 sys Maximum Resident Size: 113604 KB Page faults with physical i/o: 28549
[squid-users] Cache Log errors
Can anyone explain if these are important messages. My squid server appears to be working but im concerned: The 51.63.xx.xx and 192.168.xx.xx are peers. I am able to access the particular website via these peers but I receive the messages below. If there is any other information I can provide to investigate please say so, but also please suggest the commands I should use, as my knowledge is brief. squid:/opt/squid/var/logs # tail -f cache.log 2006/08/15 18:49:26| storeLateRelease: released 0 objects 2006/08/15 18:53:42| temporary disabling (Internal Server Error) digest from 51.63.xx.xx 2006/08/15 18:54:43| temporary disabling (Internal Server Error) digest from 51.63.xx.xx 2006/08/15 18:56:13| temporary disabling (Service Unavailable) digest from 192.168.xx.x 2006/08/15 18:58:42| temporary disabling (Internal Server Error) digest from 51.63.xx.xx 2006/08/15 18:59:43| temporary disabling (Internal Server Error) digest from 51.63.xx.xx 2006/08/15 19:05:13| temporary disabling (Gateway Time-out) digest from 192.168.xx.x 2006/08/15 19:08:43| temporary disabling (Internal Server Error) digest from 51.63.xx.xx 2006/08/15 19:09:44| temporary disabling (Internal Server Error) digest from 51.63.xx.xx 2006/08/15 19:19:14| temporary disabling (reply header too big) digest from 192.168.xx.x Levent Mehmet Network Analyst Server and Network Team [EMAIL PROTECTED] Operate Unit Market Towers, 20th Floor 1 Nine Elms Lane London SW8 5NQ E-mail: [EMAIL PROTECTED] Phone: +44 20 7084 3517 Fax: +44 20 7084 2536 This email and any files transmitted with it are confidential. If you are not the intended recipient, any reading, printing, storage, disclosure, copying or any other action taken in respect of this email is prohibited and may be unlawful. If you are not the intended recipient, please notify the sender immediately by using the reply function and then permanently delete what you have received.Incoming and outgoing email messages are routinely monitored for compliance with the Department of Healths policy on the use of electronic communications. For more information on the Department of Healths email policy, click http;//www.doh.gov.uk/emaildisclaimer.htm The original of this email was scanned for viruses by Government Secure Intranet (GSi) virus scanning service supplied exclusively by Cable Wireless in partnership with MessageLabs. On leaving the GSI this email was certified virus free. The MessageLabs Anti Virus Service is the first managed service to achieve the CSIA Claims Tested Mark (CCTM Certificate Number 2006/04/0007), the UK Government quality mark initiative for information security products and services. For more information about this please visit www.cctmark.gov.uk
