[squid-users] PID file /var/run/squid.pid not readable AND Supervising process XXX which is not our child

[Roberto Carna]

Dear, my problem is that I have two different implementations of Squid
/ Dansguardian for just 40/50 users for navigation, and sometimes the
web browsing is too slow without any clue about this, it's just better
if I restart both daemons:

1) squid 3.5.23-5+deb9u1 / dansguardian
2.10.1.1-5.1+b4
2) squid3 3.1.20-2.2+deb7u8 /
dansguardian 2.10.1.1-5+b1

I've adjusted both configurations but the problem of slow navigation
appears always.

So I'm thinking maybe is a problem of this packages combination (squid
+ dansguardian)...

Do you recommend upgrade to Debian testing version packages or just to
usetry with Squid + Squidguard ??'?

Special thanks !!!

Regards.

Dear Amos, thanks for your response.
Just a short question: if I continue using my currenbt Squid version
with " squid.service: PID file /var/run/squid.pid not readable"
warning...can I have any problem or it doesn't represent any problem?

It represents a problem, because systemd may interfere with the
auto-restart built into Squid in the event of crashes etc.
However, that problem wont affect normal operation, just the crash
handling and startup/shutdown processes of Squid. So YMMV whether that
is an issue relevant to your installation.
HTH
Amos
_______________________________________________
squid-users mailing list
http://lists.squid-cache.org/listinfo/squid-users

[Amos Jeffries]

Post by Roberto Carna
Dear, my problem is that I have two different implementations of Squid
/ Dansguardian for just 40/50 users for navigation, and sometimes the
web browsing is too slow without any clue about this, it's just better
1) squid 3.5.23-5+deb9u1 / dansguardian
2.10.1.1-5.1+b4
2) squid3 3.1.20-2.2+deb7u8 /
dansguardian 2.10.1.1-5+b1
I've adjusted both configurations but the problem of slow navigation
appears always.
So I'm thinking maybe is a problem of this packages combination (squid
+ dansguardian)...
Do you recommend upgrade to Debian testing version packages or just to
usetry with Squid + Squidguard ??'?

I certainly recommend upgrading the 3.1 package to 3.5 on general
principles - it has a lot of problems that are resolved in 3.5. Is/was
there a specific reason for that old version to still be present?


You should probably try the v4 squid package and see if it is better.
Without knowing the actual reason for the delays I'm reluctant to make a
specific recommendation for any software.


Amos

[Alex K]

Getting back to this, I face also issues that seems to be related with how
systemd handles squid.
Frequently when I try restart the VM the VM is stuch at stopping squid and
it never restarts.

Checking the differences between the autogenerated service file and the one
shipped with squid I see:

diff /run/systemd/generator.late/squid.service
squid3-3.5.23/tools/systemd/squid.service
1c1,6
< # Automatically generated by systemd-sysv-generator
---

## Copyright (C) 1996-2016 The Squid Software Foundation and contributors
##
## Squid software is distributed under GPLv2+ license and includes
## contributions from numerous individuals and organizations.
## Please see the COPYING and CONTRIBUTORS files for details.
##

4,14c9,10
< Documentation=man:systemd-sysv-generator(8)
< SourcePath=/etc/init.d/squid
< Description=LSB: Squid HTTP Proxy version 3.x
< Before=multi-user.target
< Before=multi-user.target
< Before=multi-user.target
< Before=graphical.target
< After=network-online.target
< After=remote-fs.target
< After=nss-lookup.target
< Wants=network-online.target
---

Description=Squid Web Proxy Server
After=network.target

17,20c13,15
< Type=forking
< Restart=no
< TimeoutSec=5min
< IgnoreSIGPIPE=no
---

Type=simple
ExecStart=/usr/sbin/squid -sYC -N
ExecReload=/bin/kill -HUP $MAINPID

