Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads
Thanks Alex for catching this! I was sending the wrong response. This response was related to bug report: http://bugs.squid-cache.org/show_bug.cgi?id=4117 Eliezer Eliezer Croitoru NgTech, Tech Support Mobile: +972-5-28704261 Email: ngtech1...@gmail.com -Original Message- From: squid-users On Behalf Of Alex Rousskov Sent: Wednesday, April 13, 2022 23:32 To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads On 4/13/22 16:24, Eliezer Croitoru wrote: > Can you please verify if the next is a workaround to your issue: > cache_mem 16 MB > cache deny all Just to avoid misunderstanding, bug #5055 and virtually any other bug that manifests itself in FATAL messages from noteDestinationsEnd code is unrelated to HTTP caching and is unlikely to be mitigated by changing the cache memory size and/or denying HTTP caching. Alex. > -Original Message- > From: squid-users On Behalf Of pvs > Sent: Wednesday, April 13, 2022 19:23 > To: squid-users@lists.squid-cache.org > Subject: Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads > > Thanks Alex. > > We will upgrade the squid and see if the problem recurs > > > > O 12-04-2022 19:57, Alex Rousskov wrote: >> On 4/11/22 07:26, pvs wrote: >> >>> cache.log file is attached with contents narrowed down to the time >>> just before squid process oscillating (going up and down), ultimately >>> dying. >> >> Your Squid v5.2 is probably suffering from bug #5055: >> https://bugs.squid-cache.org/show_bug.cgi?id=5055 >> >> Upgrade your Squid to v5.4.1 or later. >> >>> We tried to analyze the syslog file, squid access/cache log files, >>> not got any concrete clues. >> >> FWIW, look for messages mentioning words "FATAL": >> >>> 2022/03/02 09:05:42 kid1| FATAL: check failed: opening() >> >>> exception location: tunnel.cc(1300) noteDestinationsEnd >> >> >> >> HTH, >> >> Alex. >> ___ >> squid-users mailing list >> squid-users@lists.squid-cache.org >> http://lists.squid-cache.org/listinfo/squid-users > ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads
On 4/13/22 16:24, Eliezer Croitoru wrote: Can you please verify if the next is a workaround to your issue: cache_mem 16 MB cache deny all Just to avoid misunderstanding, bug #5055 and virtually any other bug that manifests itself in FATAL messages from noteDestinationsEnd code is unrelated to HTTP caching and is unlikely to be mitigated by changing the cache memory size and/or denying HTTP caching. Alex. -Original Message- From: squid-users On Behalf Of pvs Sent: Wednesday, April 13, 2022 19:23 To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads Thanks Alex. We will upgrade the squid and see if the problem recurs O 12-04-2022 19:57, Alex Rousskov wrote: On 4/11/22 07:26, pvs wrote: cache.log file is attached with contents narrowed down to the time just before squid process oscillating (going up and down), ultimately dying. Your Squid v5.2 is probably suffering from bug #5055: https://bugs.squid-cache.org/show_bug.cgi?id=5055 Upgrade your Squid to v5.4.1 or later. We tried to analyze the syslog file, squid access/cache log files, not got any concrete clues. FWIW, look for messages mentioning words "FATAL": 2022/03/02 09:05:42 kid1| FATAL: check failed: opening() exception location: tunnel.cc(1300) noteDestinationsEnd HTH, Alex. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads
Can you please verify if the next is a workaround to your issue: cache_mem 16 MB cache deny all Thanks, Eliezer Eliezer Croitoru NgTech, Tech Support Mobile: +972-5-28704261 Email: ngtech1...@gmail.com -Original Message- From: squid-users On Behalf Of pvs Sent: Wednesday, April 13, 2022 19:23 To: squid-users@lists.squid-cache.org Subject: Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads Thanks Alex. We will upgrade the squid and see if the problem recurs O 12-04-2022 19:57, Alex Rousskov wrote: > On 4/11/22 07:26, pvs wrote: > >> cache.log file is attached with contents narrowed down to the time >> just before squid process oscillating (going up and down), ultimately >> dying. > > Your Squid v5.2 is probably suffering from bug #5055: > https://bugs.squid-cache.org/show_bug.cgi?id=5055 > > Upgrade your Squid to v5.4.1 or later. > >> We tried to analyze the syslog file, squid access/cache log files, >> not got any concrete clues. > > FWIW, look for messages mentioning words "FATAL": > >> 2022/03/02 09:05:42 kid1| FATAL: check failed: opening() > >> exception location: tunnel.cc(1300) noteDestinationsEnd > > > > HTH, > > Alex. > ___ > squid-users mailing list > squid-users@lists.squid-cache.org > http://lists.squid-cache.org/listinfo/squid-users -- Regards, पं. विष्णु शंकर P. Vishnu Sankar टीम लीडरTeam Leader-Network Operations सी-डॉट C-DOT इलैक्ट्रॉनिक्स सिटी फेज़ IElectronics City Phase I होसूर रोड बेंगलूरु Hosur Road Bengaluru – 560100 फोन Ph91 80 25119466 -- Disclaimer : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. The sender does not accept liability for any errors or omissions in the contents of this message, which arise as a result. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads
Thanks Alex. We will upgrade the squid and see if the problem recurs O 12-04-2022 19:57, Alex Rousskov wrote: On 4/11/22 07:26, pvs wrote: cache.log file is attached with contents narrowed down to the time just before squid process oscillating (going up and down), ultimately dying. Your Squid v5.2 is probably suffering from bug #5055: https://bugs.squid-cache.org/show_bug.cgi?id=5055 Upgrade your Squid to v5.4.1 or later. We tried to analyze the syslog file, squid access/cache log files, not got any concrete clues. FWIW, look for messages mentioning words "FATAL": 2022/03/02 09:05:42 kid1| FATAL: check failed: opening() exception location: tunnel.cc(1300) noteDestinationsEnd HTH, Alex. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users -- Regards, पं. विष्णु शंकर P. Vishnu Sankar टीम लीडरTeam Leader-Network Operations सी-डॉट C-DOT इलैक्ट्रॉनिक्स सिटी फेज़ IElectronics City Phase I होसूर रोड बेंगलूरु Hosur Road Bengaluru – 560100 फोन Ph91 80 25119466 -- Disclaimer : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. The sender does not accept liability for any errors or omissions in the contents of this message, which arise as a result. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads
On 4/11/22 07:26, pvs wrote: cache.log file is attached with contents narrowed down to the time just before squid process oscillating (going up and down), ultimately dying. Your Squid v5.2 is probably suffering from bug #5055: https://bugs.squid-cache.org/show_bug.cgi?id=5055 Upgrade your Squid to v5.4.1 or later. We tried to analyze the syslog file, squid access/cache log files, not got any concrete clues. FWIW, look for messages mentioning words "FATAL": 2022/03/02 09:05:42 kid1| FATAL: check failed: opening() exception location: tunnel.cc(1300) noteDestinationsEnd HTH, Alex. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads
Hi Alex, cache.log file is attached with contents narrowed down to the time just before squid process oscillating (going up and down), ultimately dying. Regards, Vishnu On 08-04-2022 19:09, Alex Rousskov wrote: On 4/8/22 05:56, pvs wrote: > sudo /usr/squid/5.2/sbin/squid -f /etc/squid/squid.conf Next time, try starting Squid from the console/terminal using the following command: sudo /usr/squid/5.2/sbin/squid -Nd1 -f /etc/squid/squid.conf This is _not_ the right way to start Squid in production, but it is a good way to test whether you can get some error messages on the console after Squid dies during this _test_ run. > I wanted to share cache.log file, but the size is too big. You can always share a link to a (compressed) log file or at least copy-paste the last ~100 lines written just _before Squid exited_. The exiting lines, if any, would be printed above the Squid startup lines similar to these: > 2022/04/07 18:43:38.457| Created PID file (.../squid.pid) > 2022/04/07 18:43:38.459| Set Current Directory to /usr/local/squid/var > 2022/04/07 18:43:38.459| Starting Squid Cache version ... The other information you have provided was useful but not sufficient. Please keep this conversation on the squid-users list instead of responding to me personally. Thank you, Alex. > On 07-04-2022 19:09, Alex Rousskov wrote: >> On 4/7/22 00:15, pvs wrote: >> >>> On the 3rd day morning all of a sudden squid process stopped, after >>> restarting it worked 10 minutes and again stopped, this process >>> repeated and finally we removed this squid from production network. >> >>> We tried to analyze the syslog file, squid access/cache log files, >>> not got any concrete clues. >>> >>> Any clues/ideas where i can look for additional info for the squid >>> process all of a sudden dying. >> >> How do you start Squid? >> >> How many "sbin/squid" or equivalent processes are running when >> everything is working OK? >> >> You may want to share "ps aux | fgrep squid" or similar output after >> starting Squid the usual way. >> >> >> If Squid knows that it is dying, then cache.log usually has a record >> of the cause of death. Squid will often known that it is dying, but >> there are exceptions. Squid will know less if you start it with a -C >> command line option. >> >> If Squid does not know that it is dying, then whatever scripts/system >> you used to start Squid may have a record of it. Usually, those >> messages go into syslog. >> >> I know you said you looked in cache.log and syslog, but perhaps there >> are some clues there that you consider unimportant. If anything is >> logged at the time of death, consider sharing those records. >> >> >> If there are really no traces anywhere, then you are doing something >> very unusual, but you should still be able to triage the issue if you >> start Squid by hand from the terminal (add "-d1" if you are not using >> that option already) and watch the console output at the time of >> death. You will also be able to collect the exit code of the top-level >> squid process this way -- another potential clue. >> >> >> HTH, >> >> Alex. > > -- > Regards, > > पं. विष्णु शंकर P. Vishnu Sankar > टीम लीडर Team Leader-Network Operations > सी-डॉट C-DOT > इलैक्ट्रॉनिक्स सिटी फेज़ I Electronics City Phase I > होसूर रोड बेंगलूरु Hosur Road Bengaluru – 560100 > फोन Ph 91 80 25119466 > -- -- Regards, पं. विष्णु शंकर P. Vishnu Sankar टीम लीडरTeam Leader-Network Operations सी-डॉट C-DOT इलैक्ट्रॉनिक्स सिटी फेज़ IElectronics City Phase I होसूर रोड बेंगलूरु Hosur Road Bengaluru – 560100 फोन Ph91 80 25119466 -- Disclaimer : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. The sender does not accept liability for any errors or omissions in the contents of this message, which arise as a result. cache-log.rar Description: Binary data ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
Re: [squid-users] Fine tuning of Squid and OS configuration for handling more loads
On 4/8/22 05:56, pvs wrote: > sudo /usr/squid/5.2/sbin/squid -f /etc/squid/squid.conf Next time, try starting Squid from the console/terminal using the following command: sudo /usr/squid/5.2/sbin/squid -Nd1 -f /etc/squid/squid.conf This is _not_ the right way to start Squid in production, but it is a good way to test whether you can get some error messages on the console after Squid dies during this _test_ run. > I wanted to share cache.log file, but the size is too big. You can always share a link to a (compressed) log file or at least copy-paste the last ~100 lines written just _before Squid exited_. The exiting lines, if any, would be printed above the Squid startup lines similar to these: > 2022/04/07 18:43:38.457| Created PID file (.../squid.pid) > 2022/04/07 18:43:38.459| Set Current Directory to /usr/local/squid/var > 2022/04/07 18:43:38.459| Starting Squid Cache version ... The other information you have provided was useful but not sufficient. Please keep this conversation on the squid-users list instead of responding to me personally. Thank you, Alex. > On 07-04-2022 19:09, Alex Rousskov wrote: >> On 4/7/22 00:15, pvs wrote: >> >>> On the 3rd day morning all of a sudden squid process stopped, after >>> restarting it worked 10 minutes and again stopped, this process >>> repeated and finally we removed this squid from production network. >> >>> We tried to analyze the syslog file, squid access/cache log files, >>> not got any concrete clues. >>> >>> Any clues/ideas where i can look for additional info for the squid >>> process all of a sudden dying. >> >> How do you start Squid? >> >> How many "sbin/squid" or equivalent processes are running when >> everything is working OK? >> >> You may want to share "ps aux | fgrep squid" or similar output after >> starting Squid the usual way. >> >> >> If Squid knows that it is dying, then cache.log usually has a record >> of the cause of death. Squid will often known that it is dying, but >> there are exceptions. Squid will know less if you start it with a -C >> command line option. >> >> If Squid does not know that it is dying, then whatever scripts/system >> you used to start Squid may have a record of it. Usually, those >> messages go into syslog. >> >> I know you said you looked in cache.log and syslog, but perhaps there >> are some clues there that you consider unimportant. If anything is >> logged at the time of death, consider sharing those records. >> >> >> If there are really no traces anywhere, then you are doing something >> very unusual, but you should still be able to triage the issue if you >> start Squid by hand from the terminal (add "-d1" if you are not using >> that option already) and watch the console output at the time of >> death. You will also be able to collect the exit code of the top-level >> squid process this way -- another potential clue. >> >> >> HTH, >> >> Alex. > > -- > Regards, > > पं. विष्णु शंकरP. Vishnu Sankar > टीम लीडरTeam Leader-Network Operations > सी-डॉट C-DOT > इलैक्ट्रॉनिक्स सिटी फेज़ IElectronics City Phase I > होसूर रोड बेंगलूरु Hosur Road Bengaluru – 560100 > फोन Ph91 80 25119466 > -- ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
[squid-users] Fine tuning of Squid and OS configuration for handling more loads
Hello, We have setup a new squid proxy 5.2 running on Ubuntu 20.4 to provide internet access to more than 500 users without ACLs/blacklists For 2 days it worked fine except occassional 'Connection Timedout' On the 3rd day morning all of a sudden squid process stopped, after restarting it worked 10 minutes and again stopped, this process repeated and finally we removed this squid from production network. We tried to analyze the syslog file, squid access/cache log files, not got any concrete clues. Any clues/ideas where i can look for additional info for the squid process all of a sudden dying. Your help is greatly appreciated and thanks in advance -- Regards, पं. विष्णु शंकर P. Vishnu Sankar टीम लीडरTeam Leader-Network Operations सी-डॉट C-DOT इलैक्ट्रॉनिक्स सिटी फेज़ IElectronics City Phase I होसूर रोड बेंगलूरु Hosur Road Bengaluru – 560100 फोन Ph91 80 25119466 -- Disclaimer : This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. The sender does not accept liability for any errors or omissions in the contents of this message, which arise as a result. ___ squid-users mailing list squid-users@lists.squid-cache.org http://lists.squid-cache.org/listinfo/squid-users
