Dansguardian not starting after switching to Fedora 16)

[ksaarela]

Hello,

I'm upgrading our home network to Fedora 16 as I have several units running either F14 or F15.

Now with Fedora 16 I've encountered an issue with dansguardian, it won't start and I get the following message in /var/log/messages:

Apr 15 11:17:55 julia dansguardian[3759]: Starting Web Content Filter (dansguardian):
Apr 15 11:17:55 julia systemd[1]: PID file /var/run/dansguardian not readable (yet?) after start.

I have dansguardian up'n'running in F14 and F15 environment even the package seems to be quite old.

I've tried quite a few things but without success. This is getting quite annoying.

Any hints?

---------
Installed Packages
Name : dansguardian
Arch : i686
Version : 2.10.1.1
Release : 4.fc13
Size : 1.4 M
Repo : installed
From repo : fedora

[marriedto51]

I wonder whether you have a stale PID file with odd permissions? I would try first (as root):

# systemctl stop dansguardian.service
# rm -f /var/run/dansguardian
# systemctl start dansguardian.service

(I have Dansguardian running happily here on F16 -- just the version from the repositories, with almost no manual configuration.)

[ksaarela]

Hello,

and thanks for the proposal, I checked, but it didn't help.

However, I did some further debugging and found out, that dansguardian in fact is running properly after reboot.

What doesn't work seems to be related to restarting and stopping dansguardian by using /bin/systemctl, or /sbin/service or directly /etc/init.d/dansguardian, these all fail. Starting dansguardian directly /usr/sbin/dansguardian works also.

As I'm every now and then updating exceptionsitelist and restarting dansguardian accordingly, this is a bit of an annoyance.

But as dansguardian works after a reboot, and the machine I upgraded first to F16 is booted regularly anyway, situation is acceptable. (read = kids can use the computer again, and the noise level is down to normal).

[cengel]

I just upgraded to F16 this week as well and dansguardian doesn't work for me. First it addes over a minute to boot time while it waits for the start to timeout. However when I am finally able to login I can see that it is running, however if I attempt to use it it doesn't work.

I see it attempting to access squid but squid keeps failing with these in squid.log :
1334422820.782 49328 127.0.0.1 NONE_ABORTED/000 0 GET http://www.cnn.com/ - HIER_NONE/- -

I did have to modify my squid.conf after the upgrade but I just put these lines back in like I had with F14:
# Squid normally listens to port 3128
http_port 127.0.0.1:3128 transparent
#http_port 3128

# CJE Adds
visible_hostname eng
cache_effective_user squid
cache_effective_group squid
shutdown_lifetime 2 seconds


For now I have rerouted this computer to use dansguardian on another machine that is still at F14. I guess I will have to wait to upgrade that one until this issue is resolved.

[nicku]

See https://bugzilla.redhat.com/show_bug.cgi?id=756260.
Now there is a fixed package released. If you do not install that, you can work around it
with this:

#! /bin/sh
if ! ps auxwwww | grep dansguardia[n] | grep -v start-dansguardia[n]
then
echo Starting dansguardian...
sudo mkdir /var/run/dansguardian
sudo chown dansguardian.dansguardian /var/run/dansguardian
sudo systemctl start dansguardian.service
fi
sudo systemctl status dansguardian.service

[tuxbiker]

This is a super old thread and I hate to necro it, but the actual fix is correcting the pidfile in Fedora. Set the pid in /etc/dansguardian/dansguardian.conf to /var/run/dansguardian.pid, then in the /etc/init.d/dansguardian file, make sure it references that as well.