Ubic::Service - interface and the base class for any ubic service


version 1.60


    print "Service: ", $service->name;
    $status = $service->status;


Ubic::Service is the abstract base class for all ubic service classes.

It provides the common API for implementing start/stop/status operations, custom commands and tuning some metadata properties (user(), group(), check_period()).



All action methods should return Ubic::Result::Class objects. If action method returns a plain string, Ubic will wrap it into result object for you.


Start the service. Should throw an exception on failure and a result object or a string with operation result otherwise.

Starting an already running service should do nothing and return already running.


Stop the service. Should throw an exception on failure and a result object or a string with operation result otherwise.

Stopping an already stopped service should do nothing and return not running.

Successful stop of a service must disable this service.


Check the status of the service.

It should check that service is running correctly and return running if it is so.


Reload the service if possible.

Throw an exception if reloading is not implemented (default implementation already does so).


All metadata methods are read-only. All of them provide the sane defaults.


Get the port number if a service listens for a TCP port.

Default is undef.


Get the user from which the service can be controlled and will be running.

Defaults to default_user from Ubic::Settings (i.e., root for a system-wide installation, or to the installation owner for a local installation).


Get the list of groups from which the service can be controlled and will be running.

First group from the list will be used as real and effective group id, and other groups will be set as supplementary groups.

Default is an empty list, which will later be interpreted as default group of the user returned by user() method.


Period of checking a service by watchdog in seconds.

Default is 60 seconds and it is unused by the ubic.watchdog currently, so don't bother to override it by now :)


Timeout after which the watchdog will give up on checking the service and will kill itself.

This parameter exists as a precaution against incorrectly implemented status() or start() methods. If a status() method hangs, without this timeout, watchdog would stay in memory forever and never get a chance to restart a service.

This parameter is not a timeout for querying your service by HTTP or whatever your status check is. Service-specific timeouts should be configured by other means.

Default value is 60 seconds. It should not be changed unless you have a very good reason to do so (i.e., your service is so horribly slow that it can't start in 1 minute).


Services can define custom commands which don't fit into the usual start/stop/restart/status set.


Should return the list of service's custom commands, if there are any.


Should execute specified command, if it is supported. Throw an exception otherwise.


These methods should not be overridden by specific service classes. They are usually used by the code which loads service (i.e. some kind of Ubic::Multiservice) to associate service with its name.

These methods are just the simple interdependent r/w accessors.


Get or set a name of the service.

Each service with the same parent should have an unique name.

In case of subservices, this method should return the most lower-level name.

Service implementation classes shouldn't override this or other *_name methods; it's usually a service's loader job to set them correctly.


Get a fully qualified name of the service.

Each service must have a unique full_name.

Full name is a concatenation of service's short name and service's <parent_name>.


Get or set a name of the service's parent.

Service's loader (i.e. some kind of Ubic::Multiservice) is responsible for calling this method immediately after a service is constructed, like this: $service->parent_name($self->full_name) (check out Ubic::Multiservice sources for more).


A boolean value that determines the state of a service if it has never been explicitly enabled or disabled yet. Service is considered initially enabled when auto_start is true.

Default is false, so initial service status is off, and you have to run ubic start service_name to start it.


Current API for custom commands is inconvenient and doesn't support parameterized commands. It needs some refactoring.

Requiring every service to inherit from this class can be seen as undesirable by some programmers, especially by those who prefer to use Moose and roles. If you know how to make this API more role-friendly without too much of converting pains, please contact us at or at irc://


Ubic::Service::Skeleton - implement simple start/stop/status methods, and ubic will care about everything else.

Ubic::Service::Common - just like Skeleton, but all code can be passed to constructor as sub references.

Ubic::Service::SimpleDaemon - give it any binary and it will make a service from it.


Vyacheslav Matyukhin <>


This software is copyright (c) 2016 by Yandex LLC.

This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.