This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

squid not running notifications after update 5.200

after the update 5.200 i receive every hour a notification squid not running - restarted- from my asl box.


This thread was automatically locked due to age.
  • hardware specs?

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

  • p4 2 512 mb ram 40gb hd 2 nics. i dont think this is hw problem
  • something is up.  I am not getting that notification here on my little box.

    Owner:  Emmanuel Technology Consulting

    http://etc-md.com

    Former Sophos SG(Astaro) advocate/researcher/Silver Partner

    PfSense w/Suricata, ntopng, 

    Other addons to follow

  • I have exactly the same. Looking at the squid logs on my machine:-

     squid.conf line 53: acl LOCAL_PORT dstport 16497
     aclParseAclLine: Invalid ACL type 'dstport'
     squid.conf line 55: http_access allow LOCAL_NAME LOCAL_PORT
     aclParseAccessLine: ACL name 'LOCAL_PORT' not found.

    So I guess I've found my problem. Just wish I knew how to fix it [:)]
  • I have exactly the same. Looking at the squid logs on my machine:-((

    2005:03:14-12:05:10 (none) squid[692]: squid.conf line 49: acl LOCAL_PORT dstport 16497
    2005:03:14-12:05:10 (none) squid[692]: aclParseAclLine: Invalid ACL type 'dstport'
    2005:03:14-12:05:10 (none) squid[692]: squid.conf line 51: http_access allow LOCAL_NAME LOCAL_PORT
    2005:03:14-12:05:10 (none) squid[692]: aclParseAccessLine: ACL name 'LOCAL_PORT' not found.
    2005:03:14-12:05:10 (none) squid[692]: Squid is already running! Process ID 1127

     [:S]
    Jebo
    ASL v5.200 P4 2Ghz 512
  • I have the same problem as well. Same stuff in the logs.

    This didn't happen when the update first was installed. My box (and squid) has been running fine since then. Today I rebooted, and now squid won't start.

    I notice that the pid in /var/chroot-squid/var/logs/squid.pid (may not be the correct path - typed from memory) is owned by the running confd daemon. Should it be that way?
  • Hi JeBo,

    had the same problem yesterday.
    I killed the process with the ID-number xxx (For your example 1127).

    Then I used the following lines:

    /bin/bash /var/mdw/scripts/squid start

    After that it worked again till now.
  • Hi,

    That worked for me, thanks! However I removed /var/chroot-squid/var/logs/squid.pid instead of killing the process it pointed to.