Privoxy does not start after update. TW
The failure is: Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE) Is this a PAM issue? whole log: ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2021-04-19 14:04:39 CEST; 53s ago Process: 8550 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/ host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, status=0/SUCCESS) Process: 8551 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/ libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SUCCESS) Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/ privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE) CPU: 16ms Apr 19 14:04:38 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited, status=1/FAILURE Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. Apr 19 14:04:39 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities.
On 19/04/2021 14.12, Stakanov wrote:
The failure is: Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE)
Is this a PAM issue?
whole log: ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Mon 2021-04-19 14:04:39 CEST; 53s ago Process: 8550 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/ host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, status=0/SUCCESS) Process: 8551 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/ libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SUCCESS) Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/ privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE) CPU: 16ms
Apr 19 14:04:38 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited, status=1/FAILURE Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. Apr 19 14:04:39 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities.
You need more log entries. The above is the output of "systemctl status". Look instead at "journalctl" and go back to the 14:04:38 timestamp, and then back in time. -- Cheers / Saludos, Carlos E. R. (from 15.2 x86_64 at Telcontar)
In data lunedì 19 aprile 2021 15:06:16 CEST, Carlos E. R. ha scritto:
On 19/04/2021 14.12, Stakanov wrote:
The failure is: Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE)
Is this a PAM issue?
whole log: ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities
Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Mon 2021-04-19 14:04:39 CEST;
53s ago
Process: 8550 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/
host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, status=0/SUCCESS)
Process: 8551 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/
libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SUCCESS)
Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/
privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE)
CPU: 16ms
Apr 19 14:04:38 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited, status=1/FAILURE Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. Apr 19 14:04:39 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities.
You need more log entries. The above is the output of "systemctl status". Look instead at "journalctl" and go back to the 14:04:38 timestamp, and then back in time.
Well, there is nothing. Just: apr 19 14:04:39 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited, status=1/FAILURE apr 19 14:04:38 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities...
In data lunedì 19 aprile 2021 15:20:32 CEST, Stakanov ha scritto:
In data lunedì 19 aprile 2021 15:06:16 CEST, Carlos E. R. ha scritto:
On 19/04/2021 14.12, Stakanov wrote:
The failure is: Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE)
Is this a PAM issue?
whole log: ● privoxy.service - Privoxy Web Proxy With Advanced Filtering Capabilities
Loaded: loaded (/usr/lib/systemd/system/privoxy.service; enabled; vendor
preset: disabled)
Active: failed (Result: exit-code) since Mon 2021-04-19 14:04:39 CEST;
53s ago
Process: 8550 ExecStartPre=/usr/bin/cp -upf /etc/resolv.conf /etc/
host.conf /etc/hosts /etc/localtime /var/lib/privoxy/etc/ (code=exited, status=0/SUCCESS)
Process: 8551 ExecStartPre=/usr/bin/cp -upf /lib64/libresolv.so.2 /lib64/
libnss_dns.so.2 /var/lib/privoxy/lib64/ (code=exited, status=0/SUCCESS)
Process: 8552 ExecStart=/usr/sbin/privoxy --chroot --pidfile /run/
privoxy.pid --user privoxy /etc/config (code=exited, status=1/FAILURE)
CPU: 16ms
Apr 19 14:04:38 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities... Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited, status=1/FAILURE Apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. Apr 19 14:04:39 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities.
You need more log entries. The above is the output of "systemctl status". Look instead at "journalctl" and go back to the 14:04:38 timestamp, and then back in time.
Well, there is nothing. Just:
apr 19 14:04:39 silversurfer systemd[1]: Failed to start Privoxy Web Proxy With Advanced Filtering Capabilities. apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Failed with result 'exit-code'. apr 19 14:04:39 silversurfer systemd[1]: privoxy.service: Control process exited, code=exited, status=1/FAILURE apr 19 14:04:38 silversurfer systemd[1]: Starting Privoxy Web Proxy With Advanced Filtering Capabilities...
Has been reported this morning: Bug 1184945 - [Privoxy]: Fail on start "Fatal error: can't load actions file '/etc/default.action': line 710"
participants (2)
-
Carlos E. R. -
Stakanov