Bug 472141
Summary: | Privoxy no longer updates its logfile | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Frank Cox <theatre> |
Component: | privoxy | Assignee: | Karsten Hopp <karsten> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 9 | CC: | karsten |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-12-13 05:13:37 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Frank Cox
2008-11-18 22:32:25 UTC
Have you restarted privoxy in the meantime ? Are you using selinux, are there any AVC messages in any of the logfiles in /var/log ? I have restarted privoxy several times. selinux is disabled. I just double-checked that with system-config-selinux.py and it says "System Default Enforcing Mode: Disabled". I have three computers that are currently affected by this. Here are the last few lines of the logfile in the machine that I upgraded from F8 to F9 a few days ago: Nov 14 15:49:58 Privoxy(4420e950) Request: gulus.usherbrooke.ca/pub/distro/fedora/linux/releases/9/Fedora/x86_64/os/images/pxeboot/initrd.img Nov 14 15:49:59 Privoxy(4420e950) Request: gulus.usherbrooke.ca/pub/distro/fedora/linux/releases/9/Fedora/x86_64/os/images/pxeboot/initrd.img Nov 14 15:50:15 Privoxy(4420e950) Request: gulus.usherbrooke.ca/pub/distro/fedora/linux/releases/9/Fedora/x86_64/os/images/stage2.img Nov 14 15:50:15 Privoxy(4420e950) Request: gulus.usherbrooke.ca/pub/distro/fedora/linux/releases/9/Fedora/x86_64/os/images/stage2.img Nov 14 15:53:19 Privoxy(7f2e093ff6f0) Info: exiting by signal 15 .. bye As you can see, the last entries in the logfile are the final downloads using preupgrade when updating that machine from F8 to F9. Privoxy otherwise seems to be running fine and working fine. It just doesn't write to its logfile. I finally discovered the reason for this. The privoxy config file (/etc/privoxy/config) has changed defaults from what it used to be. Uncommenting this line: debug 1 # log each request destination (and the crunch reason if Privoxy in tercepted the request) causes the logging to work again. |