![](https://seccdn.libravatar.org/avatar/77cb4da5f72bc176182dcc33f03a18f3.jpg?s=120&d=mm&r=g)
On 23/11/2018 12.02, stakanov wrote:
On 23/11/2018 11.29, stakanov wrote:
How can I check why it does not start? Any suggestions? Config: I just did install the package privoxy. I rebooted in the meanwhile. I don't have it installed, so I can't check. Read the config file to find out if it has a separate log file, and then check it. That is weird. Privoxy should write to var/log/privoxy when nothing set, and
In data venerdì 23 novembre 2018 11:51:50 CET, Carlos E. R. ha scritto: this is mandatory. But in /var/log there is not log. So probably diverted to journalctl but journalctl does not report errors.... sudo dmesg clean, just a lot of martians from multicast... nothing else.
No, that means that it doesn't even start. You could explicitly specify writing to /var/log/privoxy just in case, though. Run "aa-logprof" to check that apparmor does not interfere. It is running in a chroot. You might disable that temporarily to investigate. -- Cheers / Saludos, Carlos E. R. (from 42.3 x86_64 "Malachite" at Telcontar)