topic Re: Hum Job report errors in Network Security

Hum Job report errors

mkareemashraf — Fri, 21 Feb 2020 10:57:37 GMT

Hello sir,

We are using cisco works LMS 3.1 and Hum version 1 in our network.

In common service Job information status, we getting error

1019.2306 QUICK_INTERFACE_UTILIZATION_REPORT_JOB Failed

1189.265 QUICK_INTERFACE_AVAILABILITY_REPORT_JOB Failed

These errors are generated in Common Services form Hum and After clicking the Job ID ,no information is displayed .

Please help to solve this Error.

Thanks,

kareem

Re: Hum Job report errors

Joe Clarke — Sat, 09 Aug 2008 15:27:26 GMT

There will be log files in the HUMReports directory in the standard log file location. They should correspond to your job ID. Please post them.

Re: Hum Job report errors

mkareemashraf — Sun, 10 Aug 2008 05:37:11 GMT

I HAVE ATTACHED THE LOG FILES OF HUM .

Jrm.log file is exceeded the limited size ,it is nearly 1.3 mb .

It is better to clear the log file or delete its contents.

thanks,

Re: Hum Job report errors

Joe Clarke — Sun, 10 Aug 2008 18:28:48 GMT

There are no errors here, but these are not from the jobs for which you earlier reported a problem. you mentioned jobs 1019 and 1189. Is 1188 also showing as failed? If so, enable Report Jobs debugging under HUM > Admin > Log level Settings, and run one of the failing jobs again. The new log file should have more details.

Re: Hum Job report errors

mkareemashraf — Mon, 11 Aug 2008 09:02:36 GMT

In HUM , I have enabled the debug in Report JOb.

I have attached the files and snapshot of the Job interface portlet in common services.

Re: Hum Job report errors

mkareemashraf — Mon, 11 Aug 2008 09:56:37 GMT

Please look at this file also.It has more details.

Re: Hum Job report errors

Joe Clarke — Mon, 11 Aug 2008 16:20:20 GMT

The first log looks like the job data was removed from the HUM database. That is, creating a new job with the same parameters should succeed. Have you ever reinitialized the upm database?

The second log doesn't necessarily indicate a problem. It could be that for this run, there was no threshold violation data available (i.e. between Aug 10 13:03:01 and Aug 11 13:03:01).

Re: Hum Job report errors

netsquant — Mon, 11 Aug 2008 19:22:13 GMT

try this from the servers run command window

net stop crmdmgtd

net start crmdmgtd

Re: Hum Job report errors

mkareemashraf — Tue, 12 Aug 2008 06:53:45 GMT

How can we re-initialize the UPM database (we have never done it)

Their is UPMlog which is nearly 320kb and we are unable to delete it. When we shutdown the crmdmgtd service the log was automatically deleted and when again service started log reappears.

we have not set any thresholds in HUM up till now, but even then should this show as 'Failed' (RED) in the CiscoWorks Page? This seems pretty strange that if there are no thresholds set/violations the report task would show as failed?

Re: Hum Job report errors

Joe Clarke — Tue, 12 Aug 2008 15:23:05 GMT

To reinitialize the upm database, you would have to have run:

NMSROOT/bin/perl NMSROOT/bin/dbRestoreOrig.pl dsn=upm dmprefix=UPM

I can't see another way that the job info would have been removed from the upm database, but not from JRM.

The jobs reporting failed with no data should be fixed in HUM 1.1 (part of LMS 3.1). There was an internally found bug relating to this. There is also an upcoming 1.0.1 release which should also contain the fix.

Re: Hum Job report errors

Farrukh Haroon — Wed, 13 Aug 2008 06:48:47 GMT

Thank you for your response. So should we wait for the 1.0.1 release or re-initialize the UPM database?

Regards

Farrukh

Re: Hum Job report errors

Joe Clarke — Wed, 13 Aug 2008 15:55:47 GMT

I'm not saying you should reinitialize your DB. My thought was that perhaps the database was already initialized which would explain the discrepancy between it and JRM.

If you need these reports to run again, try recreating them as new job instances.