Absent Member.. Absent Member..
Absent Member..
824 views

Reporter GatherCoda Problem

Hi,

 

I have a problem with GatherCoda, it is failed and found below error on the gather trace log :

 

 

2014/07/03 10:06:08 (E):(5164) lba-paa.customer.co.id, GatherCODA No data
2014/07/03 10:06:28 (8):(20788) lba-paa.customer.co.id, CODA:DISK: empty instance list for time range from 08/15/11 00:00:00 to 08/29/11 00:00:00
2014/07/03 10:06:36 (9):(5164) lba-paa.customer.co.id, Prepare to read 4 instances from APPLICATION (08/01/11 00:00:00 to 08/15/11 00:00:00)
2014/07/03 10:06:56 (8):(20788) lba-paa.customer.co.id, CODA:DISK: empty instance list for time range from 08/29/11 00:00:00 to 09/12/11 00:00:00
2014/07/03 10:07:04 (9):(5164) lba-paa.customer.co.id, Failed to read from APPLICATION; No data
2014/07/03 10:07:04 (E):(5164) lba-paa.customer.co.id, GatherCODA No data

 

 

if  i check directly into the servers all the operation/performance agent services are running, but i found on Systems,txt that the Request from Reporter has been ignored :

 

 

0: INF: Thu Jul  3 06:49:49 2014: coda (64539/139837520279296): Partial Request from client '10.2.116.XXX ignored
0: INF: Thu Jul  3 07:05:49 2014: coda (64539/139837520279296): Partial Request from client '10.2.116.XXX' ignored
0: INF: Thu Jul  3 07:21:50 2014: coda (64539/139837520279296): Partial Request from client '10.2.116.XXX' ignored
0: INF: Thu Jul  3 07:37:50 2014: coda (64539/139837517121280): Partial Request from client '10.2.116.XXX' ignored
0: INF: Thu Jul  3 07:53:50 2014: coda (64539/139837517121280): Partial Request from client '10.2.116.XXX' ignored
0: INF: Thu Jul  3 08:09:50 2014: coda (64539/139837516068608): Partial Request from client '10.2.116.XXX' ignored

 

Anyone has same experiences with this ?

 

 

 

Tags (1)
0 Likes
1 Reply
Absent Member.
Absent Member.

Hi,

Check whether there data exists on node or not.
Use the datafile update timestamp for same, it must be recent only. Also enough disk space must be there on installation and datafile location to store the data.

If it is fine then check the log file if there is any other report is reported or not.

Try to restart t the agent and check.

Hth,
____________________________________
Assign Kudo, if found post useful and mark it accepted if solves the issue.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.