search for: natgw

...installed CentOS 3.3 and kept the machine up2date. I installed poptop and the newest ppp-cvs version ( ppp-2.4.3-0.cvs_20040527.6) We are running a ssh + ppp tunnel for our internet tunnel/tunnel to our NOC. After the upgrade we see these error messages while starting the tunnel: Jan 24 15:00:40 natgw modprobe: modprobe: Can't locate module ppp-compress-26 Jan 24 15:00:40 natgw modprobe: modprobe: Can't locate module ppp-compress-24 Jan 24 15:00:41 natgw modprobe: modprobe: Can't locate module ppp-compress-21 Jan 24 15:00:41 natgw modprobe: modprobe: Can't locate module ppp-compr...

Hi Max, On Wed, 2 Oct 2019 15:08:43 +0000, Max DiOrio <Max.DiOrio at ieeeglobalspec.com> wrote: > As soon as I made the configuration change and restarted CTDB, it crashes. > > Oct 2 11:05:14 hq-6pgluster01 systemd: Started CTDB. > Oct 2 11:05:21 hq-6pgluster01 systemd: ctdb.service: main process exited, code=exited, status=1/FAILURE > Oct 2 11:05:21 hq-6pgluster01

...'s running them all. Also have no idea why it's listing the legacy scripts twice here, and the list is different. > > [[LAColo-Prod] root at hq-6pgluster01 ~]# ctdb event script list legacy > * 00.ctdb > 01.reclock > 05.system > 06.nfs > * 10.interface > 11.natgw > 11.routing > 13.per_ip_routing > 20.multipathd > 31.clamd > 40.vsftpd > 41.httpd > 49.winbind > 50.samba > 60.nfs > 70.iscsi > 91.lvs > > * 01.reclock > 05.system > * 06.nfs > 11.natgw > 11.routing > 13.per_ip_ro...

...pts disabled, yet the startup shows that's running them all. Also have no idea why it's listing the legacy scripts twice here, and the list is different. [[LAColo-Prod] root at hq-6pgluster01 ~]# ctdb event script list legacy * 00.ctdb 01.reclock 05.system 06.nfs * 10.interface 11.natgw 11.routing 13.per_ip_routing 20.multipathd 31.clamd 40.vsftpd 41.httpd 49.winbind 50.samba 60.nfs 70.iscsi 91.lvs * 01.reclock 05.system * 06.nfs 11.natgw 11.routing 13.per_ip_routing 20.multipathd 31.clamd 40.vsftpd 41.httpd 49.winbind 50.samba * 60.nfs...

...t's running them all. Also have no idea why it's listing the legacy scripts twice here, and the list is different. > > [[LAColo-Prod] root at hq-6pgluster01 ~]# ctdb event script list legacy > * 00.ctdb > 01.reclock > 05.system > 06.nfs > * 10.interface > 11.natgw > 11.routing > 13.per_ip_routing > 20.multipathd > 31.clamd > 40.vsftpd > 41.httpd > 49.winbind > 50.samba > 60.nfs > 70.iscsi > 91.lvs > > * 01.reclock > 05.system > * 06.nfs > 11.natgw > 11.routing > 13.per_ip_rou...

...k me as kind of odd: "Each NN must be unique and duplicates will cause undefined behaviour. I.e. having both 10.interfaces and 10.otherstuff is not allowed." I say this is odd as I have three 11's which were put in on the default install: -rwxr-xr-x 1 root root 2178 Jun 29 2009 11.natgw -rwxr-xr-x 1 root root 340 Jul 17 2009 11.route -rwxr-xr-x 1 root root 798 Jun 29 2009 11.routing So either the note is wrong, or perhaps it is part of my bug. In addition, I read in the 11.route file the comment about adding a static-routes file. I had not previously had this file so I thou...

...). CTDB CHANGES ============ * The NAT gateway and LVS features now uses the term "leader" to refer to the main node in a group through which traffic is routed and "follower" for other members of a group. The command for determining the leader has changed to "ctdb natgw leader" (from "ctdb natgw master"). The configuration keyword for indicating that a node can not be the leader of a group has changed to "follower-only" (from "slave-only"). Identical changes were made for LVS. * Remove "ctdb isnotrecmaster" c...

...). CTDB CHANGES ============ * The NAT gateway and LVS features now uses the term "leader" to refer to the main node in a group through which traffic is routed and "follower" for other members of a group. The command for determining the leader has changed to "ctdb natgw leader" (from "ctdb natgw master"). The configuration keyword for indicating that a node can not be the leader of a group has changed to "follower-only" (from "slave-only"). Identical changes were made for LVS. * Remove "ctdb isnotrecmaster" c...

