[Spacewalk-list] Spacewalk 1.4 monitoring
Jan Pazdziora
jpazdziora at redhat.com
Fri Jul 22 13:19:07 UTC 2011
On Thu, Jul 21, 2011 at 08:35:58AM +0200, "Rodriguez Nuño, Claudia" wrote:
> Hi
> It's quite a long since I wrote that message, I gave up on trying to make it work, I'm waiting for spacewalk 1.5
> Anyway, I don't know if those modifications are the problem but without them monitoring scout wouldn't start.
> Modifications are:
>
> at /usr/lib/perl5/vendor_perl/5.8.8/RHN/DB.pm
>
> @@ -370,7 +370,7 @@ sub disconnect {
> my $dbh = shift;
>
> if ($dbh->{private_from_cache}) {
> - $dbh->set_err("Can't disconnect cache-loaded RHN::DB handle");
> + $dbh->set_err(99999, "Can't disconnect cache-loaded RHN::DB handle");
> }
> else {
> $dbh->SUPER::disconnect(@_);
> @@ -533,7 +533,7 @@ sub execute_h {
> my $self = shift;
> my @params = @_;
>
> - $self->set_err("Odd number of params to execute_h") if @params % 2;
> + $self->set_err(99998, "Odd number of params to execute_h") if @params % 2;
>
> while (my ($k, $v) = (splice @params, 0, 2, ())) {
>
>
> at /usr/lib/perl5/vendor_perl/5.8.8/NOCpulse/SatConfig/GenerateConfig.pm
>
> @@ -24,7 +24,7 @@ sub handler {
>
> SatClusterRecord->LoadFromSqlWithBind(q{
> select sat_cluster.recid, sat_cluster.customer_id,
> --location_name "physical_location_name",
> ++location_name as physical_location_name,
> sat_node.max_concurrent_checks, sat_node.sched_log_level,
> sat_node.sput_log_level, sat_node.dq_log_level
> from sat_cluster, sat_node, physical_location
> @@ -41,7 +41,7 @@ sub handler {
> my $satCluster = SatClusterRecord->InstancesList->[0];
>
> my $customerId = $satCluster->get_CUSTOMER_ID;
> --my $location = $satCluster->get_physical_location_name;
> ++my $location = $satCluster->get_PHYSICAL_LOCATION_NAME;
>
> # Get the auto_update flag
> CFDBRecord->LoadFromSqlWithBind(q{
>
>
> at /usr/lib/perl5/vendor_perl/5.8.8/NOCpulse/NPRecords.pm
>
> line 338 change HostAddress for HOSTADDRESS
>
>
>
> I don't remember where did I took them from, sorry, but it is not something I came up with. I think the explanation was modifications were related to changes in database variables to capital letters, and/or something about transaction mode
>
Not -- it's commits 4a855ee10d5dd0527691dacec424896048563c5b and
dd69d8fe96a1337a65d8d645f9ecd0d9b05342d0 -- thank you for the
confirmation.
--
Jan Pazdziora
Principal Software Engineer, Satellite Engineering, Red Hat
More information about the Spacewalk-list
mailing list