Hi all,
The sysevent service in my home-made NAS (recently upgraded from
OpenSolaris 134 to Solaris Express 11) is not running:
nas@nas:~$ svcs -xv sysevent
svc:/system/sysevent:default (system event notification)
State: maintenance since February 24, 2011 06:00:56 PM UTC
Reason: Restarting too quickly.
See: http://sun.com/msg/SMF-8000-L5
See: man -M /usr/share/man -s 1M syseventd
See: /var/svc/log/system-sysevent:default.log
Impact: This service is not running.
This is what the log has:
nas@nas:~$ tail /var/svc/log/system-sysevent:default.log
[ Feb 24 18:00:52 Method "start" exited with status 0. ]
[ Feb 24 18:00:54 Stopping because process dumped core. ]
[ Feb 24 18:00:54 Executing stop method
("/lib/svc/method/svc-syseventd stop 153"). ]
[ Feb 24 18:00:54 Method "stop" exited with status 0. ]
[ Feb 24 18:00:54 Executing start method
("/lib/svc/method/svc-syseventd start"). ]
[ Feb 24 18:00:54 Method "start" exited with status 0. ]
[ Feb 24 18:00:56 Stopping because process dumped core. ]
[ Feb 24 18:00:56 Executing stop method
("/lib/svc/method/svc-syseventd stop 155"). ]
[ Feb 24 18:00:56 Method "stop" exited with status 0. ]
[ Feb 24 18:00:56 Restarting too quickly, changing state to maintenance. ]
I tried to execute the syseventd in debug mode, and got a segfault:
nas@nas:~$ pfexec /usr/lib/sysevent/syseventd -d9
syseventd[3003]: syseventd started, debug level = 9
syseventd[3003]: enter_daemon_lock: lock file = /var/run/syseventd.lock
syseventd[3003]: start the message thread running
syseventd[3003]: dispatch_message: thread started
syseventd[3003]: sigwait thread waiting for signal
syseventd[3003]: Unable to open module directory
/usr/platform/i86pc/lib/sysevent/modules/: No such file or directory
syseventd[3003]: Unable to open module directory
/usr/platform/i86pc/lib/sysevent/modules/: No such file or directory
syseventd[3003]: loading modules from /usr/lib/sysevent/modules/
syseventd[3003]: loaded module datalink_mod.so
syseventd[3003]: loaded module sysevent_reg_mod.so
syseventd[3003]: loaded module devfsadmd_mod.so
.....
syseventd[3003]: door_upcall: event 1a7 in eventbuf 48
syseventd[3003]: sysevent_reg_mod: sending event 0Xfa
syseventd[3003]: door_upcall: event 1a8 in eventbuf 49
syseventd[3003]: Waiting for 4 clients on event id 0Xf9
syseventd[3003]: door_upcall: event 1a9 in eventbuf 50
syseventd[3003]: sysevent_reg_mod: event sent 0Xfa
syseventd[3003]: Segmentation Fault
I already googled everything I could think of, but got nowhere.
I'd go back to b134, but one of the pools was updated to a newer
version of ZFS...
Is this familiar to anyone? Any ideas on what my be causing syseventd
to segfault? Some log should be checking?
Thanks!
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
