Re: [PacketFence-users] High CPU - pfcmd.pl and Perl

2020-07-22 Thread Durand fabrice via PacketFence-users
I think you have pfacct already running so radius-acct can't start because the port is already used (1813). just disable packetfence-radiusd-acct.service systemctl disable packetfence-radiusd-acct.service Regards Fabrice Le 20-07-22 à 22 h 15, Louis Scaringella via PacketFence-users a

Re: [PacketFence-users] PacketFence and Domain Join Issues

2020-07-22 Thread Louis Scaringella via PacketFence-users
Fix is on Github for this. https://github.com/inverse-inc/packetfence/issues/5681 Thank you, Louis Scaringella Security Systems Engineer Yellow Dog Networks 785-342-7903 On Jul 22, 2020, at 8:02 PM, Michael Brown via PacketFence-users wrote:  We are seeing this too. Did you find a

Re: [PacketFence-users] High CPU - pfcmd.pl and Perl

2020-07-22 Thread Louis Scaringella via PacketFence-users
In the /var/log/messages log I see this: Jul 22 18:50:37 localhost pfhttpd: [GIN] 2020/07/22 - 18:50:37 | 200 | 51.166µs |10.255.255.1 | POST "/api/v1/logs/tail" Jul 22 18:50:37 localhost systemd: packetfence-radiusd-acct.service: main process exited, code=exited, status=1/FAILURE

Re: [PacketFence-users] PacketFence and Domain Join Issues

2020-07-22 Thread Louis Scaringella via PacketFence-users
Thanks you so much! I actually just came across this on GitHub and applied the updates and things are working now across reboots. Thanks for the help! Louis Scaringella Security Systems Engineer Yellow Dog Networks, Inc 785-342-7903 > On Jul 22, 2020, at 4:22 PM, Christian McDonald > wrote:

[PacketFence-users] PF 10.1 wlc 2504 DPSK - can't connect to this network | Incorrect password

2020-07-22 Thread Juraj Tobias via PacketFence-users
setup: * PacketFence 10.1 clean centos7 install in hyper-v VM * WLC 2504 fw 8.5.151.0 * want to make use of DPSK * configured according to this guide problem: registration on reg.

Re: [PacketFence-users] PacketFence and Domain Join Issues

2020-07-22 Thread Christian McDonald via PacketFence-users
Bug with winbindd not being enabled after joining the domain...so winbindd isn’t running when you reboot. Run /usr/local/pf/addons/pf-maint.pl to pull latest patches and try again. On Wed, Jul 22, 2020 at 1:02 PM Louis Scaringella via PacketFence-users < packetfence-users@lists.sourceforge.net>

Re: [PacketFence-users] PacketFence and Domain Join Issues

2020-07-22 Thread Louis Scaringella via PacketFence-users
As an update to this, we built a CentOS 7.8 server and installed PacketFence on top of that. I suspect my issue has to do with the ens192 interface not linking to PacketFence in some way. With the OVA file, it was probably all configured to work well together. I think i’m on to something, just

[PacketFence-users] High CPU - pfcmd.pl and Perl

2020-07-22 Thread Louis Scaringella via PacketFence-users
Hello, I just install Cent OS 7.8 and installed PacketFence and applied the latest bug fixes today. When running the top command, I seem to be having an issue now where the pfcmd.pl and perl processes are continuously running and using high CPU. Any ideas where to start with investigating why

[PacketFence-users] PacketFence and Domain Join Issues

2020-07-22 Thread Michael Brown via PacketFence-users
We are seeing this too.  Did you find a solution?   We are running PacketFence 10.1.0 ZEN.  Thanks. ___ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users

[PacketFence-users] PacketFence and Domain Join Issues

2020-07-22 Thread Louis Scaringella via PacketFence-users
Hello, We are running PacketFence 10.1.0 and running into an issue when joining the domain. It seems we are able to join the domain just fine, but after a rebooting, we see the message “Cannot open network namespace RQSDomain”. When we re-join it seems to join fine and is green, but always

[PacketFence-users] Captive Portal: 502 Bad Gateway

2020-07-22 Thread Emanuele Gabrielli via PacketFence-users
Hi all, I defined a scenario where the switch port is configured so to manage the following scenario: 1) 802.1x authentication if fails: 2) mac auth authentication if fails: 3) Captive portal authentication The switch correctly applies configurations when the device doesn't