Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 1438 views
  • Users 0 members are here
Options
Suggested
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

karabela
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.
Parents
  • 0
    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
  • 0 in reply to JeBo
    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?
Reply
  • 0 in reply to JeBo
    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?
Children
No Data