Hi Jeff,
it's recommended to upgrade all and not just upgrade packetfence.
So just to be sure do:
apt update
apt upgrade
Regards
Fabrice
Le 20-10-09 à 16 h 31, Jeff Linden a écrit :
I went forward before seeing the link you provided and I just
performed apt-get install keepalived. It
http://inverse.ca/downloads/PacketFence/debian-lastrelease/pool/stretch/k/keepalived/
Le 20-10-09 à 16 h 15, Jeff Linden a écrit :
It seems to be 1.3.2-1. I’ll refresh it.
dpkg -l | grep keepalive
ii keepalived 1:1.3.2-1 amd64 Failover and monitoring daemon
for LVS c
Jeff Linden |
What is the keepalived version you are running ?
It's suppose to be keepalived-2.0.20-2.1.x86_64 but yours looks different.
Le 20-10-09 à 15 h 57, Jeff Linden a écrit :
There is one warning in the log during restart of keepalived.
# journalctl -f | grep keepalived
Oct 09 15:54:05
Can i see the keepalived.conf ?
And do you have something (like error) in the logs about keepalived
(journalctl -f | grep keepalived) when you restart it ?
Le 20-10-09 à 15 h 46, Jeff Linden a écrit :
Keepalived restarts successfully, but is not showing on the lo interface.
I performed the
Keepalived restarts successfully, but is not showing on the lo interface.
I performed the restart of keepalive using this…
# /usr/local/pf/bin/pfcmd service keepalived restart
Service StatusPID
Checking configuration sanity...
Fabrice,
I realized that I tested previously with the line commented out of
pf.conf.defaults.
I’ve put the line back in to pf.conf.defaults and re-run the test you asked
for. Here are the better results. Still no on the IP being assigned to lo,
but yes to it being in the keepalived.conf.
When you restart keepalived does the ip appear on lo ?
Does keepalived start ?
Le 20-10-09 à 15 h 20, Jeff Linden a écrit :
Fabrice,
I realized that I tested previously with the line commented out of
pf.conf.defaults.
I’ve put the line back in to pf.conf.defaults and re-run the test you
Fabrice,
ps -fe | grep keepalive
root 98543 1 0 13:56 ?00:00:00 /usr/sbin/keepalived -f
/usr/local/pf/var/conf/keepalived.conf
--pid=/usr/local/pf/var/run/keepalived.pid
root 98549 98543 0 13:56 ?00:00:00 /usr/sbin/keepalived -f
Does the ip is assigned to lo ? (ip a)
No, it is not assigned to lo. Only 127.0.0.1/8 is assigned
Check the keepalived.conf file if it contain the ip 66.70.255.147
(var/conf/keepalived.conf).
No, keepalived.conf does not contain the IP 66.70.255.147
Also check if
pfcmd configreload hard
pfcmd service keepalived generateconfig
pfcmd service keepalived restart
Le 20-10-09 à 15 h 09, Jeff Linden a écrit :
Does the ip is assigned to lo ? (ip a)
No, it is not assigned to lo. Only 127.0.0.1/8 is assigned
Check the keepalived.conf file if
Does the ip is assigned to lo ? (ip a)
Check the keepalived.conf file if it contain the ip 66.70.255.147
(var/conf/keepalived.conf).
Also check if there is not a keepalived.conf.rpmnew somewhere.
Regards
Fabrice
Le 20-10-09 à 14 h 52, Jeff Linden a écrit :
Fabrice,
ps -fe | grep
Hello Jeff,
your issue is because keepalived is not running.
let's try:
/usr/local/pf/bin/pfcmd service pf updatesystemd
systemctl restart packetfence-keepalived.service
Regards
Fabrice
Le 20-10-09 à 14 h 11, Jeff Linden via PacketFence-users a écrit :
Hello,
I’ve upgraded PacketFence
Hello,
I’ve upgraded PacketFence from 9.2 to 10.1. Since then, I’ve had trouble
getting the Captive Portal to function. Since I noticed a newer version is
available, I have now upgraded to 10.2 before writing this.
In the web interface, under Status -> Services, the haproxy-portal is enabled
Here are results again from the logs with and without the filter. Any ideas as
to why httpd.portal doesn’t match the same profile it should be when the SSID
filter is in place?
With SSID filter:
Oct 8 13:01:27 localhost packetfence_httpd.aaa: httpd.aaa(2087) INFO:
[mac:00:24:d6:5b:30:bc]
14 matches
Mail list logo
