The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 7:30am (PST)
Client Automation Standard Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

Patch Reporting Problem

Highlighted
kaps_1
Regular Collector

Patch Reporting Problem

Hi

I am facing some probs with reporting of patch.

Cleint discovery of patch seems to be Ok and also client installs the patches.

I am not able to know whether it transfers the data to radia patch server or not.

As In configuration server/data/default folder files are processed by messaging server.

There is no data in radia reporting and also no error in reporting. It's just show zero managed devices

Please advise

regards
Kaps
22 REPLIES
James Longo
Member

Re: Patch Reporting Problem

What version of Patch are you running? 2.01, or pre 2.01? Do you have the nvd_de2pa table structure? If yes you are using 2.01. Have you tried to run a DB sync? Have you looked in the RMS logs for PATCH processing?
kaps_1
Regular Collector

Re: Patch Reporting Problem

Hi Yes,

I am using the Radia Patch Manger 2.1 and Messaging Srever version is 2.o.

I am not able to know up to which stage data is coming, Is it Patch or Messaging or Reporting is having problem.

As I am using oracle.

Can anyone tell me where devices which are managed by patch are stored. So that I can be clear on one thing that data is not there in database.

Secondly, there is a proxy in between my server and Knowledge Manage is installed there But I am not using it for patch collection, i am using for usage manager only.

Thirdly, In default folder in configuration server some data comes and processed by messaging server and automatically data is removed from there.

Where lies the probs..

regards
Kaps
Nigel Hewett
Super Collector

Re: Patch Reporting Problem

Are there any errors in the messaging server logs?
kaps_1
Regular Collector

Re: Patch Reporting Problem

Hi

Now I upgraded the Messaging server 3.0
The data now comes into patch folder instead of default one in configuration server.

The data comes and I can see the files and it's processed also.

In the managed services of Inventory reports I can see the data also that so many boxes have been patched and discover services are also delivered to it.

There are no errors in messaging.

I am attaching one screen shot with this messaage showing the same.

regards
Kaps
Nigel Hewett
Super Collector

Re: Patch Reporting Problem

In reporting server home page under patch information, does it display something like:

Managed Devices: 16
Managed Bulletins: 445
Last Aquisition: 2005-11-04 10:58:39

or are they all zero?

Are you running reporting server 4.1?

Have you run the Database Sync Command to sync the RCS with your database?
James Longo
Member

Re: Patch Reporting Problem

Find a device_id that you know exists in the patch database, and replace the $DEVICE_ID string with the actual device_id of a machine, and run the following SQL statements. The first statement will return the date, and should reflect te date you ran the discover patch. If it does not reflect the date of discover patch the problem is in the processing of patch data. If the date reflects the discover patch date run the second statement.

SELECT nvd_de2pa.nvd_zobjdev, nvd_de2pa.nvd_zobjdate, nvd_de2pa.nvd_zobjmsg FROM nvd_de2pa where nvd_de2pa.nvd_zobjmsg LIKE '%' AND nvd_de2pa.nvd_zobjmsg <> 'installed' AND nvd_de2pa.nvd_zobjdev LIKE '$DEVICE_ID'

Now run this one if the date is what it should be. If 0 records return run a DB sync. make sure to replace the $DEVICE_ID with an actual machine.

SELECT nvd_de2pa.nvd_zobjdev, nvd_patch.nvd_bulletin, nvd_de2pa.nvd_zobjmsg FROM nvd_de2pa, nvd_patch where nvd_de2pa.nvd_zobjmsg LIKE '%' AND nvd_patch.nvd_bulletin LIKE '%' AND nvd_de2pa.nvd_zobjname = nvd_patch.nvd_zobjname AND nvd_de2pa.nvd_zobjmsg <> 'installed' AND nvd_patch.nvd_bulletin <> ' ' AND nvd_de2pa.nvd_zobjdev LIKE '$DEVICE_ID' order by nvd_patch.nvd_bulletin
kaps_1
Regular Collector

