Thank you, Liane, for your quick reply. On 11/2/07, Liane Praza <liane.praza at sun.com> wrote: > Peter Kovacs wrote: > > I am begging your generous help in the following (probably very simple) > > matter. > > > > I've got a service which fails to start during system start-up with > > the following message in the corresponding svc/log file: > > > > svc.startd could not set context for method: chdir: No such file or > > directory > > > > Since "clearing" the service some time after system start-up > > successfully moves it to the online state, I thought "chdir" might > > refer to one of the directories on NSF. However, by guessing just with > > my naked eyes, I'd rather say no NSF directory is involved here. > > What is the directory specified in your service's working directory? > You can probably get it like this: > > $ svcprop -p start/working_directory <your fmri> > > (or just $ svcprop <fmri> | grep working_directory)
Both commands give :default bash-3.00# svcprop -p start/working_directory oracle_listener :default bash-3.00# svcprop oracle_listener | grep working_directory start/working_directory astring :default stop/working_directory astring :default > > My guess if it isn't NFS is that it's a non-root directory mounted by > vfstab, and the service doesn't depend on filesystem/local. (Which > mounts filesystems in vfstab, and all local zfs filesystems.) My service is dependent on the network/service. In fact, network/service doesn't appear in the output of the svcs -D filesystem/local command, so I think that I should, in deed, include filesystem/local in my service's dependency list. (Probably it is /export/home which is not yet mounted as my service is started.) > > > > > I turned on Verbose Logging as described in the svc.startd man page, > > but I haven't noticed anything conspicuous in the many log lines > > appearing on the console and I have no easy access to console anyway. > > Does Verbose Logging also go into a file where I can more thoroughly > > analyze the logs? Or is there a more trivial way to go about this > > particular problem? > > The verbose logging also goes to /var/svc/log/svc.startd.log, but > unfortunately it won't tell you anything more than the log message > you've got there. > > I'm fairly convinced we have a few bugs open to improve both the error > reporting and the general ease of use of method_contexts. We had > someone working on them, but he left the group a while ago, so don't > have anyone working on the bugs right now. :/ (They're pretty decent > bugs that are just slightly bigger than bite-sized, though.) > > I couldn't find the bugs quickly, but I'll look later and make sure that > this message is mentioned to at least give back the directory name > that's failing. In my case, knowing the directory name (presumably /export/home) would probably not have helped much. I definitely needed your hint that local file systems are handled (mounted) separately from the root file system and I might have to have the file system/local service in the dependencies. (I hadn't even been aware that there was a file system/local service at all.) So I'd rather blame the general lack of familiarity on my end with all the available services and their purposes than this kind deficiencies in the SMF implementation. Thanks a lot for your help, Peter > > liane >
