Just realised why this is.
The parking system relies on the PF server being the ACTIVE in production DHCP
server.
We are not using the PF server as the production DHCP (even for the
registration subnet - ie 'no ip helpers') but are
relying on the UDP_Reflector process to send production DHCP activity to the PF
server.
When the service resets overnight it restarts the local DHCPD service running
on the PF server that causes devices to
get two separate DHCP offers on the registration subnet (The PF server's
registration portal interface is on this subnet)
one from the PF server and one form the production server - This causes issues
with colliding IP addresses. So to
avoid this we kill the DHCPD process on the PF server (Everything else still
works as it gets its DHCP data from the
UDP-Reflector).
It seems that the parking system is assuming that OMAPI is available which is
not necessarily the case.
Any ideas on how to tweak this.
Andrew
-----------------------------
Falmouth University
-----------------------------
-----Original Message-----
From: Torry, Andrew [mailto:[email protected]]
Sent: 22 August 2016 10:28
To: [email protected]
Subject: [PacketFence-users] Parking issue
Came into work this morning and whilst checking the state of our PacketFence
portal I checked my laptop's connection.
It had been parked and displayed the correct lightweight portal.
When I clicked the 'Enable' button the process of unparking started but it
never returned with the 'You device has been Un-Parked'
Instead I received an 'Internal Server Error' message.
After restarting my web browser I am still 'parked'.
Repeating the Un-parking process yields the following messages:-
PacketFence.log
Aug 22 09:48:54 release.pl(2442) INFO: violation 1300003 closed for
00:26:c7:3b:b2:6e (pf::violation::violation_close)
Aug 22 09:48:54 release.pl(2442) INFO: Removing parking actions for
00:26:c7:3b:b2:6e - 10.240.249.117 (pf::parking::remove_parking_actions)
Aug 22 09:48:54 release.pl(2442) FATAL: Can't bind : IO::Socket::INET: connect:
Connection refused
(pf::OMAPI::_build_sock)
And in pfmon.log:-
Aug 22 09:21:53 pfmon(16725) INFO: getting violations triggers for accounting
cleanup (pf::accounting::acct_maintenance)
Aug 22 09:22:00 pfmon(16736) INFO: violation 1300003 force-closed for
00:26:c7:3b:b2:6e (pf::violation::violation_force_close)
Aug 22 09:22:00 pfmon(16736) INFO: Removing parking actions for
00:26:c7:3b:b2:6e - 10.240.249.117 (pf::parking::remove_parking_actions)
Aug 22 09:22:00 pfmon(16736) ERROR: Error running task checking violations for
expiration: Can't bind : IO::Socket::INET: connect: Connection refused
(main::_runtask)
Any ideas?
Andrew
-----------------------------
Falmouth Exeter Plus
-----------------------------
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