Re: Patch Reporting Problem

Hi,

The above two queries return zero rows, i have performed database syn also from GUI of Patch Manager.

But still it's not showing any rows selected, is there any other way to see if any device is inside my database or not

As it's shows zero managed devices.

rds,
kaps
kaps_1
Regular Collector

Re: Patch Reporting Problem

What is the command for database Synch

rds
Kaps
James Longo
Member

Re: Patch Reporting Problem

If both queries return 0 rows there mmust be a problem with processing data. Can you check the RMS logs for patch processing, and check the DSN defined for patch to make sure you are looking at the same database.

Can you post the rms.cfg, or patch.dda.cfg if RMS 3.x.
James Longo
Member

Re: Patch Reporting Problem

Also run the select statements I sent you, but this time replace $DEVICE_ID with a % sign.

If you are running oracle it is case sensitive, and would return 0 rows if the case was incorrect.
kaps_1
Regular Collector

Re: Patch Reporting Problem

Hi James,

Thanks for helping me out.

I run the first query with % and it returns 8433 rows then I run for one device, It returns 30 rows.

The second query is not returninng anything despite changing device id with % as well as with some device.

Now I think data is there inside the database. But Reporting is still showing zero managed devices.

Also, Second query is not returning anything. Please let me know if any logs are required.


Regards
Kaps
James Longo
Member

Re: Patch Reporting Problem

It sounds like the nvd_zobjname values still do not match. Run the following 2 queries, and save the results of each query, and post them.

You can change the %MS05-050% to any bulletin, but make sure they are the same for both queries.

SELECT distinct nvd_bulletin, nvd_zobjname, nvd_zobjdate FROM nvd_patch WHERE nvd_bulletin LIKE '%MS05-050%'


SELECT nvd_de2pa.nvd_zobjdev, nvd_de2pa.nvd_zobjname, nvd_de2pa.nvd_zobjmsg FROM nvd_de2pa where nvd_de2pa.nvd_zobjmsg LIKE '%' AND nvd_de2pa.nvd_zobjdev LIKE '%' AND nvd_de2pa.nvd_zobjmsg LIKE '%MS05-050%' order by nvd_de2pa.nvd_zobjmsg
James Longo
Member

Re: Patch Reporting Problem

Run this test also. Each select statement is followed by my results. You can see that the results from the first query have a match in the second query. If you can not find a match for your queries you are not in sync. A DB sync shold have corrected this issue. Can you make sure the results do not match, and run a DB sync again? Make sure you are running a sync on the correct RIS/PATCH server.


This entry is in both results meaning there is a match.

B0019F00E680_AA13B89DED01_26
_______________________________________


SELECT distinct nvd_de2pa.nvd_zobjname FROM nvd_de2pa where nvd_de2pa.nvd_zobjmsg LIKE '%MS05-050%' order by nvd_zobjname

__________________________________________

B0019F00E680_AA13B89DED01_26
B0019F00E680_AA13B89DF0C0_10
B0019F00E680_AA13B89DF0C0_3
B0019F00E680_BA1314970D80_1


________________________________________

SELECT distinct nvd_zobjname FROM nvd_patch WHERE nvd_bulletin LIKE '%MS05-050%' order by nvd_zobjname

________________________________________

