Hi David, Can you check if fmd is dumping core on startup - they would accumulate in /var/fm/fmd/. (assuming you haven't modified the global core settings via coreadm). If so, we'll need to take a look at one of the core(s) to figure out why it's failing.
If there's no cores, could you try starting fmd manually (outside of SMF) as follows and send us the output (which will likely be quite large): # (cd /; /usr/lib/fm/fmd/fmd -o fg=true -o debug=all -o client.debug=true) Also, I'm cc'ing the fm-discuss alias. That's the best list for this type of question. thanks, rob David Pipe wrote: > I've just encountered a problem with Solaris 10 8/07 x86 running on a SunFire > x4150. Having just applied the latest recommended patch cluster, fmd fails to > start with an exit status of 1. svcs -xv and the log files show only that it > failed to start with a status of 1. All dependent services are online. I've > tried re-enabling the service with no luck. I've tried deleting and importing > the fmd.xml manifest without any luck. This has happened on all similar > servers after patching. All filesystems are mounted with lots of free space. > It looks like the patching has done something. Does anybody know what to do? > Help appreciated. > > > This message posted from opensolaris.org > _______________________________________________ > opensolaris-help mailing list > [email protected] _______________________________________________ opensolaris-help mailing list [email protected]
