Turn off pfbandwithd. If you have RADIUS accounting you don’t need it.
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) On Jul 29, 2015, at 3:52 , Hubert Kupper <kup...@uni-landau.de> wrote: > Hi Louis, > > pfbandwidthd is using 100% cpu time and pfbandwidthd.log shows: > > Jul 20 07:30:57 pfbandwidthd(5868) INFO: pfbandwidthd starting and writing > 5871 to /usr/local/pf/var/run/pfbandwidthd.pid (pf::services::util::createpid) > Jul 21 02:04:13 pfbandwidthd(5868) FATAL: pfbandwidthd: caught SIGTERM - > terminating (main::normal_sighandler) > Jul 21 02:04:13 pfbandwidthd(5868) FATAL: pfbandwidthd: caught SIGTERM - > terminating at /usr/local/pf/sbin/pfbandwidthd line 285 > (IO::Select::can_read) > Jul 21 02:04:13 pfbandwidthd(5868) ERROR: pfbandwidthd: caught SIGTERM - > terminating at /usr/local/pf/sbin/pfbandwidthd line 285 > (IO::Select::can_read) > Jul 21 02:05:24 pfbandwidthd(6848) INFO: pfbandwidthd starting and writing > 6851 to /usr/local/pf/var/run/pfbandwidthd.pid (pf::services::util::createpid) > Jul 28 08:06:24 pfbandwidthd(6848) FATAL: pfbandwidthd: caught SIGTERM - > terminating (main::normal_sighandler) > Jul 28 08:06:24 pfbandwidthd(6848) FATAL: pfbandwidthd: caught SIGTERM - > terminating at /usr/local/pf/sbin/pfbandwidthd line 285 > (IO::Select::can_read) > Jul 28 08:06:24 pfbandwidthd(6848) ERROR: pfbandwidthd: caught SIGTERM - > terminating at /usr/local/pf/sbin/pfbandwidthd line 285 > (IO::Select::can_read) > Jul 28 08:06:24 pfbandwidthd(6848) FATAL: panic: leave_scope inconsistency at > /usr/local/pf/sbin/pfbandwidthd line 157. > (main::) > Jul 28 08:06:24 pfbandwidthd(6848) ERROR: panic: leave_scope inconsistency at > /usr/local/pf/sbin/pfbandwidthd line 157. > (main::) > Jul 28 08:06:24 pfbandwidthd(6848) FATAL: panic: leave_scope inconsistency at > /usr/local/pf/sbin/pfbandwidthd line 157. > (main::) > Jul 28 08:06:24 pfbandwidthd(6848) ERROR: panic: leave_scope inconsistency at > /usr/local/pf/sbin/pfbandwidthd line 157. > (main::) > Jul 28 08:07:29 pfbandwidthd(10196) INFO: pfbandwidthd starting and writing > 10199 to /usr/local/pf/var/run/pfbandwidthd.pid > (pf::services::util::createpid) > Jul 29 07:59:56 pfbandwidthd(10196) FATAL: pfbandwidthd: caught SIGTERM - > terminating (main::normal_sighandler) > Jul 29 07:59:56 pfbandwidthd(10196) FATAL: pfbandwidthd: caught SIGTERM - > terminating at /usr/local/pf/sbin/pfbandwidthd line 285 > (main::) > Jul 29 07:59:56 pfbandwidthd(10196) ERROR: pfbandwidthd: caught SIGTERM - > terminating at /usr/local/pf/sbin/pfbandwidthd line 285 > (main::) > Jul 29 08:00:56 pfbandwidthd(12316) INFO: pfbandwidthd starting and writing > 12319 to /usr/local/pf/var/run/pfbandwidthd.pid > (pf::services::util::createpid) > [root@PacketFence-ZEN-5-1 logs]# > > Regards, > Hubert > > Am 28.07.2015 um 20:23 schrieb Louis Munro: >> >> On Jul 28, 2015, at 8:37 , Hubert Kupper <kup...@uni-landau.de> wrote: >> >>> there is traffic on port 1813 from the cisco switch to th server. tcpdump >>> shows it. >>> >>> mysql> select count(*) from radacct; shows count(*) 44 >> >> >> Is the MAC of the device among those listed in radacct? >> >> Something like this should return more: >> >> mysql> select >> callingstationid,acctinputoctets,acctoutputoctets,acctstarttime from radacct; >> >> >> Regards, >> -- >> Louis Munro > > ------------------------------------------------------------------------------ > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