B0019F00E680_AA13B89DDFC3_13
B0019F00E680_AA13B89DDFC3_17
B0019F00E680_AA13B89DDFC3_25
B0019F00E680_AA13B89DE040_15
B0019F00E680_AA13B89DE040_2
B0019F00E680_AA13B89DE040_23
B0019F00E680_AA13B89DE081_18
B0019F00E680_AA13B89DE081_29
B0019F00E680_AA13B89DE081_7
B0019F00E680_AA13B89DE0C2_12
B0019F00E680_AA13B89DE0C2_19
B0019F00E680_AA13B89DE0C2_33
B0019F00E680_AA13B89DECC2_20
B0019F00E680_AA13B89DECC2_4
B0019F00E680_AA13B89DED01_26
B0019F00E680_AA13B89DED01_9
B0019F00E680_AA13B89DF0C0_10
B0019F00E680_AA13B89DF0C0_3
B0019F00E680_AA13B89DF0C1_14
B0019F00E680_AA13B89DF0C1_22
B0019F00E680_AA13B89DF0C2_32
B0019F00E680_AA13B89DF0C2_5
B0019F00E680_AA13B89DF0C3_21
B0019F00E680_AA13B89DF0C3_34
B0019F00E680_BA1314970D01_31
B0019F00E680_BA1314970D80_1
B0019F00E680_DD010E213553_16
B0019F00E680_DD010E213553_30
B0019F00E680_DD014C32AC78_11
B0019F00E680_DD014C32AC78_28
B0019F00E680_DD016C8A81C8_24
B0019F00E680_DD016C8A81C8_6
B0019F00E680_DD01FA1C5925_27
B0019F00E680_DD01FA1C5925_8

kaps_1
Regular Collector

Re: Patch Reporting Problem

Hi James,

As advised I run the Queries, Only 2 queries result data one from each of your reply.

I am attaching the same,I have written in the file query as well as result.

Rest the other two queries no data.

Also, I am having presently 3 patchmgmt servers having the same database. Also, there are two more servers needs to join the same database.

Regards,
Kaps
kaps_1
Regular Collector

Re: Patch Reporting Problem

Sorry forgot to attach the files.

rds,
Kaps
Biju V George!
Honored Contributor

Re: Patch Reporting Problem

Hi Kaps,

I think design itself is the problem. I did not understand, you have in total five patch Manager servers doing patch management??
James Longo
Member

Re: Patch Reporting Problem

Your results show a match. This query should return results. Check the cache value in the RRS/config.tcl and turn all cacheenable to 0.


SELECT nvd_de2pa.nvd_zobjdev, nvd_patch.nvd_bulletin, nvd_de2pa.nvd_zobjmsg FROM nvd_de2pa, nvd_patch where nvd_de2pa.nvd_zobjmsg LIKE '%' AND nvd_patch.nvd_bulletin LIKE '%MS05-050%' AND nvd_de2pa.nvd_zobjname = nvd_patch.nvd_zobjname AND nvd_de2pa.nvd_zobjmsg <> 'installed' AND nvd_patch.nvd_bulletin <> ' ' AND nvd_de2pa.nvd_zobjdev LIKE '%' order by nvd_patch.nvd_bulletin
James Longo
Member

Re: Patch Reporting Problem

My mistake. Disregard previous entry.
James Longo
Member

Re: Patch Reporting Problem

This statement returns 0 rows?

SELECT distinct nvd_zobjname FROM nvd_patch WHERE nvd_bulletin LIKE '%MS05-050%' order by nvd_zobjname

try this one instead.


SELECT distinct nvd_bulletin, nvd_zobjname FROM nvd_patch WHERE nvd_bulletin LIKE 'MS05%' order by nvd_zobjname
James Longo
Member

Re: Patch Reporting Problem

This is starting to sound like you are running the acquire in QA, and the QA DB is not the production DB, and therefore no data in the nvd_patch table. What DB is the aquire linked to?

Look at the patch.cfg file DSN settings for the IntegrationServer you are running the aquire from. Does the DSN match the same DB we are running the queries from?

Do yo have any data in the nvd_patch table?

kaps_1
Regular Collector

Re: Patch Reporting Problem

Hi James and BIju,

Both the queries are resulting data. I am attaching the results.

However, It still shows zero managed devices.

Biju: What I intend to do is to acquire patches from one place and distribute to my slave servers and from there it will be distributed to respective clients and database is common to all the servers.

Regards
Kaps
James Longo
Member