22,28c17,19
< GuessMainPID=no
< RemainAfterExit=no
< PIDFile=/var/run/squid.pid
< SuccessExitStatus=5 6
< ExecStart=/etc/init.d/squid start
< ExecStop=/etc/init.d/squid stop
< ExecReload=/etc/init.d/squid reload
---

[Install]
WantedBy=multi-user.target

So do I just overwrite the squid.service of the system with the one
shipped with squid?

Thanx,
Alex

Dear, I have Squid/Dansguardian in a Debian 9 server.
squid 3.5.23-5+deb9u1

...

systemd[1]: squid.service: PID file /var/run/squid.pid not readable
(yet?) after start: No such file or directory
systemd[1]: squid.service: Supervising process 895 which is not our
child. We'll most likely not notice when it exits.
Is it normal or do I have to solve these? I repeat Squid is running OK...

systemd cannot cope with daemons like Squid-3. All you can do for now is
ensure that you use the init.d scripts to manage Squid. Do not use the
"service ..." commands provided by systemd.
Squid-4 packages that resolve these issues are in Debian experimental
awaiting an official upstream stable release.
NP: the major bugs preventing upstream stable are not affecting the
Debian package features. You can use the Squid-4 package now if you wish
by adding that "experimental" repository to your apt sources.list,
update apt, then install/upgrade Squid with "apt-get -t experimental
install squid".
Amos
_______________________________________________
squid-users mailing list
http://lists.squid-cache.org/listinfo/squid-users

[Alex K]

After proceeding with using the shipped service file, then systemctl
daemon-reload I do not experience any stuck reboots at the moment.

Alex

Post by Alex K
Getting back to this, I face also issues that seems to be related with how
systemd handles squid.
Frequently when I try restart the VM the VM is stuch at stopping squid and
it never restarts.
Checking the differences between the autogenerated service file and the
diff /run/systemd/generator.late/squid.service
squid3-3.5.23/tools/systemd/squid.service
1c1,6
< # Automatically generated by systemd-sysv-generator
---

## Copyright (C) 1996-2016 The Squid Software Foundation and contributors
##
## Squid software is distributed under GPLv2+ license and includes
## contributions from numerous individuals and organizations.
## Please see the COPYING and CONTRIBUTORS files for details.
##

4,14c9,10
< Documentation=man:systemd-sysv-generator(8)
< SourcePath=/etc/init.d/squid
< Description=LSB: Squid HTTP Proxy version 3.x
< Before=multi-user.target
< Before=multi-user.target
< Before=multi-user.target
< Before=graphical.target
< After=network-online.target
< After=remote-fs.target
< After=nss-lookup.target
< Wants=network-online.target
---

Description=Squid Web Proxy Server
After=network.target

17,20c13,15
< Type=forking
< Restart=no
< TimeoutSec=5min
< IgnoreSIGPIPE=no
---

Type=simple
ExecStart=/usr/sbin/squid -sYC -N
ExecReload=/bin/kill -HUP $MAINPID

22,28c17,19
< GuessMainPID=no
< RemainAfterExit=no
< PIDFile=/var/run/squid.pid
< SuccessExitStatus=5 6
< ExecStart=/etc/init.d/squid start
< ExecStop=/etc/init.d/squid stop
< ExecReload=/etc/init.d/squid reload
---

[Install]
WantedBy=multi-user.target

So do I just overwrite the squid.service of the system with the one
shipped with squid?
Thanx,
Alex

Dear, I have Squid/Dansguardian in a Debian 9 server.
squid 3.5.23-5+deb9u1

...

systemd[1]: squid.service: PID file /var/run/squid.pid not readable
(yet?) after start: No such file or directory
systemd[1]: squid.service: Supervising process 895 which is not our
child. We'll most likely not notice when it exits.
Is it normal or do I have to solve these? I repeat Squid is running

