Koozali.org: home of the SME Server

Contribs.org Forums => Koozali SME Server 10.x => Topic started by: Peasant on February 14, 2022, 11:43:01 AM

Title: Squid fails to start on new install [SOLVED]
Post by: Peasant on February 14, 2022, 11:43:01 AM

Morning all,
Fresh install, but squid will not start. Running

Code: [Select]

systemctl list-units --type=serviceshows it fails to start up.
I then tried the following:

Code: [Select]

[root@yoda run]# systemctl start squid
Job for squid.service failed because the control process exited with error code. See "systemctl status squid.service" and "journalctl -xe" for details.

And

Code: [Select]

[root@yoda run]# journalctl -xe
Feb 14 10:20:01 yoda.mycompany.co.uk CROND[13220]: (root) CMD (/usr/bin/php  /usr/bin/horde-alarms)
Feb 14 10:20:01 yoda.mycompany.co.uk CROND[13219]: pam_unix(crond:session): session closed for user root
Feb 14 10:25:01 yoda.mycompany.co.uk crond[13251]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 10:25:01 yoda.mycompany.co.uk CROND[13252]: (root) CMD (/usr/bin/php  /usr/bin/horde-alarms)
Feb 14 10:25:01 yoda.mycompany.co.uk CROND[13251]: pam_unix(crond:session): session closed for user root
Feb 14 10:25:51 yoda.mycompany.co.uk systemd[1]: Starting Squid caching proxy...
-- Subject: Unit squid.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit squid.service has begun starting up.
Feb 14 10:25:51 yoda.mycompany.co.uk squid[13288]: squid: ERROR: Could not send signal 15 to process 1805: (1) Operation not permitted
Feb 14 10:25:51 yoda.mycompany.co.uk systemd[1]: squid.service: control process exited, code=exited status=1
Feb 14 10:25:51 yoda.mycompany.co.uk systemd[1]: Failed to start Squid caching proxy.
-- Subject: Unit squid.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit squid.service has failed.
--
-- The result is failed.
Feb 14 10:25:51 yoda.mycompany.co.uk systemd[1]: Unit squid.service entered failed state.
Feb 14 10:25:51 yoda.mycompany.co.uk systemd[1]: squid.service failed.
Feb 14 10:30:01 yoda.mycompany.co.uk crond[13360]: pam_unix(crond:session): session opened for user root by (uid=0)
Feb 14 10:30:01 yoda.mycompany.co.uk CROND[13361]: (root) CMD (/usr/bin/php  /usr/bin/horde-alarms)
Feb 14 10:30:01 yoda.mycompany.co.uk CROND[13360]: pam_unix(crond:session): session closed for user root
Feb 14 10:31:15 yoda.mycompany.co.uk cvm-unix[896]: + mt-accounts@localhost
Feb 14 10:31:29 yoda.mycompany.co.uk cvm-unix[896]: + mt-accounts@localhost
Feb 14 10:31:38 yoda.mycompany.co.uk cvm-unix[896]: + mt-accounts@localhost
lines 1679-1707/1707 (END)

From what I can see it is trying to access process 1805, which is lpd. Googling says there is a squid.pid file that is causing problems in /var/run, but I can't find one.

any other ideas greatfully received.

Title: Re: Squid fails to start on new install [SOLVED]
Post by: Peasant on February 14, 2022, 11:57:48 AM

Problem solved. I'd found on google that this problem can be caused by a squid.pid file upsetting squid, but the location was /var/run/squid.pid

The file is actually located in /var/log/squid. I deleted the squid.pid in here, restarted squid and Bob's your Auntie, all is working again.

Title: Re: Squid fails to start on new install [SOLVED]
Post by: ReetP on February 14, 2022, 06:44:15 PM

Nice work!!

Title: Re: Squid fails to start on new install [SOLVED]
Post by: Peasant on February 14, 2022, 08:04:00 PM

Thanks.

Just for completeness, the problem appeared when neither Edge nor Opera would connect to the Internet on client PC's. Firefox worked fine. The only other symptom was the client machines were slow to get an internet connection.