Ubuntu
squidguard package

  1. Bug #1313200
  2. Comment #3

Comment 3 for bug 1313200

Revision history for this message
Joerg Delker (ubuntu-delker) wrote :

When upgrading to trusty, this error has hit me, too.

After some investigation I figured that there are some flaws in /usr/sbin/update-squidgard, which is called during the configure phase on install/update.

1) update-squidguard calls a "su - proxy squidguard ..." at the end to rebuild the database.
This fails with
    Rebuild SquidGuard database - this can take a while.
    This account is currently not available.
That's no surprise because the "proxy" user was created previously with
    proxy:x:13:13:proxy:/bin:/usr/sbin/nologin
The invocation of "su" checks for a valid shell, which "/usr/sbin/nologin" isn't.

2) update-squidguard tries to restart squid at the very end, but actually fails to do so, because it checks for appropriate init.d files.
With squid3 (3.3.8-1ubuntu6) there aren't any, because this package is already upstart enabled.