Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #163934 > unrolled thread

Squid3 doesn't listen on any port on Jessie

Back to article view | Back to linux.debian.user

Contents

  Squid3 doesn't listen on any port on Jessie Willy Ted MANGA <willy.manga@auf.org> - 2016-02-08 11:30 +0100
    Re: Squid3 doesn't listen on any port on Jessie <tomas@tuxteam.de> - 2016-02-08 12:00 +0100
      Re: Squid3 doesn't listen on any port on Jessie Willy Ted MANGA <willy.manga@auf.org> - 2016-02-08 12:40 +0100
    Re: Squid3 doesn't listen on any port on Jessie Ron Leach <ronleach@tesco.net> - 2016-02-08 13:00 +0100
      Re: Squid3 doesn't listen on any port on Jessie Willy Ted MANGA <willy.manga@auf.org> - 2016-02-08 13:30 +0100
        Re: Squid3 doesn't listen on any port on Jessie <tomas@tuxteam.de> - 2016-02-08 22:10 +0100

#163934 — Squid3 doesn't listen on any port on Jessie

[Multipart message — attachments visible in raw view] — view raw

Hello,
I just upgraded my server from wheezy to jessie and my squid3 doesn't
listen to any port . :-\

I even remove all my settings and just modify `http_port` directive to
`http_port 3128 intercept` . But I doesn't work either .

I have attached an excerpt of the cache.log .


I don't know what's wrong .

-- 
Cordialement,
Willy Ted MANGA

[toc] | [next] | [standalone]

#163935

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 08, 2016 at 11:20:30AM +0100, Willy Ted MANGA wrote:
> Hello,
> I just upgraded my server from wheezy to jessie and my squid3 doesn't
> listen to any port . :-\
> 
> I even remove all my settings and just modify `http_port` directive to
> `http_port 3128 intercept` . But I doesn't work either .
> 
> I have attached an excerpt of the cache.log .
> 
> 
> I don't know what's wrong .
> 
> -- 
> Cordialement,
> Willy Ted MANGA

> 2016/02/08 09:39:17 kid1| Set Current Directory to /var/spool/squid3
[...]
> 2016/02/08 09:39:17 kid1| ERROR: No forward-proxy ports configured.
> 2016/02/08 09:39:17 kid1| ERROR: No forward-proxy ports configured.

I can't say this is the problem, but the Interwebs come up with this:

  <http://wiki.squid-cache.org/KnowledgeBase/NoForwardProxyPorts>

What do you see when you issue "netstat -antp" (as root/sudo)?
Is squid listening on anything? Is anything else listening on
port 3128?

regards
- -- t
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAla4a1MACgkQBcgs9XrR2kZYGQCff1EK2WOSD8Y12MfRbYtLGq6j
voEAn1eoBh1S2duSomA/3WXLOnpxZUVb
=zMiY
-----END PGP SIGNATURE-----

[toc] | [prev] | [next] | [standalone]

#163936

[Multipart message — attachments visible in raw view] — view raw

Hello,

Le 08/02/2016 11:17, tomas@tuxteam.de a écrit :
> On Mon, Feb 08, 2016 at 11:20:30AM +0100, Willy Ted MANGA wrote:
>> [...] 2016/02/08 09:39:17 kid1| ERROR: No forward-proxy ports
>> configured. 2016/02/08 09:39:17 kid1| ERROR: No forward-proxy
>> ports configured.
>
> I can't say this is the problem, but the Interwebs come up with
> this:
>
> <http://wiki.squid-cache.org/KnowledgeBase/NoForwardProxyPorts>

I saw this page earlier but I'm not sure to understand the solution.
Nothing is using the 3128 right now.

I tried without interception too ; squid doesn't listen either.

>
> What do you see when you issue "netstat -antp" (as root/sudo)? Is
> squid listening on anything? Is anything else listening on port
> 3128?

