On Jun 17, 2015, at 13:57 , heupink <heup...@gmail.com> wrote:
> - Question: shouldd 'DNS name of the domain' perhaps better be called > REALM? Or are we not supposed to enter the realm in capitals there? > I suppose so. > - One thing that is NOT working better (and I had really hoped it would) > is pfdns reliability. PF keeps thinking it's not running, restarting it, > but: " Couldn't create UDP socket: Address already in use". It seems to > be running, but pf doesn't seem to detect that: > >> root@pf:/usr/local/pf/logs# lsof -i :53 >> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME >> pfdns 5320 root 9u IPv4 43258 0t0 TCP 10.19.0.1:domain (LISTEN) >> pfdns 5320 root 11u IPv4 43260 0t0 UDP 10.19.0.1:domain >> pfdns 5320 root 13u IPv4 43262 0t0 TCP 10.0.2.1:domain (LISTEN) >> pfdns 5320 root 23u IPv4 43264 0t0 UDP 10.0.2.1:domain >> pfdns 5320 root 29u IPv4 43266 0t0 TCP 10.0.3.1:domain (LISTEN) >> pfdns 5320 root 30u IPv4 43268 0t0 UDP 10.0.3.1:domain >> root@pf:/usr/local/pf/logs# > > The web admin also reports pfdns is NOT running. Can you see if there are pid files for pfdns in /usr/local/pf/var/run ? And what pid they contain if they do exist? > > Same goes for carbon-cache and carbon-relay, they are running: >> root@pf:/usr/local/pf/logs# ps aux | grep carbon >> pf 3712 0.5 0.2 84508 14648 ? Sl 19:20 0:08 >> /usr/bin/python /usr/bin/carbon-cache >> --config=/usr/local/pf/var/conf/carbon.conf >> --pidfile=/usr/local/pf/var/run/carbon-cache.pid --logdir=/usr/local/pf/logs >> start >> pf 3722 0.4 0.2 77672 14516 ? S 19:20 0:06 >> /usr/bin/python /usr/bin/carbon-relay >> --config=/usr/local/pf/var/conf/carbon.conf >> --pidfile=/usr/local/pf/var/run/carbon-relay.pid --logdir=/usr/local/pf/logs >> start >> root@pf:/usr/local/pf/logs# > > And surprise: The web admin gui reports them as running... > > I hoped that a fresh install would have solved these issues too, but alas... Perhaps something is missing here, but I don’t see the problem. The dashboard says they are running and yet they are? I am going to assume a missing negation in there ;-) I would advise the same check as for pfdns: see if there any pid file in /usr/local/pf/var/run for the carbon daemons. There may be an old pid file that prevents a new one from being created. Delete it, kill the relevant services (from the command line) and restart them. Regards, -- Louis Munro lmu...@inverse.ca :: www.inverse.ca +1.514.447.4918 x125 :: +1 (866) 353-6153 x125 Inverse inc. :: Leaders behind SOGo (www.sogo.nu) and PacketFence (www.packetfence.org) ------------------------------------------------------------------------------ _______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
