* Mark Maule <mark_maule at yahoo.com> [2009-12-09 16:48]: > Hi: > > I'm developing a custom boot archive/root based on ONNV (currently b126 I > think) for an appliance, and am having trouble getting the svc > infrastructure up and running. Currently, when I start svc.startd, both > svc.startd and svc.configd are spinning wildly, accumulating cpu time, but > neither appear to be making forward progress or logging anything. > > I'm currently starting svc.startd by hand - have it commented out of > /etc/inittab since the current behavior seems to livelock my system (at least > I don't get any serial console output). > > My boot archive generation script "generates" /etc/svc/repository.db as: > > pfexec cp $ON_Root/lib/svc/seed/global.db $TargetRoot/etc/svc/repository.db > > I attempted to make a couple of small changes to get more logging with no > effect: > > cat > $Tmpdir/svccfg << EOF > repository $TargetRoot/etc/svc/repository.db > select svc:/system/svc/restarter:default > addpg options application > setprop options/boot_messages = astring: "verbose" > setprop options/logging = astring: "debug" > EOF > > pfexec svccfg -v -f $Tmpdir/svccfg > > Adding -m verbose to the boot line didn't yield any additional debug either.
That's strange. You might want to try -m debug and -m milestone=none. > If I grab a core of configd/startd, I see them here: ... You can use either pstack(1) or truss(1) here, to skip the core file generation (and to see all thread stacks). I'd recommend using truss(1) and seeing what each process is trying to do. > I suspect I am missing some required files, or I am not setting up the > initial repository.db correctly. Any help would be greatly > appreciated. seed/global.db is supposed to be sufficient to rebuild the repository--to get to svc:/system/manifest-import, that is. Some sanity questions: - is /etc/svc/volatile being mounted? - does it have any contents? (What are they?) Cheers Stephen -- sch at sun.com http://blogs.sun.com/sch/
