免费注册 查看新帖 |

Chinaunix

  平台 论坛 博客 文库
最近访问板块 发新帖
查看: 1519 | 回复: 0

system/sysevent:default failed fatally: transitioned to maintenance (文档 ID 145 [复制链接]

论坛徽章:
0
发表于 2016-01-28 17:51 |显示全部楼层
system/sysevent:default failed fatally: transitioned to maintenance (文档 ID 1453076.1) 转到底部  


--------------------------------------------------------------------------------

In this Document


Symptoms
Cause
Solution
References

--------------------------------------------------------------------------------



Applies to:
Solaris SPARC Operating System - Version 10 10/08 U6 and later
Information in this document applies to any platform.
***Checked for relevance on 04-Jul-2014***
Symptoms
A system will occasionally fail to boot, and report a problem with the sysevent service:

Apr 16 10:34:24 svc.startd[7]: svc:/system/sysevent:default: Method "/lib/svc/method/svc-syseventd start" failed with exit status 95.
Apr 16 10:34:24 svc.startd[7]: system/sysevent:default failed fatally: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance ModeThe /lib/svc/method/svc-syseventd startup method can be edited to put the sysevent command into debug mode with the following syntax:

/usr/lib/sysevent/syseventd -d 10 >/dev/msglog 2>&1
This command will provide output like the following:

syseventd[144]: Waiting for 5 clients on event id 0Xea
syseventd[144]: Waiting for 4 clients on event id 0Xea
syseventd[144]: Waiting for 3 clients on event id 0Xea
syseventd[144]: Waiting for 2 clients on event id 0Xea
syseventd[144]: Waiting for 1 clients on event id 0Xea
syseventd[144]: Start delivery for client 3 with retry count 0
syseventd[144]: Deliver to module client picl_slm.so
syseventd[144]: eventbuf 33 dispatched
syseventd[144]: dispatch_message: thread started
syseventd[144]: Cleaning up clients for event 0Xea
syseventd[144]: Delivery of 0Xea complete for client 0 retry count 0 status 0
syseventd[144]: Delivery of 0Xea complete for client 1 retry count 0 status 0
syseventd[144]: Delivery of 0Xea complete for client 2 retry count 0 status 0
syseventd[144]: Delivery of 0Xea complete for client 3 retry count 0 status 0
syseventd[144]: Delivery of 0Xea complete for client 4 retry count 0 status 0
syseventd[144]: Event delivery complete for id 0Xea
syseventd[144]: No more events
syseventd[144]: Completed delivery with error 0
syseventd[144]: No more events to process for client 3
Apr 19 15:54:32 svc.startd[7]: svc:/system/sysevent:default: Method or service exit timed out.  Killing contract 20.
Apr 19 15:54:33 svc.startd[7]: system/sysevent:default failed: transitioned to maintenance (see 'svcs -xv' for details)
Requesting System Maintenance ModePlease review the man page on syseventd(1M) if necessary for syntax.

http://docs.oracle.com/cd/E26502 ... d-1m.html#scrolltoc

Cause
There were 2 issues in this situation:

1.  A mismatch between the /etc/system file and the /etc/vfstab file caused the sysevent service to experience an error and go into maintenance mode:

/etc/system

*rootdev:/pseudo/md@0:0,0,blk   <--- note this is commented out, so the system will boot with the ufs driver for root/etc/vfstab

/dev/md/dsk/d0 /dev/md/rdsk/d0   /   ufs   1     no    -   <--- root file system is documented here as being under SVM control, so the kernel is using the wrong driver to access it2.  The syseventd process itself was taking longer than 60 seconds to execute, causing a SMF timeout.  This occurred after the mismatch was resolved.

Solution
1.  To solve the mismatch between /etc/system and the /etc/vfstab files, migrate the /etc/vfstab file to standard ufs slices so it matches the /etc/system file:

/etc/vfstab

/dev/dsk/c1t1d0s0       /dev/rdsk/c1t1d0s0      /       ufs     1       no      -2.  To resolve the sysevent service timeout, edit the properties of the service and then restart it:

# svccfg -s svc:/system/sysevent
svc:/system/sysevent> listprop
.....
start/timeout_seconds             count    60
.....
svc:/system/sysevent> setprop start/timeout_seconds="300"
svc:/system/sysevent> listprop
.....
start/timeout_seconds             count    300
.....
svc:/system/sysevent> exit
# svcadm refresh sysevent
# svcadm restart sysevent
# svcprop sysevent
.....
start/timeout_seconds count 300
.....
您需要登录后才可以回帖 登录 | 注册

本版积分规则 发表回复

DTCC2020中国数据库技术大会

【架构革新 高效可控】2020年12月21日-23日第十一届中国数据库技术大会将在北京隆重召开。

大会设置2大主会场,20+技术专场,将邀请超百位行业专家,重点围绕数据架构、AI与大数据、传统企业数据库实践和国产开源数据库等内容展开分享和探讨,为广大数据领域从业人士提供一场年度盛会和交流平台。

http://dtcc.it168.com


大会官网>>
  

北京盛拓优讯信息技术有限公司. 版权所有 16024965号-6 北京市公安局海淀分局网监中心备案编号:11010802020122
中国互联网协会会员  联系我们:huangweiwei@it168.com
感谢所有关心和支持过ChinaUnix的朋友们 转载本站内容请注明原作者名及出处

清除 Cookies - ChinaUnix - Archiver - WAP - TOP