On 5/19/15 6:06 , Giorgio Valoti wrote: > Hi all, > I have installed BuildBot (via pip) on a zone (version 20150417T032339Z) and > I’m trying to register it as a service in SMF. > > The process starts correctly with: > >> /opt/local/bin/buildbot start /var/buildbot/masters/master01 > … >> 2015-05-19 12:20:47+0000 [-] BuildMaster is running >> The buildmaster appears to have (re)started correctly. > > > So I created a manifest file like the one that follows, but when I try to > enable it the operation hangs indefinitely: >> /usr/sbin/svcadm -v enable -s buildmaster >> svc:/buildmaster:default enabled. > > > I have tried to exclude issues with the daemonization process, but I get the > same behavior. Does anyone have some suggestion? It would be really > appreciated. > > <?xml version='1.0'?> > <!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'> > <service_bundle type='manifest' name='export'> > <service name='buildmaster' type='service' version='0'> > <create_default_instance enabled='true'/> > <single_instance/> > <dependency name='network' grouping='require_all' restart_on='error' > type='service'> > <service_fmri value='svc:/milestone/network:default'/> > </dependency> > <dependency name='filesystem-local' grouping='require_all' > restart_on='none' type='service'> > <service_fmri value='svc:/system/filesystem/local:default'/> > </dependency> > <dependency name='config-file' grouping='require_all' > restart_on='refresh' type='path'> > <service_fmri > value='file://localhost/var/buildbot/masters/master01/master.cfg'/> > </dependency> > <method_context> > <method_credential user='buildbot' group='buildbot' /> > <method_environment> > <envvar name='PATH' value='/usr/bin:/usr/sbin:/opt/local/bin' /> > </method_environment> > </method_context> > <exec_method name='start' type='method' exec='/opt/local/bin/buildbot > start /var/buildbot/masters/master01' timeout_seconds='10'/> > <exec_method name='stop' type='method' exec='/opt/local/bin/buildbot stop > /var/buildbot/masters/master01' timeout_seconds='10'/> > <exec_method name='restart' type='method' exec='/opt/local/bin/buildbot > restart /var/buildbot/masters/master01' timeout_seconds='10'/> > <exec_method name='refresh' type='method' exec='/opt/local/bin/buildbot > reconfig /var/buildbot/masters/master01' timeout_seconds='10'/> > <property_group name='startd' type='framework'> > <propval name='ignore_error' type='astring' value='core,signal'/> > </property_group> > <stability value='Evolving'/> > <template> > <common_name> > <loctext xml:lang='C'>Buildmaster: BuildBot master daemon</loctext> > </common_name> > <documentation> > <manpage title='buildbot' section='1M' manpath='/opt/local/man'/> > </documentation> > </template> > </service> > </service_bundle> >
When you're doing this, do you find that if you run svcs against this, that there's an asterisk next to the state column? Is the buildbot binary supposed to daemonize itself? Robert ------------------------------------------- smartos-discuss Archives: https://www.listbox.com/member/archive/184463/=now RSS Feed: https://www.listbox.com/member/archive/rss/184463/25769125-55cfbc00 Modify Your Subscription: https://www.listbox.com/member/?member_id=25769125&id_secret=25769125-7688e9fb Powered by Listbox: http://www.listbox.com
