I upgraded from 5.4.0 to 5.5.2 . There are a few things I had to correct after
the upgrade. Here is the list
Errors when trying to boot after upgrade
FATAL - unknown configuration parameter alerting.wins_server if you added the
parameter yourself make sure it is present in conf/documentation.conf
FATAL - unknown configuration parameter alerting.admin_netbiosname if you added
the parameter yourself make sure it is present in conf/documentation.conf
WARNING - invalid parameter billing_engine for profile default
In the Documenation.conf I had to add
[alerting.wins_server]
type=text
description=<<EOT
Wins Server
EOT
[alerting.admin_netbiosname]
type=text
description=<<EOT
Netbios Name
EOT
In the profiles.conf
I removed the billing_engine=disabled line
The radius server would not start because of this error in the radiusd.log file
Wed Dec 16 09:59:27 2015 : Error: Failed binding to authentication address
172.18.2.90 port 1812 as server packetfence: Address already in use
Wed Dec 16 09:59:27 2015 : Error: /usr/local/pf/raddb//auth.conf[9]: Error
binding to port for 172.18.2.90 port 1812
So I went into the radius.conf and commented out these portions
listen {
type = auth
ipaddr = %%management_ip%%
port = 0
virtual_server = packetfence
}
listen {
ipaddr = %%management_ip%%
port = 0
type = acct
virtual_server = packetfence
}
They appear to be starting twice once in this conf and once in the auth.conf
The big issue I have now that it is running again is that every node in the
database about 20 times. Is there an easy way to clean up the database. I
can't seem to connect to the DB from the outside and don't want to tackle it
from the commandline if possible.
Thanks
Dan Nelson
Nutraceutical Corporation
801-334-3702
------------------------------------------------------------------------------
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
