Jesse writes:
> By following the steps to enable verbose logging (as described in man
> svc.startd), I somehow managed to cause several services to go into
> maintenance. system/cron, system/sac, network/rpc/bind, system/basicreg and
> others have all failed, many due to "Start method exited with
> $SMF_EXIT_ERR_CONFIG." So, I figure I must have unknowingly mangled one of
> the steps in enabling verbose logging and caused a problem with the
> configuration of svc.startd.
>
> I ran /lib/svc/bin/restore_repository with the -seed- option to try to fix
> it, to no avail. Same problems persist.
>
> Any tips on how I might solve this, and if not, is there a more robust way
> to blow away and import a new repository without reinstalling my system?
>
> Thanks,
>
> -Jesse
>
>
> This message posted from opensolaris.org
> _______________________________________________
> smf-discuss mailing list
> smf-discuss at opensolaris.org
Jesse,
I have a few questions for you. First of all which version of Solaris are
you running and what is your hardware architecture? Is the method that you
used to enable verbose logging the one where you used svccfg to set the
options/logging property to verbose? On the first boot after restoring the
seed repository, did the system load a whole lot (140-180 or so) of service
descriptions? Was this reboot still in verbose mode, or did it revert to
quiet mode? Now that the system is rebooted, what is the output of
svccfg -s svc:/system/svc/restarter:default listpg
and
svcs -x
I may ask you to send me some of your logs, but let's get started with these
questions.
tom
