* Updated the RPM to .13 to disable postun's disabling of postgres, which breaks Anvil! software using the database during RPM updates.
* Fixed a logging bug where the number of DB connections was not inserting the number properly.
* Fixed exits in tools/anvil-prep-database.
Signed-off-by: Digimer <digimer@alteeve.ca>
@ -230,7 +230,7 @@ The database connection error was:
<keyname="log_0129">all</key><!-- Used when logging DB writes to all DBs -->
<keyname="log_0129">all</key><!-- Used when logging DB writes to all DBs -->
<keyname="log_0130"><![CDATA[[ Error ] - The method: [#!variable!method!#] was called and the parameter: [#!variable!parameter!#] was passed an invalid UUID: [#!variable!uuid!#].]]></key>
<keyname="log_0130"><![CDATA[[ Error ] - The method: [#!variable!method!#] was called and the parameter: [#!variable!parameter!#] was passed an invalid UUID: [#!variable!uuid!#].]]></key>
<keyname="log_0132">Connected to: [#!variable!connections!#] database(s).</key>
<keyname="log_0132">Connected to: [#!data!sys::db_connections!#] database(s).</key>
<keyname="log_0133">Failed to read the system UUID. Received a non-UUID string: [#!variable!uuid!#]. Is the user: [#!variable!user!#] in the 'kmem' group?</key>
<keyname="log_0133">Failed to read the system UUID. Received a non-UUID string: [#!variable!uuid!#]. Is the user: [#!variable!user!#] in the 'kmem' group?</key>
<keyname="log_0134">The read host UUID: [#!variable!uuid!#] does not appear to be a valid UUID.</key>
<keyname="log_0134">The read host UUID: [#!variable!uuid!#] does not appear to be a valid UUID.</key>
<keyname="log_0135">Runtime was approximately: [#!variable!runtime!#] seconds.</key>
<keyname="log_0135">Runtime was approximately: [#!variable!runtime!#] seconds.</key>
@ -460,6 +460,14 @@ Here we will inject 't_0006', which injects 't_0001' which has a variable: [#!st
<keyname="error_0030"><![CDATA[Failed to process the template: [<span class="code">#!variable!template!#</span>] in the template file: [<span class="code">#!variable!file!#</span>]. Details of the problem should be in: [<span class="code">#!data!sys::log_file!#</span>].]]></key>
<keyname="error_0030"><![CDATA[Failed to process the template: [<span class="code">#!variable!template!#</span>] in the template file: [<span class="code">#!variable!file!#</span>]. Details of the problem should be in: [<span class="code">#!data!sys::log_file!#</span>].]]></key>
<keyname="error_0031">The 'host-uuid': [#!variable!host_uuid!#] is not valid.</key>
<keyname="error_0031">The 'host-uuid': [#!variable!host_uuid!#] is not valid.</key>
<keyname="error_0032">The '#!variable!switch!#' switch is missing.</key>
<keyname="error_0032">The '#!variable!switch!#' switch is missing.</key>
<keyname="error_0033">The job UUID was passed via '--job-uuid' but the passed in value: [#!variable!uuid!#] is not a valid UUID.</key>
<keyname="error_0034">The job UUID was passed via '--job-uuid': [#!variable!uuid!#] doesn't match a job in the database.</key>
<keyname="error_0035">
The update appears to have not completed successfully. The output was:
====
#!variable!output!#
====
</key>
<!-- These are units, words and so on used when displaying information. -->
<!-- These are units, words and so on used when displaying information. -->
job_host_uuiduuidnotnull,-- This is the host that requested the job
job_host_uuiduuidnotnull,-- This is the host that requested the job
job_commandtextnotnull,-- This is the command to run (usually a shell call).
job_commandtextnotnull,-- This is the command to run (usually a shell call).
job_datatextnotnull,-- This is optional data to be used by anvil-data
job_datatextnotnull,--
job_picked_up_bynumericnotnulldefault0,-- This is the PID of the 'anvil-jobs' script that picked up the job.
job_picked_up_bynumericnotnulldefault0,-- This is the PID of the 'anvil-jobs' script that picked up the job.
job_picked_up_atnumericnotnulldefault0,-- This is unix timestamp of when the job was picked up.
job_picked_up_atnumericnotnulldefault0,-- This is unix timestamp of when the job was picked up.
job_updatednumericnotnulldefault0,-- This is unix timestamp that is perdiodically updated for jobs that take a long time. It is used to help determine when a job is hung.
job_updatednumericnotnulldefault0,-- This is unix timestamp that is perdiodically updated for jobs that take a long time. It is used to help determine when a job is hung.