@ -24,6 +24,11 @@ Set the log level to 1, 2 or 3 respectively. Be aware that level 3 generates a s
\fB\-\-age\-out\-database\fR
\fB\-\-age\-out\-database\fR
This requests the database check for records that are too old and purge them.
This requests the database check for records that are too old and purge them.
.TP
.TP
\fB\-\-auto\-grow\-pv\fR
This looks at LVM physical volumes on the local host. For each one that is found, 'parted' is called to check if there's more that 1 GiB of free space available after it. If so, it will extend the PV partition to use the free space.
.TP
If you deleted the default '/home' partition during the install of a subnode or DR host, this should give you that space back.
.TP
\fB\-\-check\-configured\fR
\fB\-\-check\-configured\fR
Check to see if the host is marked as configured or yet.
Check to see if the host is marked as configured or yet.
.TP
.TP
@ -33,6 +38,9 @@ This checks to see if the database is enabled or not.
\fB\-\-check\-network\-mapping\fR
\fB\-\-check\-network\-mapping\fR
This reports if the host is currently in network mapping (this disables several features and watches the network states much more frequently)
This reports if the host is currently in network mapping (this disables several features and watches the network states much more frequently)
.TP
.TP
\fB\-\-confirm\fR
This confirms actions that would normally prompt the user to confirm before proceeding.
.TP
\fB\-\-database\-active\fR
\fB\-\-database\-active\fR
This enables the database on the local Striker dashboard.
This enables the database on the local Striker dashboard.
@ -735,6 +735,7 @@ The XML that failed sanity check was:
]]></key>
]]></key>
<keyname="error_0465"><![CDATA[The file: [#!variable!file!#] doesn't exist on the target: [#!variable!target!#].]]></key>
<keyname="error_0465"><![CDATA[The file: [#!variable!file!#] doesn't exist on the target: [#!variable!target!#].]]></key>
<keyname="error_0466"><![CDATA[The Anvil! string (name or UUID): [#!variable!string!#] didn't match any known Anvil! in the database.]]></key>
<keyname="error_0466"><![CDATA[The Anvil! string (name or UUID): [#!variable!string!#] didn't match any known Anvil! in the database.]]></key>
<keyname="error_0467"><![CDATA[[ Error ] - The repartition attemp failed! Reloading the partition table now!]]]></key>
<!-- Files templates -->
<!-- Files templates -->
<!-- NOTE: Translating these files requires an understanding of which lines are translatable -->
<!-- NOTE: Translating these files requires an understanding of which lines are translatable -->
@ -2633,6 +2634,22 @@ The file: [#!variable!file!#] needs to be updated. The difference is:
<keyname="log_0818">The server: [#!variable!server_name!#] libvirt definition will now be updated.</key>
<keyname="log_0818">The server: [#!variable!server_name!#] libvirt definition will now be updated.</key>
<keyname="log_0819">Check to verify that the connection to the server: [#!variable!server_name!#] is valid.</key>
<keyname="log_0819">Check to verify that the connection to the server: [#!variable!server_name!#] is valid.</key>
<keyname="log_0820">The network mapping flag is NOT set.</key>
<keyname="log_0820">The network mapping flag is NOT set.</key>
<keyname="log_0821">No device found for PV: [#!variable!pv_name!#], skipping it.</key>
<keyname="log_0822">Found: [#!variable!free_space!#] free space after the PV partition: [#!variable!device_path!#:#!variable!pv_partition!#]! Will grow the partition to use the free space.</key>
<keyname="log_0823">Found: [#!variable!free_space!#] free space after the PV partition: [#!variable!device_path!#:#!variable!pv_partition!#]. This is too small for auto-growing the partition.</key>
<keyname="log_0824">Found the PV partition: [#!variable!device_path!#:#!variable!device_partition!#], but there's another partition after it. Not going to grow it, of course.</key>
<keyname="log_0825">The partition: [#!variable!pv_name!#] appears to have been grown successfully. The new partition scheme is:
====
#!variable!output!#
====
</key>
<keyname="log_0826">The resize appears to have been successful. The physical volume: [#!variable!pv_name!#] details are now:
====
#!variable!output!#
====
</key>
<keyname="log_0827">The physical volume: [#!variable!pv_name!#] has been resized!</key>
<keyname="log_0828">The user answered: [#!variable!answer!#]</key>
<!-- Messages for users (less technical than log entries), though sometimes used for logs, too. -->
<!-- Messages for users (less technical than log entries), though sometimes used for logs, too. -->
<keyname="message_0001">The host name: [#!variable!target!#] does not resolve to an IP address.</key>
<keyname="message_0001">The host name: [#!variable!target!#] does not resolve to an IP address.</key>
@ -3186,6 +3203,26 @@ Proceed? [y/N]</key>
<keyname="message_0355">This host is already NOT configured to map the network.</key>
<keyname="message_0355">This host is already NOT configured to map the network.</key>
<keyname="message_0356">This host is no longer configured to map the network.</key>
<keyname="message_0356">This host is no longer configured to map the network.</key>
<keyname="message_0357">No hosts with IPMI found, done.</key>
<keyname="message_0357">No hosts with IPMI found, done.</key>
<keyname="message_0358">Searching for free space to grow PVs into.</key>
<keyname="message_0359">- The '--confirm' switch was used, proceeding.</key>
<keyname="message_0360"><![CDATA[
[ Warning ] - Auto-growing the LVM physical volumes could, in some case, leave the system unbootable.
The steps that will taken are;
- LVM Pyhiscal volumes will be found.
- For each found, 'parted' is used to see if there is > 1GiB of free space available.
- If so, and if no other partitions are after it, it will be grown to use the free space.
- The PV itself will then be resized to use the new space
This is generally used just after initializing a new subnode or DR host. If this host has real data
on it, please proceed with caution.
The partition table will be backed up, and if the partition resize fails, the partition table will be
reloaded automatically. If this host has real data, ensure a complete backup is available before
proceeding.
]]></key>
<keyname="message_0361">- [ Note ] - The original partition table for: [#!variable!device_path!#] has been saved to: [#!variable!partition_backup!#]
If anything goes wrong, we will attempt to recover automatically. If needed, you can try
<keyname="name_0001">Normal Password</key><!-- none in mail-server -->
<keyname="name_0001">Normal Password</key><!-- none in mail-server -->
@ -3933,7 +3970,11 @@ We will wait: [#!variable!waiting!#] seconds and then try again. We'll give up i
<keyname="warning_0156">[ Warning ] - The file: [#!variable!file_path!#] needed to provision the server: [#!variable!server_name!#] was found, but it's not ready yet.</key>
<keyname="warning_0156">[ Warning ] - The file: [#!variable!file_path!#] needed to provision the server: [#!variable!server_name!#] was found, but it's not ready yet.</key>
<keyname="warning_0157">[ Warning ] - Waiting for a bit, and then will check if files are ready.</key>
<keyname="warning_0157">[ Warning ] - Waiting for a bit, and then will check if files are ready.</key>
<keyname="warning_0158">[ Warning ] - There is a duplicate storage group named: [#!variable!group_name!#]. Keeping the group with UUID: [#!variable!keep_uuid!#], and deleting the group with the UUID: [#!variable!delete_uuid!#]</key>
<keyname="warning_0158">[ Warning ] - There is a duplicate storage group named: [#!variable!group_name!#]. Keeping the group with UUID: [#!variable!keep_uuid!#], and deleting the group with the UUID: [#!variable!delete_uuid!#]</key>
<keyname="warning_0159">Please specify a storage group to use to add the new drive to.</key>
<keyname="warning_0159">[ Warning ] - The system call: [#!variable!shell_call!#] returned the non-zero return code: [#!variable!return_code!#]. The command output, if anything, was:
====
#!variable!output!#
====
</key>
<keyname="warning_0160"> Warning!
<keyname="warning_0160"> Warning!
[ Warning ] - When trying to create the local meta-data on: [#!variable!drbd_resource!#/#!variable!next_drbd_volume!#]
[ Warning ] - When trying to create the local meta-data on: [#!variable!drbd_resource!#/#!variable!next_drbd_volume!#]
[ Warning ] - using the command: [#!variable!shell_call!#]
[ Warning ] - using the command: [#!variable!shell_call!#]
@ -3970,6 +4011,7 @@ We will try to proceed anyway.</key>
#!variable!error!#
#!variable!error!#
====
====
</key>
</key>
<keyname="warning_0168">Please specify a storage group to use to add the new drive to.</key>