Discussion:
[Check_mk (english)] sporadic check failures of check_mk-oracle_rman
Björn Kaltofen
2018-10-17 13:47:33 UTC
Permalink
Hello,

I'm using the mk_oracle plugin to monitor several databases on a two node RAC cluster.
The mk_oracle script comes from Check_MK version 1.4.0p34.

On one database the check for RMAN INC0 Backup fails sporadically:


Host: orarac01-scan

Alias: orarac01-scan

Address: 0.0.0.0

Service: ORA FNDBP8.DB_INCR_0 RMAN Backup

State: UNKNOWN -> UNKNOWN (PROBLEM)

Command: check_mk-oracle_rman

Output: UNKNOWN - check failed - please submit a crash report!

Perfdata:
Crash dump: <I'll send the string, if it's needed for analysis>

There are several other databases with the same RMAN backup type, that never fail with a crash dump.
The recovery always comes with the following agent check.


Host: orarac01-scan

Alias: orarac01-scan

Address: 0.0.0.0

Service: ORA FNDBP8.DB_INCR_0 RMAN Backup

State: UNKNOWN -> OK (RECOVERY)

Command: check_mk-oracle_rman

Output: OK - Last backup 16 hours ago

Perfdata: age=58800;;;;

I executed the SQL from the mk_oracle script against the affected database. It takes 1 second to execute, but it's the same on the other databases. So performance does not seem to be the issue.

Do you have any idea, why the check crashes sometimes?

Best regards,
Björn

--
Björn Kaltofen
Senior Database Consultant

[cid:MCS_Logo_2_aa2c829e-ae6b-4f81-9be7-eef858b01aff.png]
MCS GmbH

Essener Bogen 17 | 22419 Hamburg
T +49 40 53773-0 | F +49 40 53773-200
***@mcs.de | www.mcs.de<http://www.mcs.de/>

Eingetragen im Handelsregister B des Amtsgerichts Hamburg HRB 144607
Geschäftsführer: Eckard Kabel, Thomas Noglik
Thorsten Bruhns via checkmk-en
2018-10-17 18:47:44 UTC
Permalink
Hello,

I need the agent output from the report for doing some analysis. The
last couple of lines from the callstack with lines from oracle_rman are
welcome as well.


Kind Regards

Thorsten Bruhns
Post by Björn Kaltofen
Hello,
I’m using the mk_oracle plugin to monitor several databases on a two
node RAC cluster.
The mk_oracle script comes from Check_MK version 1.4.0p34.
Host:     orarac01-scan
Alias:    orarac01-scan
Address:  0.0.0.0
Service:  ORA FNDBP8.DB_INCR_0 RMAN Backup
State:    UNKNOWN -> UNKNOWN (PROBLEM)
Command:  check_mk-oracle_rman
Output:   UNKNOWN - check failed - please submit a crash report!
Crash dump: <I’ll send the string, if it’s needed for analysis>
There are several other databases with the same RMAN backup type, that
never fail with a crash dump.
The recovery always comes with the following agent check.
Host:     orarac01-scan
Alias:    orarac01-scan
Address:  0.0.0.0
Service:  ORA FNDBP8.DB_INCR_0 RMAN Backup
State:    UNKNOWN -> OK (RECOVERY)
Command:  check_mk-oracle_rman
Output:   OK - Last backup 16 hours ago
Perfdata: age=58800;;;;
I executed the SQL from the mk_oracle script against the affected
database. It takes 1 second to execute, but it’s the same on the other
databases. So performance does not seem to be the issue.
Do you have any idea, why the check crashes sometimes?
Best regards,
Björn
--
*Björn Kaltofen*
Senior Database Consultant
*MCS GmbH*
**Essener Bogen 17 | 22419 Hamburg
T +49 40 53773-0 | F +49 40 53773-200
Eingetragen im Handelsregister B des Amtsgerichts Hamburg HRB 144607
Geschäftsführer: Eckard Kabel, Thomas Noglik
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
Virenfrei. www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
_______________________________________________
checkmk-en mailing list
Manage your subscription or unsubscribe
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
Björn Kaltofen
2018-10-18 15:15:06 UTC
Permalink
Hello Thorsten,

thanks for your reply.

This is the agent output for RMAN Backups of the corresponding database:

<<<oracle_rman:sep(124)>>>
FNDBP8|COMPLETED|2018-10-18_04:00:40|2018-10-18_04:00:40|DB_INCR|0|788|0
FNDBP8|COMPLETED||2018-10-18_16:45:16|CONTROLFILE||24|0
FNDBP8|COMPLETED|2018-10-18_17:09:11|2018-10-18_16:45:08|ARCHIVELOG||24|

What do you mean with callstack? Where do I get that from?

Best regards,
Björn


--
Björn Kaltofen
Senior Database Consultant

[cid:MCS_Logo_2_aa2c829e-ae6b-4f81-9be7-eef858b01aff.png]
MCS GmbH

Essener Bogen 17 | 22419 Hamburg
T +49 40 53773-0 | F +49 40 53773-200
***@mcs.de | www.mcs.de<http://www.mcs.de/>

Eingetragen im Handelsregister B des Amtsgerichts Hamburg HRB 144607
Geschäftsführer: Eckard Kabel, Thomas Noglik




Von: Thorsten Bruhns [mailto:***@googlemail.com]
Gesendet: Mittwoch, 17. Oktober 2018 20:48
An: Björn Kaltofen <***@mcs.de>; checkmk-***@lists.mathias-kettner.de
Betreff: Re: [Check_mk (english)] sporadic check failures of check_mk-oracle_rman


Hello,

I need the agent output from the report for doing some analysis. The last couple of lines from the callstack with lines from oracle_rman are welcome as well.



Kind Regards

Thorsten Bruhns

Am 17.10.2018 um 15:47 schrieb Björn Kaltofen:
Hello,

I'm using the mk_oracle plugin to monitor several databases on a two node RAC cluster.
The mk_oracle script comes from Check_MK version 1.4.0p34.

On one database the check for RMAN INC0 Backup fails sporadically:


Host: orarac01-scan

Alias: orarac01-scan

Address: 0.0.0.0

Service: ORA FNDBP8.DB_INCR_0 RMAN Backup

State: UNKNOWN -> UNKNOWN (PROBLEM)

Command: check_mk-oracle_rman

Output: UNKNOWN - check failed - please submit a crash report!

Perfdata:
Crash dump: <I'll send the string, if it's needed for analysis>

There are several other databases with the same RMAN backup type, that never fail with a crash dump.
The recovery always comes with the following agent check.


Host: orarac01-scan

Alias: orarac01-scan

Address: 0.0.0.0

Service: ORA FNDBP8.DB_INCR_0 RMAN Backup

State: UNKNOWN -> OK (RECOVERY)

Command: check_mk-oracle_rman

Output: OK - Last backup 16 hours ago

Perfdata: age=58800;;;;

I executed the SQL from the mk_oracle script against the affected database. It takes 1 second to execute, but it's the same on the other databases. So performance does not seem to be the issue.

Do you have any idea, why the check crashes sometimes?

Best regards,
Björn




_______________________________________________

checkmk-en mailing list

checkmk-***@lists.mathias-kettner.de<mailto:checkmk-***@lists.mathias-kettner.de>

Manage your subscription or unsubscribe

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

Loading...