Re: [PacketFence-users] Cluster PF 8.0.1
Hello Jeimerson, it looks that something is already listening on the port 3306. Can you check with netstat ? Regards Fabrice Le 2018-05-16 à 04:35, Jeimerson C. Chaves via PacketFence-users a écrit : Hello, I am configuring the Cluster, as it appears in how to, but, after configuring mysql, it restarts and does not run anymore. Well, you're trying to run on the VIP IP. Follow log. May 16 08:25:57 pfence01 mysqld_safe: mysqld from pid file /var/lib/mysql/pfence01.pid ended May 16 08:25:58 pfence01 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release. May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB) starting as process 5868 ... May 16 08:25:58 pfence01 mysqld: 2018-05-16 08:25:58 7f104b06f900 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: Using mutexes to ref count buffer pool pages May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: The InnoDB memory heap is disabled May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: Compressed tables use zlib 1.2.7 May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: Using Linux native AIO May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: Using generic crc32 instructions May 16 08:25:58 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: Initializing buffer pool, size = 500.0M May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:58 139707954952448 [Note] InnoDB: Completed initialization of buffer pool May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [Note] InnoDB: Highest supported file format is Barracuda. May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [Note] InnoDB: 128 rollback segment(s) are active. May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [Note] InnoDB: Waiting for purge to start May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 2188830 May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139706826196736 [Note] InnoDB: Dumping buffer pool(s) not yet started May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [Note] Plugin 'FEEDBACK' is disabled. May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [Note] Server socket created on IP: '10.161.16.20'. May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 99: Cannot assign requested address May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [ERROR] Do you already have another mysqld server running on port: 3306 ? May 16 08:25:59 pfence01 mysqld: 2018-05-16 8:25:59 139707954952448 [ERROR] Aborting May 16 08:25:59 pfence01 mysqld: ^C [root@pfence01 ~]# tailf /usr/local/pf/logs/packetfence.log May 16 08:24:57 pfence01 packetfence: FATAL -e(647): unable to connect to database: Access denied for user 'pf'@'localhost' (using password: YES) at -e line 1. (pf::db::db_connect) May 16 08:24:59 pfence01 packetfence: WARN -e(647): Problem trying to run command: LANG=C sudo /sbin/iptables -S | grep input-management-if called from manager::iptables::isAlive. Child exited with non-zero value 1 (pf::util::pf_run) May 16 08:25:00 pfence01 packetfence: WARN -e(647): Problem trying to run command: LANG=C sudo /sbin/iptables -S | grep input-management-if called from manager::iptables::isAlive. Child exited with non-zero value 1 (pf::util::pf_run) May 16 08:25:00 pfence01 packetfence: INFO -e(647): saving existing iptables to /usr/local/pf/var/iptables.bak (pf::iptables::iptables_save) May 16 08:25:00 pfence01 packetfence: WARN -e(647): We are using IPSET (pf::ipset::iptables_generate) May 16 08:25:00 pfence01 packetfence: INFO -e(647): flushing iptables (pf::ipset::iptables_flush_mangle) May 16 08:25:01 pfence01 packetfence: INFO -e(647): Adding Forward rules to allow connections to the OAuth2 Providers and passthrough. (pf::iptables::generate_passthrough_rules) May 16 08:25:01 pfence01 packetfence: INFO -e(647): Adding NAT Masquerade statement. (pf::iptables::generate_passthrough_rules) May 16 08:25:01 pfence01 packetfence: INFO
Re: [PacketFence-users] Cluster PF 8.0.1
Hello Jeimerson, follow exactly what you have in https://packetfence.org/doc/PacketFence_Clustering_Guide.html . A quick look show me that you defined VIP on each interfaces, it's only use when you do a cluster of 2 with corosync and pacemaker. So follow the documentation and it should be good. Regards Fabrice Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit : Hi, Fabrice, Hello, I'm redoing the how to, for the fifteenth time, As you can see in the screenscreens, you can see that Mysql runs in the IP VIP. It only ran after I made the change in the configuration file. I am using VMware ESXi for the lab. The in port services 1443 and 9090 do not run in the IP of the management, only ip VIP. Thank you in advance. pf.conf # Hostname of PacketFence system. This is concatenated with the domain in Apache rewriting rules and therefore must be resolvable by clients. hostname=pfence001 # # general.dhcpservers # # Comma-delimited list of DHCP servers. Passthroughs are created to allow DHCP transactions from even "trapped" nodes. dhcpservers=127.0.0.1,10.161.16.21 [alerting] # # alerting.emailaddr # # Email address to which notifications of rogue DHCP servers, violations with an action of "email", or any other # PacketFence-related message goes to. emailaddr=pfence@localhost [database] # # database.pass # # Password for the mysql database used by PacketFence. Changing this parameter after the initial configuration will *not* change it in the database it self, only in the configuration. pass=zaq12wsx [advanced] # # advanced.hash_passwords # # The algorithm to use to hash the passwords in the local database. hash_passwords=ntlm [interface eth0] ip=10.161.16.28 type=management,portal,radius,high-availability vip=10.60.60.20 mask=255.255.255.0 [interface eth3] enforcement=vlan ip=10.60.60.28 type=internal vip=10.60.60.20 mask=255.255.255.0 [interface eth4] enforcement=vlan ip=10.70.70.28 type=internal vip=10.70.70.20 mask=255.255.255.0 ### log mariadb_error May 17 09:51:30 pfence01 mysqld: May 17 09:51:33 pfence01 mysqld_safe: mysqld from pid file /var/lib/mysql/pfence01.pid ended May 17 09:51:34 pfence01 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a future release. May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] /usr/sbin/mysqld (mysqld 10.1.21-MariaDB) starting as process 7740 ... May 17 09:51:34 pfence01 mysqld: 2018-05-17 09:51:34 7fa1e4855900 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator. May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Using mutexes to ref count buffer pool pages May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: The InnoDB memory heap is disabled May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Compressed tables use zlib 1.2.7 May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Using Linux native AIO May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Using generic crc32 instructions May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Initializing buffer pool, size = 500.0M May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Completed initialization of buffer pool May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Highest supported file format is Barracuda. May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: 128 rollback segment(s) are active. May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Waiting for purge to start May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.34-79.1 started; log sequence number 2229581 May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 140332171757312 [Note] InnoDB: Dumping buffer pool(s) not yet started May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] Plugin 'FEEDBACK' is disabled. May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [Note] Server socket created on IP: '10.60.60.20'. May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 [ERROR] Can't start server: Bind on TCP/IP port. Got error: 99: Cannot assign reques
Re: [PacketFence-users] Cluster PF 8.0.1
Hello Fabrice, In the how to, my interpretation is that we have to define VIP for every single interface. In order to create a new cluster, you need to configure /usr/local/pf/conf/cluster.conf on the first server of your cluster. You will need to configure it with your server hostname. To get it use : hostname in a command line. In the case of this example it will be pf1.example.com. The CLUSTER section represents the virtual IP addresses of your cluster that will be shared by your servers. In this example, eth0 is the management interface, eth1.2 is the registration interface and eth1.3 is the isolation interface. On the first server, create a configuration similar to this : [CLUSTER] management_ip=192.168.1.10 [CLUSTER interface eth0] ip=192.168.1.10 [CLUSTER interface eth1.2] ip=192.168.2.10 [CLUSTER interface eth1.3] ip=192.168.3.10 [pf1.example.com] management_ip=192.168.1.5 [pf1.example.com interface eth0] ip=192.168.1.5 [pf1.example.com interface eth1.2] ip=192.168.2.5 [pf1.example.com interface eth1.3] ip=192.168.3.5 [pf2.example.com] management_ip=192.168.1.6 [pf2.example.com interface eth0] ip=192.168.1.6 [pf2.example.com interface eth1.2] ip=192.168.2.6 [pf2.example.com interface eth1.3] ip=192.168.3.6 [pf3.example.com] management_ip=192.168.1.7 [pf3.example.com interface eth0] ip=192.168.1.7 [pf3.example.com interface eth1.2] ip=192.168.2.7 [pf3.example.com interface eth1.3] ip=192.168.3.7 Com os melhores cumprimentos. Jeimerson Chaves Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros informáticos com ele transmitidos são confidenciais, podem conter informação privilegiada e destinam-se ao conhecimento e uso exclusivo da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos mesmos ser alterado. Caso tenha recebido este e-mail indevidamente, queira informar de imediato o remetente e proceder à destruição da mensagem e de eventuais cópias. Confidentiality Warning: This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual or entity to whom they are addressed. Their contents may not be altered. lf you are not the intended recipient of this communication please notify the sender and delete and destroy all copies immediately. 2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users : > Hello Jeimerson, > > follow exactly what you have in > https://packetfence.org/doc/PacketFence_Clustering_Guide.html . > > A quick look show me that you defined VIP on each interfaces, it's only use > when you do a cluster of 2 with corosync and pacemaker. > > So follow the documentation and it should be good. > > Regards > > Fabrice > > > > Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit : > > Hi, Fabrice, > > Hello, I'm redoing the how to, for the fifteenth time, > As you can see in the screenscreens, you can see that Mysql runs in the IP > VIP. > It only ran after I made the change in the configuration file. > I am using VMware ESXi for the lab. > The in port services 1443 and 9090 do not run in the IP of the > management, only ip VIP. > > Thank you in advance. > > > pf.conf > > # Hostname of PacketFence system. This is concatenated with the > domain in Apache rewriting rules and therefore must be resolvable by > clients. > hostname=pfence001 > # > # general.dhcpservers > # > # Comma-delimited list of DHCP servers. Passthroughs are created to > allow DHCP transactions from even "trapped" nodes. > dhcpservers=127.0.0.1,10.161.16.21 > > [alerting] > # > # alerting.emailaddr > # > # Email address to which notifications of rogue DHCP servers, > violations with an action of "email", or any other > # PacketFence-related message goes to. > emailaddr=pfence@localhost > > [database] > # > # database.pass > # > # Password for the mysql database used by PacketFence. Changing this > parameter after the initial configuration will *not* change it in the > database it self, only in the configuration. > pass=zaq12wsx > > [advanced] > # > # advanced.hash_passwords > # > # The algorithm to use to hash the passwords in the local database. > hash_passwords=ntlm > > [interface eth0] > ip=10.161.16.28 > type=management,portal,radius,high-availability > vip=10.60.60.20 > mask=255.255.255.0 > > [interface eth3] > enforcement=vlan > ip=10.60.60.28 > type=internal > vip=10.60.60.20 > mask=255.255.255.0 > > [interface eth4] > enforcement=vlan > ip=10.70.70.28 > type=internal > vip=10.70.70.20 > mask=255.255.255.0 > > ### > > log mariadb_error > > > May 17 09:51:30 pfence01 mysqld: > May 17 09:51:33 pfence01 mysqld_safe: mysqld from pid file > /var/lib/mysql/pfence01.pid ended > May 17 09:51:34 pfence01 mysqld_safe: Starting mysqld daemon with > databases from /var/lib/mysql > May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34 14000406528 > [Warning] 'THREAD_CONCURRENCY' is deprecated and will be removed in a > future release. > May 17 09:51:34 pfence0
Re: [PacketFence-users] Cluster PF 8.0.1
Le 2018-05-17 à 09:09, Jeimerson C. Chaves via PacketFence-users a écrit : Hello Fabrice, In the how to, my interpretation is that we have to define VIP for every single interface. It's written nowhere in the documentation and this is probably why you can't start mysql, so remove all the vip parameter you have in pf.conf and do a "pfcmd configreload hard" The cluster.conf looks good. Regards Fabrice In order to create a new cluster, you need to configure /usr/local/pf/conf/cluster.conf on the first server of your cluster. You will need to configure it with your server hostname. To get it use : hostname in a command line. In the case of this example it will be pf1.example.com. The CLUSTER section represents the virtual IP addresses of your cluster that will be shared by your servers. In this example, eth0 is the management interface, eth1.2 is the registration interface and eth1.3 is the isolation interface. On the first server, create a configuration similar to this : [CLUSTER] management_ip=192.168.1.10 [CLUSTER interface eth0] ip=192.168.1.10 [CLUSTER interface eth1.2] ip=192.168.2.10 [CLUSTER interface eth1.3] ip=192.168.3.10 [pf1.example.com] management_ip=192.168.1.5 [pf1.example.com interface eth0] ip=192.168.1.5 [pf1.example.com interface eth1.2] ip=192.168.2.5 [pf1.example.com interface eth1.3] ip=192.168.3.5 [pf2.example.com] management_ip=192.168.1.6 [pf2.example.com interface eth0] ip=192.168.1.6 [pf2.example.com interface eth1.2] ip=192.168.2.6 [pf2.example.com interface eth1.3] ip=192.168.3.6 [pf3.example.com] management_ip=192.168.1.7 [pf3.example.com interface eth0] ip=192.168.1.7 [pf3.example.com interface eth1.2] ip=192.168.2.7 [pf3.example.com interface eth1.3] ip=192.168.3.7 Com os melhores cumprimentos. Jeimerson Chaves Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros informáticos com ele transmitidos são confidenciais, podem conter informação privilegiada e destinam-se ao conhecimento e uso exclusivo da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos mesmos ser alterado. Caso tenha recebido este e-mail indevidamente, queira informar de imediato o remetente e proceder à destruição da mensagem e de eventuais cópias. Confidentiality Warning: This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual or entity to whom they are addressed. Their contents may not be altered. lf you are not the intended recipient of this communication please notify the sender and delete and destroy all copies immediately. 2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users : Hello Jeimerson, follow exactly what you have in https://packetfence.org/doc/PacketFence_Clustering_Guide.html . A quick look show me that you defined VIP on each interfaces, it's only use when you do a cluster of 2 with corosync and pacemaker. So follow the documentation and it should be good. Regards Fabrice Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit : Hi, Fabrice, Hello, I'm redoing the how to, for the fifteenth time, As you can see in the screenscreens, you can see that Mysql runs in the IP VIP. It only ran after I made the change in the configuration file. I am using VMware ESXi for the lab. The in port services 1443 and 9090 do not run in the IP of the management, only ip VIP. Thank you in advance. pf.conf # Hostname of PacketFence system. This is concatenated with the domain in Apache rewriting rules and therefore must be resolvable by clients. hostname=pfence001 # # general.dhcpservers # # Comma-delimited list of DHCP servers. Passthroughs are created to allow DHCP transactions from even "trapped" nodes. dhcpservers=127.0.0.1,10.161.16.21 [alerting] # # alerting.emailaddr # # Email address to which notifications of rogue DHCP servers, violations with an action of "email", or any other # PacketFence-related message goes to. emailaddr=pfence@localhost [database] # # database.pass # # Password for the mysql database used by PacketFence. Changing this parameter after the initial configuration will *not* change it in the database it self, only in the configuration. pass=zaq12wsx [advanced] # # advanced.hash_passwords # # The algorithm to use to hash the passwords in the local database. hash_passwords=ntlm [interface eth0] ip=10.161.16.28 type=management,portal,radius,high-availability vip=10.60.60.20 mask=255.255.255.0 [interface eth3] enforcement=vlan ip=10.60.60.28 type=internal vip=10.60.60.20 mask=255.255.255.0 [interface eth4] enforcement=vlan ip=10.70.70.28 type=internal vip=10.70.70.20 mask=255.255.255.0 ### log mariadb_error May 17 09:51:30 pfence01 mysqld: May 17 09:51:33 pfence01 mysqld_safe: mysqld from pid file /var/lib/mysql/pfence01.pid ended May 17 09:51:34 pfence01 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql May 17 09:51:34 pfence01 mysqld: 2018-05-17 9:51:34
Re: [PacketFence-users] Cluster PF 8.0.1
So VIP address is only for the management interface correct? Do we have to point to that VIP address in the other managements interface? Something like this: eth0 in pfence01: IP: 10.160.26.28 VIP: 10.160.26.20 eth0 in pfence02: IP: 10.160.26.29 VIP: 10.160.26.20 eth0 in pfence03: IP: 10.160.26.30 VIP: 10.160.26.20 Kind Regards Com os melhores cumprimentos. Jeimerson Chaves Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros informáticos com ele transmitidos são confidenciais, podem conter informação privilegiada e destinam-se ao conhecimento e uso exclusivo da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos mesmos ser alterado. Caso tenha recebido este e-mail indevidamente, queira informar de imediato o remetente e proceder à destruição da mensagem e de eventuais cópias. Confidentiality Warning: This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual or entity to whom they are addressed. Their contents may not be altered. lf you are not the intended recipient of this communication please notify the sender and delete and destroy all copies immediately. 2018-05-17 14:31 GMT+01:00 Fabrice Durand via PacketFence-users : > > > Le 2018-05-17 à 09:09, Jeimerson C. Chaves via PacketFence-users a écrit : >> >> Hello Fabrice, >> >> In the how to, my interpretation is that we have to define VIP for >> every single interface. > > It's written nowhere in the documentation and this is probably why you can't > start mysql, so remove all the vip parameter you have in pf.conf and do a > "pfcmd configreload hard" > The cluster.conf looks good. > > Regards > Fabrice > > >> >> >> In order to create a new cluster, you need to configure >> /usr/local/pf/conf/cluster.conf on the first server of your cluster. >> >> You will need to configure it with your server hostname. To get it use >> : hostname in a command line. >> >> In the case of this example it will be pf1.example.com. >> >> The CLUSTER section represents the virtual IP addresses of your >> cluster that will be shared by your servers. >> >> In this example, eth0 is the management interface, eth1.2 is the >> registration interface and eth1.3 is the isolation interface. >> >> On the first server, create a configuration similar to this : >> >> [CLUSTER] >> management_ip=192.168.1.10 >> >> [CLUSTER interface eth0] >> ip=192.168.1.10 >> >> [CLUSTER interface eth1.2] >> ip=192.168.2.10 >> >> [CLUSTER interface eth1.3] >> ip=192.168.3.10 >> >> [pf1.example.com] >> management_ip=192.168.1.5 >> >> [pf1.example.com interface eth0] >> ip=192.168.1.5 >> >> [pf1.example.com interface eth1.2] >> ip=192.168.2.5 >> >> [pf1.example.com interface eth1.3] >> ip=192.168.3.5 >> >> [pf2.example.com] >> management_ip=192.168.1.6 >> >> [pf2.example.com interface eth0] >> ip=192.168.1.6 >> >> [pf2.example.com interface eth1.2] >> ip=192.168.2.6 >> >> [pf2.example.com interface eth1.3] >> ip=192.168.3.6 >> >> [pf3.example.com] >> management_ip=192.168.1.7 >> >> [pf3.example.com interface eth0] >> ip=192.168.1.7 >> >> [pf3.example.com interface eth1.2] >> ip=192.168.2.7 >> >> [pf3.example.com interface eth1.3] >> ip=192.168.3.7 >> Com os melhores cumprimentos. >> >> Jeimerson Chaves >> >> Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros >> informáticos com ele transmitidos são confidenciais, podem conter >> informação privilegiada e destinam-se ao conhecimento e uso exclusivo >> da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos >> mesmos ser alterado. Caso tenha recebido este e-mail indevidamente, >> queira informar de imediato o remetente e proceder à destruição da >> mensagem e de eventuais cópias. >> >> Confidentiality Warning: This e-mail and any files transmitted with it >> are confidential and may be privileged and are intended solely for the >> use of the individual or entity to whom they are addressed. Their >> contents may not be altered. lf you are not the intended recipient of >> this communication please notify the sender and delete and destroy all >> copies immediately. >> >> >> >> >> 2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users >> : >>> >>> Hello Jeimerson, >>> >>> follow exactly what you have in >>> https://packetfence.org/doc/PacketFence_Clustering_Guide.html . >>> >>> A quick look show me that you defined VIP on each interfaces, it's only >>> use >>> when you do a cluster of 2 with corosync and pacemaker. >>> >>> So follow the documentation and it should be good. >>> >>> Regards >>> >>> Fabrice >>> >>> >>> >>> Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit >>> : >>> >>> Hi, Fabrice, >>> >>> Hello, I'm redoing the how to, for the fifteenth time, >>> As you can see in the screenscreens, you can see that Mysql runs in the >>> IP >>> VIP. >>> It only ran after I made the change in the configuration file. >>> I am using VMware ESXi for the lab. >>> The in port services 1443 and 9090 do
Re: [PacketFence-users] Cluster PF 8.0.1
No, if you do a cluster of 3 then all the vip are defined in cluster.conf and not in pf.conf, so if you still have some vip= parameters in pf.conf then remove them. If you do a cluster of 2 (active/passive) then you have to deal with vip= in pf.conf. Regards Fabrice Le 2018-05-17 à 10:00, Jeimerson C. Chaves via PacketFence-users a écrit : So VIP address is only for the management interface correct? Do we have to point to that VIP address in the other managements interface? Something like this: eth0 in pfence01: IP: 10.160.26.28 VIP: 10.160.26.20 eth0 in pfence02: IP: 10.160.26.29 VIP: 10.160.26.20 eth0 in pfence03: IP: 10.160.26.30 VIP: 10.160.26.20 Kind Regards Com os melhores cumprimentos. Jeimerson Chaves Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros informáticos com ele transmitidos são confidenciais, podem conter informação privilegiada e destinam-se ao conhecimento e uso exclusivo da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos mesmos ser alterado. Caso tenha recebido este e-mail indevidamente, queira informar de imediato o remetente e proceder à destruição da mensagem e de eventuais cópias. Confidentiality Warning: This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual or entity to whom they are addressed. Their contents may not be altered. lf you are not the intended recipient of this communication please notify the sender and delete and destroy all copies immediately. 2018-05-17 14:31 GMT+01:00 Fabrice Durand via PacketFence-users : Le 2018-05-17 à 09:09, Jeimerson C. Chaves via PacketFence-users a écrit : Hello Fabrice, In the how to, my interpretation is that we have to define VIP for every single interface. It's written nowhere in the documentation and this is probably why you can't start mysql, so remove all the vip parameter you have in pf.conf and do a "pfcmd configreload hard" The cluster.conf looks good. Regards Fabrice In order to create a new cluster, you need to configure /usr/local/pf/conf/cluster.conf on the first server of your cluster. You will need to configure it with your server hostname. To get it use : hostname in a command line. In the case of this example it will be pf1.example.com. The CLUSTER section represents the virtual IP addresses of your cluster that will be shared by your servers. In this example, eth0 is the management interface, eth1.2 is the registration interface and eth1.3 is the isolation interface. On the first server, create a configuration similar to this : [CLUSTER] management_ip=192.168.1.10 [CLUSTER interface eth0] ip=192.168.1.10 [CLUSTER interface eth1.2] ip=192.168.2.10 [CLUSTER interface eth1.3] ip=192.168.3.10 [pf1.example.com] management_ip=192.168.1.5 [pf1.example.com interface eth0] ip=192.168.1.5 [pf1.example.com interface eth1.2] ip=192.168.2.5 [pf1.example.com interface eth1.3] ip=192.168.3.5 [pf2.example.com] management_ip=192.168.1.6 [pf2.example.com interface eth0] ip=192.168.1.6 [pf2.example.com interface eth1.2] ip=192.168.2.6 [pf2.example.com interface eth1.3] ip=192.168.3.6 [pf3.example.com] management_ip=192.168.1.7 [pf3.example.com interface eth0] ip=192.168.1.7 [pf3.example.com interface eth1.2] ip=192.168.2.7 [pf3.example.com interface eth1.3] ip=192.168.3.7 Com os melhores cumprimentos. Jeimerson Chaves Aviso de Confidencialidade: Este e-mail e quaisquer ficheiros informáticos com ele transmitidos são confidenciais, podem conter informação privilegiada e destinam-se ao conhecimento e uso exclusivo da pessoa ou entidade a quem são dirigidos, não podendo o conteúdo dos mesmos ser alterado. Caso tenha recebido este e-mail indevidamente, queira informar de imediato o remetente e proceder à destruição da mensagem e de eventuais cópias. Confidentiality Warning: This e-mail and any files transmitted with it are confidential and may be privileged and are intended solely for the use of the individual or entity to whom they are addressed. Their contents may not be altered. lf you are not the intended recipient of this communication please notify the sender and delete and destroy all copies immediately. 2018-05-17 13:39 GMT+01:00 Fabrice Durand via PacketFence-users : Hello Jeimerson, follow exactly what you have in https://packetfence.org/doc/PacketFence_Clustering_Guide.html . A quick look show me that you defined VIP on each interfaces, it's only use when you do a cluster of 2 with corosync and pacemaker. So follow the documentation and it should be good. Regards Fabrice Le 2018-05-17 à 06:08, Jeimerson C. Chaves via PacketFence-users a écrit : Hi, Fabrice, Hello, I'm redoing the how to, for the fifteenth time, As you can see in the screenscreens, you can see that Mysql runs in the IP VIP. It only ran after I made the change in the configuration file. I am using VMware ESXi for the lab. The in port services 1443 and 9090 do not run in the IP of the