S98gcstartup is Holding the OS From Coming up Completely

最新推荐文章于 2022-05-07 10:49:00 发布

原创最新推荐文章于 2022-05-07 10:49:00 发布 · 933 阅读

0 ·

CC 4.0 BY-SA版权

Exadata 专栏收录该内容

13 篇文章

订阅专栏

本文探讨了 Oracle Grid Infrastructure 在节点重启后自动启动失败的问题，具体表现为 GI 相关进程如 ohasd.bin 和 S98gcstartup 等在系统中运行异常。分析指出，这是由于为 Grid Control Agent 用户自定义的 OS 登录配置导致 rc 脚本 ‘S98gcstartup’ 在执行特定命令时陷入僵局。通过测试，发现该问题源于在非交互模式下执行命令时等待用户输入完成执行，这归因于自定义的配置文件。解决方案包括修改配置文件以允许非交互执行或调整启动脚本以适应自定义配置。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

[root@erpdb01 ~]#ps -ef|grep d.bin
root 9541 1 0 17:16 ? 00:00:00 /u01/PSPROD/11.2.0.4/grid/bin/ohasd.bin reboot
root 26554 25254 0 20:14 pts/0 00:00:00 grep d.bin
[root@erpdb01 ~]#ps -ef|grep rc
root 5461 1 0 17:15 ? 00:00:00 /bin/bash /etc/rc.d/rc 3
root 9325 1 0 17:16 ? 00:00:00 /bin/bash /etc/rc3.d/S75compmon watch
root 11123 5461 0 17:16 ? 00:00:00 /bin/sh /etc/rc3.d/S98gcstartup start
root 26556 25254 0 20:14 pts/0 00:00:00 grep rc

comment:
----------------

the normal status should be:

oracle 8902 1 0 Dec01 ? 00:00:27 /u01/app/11.2.0/grid/bin/tnslsnr LISTENER -inherit
root 26733 1 0 Nov19 ? 01:22:37 /u01/app/11.2.0/grid/bin/ohasd.bin reboot
root 26881 26853 0 23:16 pts/0 00:00:00 grep d.bin
oracle 26924 1 0 Nov19 ? 00:34:29 /u01/app/11.2.0/grid/bin/oraagent.bin
oracle 26935 1 0 Nov19 ? 00:00:37 /u01/app/11.2.0/grid/bin/mdnsd.bin
oracle 26946 1 0 Nov19 ? 00:08:34 /u01/app/11.2.0/grid/bin/gpnpd.bin
oracle 26956 1 0 Nov19 ? 01:17:48 /u01/app/11.2.0/grid/bin/gipcd.bin
root 26959 1 0 Nov19 ? 01:23:25 /u01/app/11.2.0/grid/bin/orarootagent.bin
root 26973 1 1 Nov19 ? 04:25:03 /u01/app/11.2.0/grid/bin/osysmond.bin
root 26984 1 0 Nov19 ? 00:14:46 /u01/app/11.2.0/grid/bin/cssdmonitor
root 27002 1 0 Nov19 ? 00:14:11 /u01/app/11.2.0/grid/bin/cssdagent
.....

root 3613 1 0 Oct27 ? 00:00:00 /bin/sh /etc/init.d/init.ohasd run <<<<<<<<<<<

看看官方说法：

Grid Infrastructure Fails To Start After Node Reboot as S98gcstartup is Holding the OS From Coming up Completely (文档 ID 1389156.1)

转到底部

In this Document
  Symptoms
  Changes
  Cause
  Solution

APPLIES TO:

Oracle Exadata Storage Server Software - Version: 11.2.1.2.0 and later [Release: 11.2 and later ]
Oracle Server - Enterprise Edition - Version: 11.2.0.1 and later [Release: 11.2 and later]
Information in this document applies to any platform.

SYMPTOMS

11gR2 GI fails to start automatically after node reboot:

- Following are the GI startup related processes running in the system

 
          # ps -eaf | grep rc | grep -v grep 
 root 3551 1 0 Jun07 ? 00:00:00 /bin/bash /etc/rc.d/rc 3 
 root 5672 3551 0 Jun07 ? 00:00:00 /bin/sh /etc/rc3.d/S98gcstartup start 
 
 >> Note: S98gcstartup stuck
 
          # ps -eaf | grep ohasd | grep -v grep 
 root 5667 1 0 Jun07 ? 00:00:00 /opt/app/11.2.0.2/grid/bin/ohasd.bin reboot
 
 >> Note: output missing the following:
 
 root      2461     1  0  2011 ?        00:00:00 /bin/sh /etc/init.d/init.ohasd run

CHANGES

Customized OS login profile for the Grid Control Agent user.

CAUSE

Due to the customized OS login profile for Grid Control Agent user(oracle in this case), rc script " S98gcstartup" is stuck while executing the following command:

/bin/su - oracle -c /opt/app/oracle/product/11.2.0/agent11g/install/unix/scripts/agentstup start

As rc script invoked in non-interactive mode during node reboot, "su - oracle -c <command>" is waiting for user input to complete the execution (due to customized .profile). To test: