Hi all,
I'm just installing version 4.3 for the first time and so far I like that you
can configure the VIPs from the web interface, thanks for this :)
However, when I declare the VIP for the registration and isolation networks I
can no longer start packetfence, commenting the lines out of pf.conf and the
services start with no issue. It works on the management interface with no
issue.
Output is:
[root@hallsnac03 ~]# service packetfence restart
Restarting PacketFence...service|command
dhcpd|already stopped
httpd.admin|stop
httpd.portal|already stopped
httpd.proxy|already stopped
httpd.webservices|stop
pfbandwidthd|already stopped
pfdetect|already stopped
pfdhcplistener|stop
pfdns|stop
pfmon|stop
pfsetvlan|stop
radiusd|stop
snmptrapd|stop
snort|already stopped
suricata|already stopped
memcached|stop
memcached|start
httpd: Could not reliably determine the server's fully qualified domain name,
using hallsnac03.internal.uwic.ac.uk for ServerName
httpd.admin|start
Checking configuration sanity...
Internet Systems Consortium DHCP Server 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Not searching LDAP since ldap-server, ldap-port and ldap-base-dn were not
specified in the config file
Wrote 16 leases to leases file.
Listening on LPF/eth0.705/00:1b:78:37:89:cc/10.1.5.0/24
Sending on LPF/eth0.705/00:1b:78:37:89:cc/10.1.5.0/24
Listening on LPF/eth0.704/00:1b:78:37:89:cc/10.100.0.0/20
Sending on LPF/eth0.704/00:1b:78:37:89:cc/10.100.0.0/20
Sending on Socket/fallback/fallback-net
dhcpd|start
httpd: Could not reliably determine the server's fully qualified domain name,
using hallsnac03.internal.uwic.ac.uk for ServerName
(99)Cannot assign requested address: make_sock: could not bind to address
10.100.0.6:80
no listening sockets available, shutting down
Unable to open logs
httpd.portal|not started
httpd: Could not reliably determine the server's fully qualified domain name,
using hallsnac03.internal.uwic.ac.uk for ServerName
httpd.webservices|start
pfdhcplistener|start
pfdns|start
pfmon|start
snmptrapd|start
pfsetvlan|start
radiusd|start
pf.conf networking is:
[interface eth0.703]
ip=10.1.3.7
type=management
mask=255.255.255.0
vip=10.1.3.12
[interface eth0.704]
enforcement=vlan
ip=10.100.0.5
type=internal
mask=255.255.240.0
vip=10.100.0.6
[interface eth0.705]
enforcement=vlan
ip=10.1.5.7
type=internal
mask=255.255.255.0
vip=10.1.5.11
[interface eth1]
ip=10.1.227.2
type=none,high-availability
mask=255.255.255.252
Also, I had to comment out the high-availability interface out of my
networks.conf as the configurator seemed to want to put it in there.
Any thoughts on what I've missed setting up the VIP on these two interfaces? Do
I perhaps need to set them up as an interface in the heartbeat config?
Cheers,
Andi
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users