OK...
systemd cannot cope with daemons like Squid-3. All you can do for now is
ensure that you use the init.d scripts to manage Squid. Do not use the
"service ..." commands provided by systemd.
Squid-4 packages that resolve these issues are in Debian experimental
awaiting an official upstream stable release.
NP: the major bugs preventing upstream stable are not affecting the
Debian package features. You can use the Squid-4 package now if you wish
by adding that "experimental" repository to your apt sources.list,
update apt, then install/upgrade Squid with "apt-get -t experimental
install squid".
Amos
_______________________________________________
squid-users mailing list
http://lists.squid-cache.org/listinfo/squid-users

[Eliezer Croitoru]

Hey Alex,



What OS exactly is shipping this service file?


Thanks,

Eliezer



----

<http://ngtech.co.il/lmgtfy/> Eliezer Croitoru
Linux System Administrator
Mobile: [phone]
Email: ***@ngtech.co.il





From: squid-users <squid-users-***@lists.squid-cache.org> On Behalf Of Alex K
Sent: Saturday, June 9, 2018 16:31
To: Amos Jeffries <***@treenet.co.nz>
Cc: squid-***@lists.squid-cache.org
Subject: Re: [squid-users] PID file /var/run/squid.pid not readable AND Supervising process XXX which is not our child



Getting back to this, I face also issues that seems to be related with how systemd handles squid.

Frequently when I try restart the VM the VM is stuch at stopping squid and it never restarts.



Checking the differences between the autogenerated service file and the one shipped with squid I see:



diff /run/systemd/generator.late/squid.service squid3-3.5.23/tools/systemd/squid.service
1c1,6
< # Automatically generated by systemd-sysv-generator
---

## Copyright (C) 1996-2016 The Squid Software Foundation and contributors
##
## Squid software is distributed under GPLv2+ license and includes
## contributions from numerous individuals and organizations.
## Please see the COPYING and CONTRIBUTORS files for details.
##

4,14c9,10
< Documentation=man:systemd-sysv-generator(8)
< SourcePath=/etc/init.d/squid
< Description=LSB: Squid HTTP Proxy version 3.x
< Before=multi-user.target
< Before=multi-user.target
< Before=multi-user.target
< Before=graphical.target
< After=network-online.target
< After=remote-fs.target
< After=nss-lookup.target
< Wants=network-online.target
---

Description=Squid Web Proxy Server
After=network.target

17,20c13,15
< Type=forking
< Restart=no
< TimeoutSec=5min
< IgnoreSIGPIPE=no
---

Type=simple
ExecStart=/usr/sbin/squid -sYC -N
ExecReload=/bin/kill -HUP $MAINPID

22,28c17,19
< GuessMainPID=no
< RemainAfterExit=no
< PIDFile=/var/run/squid.pid
< SuccessExitStatus=5 6
< ExecStart=/etc/init.d/squid start
< ExecStop=/etc/init.d/squid stop
< ExecReload=/etc/init.d/squid reload
---

[Install]
WantedBy=multi-user.target

So do I just overwrite the squid.service of the system with the one shipped with squid?



Thanx,

Alex

Dear, I have Squid/Dansguardian in a Debian 9 server.
squid 3.5.23-5+deb9u1

...

systemd[1]: squid.service: PID file /var/run/squid.pid not readable
(yet?) after start: No such file or directory
systemd[1]: squid.service: Supervising process 895 which is not our
child. We'll most likely not notice when it exits.
Is it normal or do I have to solve these? I repeat Squid is running OK...

systemd cannot cope with daemons like Squid-3. All you can do for now is
ensure that you use the init.d scripts to manage Squid. Do not use the
"service ..." commands provided by systemd.

Squid-4 packages that resolve these issues are in Debian experimental
awaiting an official upstream stable release.
NP: the major bugs preventing upstream stable are not affecting the
Debian package features. You can use the Squid-4 package now if you wish
by adding that "experimental" repository to your apt sources.list,
update apt, then install/upgrade Squid with "apt-get -t experimental
install squid".

Amos

[Amos Jeffries]

Post by Eliezer Croitoru
Hey Alex,
What OS exactly is shipping this service file?
3.5.23-5+deb9u1

