That just means that the dataload got interrupted for some reason, and never 
marked it as "completed."

Just delete those "status: running" rows from the table, and the next ODW 
import will pick up where it left off.

Mike



-----Original Message-----
From: [email protected] on behalf of Ben Spade
Sent: Tue 10/20/2009 6:48 PM
To: [email protected]
Subject: [opsview-users] Problem with ODW - thinks 'there are runningdataloads'
 

The master servers are complaining that the 'Opsview Data Warehouse Status' is 
critical. 
(I have two Opsview installations, with a shared ODW database, one of them 
being 'opsview_instance_id' of 1, the other 'opsview_instance_id' of 2). When I 
look at the common ODW database, I see:
mysql> select * from dataloads where status != 'success'\G
*************************** 1. row ***************************
                 id: 832
opsview_instance_id: 1
 period_start_timev: 1256018400
   period_end_timev: 1256021999
   load_start_timev: 1256022241
     load_end_timev: NULL
             status: running
*************************** 2. row ***************************
                 id: 836
opsview_instance_id: 2
 period_start_timev: 1256032800
   period_end_timev: 1256036399
   load_start_timev: 1256036642
     load_end_timev: NULL
             status: running
2 rows in set (0.00 sec)

but there is nothing running against that database.  

So what do I do?  I see where the perl code is finding the above records and 
refusing to proceed, so what do I have to do to make it happy?

Thanks in advance,
Ben

That just means that the dataload got interrupted for some reason, and never 
marked it as "completed."

Just delete those "status: running" rows from the table, and the next ODW 
import will pick up where it left off.

Mike



-----Original Message-----
From: [email protected] on behalf of Ben Spade
Sent: Tue 10/20/2009 6:48 PM
To: [email protected]
Subject: [opsview-users] Problem with ODW - thinks 'there are runningdataloads'
 

The master servers are complaining that the 'Opsview Data Warehouse Status' is 
critical. 
(I have two Opsview installations, with a shared ODW database, one of them 
being 'opsview_instance_id' of 1, the other 'opsview_instance_id' of 2). When I 
look at the common ODW database, I see:
mysql> select * from dataloads where status != 'success'\G
*************************** 1. row ***************************
                 id: 832
opsview_instance_id: 1
 period_start_timev: 1256018400
   period_end_timev: 1256021999
   load_start_timev: 1256022241
     load_end_timev: NULL
             status: running
*************************** 2. row ***************************
                 id: 836
opsview_instance_id: 2
 period_start_timev: 1256032800
   period_end_timev: 1256036399
   load_start_timev: 1256036642
     load_end_timev: NULL
             status: running
2 rows in set (0.00 sec)

but there is nothing running against that database.  

So what do I do?  I see where the perl code is finding the above records and 
refusing to proceed, so what do I have to do to make it happy?

Thanks in advance,
Ben

_______________________________________________
Opsview-users mailing list
[email protected]
http://lists.opsview.org/lists/listinfo/opsview-users

Reply via email to