<font size=2 face="sans-serif">Hi Antony,</font>
<br><font size=2 face="sans-serif">I found where was the issue,</font>
<br><font size=2 face="sans-serif">Actually access given to the site was
based on LDAP group membership when user try to launch recording from site,
the .wax file will be played from local machine IP , which is getting blocked.</font>
<br><font size=2 face="sans-serif">created ACL to allow specific ip to
access the Site and it worked.</font>
<br><font size=2 face="sans-serif">Thank for point to direction to review
log file</font>
<br>
<br><font size=2 face="sans-serif">Thanks & Regards<br>
Nilesh Suresh Gavali<br>
</font>
<br>
<br>
<br>
<br><font size=1 color=#5f5f5f face="sans-serif">From:
</font><font size=1 face="sans-serif">squid-users-request@lists.squid-cache.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">To:
</font><font size=1 face="sans-serif">squid-users@lists.squid-cache.org</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Date:
</font><font size=1 face="sans-serif">07/11/2017 12:47</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Subject:
</font><font size=1 face="sans-serif">squid-users
Digest, Vol 39, Issue 10</font>
<br><font size=1 color=#5f5f5f face="sans-serif">Sent by:
</font><font size=1 face="sans-serif">"squid-users"
<squid-users-bounces@lists.squid-cache.org></font>
<br>
<hr noshade>
<br>
<br>
<br><tt><font size=2>Send squid-users mailing list submissions to<br>
squid-users@lists.squid-cache.org<br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
</font></tt><a href="http://lists.squid-cache.org/listinfo/squid-users"><tt><font size=2>http://lists.squid-cache.org/listinfo/squid-users</font></tt></a><tt><font size=2><br>
or, via email, send a message with subject or body 'help' to<br>
squid-users-request@lists.squid-cache.org<br>
<br>
You can reach the person managing the list at<br>
squid-users-owner@lists.squid-cache.org<br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of squid-users digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. window media player can not play .wax file via Squid
proxy<br>
(Nilesh Gavali)<br>
2. Re: window media player can not play .wax file via
Squid<br>
proxy (Antony Stone)<br>
3. Squid and CPU 100% (Vieri)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Mon, 6 Nov 2017 12:22:11 +0000<br>
From: Nilesh Gavali <nilesh.gavali@tcs.com><br>
To: squid-users@lists.squid-cache.org<br>
Subject: [squid-users] window media player can not play .wax file via<br>
Squid
proxy<br>
Message-ID:<br>
<OF06172801.D41F2471-ON802581D0.00435D9F-802581D0.0043F244@tcs.com><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Hi Team.<br>
We are having squid deployed for users which work well for browsing <br>
internet. Recently we received complaint from some users who access one
of <br>
the vendor URL to listen audio recordings.<br>
The procedure they follow as<br>
login to Vendor portal URL via squid proxy<br>
select recording option<br>
select recording , it will get downloaded as .wax file<br>
user open .wax file in media player after which they get error message
as <br>
unable to play media.<br>
<br>
I checked the .wax file which contains link to media file on their same
<br>
portal URL. but window media player cant access it.<br>
<br>
Not sure what is wrong here. I traced squid access logs and able to see
<br>
the request going to vendor portal but still window media player cant play
<br>
this file<br>
<br>
Need urgent help if anyone work on this kind of requirement.<br>
<br>
<br>
Thanks & Regards<br>
Nilesh Suresh Gavali<br>
=====-----=====-----=====<br>
Notice: The information contained in this e-mail<br>
message and/or attachments to it may contain <br>
confidential or privileged information. If you are <br>
not the intended recipient, any dissemination, use, <br>
review, distribution, printing or copying of the <br>
information contained in this e-mail message <br>
and/or attachments to it are strictly prohibited. If <br>
you have received this communication in error, <br>
please notify us by reply e-mail or telephone and <br>
immediately and permanently delete the message <br>
and any attachments. Thank you<br>
<br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <</font></tt><a href="http://lists.squid-cache.org/pipermail/squid-users/attachments/20171106/44c0b16c/attachment-0001.html"><tt><font size=2>http://lists.squid-cache.org/pipermail/squid-users/attachments/20171106/44c0b16c/attachment-0001.html</font></tt></a><tt><font size=2>><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Mon, 6 Nov 2017 12:36:07 +0000<br>
From: Antony Stone <Antony.Stone@squid.open.source.it><br>
To: squid-users@lists.squid-cache.org<br>
Subject: Re: [squid-users] window media player can not play .wax file<br>
via
Squid proxy<br>
Message-ID: <201711061236.07563.Antony.Stone@squid.open.source.it><br>
Content-Type: Text/Plain; charset="iso-8859-15"<br>
<br>
On Monday 06 November 2017 at 12:22:11, Nilesh Gavali wrote:<br>
<br>
> Hi Team.<br>
> We are having squid deployed for users which work well for browsing<br>
> internet. Recently we received complaint from some users who access
one of<br>
> the vendor URL to listen audio recordings.<br>
> The procedure they follow as<br>
> login to Vendor portal URL via squid proxy<br>
> select recording option<br>
> select recording , it will get downloaded as .wax file<br>
> user open .wax file in media player after which they get error message
as<br>
> unable to play media.<br>
> <br>
> I checked the .wax file which contains link to media file on their
same<br>
> portal URL. but window media player cant access it.<br>
<br>
What type of URL is it? HTTP? HTTPS? Something else?<br>
<br>
> Not sure what is wrong here. I traced squid access logs and able to
see<br>
> the request going to vendor portal<br>
<br>
Which request?<br>
<br>
The browser request for the .wax file, or the media player request for
the <br>
actual media file?<br>
<br>
> but still window media player cant play this file<br>
<br>
It basically sounds as though either:<br>
<br>
- Windows media player is trying to access a URL directly without
going <br>
through the proxy, or<br>
<br>
- Windows media player is requesting a URL type which Squid can't handle<br>
<br>
Tell us what URLs you're seeing in the access log, and what URL is contained
<br>
in the .wax file - that might give us more of a clue.<br>
<br>
<br>
Antony.<br>
<br>
-- <br>
Douglas was one of those writers who honourably failed to get anywhere
with <br>
'weekending'. It put a premium on people who could write things that
lasted <br>
thirty seconds, and Douglas was incapable of writing a single sentence
that <br>
lasted less than thirty seconds.<br>
<br>
- Geoffrey Perkins, about Douglas Adams<br>
<br>
Please reply to the list;<br>
please *don't* CC me.<br>
<br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Tue, 7 Nov 2017 11:42:11 +0000 (UTC)<br>
From: Vieri <rentorbuy@yahoo.com><br>
To: "squid-users@lists.squid-cache.org"<br>
<squid-users@lists.squid-cache.org><br>
Subject: [squid-users] Squid and CPU 100%<br>
Message-ID: <348071111.3798275.1510054931204@mail.yahoo.com><br>
Content-Type: text/plain; charset=UTF-8<br>
<br>
Sorry to bring this back up, but every now and then (few days) I need to
restart squid because its CPU usage goes up to 100% for a long time (irresponsive).<br>
<br>
Right before restarting Squid:<br>
<br>
# free [11/07/17 11:18:52]<br>
total used free shared buff/cache available<br>
Mem: 32865056 14811320 1374212 157028 16679524 17557656<br>
Swap: 37036988 287320 36749668<br>
<br>
# squidclient mgr:info [11/07/17 11:18:52]<br>
<br>
# squidclient mgr:mem [11/07/17 11:19:02]<br>
<br>
# squidclient mgr:storedir [11/07/17 11:19:22]<br>
<br>
# squidclient mgr:filedescriptors [11/07/17 11:19:42]<br>
<br>
# squidclient mgr:events [11/07/17 11:20:12]<br>
<br>
In other words, squidclient does not get any info from squid (waited max
30 seconds - maybe I need to wait more).<br>
<br>
I also dumped an strace here:<br>
</font></tt><a href="https://drive.google.com/file/d/1yed-sNWrc6KBQSOV7KPbrYOForwwtkCe/view?usp=sharing"><tt><font size=2>https://drive.google.com/file/d/1yed-sNWrc6KBQSOV7KPbrYOForwwtkCe/view?usp=sharing</font></tt></a><tt><font size=2><br>
<br>
You probably won't be able to draw any conclusions so I'll try to update
to squid-3.5.27-20171101-re69e56c (I'm now running 3.5.27-20170916-re69e56c).<br>
<br>
Note that stopping Squid with:<br>
<br>
/usr/sbin/squid -k shutdown -f /etc/squid/squid.conf -n squid<br>
<br>
takes a LONG time, but it eventually does stop (the process dies out).<br>
<br>
I can then restart it cleanly.<br>
<br>
I don't need to kill the pid (unless I'm told to hurry up).<br>
<br>
After checking the log I can see these messages:<br>
<br>
2017/11/07 11:16:59 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:16:59 kid1| comm_open: socket failure: (24) Too many open
files<br>
<br>
Now, you can notice that the max_filedescriptors is quite high, and was
set correctly before and after the issue I'm reporting:<br>
<br>
# tail -n 100000 /var/log/squid/cache.log | grep -i descript<br>
2017/11/06 06:36:14 kid1| With 32768 file descriptors available<br>
2017/11/07 11:15:15 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:15:31 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:16:13 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:16:59 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:17:35 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:17:51 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:18:07 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:18:25 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:18:45 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:19:03 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:19:19 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:19:35 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:19:53 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:20:09 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:20:28 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:20:44 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:21:01 kid1| WARNING! Your cache is running out of filedescriptors<br>
2017/11/07 11:23:05 kid1| With 32768 file descriptors available<br>
<br>
So I'm worried that 32768 may not be enough.<br>
Is this weird, or should I really increase this value?<br>
<br>
Thanks,<br>
<br>
Vieri<br>
<br>
<br>
------------------------------<br>
<br>
Subject: Digest Footer<br>
<br>
_______________________________________________<br>
squid-users mailing list<br>
squid-users@lists.squid-cache.org<br>
</font></tt><a href="http://lists.squid-cache.org/listinfo/squid-users"><tt><font size=2>http://lists.squid-cache.org/listinfo/squid-users</font></tt></a><tt><font size=2><br>
<br>
<br>
------------------------------<br>
<br>
End of squid-users Digest, Vol 39, Issue 10<br>
*******************************************<br>
</font></tt>
<br>