nothing as you can see in my attachment :(


-- 
Cordialement,
Willy Ted MANGA

[toc] | [prev] | [next] | [standalone]

#163937

On 08/02/2016 10:20, Willy Ted MANGA wrote:
> Hello,
> I just upgraded my server from wheezy to jessie and my squid3 doesn't
> listen to any port . :-\
>


We just had a similar problem with a new squid 3 install on another 
distro.  (For historical reasons we have one old server running 
Fedora, just updated to Fedora 23 "server" configuration.)

In our case, squid was 'listening' fine on 3128 - but it wasn't 
'hearing' anything; the firewall was completely locked down in that 
last Fedora update (only port 22 was open, if I recall).  I mention 
this because, though we don't use Jessie, that Fedora update uses 
systemd, and SElinux(?) and this very restrictive firewall 
configuration, out of the box.  Even installing squid did *not* open 
the port 3128; the firewall had to adjusted by hand, and then squid 
worked fine.

As I say, we're still on Wheezy with our remaining systems, so I don't 
know whether Jessie is closer to that Fedora arrangement, or not, but 
thought this experience might help.

Have you also checked the squid/jessie configuration notes?  In moving 
to systemd on our fedora system, some of the 'conf' files moved from 
/etc/... to /usr/... and this seemed to be a consequence of systemd 
(in Fedora's case), but I don't know what happens in Jessie.  Just to 
check whether the conf files you are changing are the ones being used.

Ron

[toc] | [prev] | [next] | [standalone]

#163938

Hi,

Le 08/02/2016 12:28, Ron Leach a écrit :
> On 08/02/2016 10:20, Willy Ted MANGA wrote:
>> Hello,
>> I just upgraded my server from wheezy to jessie and my squid3 doesn't
>> listen to any port . :-\
>>
>[...] 
> 
> We just had a similar problem with a new squid 3 install on another
> distro.  (For historical reasons we have one old server running Fedora,
> just updated to Fedora 23 "server" configuration.)
> 
> In our case, squid was 'listening' fine on 3128 - but it wasn't
> 'hearing' anything; the firewall was completely locked down in that last
> Fedora update (only port 22 was open, if I recall).  I mention this
> because, though we don't use Jessie, that Fedora update uses systemd,
> and SElinux(?) and this very restrictive firewall configuration, out of
> the box.  Even installing squid did *not* open the port 3128; the
> firewall had to adjusted by hand, and then squid worked fine.

In my case the firewall rules are OK. Squid do not listen at all.


> As I say, we're still on Wheezy with our remaining systems, so I don't
> know whether Jessie is closer to that Fedora arrangement, or not, but
> thought this experience might help.

Jessie comes with systemd by default.


> Have you also checked the squid/jessie configuration notes?  In moving
> to systemd on our fedora system, some of the 'conf' files moved from
> /etc/... to /usr/... and this seemed to be a consequence of systemd (in
> Fedora's case), but I don't know what happens in Jessie.  Just to check
> whether the conf files you are changing are the ones being used.

The conf files remain at the same place. But I suspect a strange
behavior of systemd .

It's not the same issue as #800341 [1] but at first launch I got a
bungled file because of misconfiguration. I fixed it but it did not
solve the issue on port .


1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800341



-- 
Cordialement,
Willy Ted MANGA

[toc] | [prev] | [next] | [standalone]

#163955

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Feb 08, 2016 at 01:24:24PM +0100, Willy Ted MANGA wrote:
> Hi,

[...]

> In my case the firewall rules are OK. Squid do not listen at all.

[...]

> Jessie comes with systemd by default.

[...]

> The conf files remain at the same place. But I suspect a strange
> behavior of systemd .
> 
> It's not the same issue as #800341 [1] but at first launch I got a
> bungled file because of misconfiguration. I fixed it but it did not
> solve the issue on port .
> 
> 
> 1. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800341

What happens if you try to start squid "by hand", once the computer
is running? I mean not via sysctl? Perhaps use option -N to keep it
in foreground.

You might thus differentiate whether it's an init problem or a squid
config problem.

Do the systemd logs say anything?

Regards
- -- tomás
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iEYEARECAAYFAla4+lMACgkQBcgs9XrR2ka/7gCeMWsyhVEA4ItfGRnvKW/0eIOo
ersAniAzpXidMGZ50BDHe6OZ3QmGIDaF
=FYtZ
-----END PGP SIGNATURE-----

[toc] | [prev] | [standalone]

Back to top | Article view | linux.debian.user

csiph-web