Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Backend Log Error

Hi

in Backend Log of my MARS I find literally hundreds of messages as follows:

7/24/08 4:50:26 PM CEST Error ./device_monitor Thread 41372592:Device monitor trying to add entry with interfaceId = 0 to pn_report_result table. Skipping.

Any suggestions how I can identify the device which causes this error?

Thanks

1 ACCEPTED SOLUTION

Accepted Solutions

Re: Backend Log Error

Actually it seems you are hitting another bug :)

CSCsr13959 Bug Details

MARS- Log entry filling up backend logs

Symptom:

If cu has hit bug CSCsm98109 and has upgraded to x.3.4 or above then the log that was created in the resolution of this original bug will fill up the backend logs with thousands of the following log:

Device monitor trying to add entry with interfaceId = 0 to pn_report_result table. Skipping

Conditions:

Must be hitting original bug CSCsm98109 and have upgraded to x.3.4 or higher.

Workaround:

None

Regards

Farrukh

14 REPLIES
Silver

Re: Backend Log Error

This error looks like a high CPU usage , it might be impact on the performances of the system.

http://www.cisco.com/en/US/docs/security/security_management/cs-mars/4.3/compatibility/local_controller/dtlc43x.html

Community Member

Re: Backend Log Error

No, CPU usage is in the range from 5% to 15% which I find quite moderate. Our system seems to run fine.

My initial question was, how I can find out the source of this error message. I have about 300 devices in our system - and one of them seems to cause this error. And I haven't the time to check every single one

Re: Backend Log Error

Please check the logging messages below/above the message you posted. If this is the only one, try re-adjusting the logging levels in MARS. (Admin >> System Maint >> Logging Levels). Do it for "device_monitor".

Regards

Farrukh

Community Member

Re: Backend Log Error

Please note, that it is an error message. I don't find it useful to suppress error messages in logfiles.

Gold

Re: Backend Log Error

I think Farrukh is suggesting that you try increasing the verbosity of the logs for the device_monitor process. By default, it will be at INFO level. You can increase to DEBUG or TRACE.

Community Member

Re: Backend Log Error

Oh, right, sorry, that was a misunderstanding on my part. Will have a go at this!

Re: Backend Log Error

Thanks for the clarification Mathew, I was really perplexed by the response (and rating) I got. Was wondering if it was a communication issue :)

Regards

Farrukh

Community Member

Re: Backend Log Error

Unfortunately I'm getting nowhere. I've increased the level of the device_monitor process to 'trace' (which is said to be more verbose than 'debug'). Now I'm getting this output:

8/8/08 12:58:30 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:58:40 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:58:50 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:59:00 PM CEST Info ./superV Thread 88800176:Earliest event time in filled DB partitions: 1212561551

8/8/08 12:59:00 PM CEST Info ./superV Thread 88800176:Available space in /pnarchive partition: 70297 M

8/8/08 12:59:00 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:59:00 PM CEST Info ./superV Thread 88800176:/pnarchive/tmp used 97 M disk space

8/8/08 12:59:10 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:59:10 PM CEST Info ./pnparser Thread 2845285296:

8/8/08 12:59:11 PM CEST Info ./pnparser 2016:message rate: 821.789978 msgs/sec, total: 900000 msgs, total avg rate: 772.230698 msgs/sec

8/8/08 12:59:20 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:59:30 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:59:40 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:59:48 PM CEST Info ./pnparser Thread 2866265008:Netflow Shared Buffer Store EventRate: 818.804198 Running Avg EventRate: 791.871948

8/8/08 12:59:50 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 12:59:51 PM CEST Info ./pnparser Thread 2876754864:Thread 1: netflow messageRate: 1323, CacheQueueSize: 0:18, eventQueueSize:2982, fireQueueSize: 0, sessionQueueSize: 12945:12993:24593, netflowQueueSize: 0

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:----------Start Detection.

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:Finish polling.

8/8/08 12:59:56 PM CEST Error ./device_monitor Thread 106175408:Device monitor trying to add entry with interfaceId = 0 to pn_report_result table. Skipping.

... and the previous line being repeated about 6400 times (!), and finally the following lines...

8/8/08 12:59:56 PM CEST Error ./device_monitor Thread 106175408:Device monitor trying to add entry with interfaceId = 0 to pn_report_result table. Skipping.

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:Skipped writing report-result logs! Run mode is 0.

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:Skipped writing report-result logs! Run mode is 0.

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:Skipped writing report-result logs! Run mode is 0.

8/8/08 12:59:56 PM CEST Trace ./device_monitor Thread 106175408:Inserted 74 rows (array capacity 50000)

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:Finish generating the report.

8/8/08 12:59:56 PM CEST Debug ./device_monitor 2017:Error waiting for the DB change semaphore, returned 4

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:Finish storing the file.

8/8/08 12:59:56 PM CEST Debug ./device_monitor Thread 106175408:Finish Detection.

8/8/08 1:00:00 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 1:00:10 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 1:00:20 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 1:00:30 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 1:00:40 PM CEST Trace ./device_monitor 0045:Received message of type 100

8/8/08 1:00:50 PM CEST Trace ./device_monitor 0045:Received message of type 100

Previously I had the 'Monitor Resource Usage' on for the core devices, but now I switched them to 'NO'. This does not help with the amount of lines in the log. Even worse: I get the impression they're getting more and more.

Re: Backend Log Error

Please can you let me know the MARS model and version you are running right now?

Regards

Farrukh

Community Member

Re: Backend Log Error

We use a MARS Model 110

Product Version is 5.3.5 ( 2934 )

Regards, Beat

Re: Backend Log Error

As per the release notes, a bug similar to this syslog was fixed in 5.3.4

CSCsm98109

Resource Utilization Report shows multiple bad entries (device_monitor)

MARS Oracle database reporting 0 values on index tables.

Another one which is still an 'open caveat' is the following:

CSCsi65713

Index needs to be removed for the pn_report_result table

But this one seems to be open to Cisco employees only.

I would suggest that you proceed and open a case with TAC.

Regards

Farrukh

Re: Backend Log Error

Actually it seems you are hitting another bug :)

CSCsr13959 Bug Details

MARS- Log entry filling up backend logs

Symptom:

If cu has hit bug CSCsm98109 and has upgraded to x.3.4 or above then the log that was created in the resolution of this original bug will fill up the backend logs with thousands of the following log:

Device monitor trying to add entry with interfaceId = 0 to pn_report_result table. Skipping

Conditions:

Must be hitting original bug CSCsm98109 and have upgraded to x.3.4 or higher.

Workaround:

None

Regards

Farrukh

Community Member

Re: Backend Log Error

Thanks Farrukh

That's it. Exactly my case. Amazing though, that it's now in the 'fixed' status.

I'll try and open a case via our supplier.

Regards, Beat

Community Member

Re: Backend Log Error

Beat, if you thing your problem is resolved, it is always motivating to rate the post accordingly and mark the post as "Resolved". Those guys really go off the track to help us and it is our responsibility to encourage and highlight them.

Please rate this conversation as "resolved my issue" based on Farrukh's recomendations that solved your problem.

thanks.

Mohsin

325
Views
35
Helpful
14
Replies
CreatePlease to create content