暂无图片
暂无图片
1
暂无图片
暂无图片
暂无图片

系统message: Starting execution of Oracle Clusterware init.ohasd

原创 问题归档 2019-04-14
2247

问题描述

集群:12.1.0.2

在系统message日志中时常出现logger: Starting execution of Oracle Clusterware init.ohasd,是什么原因导致的。

专家解答

Starting of Grid Infrastructure (GI) 12c with the text "Starting execution of Oracle Clusterware init.ohasd" logs to syslog as an error and not as an information

Following logs should be lowered to info instead of err priority:

[Thu Aug 31 18:12:16][13844][root@<nodename1>:~][0]# grep init.ohasd /var/log/messages
May 20 14:15:18 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd
May 21 02:03:28 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd
May 21 05:38:44 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd
May 21 06:22:17 rachost1 logger: Starting execution of Oracle Clusterware init.ohasd


The impact is, monitoring tools scanning for errors in syslog, give false alerts and tickets when a normal GI startup happens.

The monitoring tool checks the content of /var/log/messages_err. This file results of this line in the rsyslogd configuration:


*.error /var/log/messages_err

ohasd and init.crs utilizes p.err for informational messages. This is reported through bug 26738408, which is closed as duplicate of 26733329

 

Bug 26733329 fixed in future release. Request/download and apply one-off patch if the system is impacted

最后修改时间:2019-04-14 14:34:28
「喜欢这篇文章,您的关注和赞赏是给作者最好的鼓励」
关注作者
【版权声明】本文为墨天轮用户原创内容,转载时必须标注文章的来源(墨天轮),文章链接,文章作者等基本信息,否则作者和墨天轮有权追究责任。如果您发现墨天轮中有涉嫌抄袭或者侵权的内容,欢迎发送邮件至:contact@modb.pro进行举报,并提供相关证据,一经查实,墨天轮将立刻删除相关内容。

评论