On Thu, 1 Sep 2016, Cristian Ionescu-Idbohrn wrote:
>
> > dpkg -i /var/cache/apt/archives/privoxy_3.0.25-2_amd64.de
> > instead of using apt-get (which may use some external hooks).
>
> Same, same, but different ;)
>
> ,----
> | root 5478 0.5 0.7 138344 118304 pts/48 S+ 13:15 0:00 |
> \_ dpkg -i /var/cache/apt/archives/privoxy_3.0.25-2_amd64.deb
> | root 5479 0.0 0.0 4304 720 pts/48 S+ 13:15 0:00 |
> \_ sh -c (test -x /usr/lib/needrestart/dpkg-status &&
> /usr/lib/needrestart/dpkg-status || cat > /dev/null)
> | root 5480 0.0 0.0 4304 92 pts/48 S+ 13:15 0:00 |
> | \_ sh -c (test -x /usr/lib/needrestart/dpkg-status &&
> /usr/lib/needrestart/dpkg-status || cat > /dev/null)
> | root 5481 0.0 0.0 4304 800 pts/48 S+ 13:15 0:00 |
> | \_ /bin/sh /usr/lib/needrestart/dpkg-status
> | root 5535 0.2 0.1 70404 21540 pts/48 S+ 13:15 0:00 |
> \_ /usr/bin/perl -w /usr/share/debconf/frontend
> /var/lib/dpkg/info/privoxy.postinst configure 3.0.25-2
> | root 5543 0.0 0.0 0 0 pts/48 Z+ 13:15 0:00 |
> \_ [privoxy.postins] <defunct>
> `----
>
> Yes, I do have needrestart installed too on a few boxes, but not all.
> One of them (a testing/stretch) where needrestart isn't installed
> misbehaves in the same manner.
>
> I see no debconf dialog.
>
> Killing 5535 gets me here:
>
> ,----
> | dpkg: error processing package privoxy (--install):
> | subprocess installed post-installation script was killed by signal
> (Terminated)
> | Processing triggers for systemd (231-5) ...
> | Processing triggers for readahead-fedora (2:1.5.6-5.2) ...
> | Processing triggers for doc-base (0.10.7) ...
> | Processing 3 changed doc-base files, 2 added doc-base files...
> | Registering documents with scrollkeeper...
> | Processing triggers for man-db (2.7.5-1) ...
> | Errors were encountered while processing:
> | privoxy
> `----
>
> And:
>
> # dpkg --configure -a
>
> cleans it up.
>
> > Sorry, I'm still digging in the fog, since I cannot reproduce the
> > issue and do not fully understand, what goes wrong on your system...
>
> No worries, as long as it's only me and there's a way out :)
Did another experiment:
# dpkg-reconfigure privoxy
[ ok ] Stopping filtering proxy server: privoxy.
Configuring privoxy
-------------------
Please enter a space separated list of address:port combinations on
which
Privoxy will listen for client requests.
Adresses on with Privoxy listens: 127.0.0.1:8118
Replacing config file /etc/privoxy/config with new version
[ ok ] Starting filtering proxy server: privoxy.
and hangs there. No more questians asked. The process table shows:
root 25980 0.6 0.1 71172 22280 pts/12 S+ 15:03 0:00
\_ /usr/bin/perl -w /usr/sbin/dpkg-reconfigure privoxy
root 26034 0.0 0.0 0 0 pts/12 Z+ 15:03 0:00
\_ [privoxy.postins] <defunct>
Killing 25980, to clean up.
The /etc/privoxy/config was updated and the daemon is running, though.
Cheers,
--
Cristian
