Squid won't start, uid 62: exited on signal 6



  • Upon startup of my box I receive "uid 62: exited on signal 6" on squid.
    I did a search but didn't find anything more than clear your cache comments.

    I've cleared the cache and this is a new setup. The only way I've found to get rid of the error is to tell SquidGuard to download the blacklist rules again.

    Has anyone else had this problem and if so how did you fix it? It sure would be nice if Squid would startup on reboot.

    Jan 20 15:06:43	kernel: pid 49278 (squid), uid 62: exited on signal 6
    Jan 20 15:06:40	kernel: pid 86986 (squid), uid 62: exited on signal 6
    Jan 20 15:06:37	kernel: pid 32598 (squid), uid 62: exited on signal 6
    Jan 20 15:06:34	kernel: pid 68708 (squid), uid 62: exited on signal 6
    Jan 20 15:06:31	kernel: pid 16949 (squid), uid 62: exited on signal 6
    Jan 20 15:05:53	kernel: pid 10203 (squid), uid 62: exited on signal 6
    Jan 20 15:05:40	kernel: pid 78545 (squid), uid 62: exited on signal 6
    Jan 20 15:00:03	kernel: pid 16615 (squid), uid 62: exited on signal 6
    Jan 20 14:59:23	kernel: pid 77482 (squid), uid 62: exited on signal 6
    Jan 20 14:59:19	kernel: pid 24186 (squid), uid 62: exited on signal 6
    Jan 20 14:59:16	kernel: pid 71572 (squid), uid 62: exited on signal 6
    Jan 20 14:59:13	kernel: pid 10183 (squid), uid 62: exited on signal 6
    Jan 20 14:59:10	kernel: pid 28286 (squid), uid 62: exited on signal 6
    Jan 20 14:58:28	kernel: pid 83145 (squid), uid 62: exited on signal 6
    Jan 20 14:58:25	kernel: pid 37215 (squid), uid 62: exited on signal 6
    Jan 20 14:58:22	kernel: pid 92141 (squid), uid 62: exited on signal 6
    Jan 20 14:58:19	kernel: pid 41781 (squid), uid 62: exited on signal 6
    Jan 20 14:58:16	kernel: pid 95251 (squid), uid 62: exited on signal 6
    Jan 20 14:57:29	kernel: pid 18052 (squid), uid 62: exited on signal 6
    Jan 20 14:57:26	kernel: pid 69342 (squid), uid 62: exited on signal 6
    Jan 20 14:57:23	kernel: pid 21719 (squid), uid 62: exited on signal 6
    Jan 20 14:57:20	kernel: pid 73198 (squid), uid 62: exited on signal 6
    Jan 20 14:57:16	kernel: pid 27590 (squid), uid 62: exited on signal 6
    Jan 20 14:56:30	kernel: pid 46404 (squid), uid 62: exited on signal 6
    Jan 20 14:56:27	kernel: pid 99518 (squid), uid 62: exited on signal 6
    Jan 20 14:56:24	kernel: pid 52186 (squid), uid 62: exited on signal 6
    Jan 20 14:56:21	kernel: pid 4581 (squid), uid 62: exited on signal 6
    Jan 20 14:56:18	kernel: pid 59890 (squid), uid 62: exited on signal 6
    Jan 20 14:55:31	kernel: pid 83369 (squid), uid 62: exited on signal 6
    Jan 20 14:55:28	kernel: pid 35210 (squid), uid 62: exited on signal 6
    Jan 20 14:55:25	kernel: pid 87690 (squid), uid 62: exited on signal 6
    


  • Bump!

    Another thing I noticed in the logs…

    php-fpm[240]: /rc.start_packages: The command '/usr/pbi/squid-amd64/sbin/squid -k reconfigure' returned exit code '1', the output was '2016/01/21 14:44:46| parseConfigFile: squid.conf:85 unrecognized: 'url_rewrite_bypass' squid: ERROR: Could not send signal 1 to process 17851: (3) No such process'

    And again, just downloading the blacklist brings squid back up.



  • Kill squid, run squid -z in shell.

    Should fix it.



  • Yea, I thought so too.
    Done that a few times, seems to fix squid when it's being stupid.
    I delete the cache, run squid -z, tell squidguard to download the black list and wham! everything fires. After a reboot squid and squidguard services are stopped with the same error. A download of the blacklist fires the services again and eliminates the error.



  • What version of Squid, SquidGuard, and PFSense are you running?



  • 4.3.10 and 1.9.18
    I attached a screen shot.




  • Ditch the 2.7 branch and try the 3.4 branch…  2.7 isn't being maintained, and is troublesome at best.



  • good to know, I'll make some changes.


Log in to reply