RE: [squid-users] RE: Anacron log entries
From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: Monday, May 17, 2010 9:59 PM Well, there you go. Debug level #2 is full of debugging traces. FWIW: level 0 - critical failure messages. level 1 - warnings and important notices level 2 thru 9 - debug traces (section specific) This is why the recommended level is 1 and not 2 or higher. Amos I'll try that - but there are too things to note.. 1) I initially increased the debugging to see the auth failures - which I couldn't see - despite going to 9. In fact, I saw no difference between 1 and 2 so that's why I left it at that. 2) My logging options are to output to: 1128 access_log /var/log/squid3/access.log combined 1137 cache_log /var/log/squid3/cache.log I meant to send this out on Friday. Anacron doesn't seem to have sent me the notice since I made the change, but nonetheless, I'm curious as to why that would make a difference. My assumption is that no matter what I put the debugging level at, it should log to file, not to anacron. They are part of the configuration file loading. The system log is used for initial startup messages before the cache.log file is configured for use. debug_options takes effect immediately on being read in, but cache.log opening is done after the config load is finished and the final cache.log location is known (it can currently be specific twice or more with different filenames). That would imply that squid is also being restarted on a daily basis.. Is that implication correct? Is that behaviour correct? Simon
RE: [squid-users] RE: Anacron log entries
On Wed, 19 May 2010 16:28:08 +0200, Simon Brereton simon.brere...@dada.net wrote: From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: Monday, May 17, 2010 9:59 PM Well, there you go. Debug level #2 is full of debugging traces. FWIW: level 0 - critical failure messages. level 1 - warnings and important notices level 2 thru 9 - debug traces (section specific) This is why the recommended level is 1 and not 2 or higher. Amos I'll try that - but there are too things to note.. 1) I initially increased the debugging to see the auth failures - which I couldn't see - despite going to 9. In fact, I saw no difference between 1 and 2 so that's why I left it at that. 2) My logging options are to output to: 1128 access_log /var/log/squid3/access.log combined 1137 cache_log /var/log/squid3/cache.log I meant to send this out on Friday. Anacron doesn't seem to have sent me the notice since I made the change, but nonetheless, I'm curious as to why that would make a difference. My assumption is that no matter what I put the debugging level at, it should log to file, not to anacron. They are part of the configuration file loading. The system log is used for initial startup messages before the cache.log file is configured for use. debug_options takes effect immediately on being read in, but cache.log opening is done after the config load is finished and the final cache.log location is known (it can currently be specific twice or more with different filenames). That would imply that squid is also being restarted on a daily basis.. Is that implication correct? Is that behaviour correct? Yes, it does appears so. Behaviour correctness depends on what is being done at the time of restart. The only normal operation which is done daily by external processes is log rotation. That should be using squid -k rotate. However, there may be other opeartions somewhere in your setup that mean a full restart is required. Amos
RE: [squid-users] RE: Anacron log entries
From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: Friday, May 14, 2010 1:32 AM Simon Brereton wrote: From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: Wednesday, May 12, 2010 4:06 PM ons 2010-05-12 klockan 14:40 +0200 skrev Simon Brereton: /etc/cron.daily/logrotate: 2010/05/05 07:35:20.152| aclParseUserList: parsing user list 2010/05/05 07:35:20.152| aclParseUserList: parsing user list Looks like debug output. What is your debug_options directive set to? 1245 # TAG: debug_options 1246 # Logging options are set as section,level where each source file 1247 # is assigned a unique section. Lower levels result in less 1248 # output, Full debugging (level 9) can result in a very large 1249 # log file, so be careful. The magic word ALL sets debugging 1250 # levels for all sections. We recommend normally running with 1251 # ALL,1. 1252 # 1253 #Default: 1254 # debug_options ALL,1 1255 debug_options all,2 I had it as ALL, but when I increaded it to ALL,9 to do some debugging, nothing extra appeared in the logs. Google pulled up someone with the same issue - or maybe I saw it go by on the list - that writing it as all would fix that (but I'd already solved my issue). Anacron emails me these lines whether it's ALL or all.. Simon Well, there you go. Debug level #2 is full of debugging traces. FWIW: level 0 - critical failure messages. level 1 - warnings and important notices level 2 thru 9 - debug traces (section specific) This is why the recommended level is 1 and not 2 or higher. Amos I'll try that - but there are too things to note.. 1) I initially increased the debugging to see the auth failures - which I couldn't see - despite going to 9. In fact, I saw no difference between 1 and 2 so that's why I left it at that. 2) My logging options are to output to: 1128 access_log /var/log/squid3/access.log combined 1137 cache_log /var/log/squid3/cache.log I meant to send this out on Friday. Anacron doesn't seem to have sent me the notice since I made the change, but nonetheless, I'm curious as to why that would make a difference. My assumption is that no matter what I put the debugging level at, it should log to file, not to anacron. Cheers Simon
RE: [squid-users] RE: Anacron log entries
On Mon, 17 May 2010 19:35:50 +0200, Simon Brereton simon.brere...@dada.net wrote: From: Amos Jeffries [mailto:squ...@treenet.co.nz] Sent: Friday, May 14, 2010 1:32 AM Simon Brereton wrote: From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: Wednesday, May 12, 2010 4:06 PM ons 2010-05-12 klockan 14:40 +0200 skrev Simon Brereton: /etc/cron.daily/logrotate: 2010/05/05 07:35:20.152| aclParseUserList: parsing user list 2010/05/05 07:35:20.152| aclParseUserList: parsing user list Looks like debug output. What is your debug_options directive set to? 1245 # TAG: debug_options 1246 # Logging options are set as section,level where each source file 1247 # is assigned a unique section. Lower levels result in less 1248 # output, Full debugging (level 9) can result in a very large 1249 # log file, so be careful. The magic word ALL sets debugging 1250 # levels for all sections. We recommend normally running with 1251 # ALL,1. 1252 # 1253 #Default: 1254 # debug_options ALL,1 1255 debug_options all,2 I had it as ALL, but when I increaded it to ALL,9 to do some debugging, nothing extra appeared in the logs. Google pulled up someone with the same issue - or maybe I saw it go by on the list - that writing it as all would fix that (but I'd already solved my issue). Anacron emails me these lines whether it's ALL or all.. Simon Well, there you go. Debug level #2 is full of debugging traces. FWIW: level 0 - critical failure messages. level 1 - warnings and important notices level 2 thru 9 - debug traces (section specific) This is why the recommended level is 1 and not 2 or higher. Amos I'll try that - but there are too things to note.. 1)I initially increased the debugging to see the auth failures - which I couldn't see - despite going to 9. In fact, I saw no difference between 1 and 2 so that's why I left it at that. 2)My logging options are to output to: 1128 access_log /var/log/squid3/access.log combined 1137 cache_log /var/log/squid3/cache.log I meant to send this out on Friday. Anacron doesn't seem to have sent me the notice since I made the change, but nonetheless, I'm curious as to why that would make a difference. My assumption is that no matter what I put the debugging level at, it should log to file, not to anacron. They are part of the configuration file loading. The system log is used for initial startup messages before the cache.log file is configured for use. debug_options takes effect immediately on being read in, but cache.log opening is done after the config load is finished and the final cache.log location is known (it can currently be specific twice or more with different filenames). Amos
RE: [squid-users] RE: Anacron log entries
From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: Wednesday, May 12, 2010 4:06 PM ons 2010-05-12 klockan 14:40 +0200 skrev Simon Brereton: /etc/cron.daily/logrotate: 2010/05/05 07:35:20.152| aclParseUserList: parsing user list 2010/05/05 07:35:20.152| aclParseUserList: parsing user list Looks like debug output. What is your debug_options directive set to? 1245 # TAG: debug_options 1246 # Logging options are set as section,level where each source file 1247 # is assigned a unique section. Lower levels result in less 1248 # output, Full debugging (level 9) can result in a very large 1249 # log file, so be careful. The magic word ALL sets debugging 1250 # levels for all sections. We recommend normally running with 1251 # ALL,1. 1252 # 1253 #Default: 1254 # debug_options ALL,1 1255 debug_options all,2 I had it as ALL, but when I increaded it to ALL,9 to do some debugging, nothing extra appeared in the logs. Google pulled up someone with the same issue - or maybe I saw it go by on the list - that writing it as all would fix that (but I'd already solved my issue). Anacron emails me these lines whether it's ALL or all.. Simon
Re: [squid-users] RE: Anacron log entries
Simon Brereton wrote: From: Henrik Nordström [mailto:hen...@henriknordstrom.net] Sent: Wednesday, May 12, 2010 4:06 PM ons 2010-05-12 klockan 14:40 +0200 skrev Simon Brereton: /etc/cron.daily/logrotate: 2010/05/05 07:35:20.152| aclParseUserList: parsing user list 2010/05/05 07:35:20.152| aclParseUserList: parsing user list Looks like debug output. What is your debug_options directive set to? 1245 # TAG: debug_options 1246 # Logging options are set as section,level where each source file 1247 # is assigned a unique section. Lower levels result in less 1248 # output, Full debugging (level 9) can result in a very large 1249 # log file, so be careful. The magic word ALL sets debugging 1250 # levels for all sections. We recommend normally running with 1251 # ALL,1. 1252 # 1253 #Default: 1254 # debug_options ALL,1 1255 debug_options all,2 I had it as ALL, but when I increaded it to ALL,9 to do some debugging, nothing extra appeared in the logs. Google pulled up someone with the same issue - or maybe I saw it go by on the list - that writing it as all would fix that (but I'd already solved my issue). Anacron emails me these lines whether it's ALL or all.. Simon Well, there you go. Debug level #2 is full of debugging traces. FWIW: level 0 - critical failure messages. level 1 - warnings and important notices level 2 thru 9 - debug traces (section specific) This is why the recommended level is 1 and not 2 or higher. Amos -- Please be using Current Stable Squid 2.7.STABLE9 or 3.1.3
Re: [squid-users] RE: Anacron log entries
ons 2010-05-12 klockan 14:40 +0200 skrev Simon Brereton: /etc/cron.daily/logrotate: 2010/05/05 07:35:20.152| aclParseUserList: parsing user list 2010/05/05 07:35:20.152| aclParseUserList: parsing user list Looks like debug output. What is your debug_options directive set to? Regards Henrik