Current Debian stable. It is not shipped exactly, but generates on
install from the init.d file inserv headers in the absence of a shipped
.service.

"
# Automatically generated by systemd-sysv-generator
SourcePath=/etc/init.d/squid
"


Amos

[Eliezer Croitoru]

It was hard for me to understand the diff\patch without the original file in plain text.
< GuessMainPID=no
< RemainAfterExit=no
< PIDFile=/var/run/squid.pid
< SuccessExitStatus=5 6
< ExecStart=/etc/init.d/squid start
< ExecStop=/etc/init.d/squid stop
< ExecReload=/etc/init.d/squid reload

The above now makes more sense but.. replacing the service file and removing the /etc/init.d/squid file should be the real way to run squid.
I do not know if and when Debian Stable would upgrade their package but as long as you don't upgrade it automatically it would be suffice.

Eliezer

----
Eliezer Croitoru
Linux System Administrator
Mobile: [phone]
Email: ***@ngtech.co.il



-----Original Message-----
From: Amos Jeffries <***@treenet.co.nz>
Sent: Monday, June 11, 2018 09:25
To: Eliezer Croitoru <***@ngtech.co.il>; 'Alex K' <***@gmail.com>
Cc: squid-***@lists.squid-cache.org
Subject: Re: [squid-users] PID file /var/run/squid.pid not readable AND Supervising process XXX which is not our child

Post by Eliezer Croitoru
Hey Alex,
What OS exactly is shipping this service file?
3.5.23-5+deb9u1

Current Debian stable. It is not shipped exactly, but generates on
install from the init.d file inserv headers in the absence of a shipped
.service.

"
# Automatically generated by systemd-sysv-generator
SourcePath=/etc/init.d/squid
"


Amos

[Amos Jeffries]

Post by Eliezer Croitoru
It was hard for me to understand the diff\patch without the original file in plain text.
< GuessMainPID=no
< RemainAfterExit=no
< PIDFile=/var/run/squid.pid
< SuccessExitStatus=5 6
< ExecStart=/etc/init.d/squid start
< ExecStop=/etc/init.d/squid stop
< ExecReload=/etc/init.d/squid reload
The above now makes more sense but.. replacing the service file and removing the /etc/init.d/squid file should be the real way to run squid.

That assumes that systemd is going to be the init. Debian allows user
replacement of the init system with at least three to choose from. So
multiple init files need to be installed. This is just how it handles
the absence of a .service file for the newer default init while packages
transition to supporting both.

Amos

[Alex K]

Hi,

Had no more issues after using the service file shipped with source code.

What I did was:
cp squid.service /etc/systemd/system
systemctl daemon-reload
systemctl enable squid
systemctl start squid

Alex

Post by Eliezer Croitoru
It was hard for me to understand the diff\patch without the original file in plain text.
< GuessMainPID=no
< RemainAfterExit=no
< PIDFile=/var/run/squid.pid
< SuccessExitStatus=5 6
< ExecStart=/etc/init.d/squid start
< ExecStop=/etc/init.d/squid stop
< ExecReload=/etc/init.d/squid reload
The above now makes more sense but.. replacing the service file and
removing the /etc/init.d/squid file should be the real way to run squid.
I do not know if and when Debian Stable would upgrade their package but as
long as you don't upgrade it automatically it would be suffice.
Eliezer
----
Eliezer Croitoru
Linux System Administrator
Mobile: [phone]
-----Original Message-----
Sent: Monday, June 11, 2018 09:25
Subject: Re: [squid-users] PID file /var/run/squid.pid not readable AND
Supervising process XXX which is not our child

Post by Eliezer Croitoru
Hey Alex,
What OS exactly is shipping this service file?
3.5.23-5+deb9u1

Current Debian stable. It is not shipped exactly, but generates on
install from the init.d file inserv headers in the absence of a shipped
.service.
"
# Automatically generated by systemd-sysv-generator
SourcePath=/etc/init.d/squid
"
Amos