Re: Patch Reporting Problem

The results show that nvd_patch table nvd_zobjname has an entry for MS05-050. The following query will show if there is a matching entry in the nvd_de2pa table.

SELECT nvd_de2pa.nvd_zobjdev, nvd_patch.nvd_bulletin, nvd_de2pa.nvd_zobjmsg FROM nvd_de2pa, nvd_patch where nvd_de2pa.nvd_zobjmsg LIKE '%' AND nvd_patch.nvd_bulletin LIKE '%MS05-050%' AND nvd_de2pa.nvd_zobjname = nvd_patch.nvd_zobjname AND nvd_de2pa.nvd_zobjmsg <> 'installed' AND nvd_patch.nvd_bulletin <> ' ' AND nvd_de2pa.nvd_zobjdev LIKE '%' order by nvd_patch.nvd_bulletin

---------------------------------------------
What does the following produce? Run each select statement seperately. I found matches for each nvd_zobjname.

SELECT * from nvd_de2pa WHERE nvd_zobjname = 'B002A9B7AB00_BA1314970D80_12'

SELECT * from nvd_de2pa WHERE nvd_zobjname = 'B002A9B7AB00_AA13B89DF0C1_15'

SELECT * from nvd_de2pa WHERE nvd_zobjname = 'B002A9B7AB00_AA13B89DED01_5'

SELECT * from nvd_de2pa WHERE nvd_zobjname = 'B002A9B7AB00_AA13B89DE081_11'

SELECT * from nvd_de2pa WHERE nvd_zobjname = 'B002A9B7AB00_AA13B89DE040_8'

SELECT * from nvd_de2pa WHERE nvd_zobjname = 'B002A9B7AB00_AA13B89DDFC3_18'


---------------------------------------------

I compared the results from an earlier entry from the results of the latest entry, and posted them below. I do see a match each select statment above.

SELECT distinct nvd_de2pa.nvd_zobjname FROM nvd_de2pa where nvd_de2pa.nvd_zobjmsg LIKE '%MS05-050%' order by nvd_zobjname


NVD_ZOBJNAME
--------------------------------
B002A8655041_AA13B89DDFC3_18
B002A8655041_AA13B89DE040_8
B002A8655041_AA13B89DED01_5
B002A8655041_BA1314970D80_12
B002A9B7AB00_AA13B89DDFC3_18
B002A9B7AB00_AA13B89DE040_8
B002A9B7AB00_AA13B89DE081_11
B002A9B7AB00_AA13B89DED01_5
B002A9B7AB00_AA13B89DF0C1_15
B002A9B7AB00_BA1314970D80_12

10 rows selected.

--------------------------------------------


SELECT distinct nvd_zobjname FROM nvd_patch WHERE nvd_bulletin LIKE '%MS05-050%' order by nvd_zobjname ;


NVD_ZOBJNAME
--------------------------------
B002A9B7AB00_AA13B89DDFC3_18
B002A9B7AB00_AA13B89DE040_8
B002A9B7AB00_AA13B89DE081_11
B002A9B7AB00_AA13B89DE0C2_4
B002A9B7AB00_AA13B89DECC2_3
B002A9B7AB00_AA13B89DED01_5
B002A9B7AB00_AA13B89DF0C0_10
B002A9B7AB00_AA13B89DF0C1_15
B002A9B7AB00_AA13B89DF0C2_6
B002A9B7AB00_AA13B89DF0C3_2
B002A9B7AB00_BA1314970D01_9
B002A9B7AB00_BA1314970D80_12
B002A9B7AB00_BA135E687601_14
B002A9B7AB00_BA135E687640_16
B002A9B7AB00_BA135E687680_7
B002A9B7AB00_BA135E6876C0_17
B002A9B7AB00_BA135E6876C1_13
B002A9B7AB00_BA1372A29880_1

18 rows selected.
//Add this to "OnDomLoad" event