[squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-12 Thread Priya Agarwal
Hi, I know this must be a very common error. But I am unable to remove it. My permissions are set correct. Network connection is also fine. Here is my log: root@t4240qds:~# /usr/sbin/squid -NCd1 2015/02/12 11:44:06| Set Current Directory to /var/cache/squid 2015/02/12 11:44:06| Starting Squid Cac

[squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-08-28 Thread Howard Waterfall
Ubuntu 14.04 Squid 3.5.5 Hi - I'm having pretty much exactly the same problem as Priya. I didn't see a resolution so I'm picking up the thread. I've installed and run squid 3.5.5 previously w/o a problem using: sudo apt-get install squid I want to filter by mac address though, so I purged that

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-12 Thread Antony Stone
On Thursday 12 Feb 2015 at 11:01, Priya Agarwal wrote: > My permissions are set correct. Please show us the output of: ls -al /var/logs/access.log > 2015/02/12 11:44:06| Logfile: opening log daemon:/var/logs/access.log > 2015/02/12 11:44:06| Logfile Daemon: opening log /var/logs/access.log > 20

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-12 Thread Amos Jeffries
On 13/02/2015 12:08 a.m., Antony Stone wrote: > On Thursday 12 Feb 2015 at 11:01, Priya Agarwal wrote: > >> My permissions are set correct. > > Please show us the output of: > > ls -al /var/logs/access.log ... and squid -v > >> 2015/02/12 11:44:06| Logfile: opening log daemon:/var/logs/acces

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-12 Thread Priya Agarwal
These are the output: root@t4240qds:~# /usr/sbin/squid ls -al /var/logs/access.log 2015/02/13 04:38:18| http_port_port: missing Port: l FATAL: Bungled (null) line 0: Squid Cache (Version 3.4.7): Terminated abnormally. CPU Usage: 0.006 seconds = 0.003 user + 0.003 sys Maximum Resident Size: 11056 K

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Antony Stone
On Friday 13 Feb 2015 at 03:53, Priya Agarwal wrote: > These are the output: > > root@t4240qds:~# /usr/sbin/squid ls -al /var/logs/access.log Thanks, but I asked for the output of ls -al /var/logs/access.log There is no squid command in there. All I want to see is that this file (and

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Antony Stone
On Friday 13 Feb 2015 at 09:12, Antony Stone wrote: > On Friday 13 Feb 2015 at 03:53, Priya Agarwal wrote: > > These are the output: > > > > root@t4240qds:~# /usr/sbin/squid ls -al /var/logs/access.log > > Thanks, but I asked for the output of > > ls -al /var/logs/access.log > > There is

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Priya Agarwal
So sorry. In squid.conf I had done cache_effective_user to nobody and set permissions of /var and /usr to nobody. So those are the permissions. root@t4240qds:/var/logs# ls -al /var/logs/access.log ls: cannot access /var/logs/access.log: No such file or directory root@t4240qds:/var/logs# ls -ld /va

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Antony Stone
On Friday 13 Feb 2015 at 11:06, Priya Agarwal wrote: > So sorry. In squid.conf I had done cache_effective_user to nobody and set > permissions of /var and /usr to nobody. So those are the permissions. Are you saying that /var is owned by 'nobody'? That sounds like a problem for the system to me.

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Priya Agarwal
Then It is unable to write cache.log: Here is the output: root@t4240qds:~# /usr/sbin/squid -k parse 2015/02/13 12:27:14| Startup: Initializing Authentication Schemes ... 2015/02/13 12:27:14| Startup: Initialized Authentication Scheme 'basic' 2015/02/13 12:27:14| Startup: Initialized Authentication

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Priya Agarwal
root@t4240qds:~# chown -R nobody:nogroup /var/logs root@t4240qds:~# /usr/sbin/squid -k parse 2015/02/13 12:27:14| Startup: Initializing Authentication Schemes ... 2015/02/13 12:27:14| Startup: Initialized Authentication Scheme 'basic' 2015/02/13 12:27:14| Startup: Initialized Authentication Scheme

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Amos Jeffries
On 14/02/2015 12:45 a.m., Priya Agarwal wrote: > root@t4240qds:~# chown -R nobody:nogroup /var/logs STOP!!! You are demonstrating in the last few posts that you do not understand how the command line tools or the permissions work. Please stop right now from doing anything on your own. This may

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-13 Thread Priya Agarwal
In the adduser command --disabled-login and --disabled password options are not there in my system. Got this: root@t4240qds:~# adduser --system --no-create-home \ > --disabled-login --disabled-password \ > --ingroup squid squid adduser: unrecognized option '--disabled-login' Tinylogin v1.4 (2015.0

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-02-14 Thread Amos Jeffries
On 14/02/2015 6:13 p.m., Priya Agarwal wrote: > > I had also set the permission of '/usr ' to nobody. I can reboot my system > with the default permissions if I have screwd up my system way too much. If Okay. Do that. Then let me know what the output is from: ls -la /var ls -la /var/logs

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-08-28 Thread Howard Waterfall
Sorry, I thought that by copying the subject line of Priya's message thread, I would have continued the thread. Here's the link for context: http://lists.squid-cache.org/pipermail/squid-users/2015-February/002131.html Cheers, Deiter On Fri, Aug 28, 2015 at 8:31 AM, Howard Waterfall wrote: > Ubu

Re: [squid-users] logfileHandleWrite: daemon:/var/logs/access.log: error writing ((32) Broken pipe)

2015-08-30 Thread Howard Waterfall
Resolved; well sort of! I've been setting up log file permissions to jibe with the *cache_effective_user* tag in /etc/squid3/squid.conf, which I had set to squid. As I was troubleshooting, I also changed the *http_port* tag from 8080, but I noticed the output when I tried starting squid remained 8