...). CTDB CHANGES ============ * The NAT gateway and LVS features now uses the term "leader" to refer to the main node in a group through which traffic is routed and "follower" for other members of a group. The command for determining the leader has changed to "ctdb natgw leader" (from "ctdb natgw master"). The configuration keyword for indicating that a node can not be the leader of a group has changed to "follower-only" (from "slave-only"). Identical changes were made for LVS. * Remove "ctdb isnotrecmaster" c...

...). CTDB CHANGES ============ * The NAT gateway and LVS features now uses the term "leader" to refer to the main node in a group through which traffic is routed and "follower" for other members of a group. The command for determining the leader has changed to "ctdb natgw leader" (from "ctdb natgw master"). The configuration keyword for indicating that a node can not be the leader of a group has changed to "follower-only" (from "slave-only"). Identical changes were made for LVS. * Remove "ctdb isnotrecmaster" c...

...). CTDB CHANGES ============ * The NAT gateway and LVS features now uses the term "leader" to refer to the main node in a group through which traffic is routed and "follower" for other members of a group. The command for determining the leader has changed to "ctdb natgw leader" (from "ctdb natgw master"). The configuration keyword for indicating that a node can not be the leader of a group has changed to "follower-only" (from "slave-only"). Identical changes were made for LVS. * Remove "ctdb isnotrecmaster" c...

...). CTDB CHANGES ============ * The NAT gateway and LVS features now uses the term "leader" to refer to the main node in a group through which traffic is routed and "follower" for other members of a group. The command for determining the leader has changed to "ctdb natgw leader" (from "ctdb natgw master"). The configuration keyword for indicating that a node can not be the leader of a group has changed to "follower-only" (from "slave-only"). Identical changes were made for LVS. * Remove "ctdb isnotrecmaster" c...

...root at fs1:~# ctdb scriptstatus 11 scripts were executed last monitor cycle 00.ctdb Status:OK Duration:0.031 Fri Dec 5 14:00:52 2014 01.reclock Status:OK Duration:0.125 Fri Dec 5 14:00:52 2014 10.interface Status:OK Duration:0.215 Fri Dec 5 14:00:52 2014 11.natgw Status:OK Duration:0.021 Fri Dec 5 14:00:53 2014 11.routing Status:OK Duration:0.037 Fri Dec 5 14:00:53 2014 13.per_ip_routing Status:OK Duration:0.021 Fri Dec 5 14:00:53 2014 20.multipathd Status:DISABLED 31.clamd Status:DISABLED 40.vsftpd...

...potential performance impacts on nodes * CTDB_RECOVERY_LOCK now supports specification of an external helper to take and hold the recovery lock See the RECOVERY LOCK section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands * The onnode command no longer supports the "recmaster", "lvs" and "natgw" node specifications * Faster rese...

...potential performance impacts on nodes * CTDB_RECOVERY_LOCK now supports specification of an external helper to take and hold the recovery lock See the RECOVERY LOCK section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands * The onnode command no longer supports the "recmaster", "lvs" and "natgw" node specifications * Faster rese...

...tential performance impacts on nodes. * CTDB_RECOVERY_LOCK now supports specification of an external helper to take and hold the recovery lock. See the RECOVERY LOCK section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. *...

...tential performance impacts on nodes. * CTDB_RECOVERY_LOCK now supports specification of an external helper to take and hold the recovery lock. See the RECOVERY LOCK section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. *...

...tential performance impacts on nodes. * CTDB_RECOVERY_LOCK now supports specification of an external helper to take and hold the recovery lock. See the RECOVERY LOCK section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. *...

...tential performance impacts on nodes. * CTDB_RECOVERY_LOCK now supports specification of an external helper to take and hold the recovery lock. See the RECOVERY LOCK section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. *...

...tential performance impacts on nodes. * CTDB_RECOVERY_LOCK now supports specification of an external helper to take and hold the recovery lock. See the RECOVERY LOCK section in ctdb(7) for details. Documentation for writing helpers is provided in doc/cluster_mutex_helper.txt. * "ctdb natgwlist" has been replaced by a top level "ctdb natgw" command that has "master", "list" and "status" subcommands. * The 'onnode' command no longer supports the "recmaster", "lvs" and "natgw" node specifications. *...