View source for SME10 serviceControl

From SME Server
You do not have permission to edit this page, for the following reason:
The action you have requested is limited to users in the group: Users.
You can view and copy the source of this page.
===Versions previous to 10: boot process and service control===
SysVinit is used, with initscripts built to handle a specific run level rc7.d. Over that we use Runit to handle services indexed in /services / and /var/services. 

A cli wrapper for the command service /sbin/e-smith/service has been created so that only initscripts which exist in run-level 7 can be run. This ensures that the supervised service is run, if one exists, and protects against running e.g. "service httpd restart" directly. The wrapper will also choose between an sv command for runit processes or a regular call to /etc/rc.d/init.d/ scripts.
* /sbin/e-smith/service
<syntaxhighlight lang="bash">
#! /bin/sh

runlevel=$(runlevel | cut -d" " -f2)

if [ "$runlevel" = "4" ]
then
    if ls /etc/rc7.d/S??$1 >/dev/null 2>/dev/null
    then
       script=$(ls /etc/rc7.d/S??$1 | head -1)
       exec $script $2
    fi

    echo "'$1' is not a valid service name" 1>&2
    exit 1
else
    exec /sbin/service "$@"
fi

</syntaxhighlight>

=== Version 10 on: boot process and service control ===

==== Current SME10 alpha boot process and service control ====
Systemd is the new Linux standard to handle services and service monitoring and is enforced upstream. Systemd will supersede all /etc/rc.d/init.d/ scripts and calls to /usr/sbin/service.

We have added a first systemd unit to bootstrap the console and made it a drop in replacement of Sysvinit to boot all processes linked in /etc/rc.d/rc7.d/.

From there we could continue in this way, or try to move as many processes as we can to systemd. That works, but is even more complex than it was in the previous SME versions. Additionally we can not guarantee—without further scripts—that an issued ''systemctl start httpd'' would be blocked.
* new startup with console see /usr/share/perl5/vendor_perl/esmith/console/startup.pm
<syntaxhighlight lang="perl">
package esmith::console::startup;
use Locale::gettext;
use esmith::console;
use esmith::ConfigDB;
use strict;
use warnings;

sub new
{
    my $class = shift;
    my $self = {
                @_,
               };
    bless $self, $class;
    return $self;
}

sub startup_callback {
    my $fd = shift;
    my @out = ();
    my $done = 0;

    use DirHandle;
    my $d = DirHandle->new("/etc/rc7.d");
    my @services = sort
        {
            $a =~ /^S(\d+)/; my $A = $1;
            $b =~ /^S(\d+)/; my $B = $1;
            $A <=> $B
        } grep { /^S/ } $d->read;
    my $rows = 12;
    my $status_col = 65;

    my $db = esmith::ConfigDB->open_ro;
    my $rec = $db->get('smb');
    my $i=0;
    foreach (@services) {
        $i=$i+1;
        next unless /^S(\d+)([^\.][\.\w\-]+)$/;
        next unless $2 eq "smb";
        splice @services,$i-1 , 1, "S${1}4smbd", "S${1}5nmbd"  unless ($rec and $rec->prop('status') eq 'disabled');
        last;
    }


    open(STDOUT, ">&STDERR");
    foreach (@services)
    {
       sleep 1;
       my $percent = int(($done * 100) / ($#services + 1));
       $done += 1;
       my $link = $_;
       #warn "Looking at symlink $_\n";
       next unless /^S\d+([^\.][\.\w\-]+)$/; # Untaint service name
       my $service = $1;
       #my $db = esmith::ConfigDB->open_ro;
       $rec = $db->get($service);
       do
       {
            warn "not starting disabled service $service\n";
            next;
       } unless ($rec and $rec->prop('status') eq 'enabled');
       my $prompt = "starting ";
       my $supervised = -x "/service/$service/run";
       my @cmd;
       if (-x "/service/$service/run")
       {
            $prompt .= " supervised service $service";
            warn "starting supervised service $service\n";
            @cmd = ("sv", "up", "/service/$service");
       }
       elsif (-x "/etc/init.d/$service")
       {
            $prompt .= " unsupervised service $service";
            warn "starting unsupervised service $service\n";
            @cmd = ("/etc/init.d/$service", "start");
       }
       else
       {
            warn "ignoring unknown service $service: bogus start symlink $link\n";
            next;
       }

       push @out, "$prompt\n";
       print $fd "XXX\n";
       print $fd "$percent\n";
       my @show = $#out > $rows ? @out[$#out - $rows .. $#out] : @out;
       do { print $fd $_ } foreach @show;
       print $fd "XXX\n";
       $prompt .= " " x ($status_col - length($prompt));
       $prompt .= system(@cmd) ? "\\Z1FAILED\\Zn" : "\\Z2OK\\Zn";
       $out[-1] = "$prompt\n";
       @show = $#out > $rows ? @out[$#out - $rows .. $#out] : @out;
       print $fd "XXX\n";
       print $fd "$percent\n";
       do { print $fd $_ } foreach @show;
       print $fd "XXX\n";
    }
    print $fd "100\n";
    sleep 2;
    return undef;
};

my $console = esmith::console->new;

sub doit
{
    my ($self, $console, $db) = @_;

    $console->infobox
        (
         title   => gettext("Starting system services"),
         text    => "\n" .
                    gettext("Please standby while system services are started ..."
),
        );

    system(qw(touch /var/lock/subsys/backup-running));
    system(qw(chown admin /var/lock/subsys/backup-running));
    sleep(6);  # Wait to be certain that all runsv services have been started.
    $console->gauge(\&startup_callback,
        text => '',
        title => 'Starting system services',
        colors => 1,
        no_collapse => 1);
}

#use esmith::console;
#use esmith::ConfigDB;
#esmith::console::startup->new->doit(esmith::console->new(),
#  esmith::ConfigDB->open);
1;

</syntaxhighlight>
* a new /sbin/e-smith/service
<syntaxhighlight lang="bash" line="1">
#! /bin/sh
# prevent initscript to use systemctl
export SYSTEMCTL_SKIP_REDIRECT=1
. /etc/rc.d/init.d/functions

# what is our current runlevel
runlevel=$(systemctl get-default)
SERVICE=$1
USAGE="Usage: service SERVICENAME [ACTION]"

#if no servicename is provided return usage
if [[ "${SERVICE}" == "" ]]
then
   echo ${USAGE} >&2
   exit
fi

if [ "$runlevel" = "multi-user.target" ]
then
    if ls /etc/rc7.d/S??$1 >/dev/null 2>/dev/null
    then
       script=$(ls /etc/rc7.d/S??$1 | head -1)
       exec $script $2

    elif ls /usr/lib/systemd/system/${SERVICE}.service >/dev/null 2>/dev/null || ls /etc/systemd/system/${SERVICE}.service >/dev/null 2>/dev/null
    then
	 if [[ "$2" == "" ]] ; then
         echo "'$1' requires an action" 1>&2
         echo ${USAGE} >&2
         exit
        elif  [[ $2 == "status" ]] ; then
         exec /bin/systemctl status -n0 ${SERVICE}
         exit
        elif [[ $2 == "start" ]] ; then
         echo -n  "Starting ${SERVICE}" 2>/dev/null
        elif [[ $2 == "stop" ]] ; then
         echo -n  "Stopping ${SERVICE}" 2>/dev/null
        elif [[ $2 == "restart" ]] ; then
         echo -n  "Restarting ${SERVICE}" 2>/dev/null
        else
         echo -n  "Sending $2 signal to ${SERVICE}" 2>/dev/null
        fi
        /bin/systemctl $2 ${SERVICE}.service> /dev/null
        if [ $? -ne 0 ]; then
         echo_failure
        else
         echo_success
        fi
        echo
        exit
    fi

    echo "'$1' is not a valid service name" 1>&2
    exit 1
else
    exec /sbin/service "$@"
fi

</syntaxhighlight>
* And the current controlService perl function from /usr/share/perl5/vendor_perl/esmith/util.pm
<syntaxhighlight lang="perl" line="1">
=pod

=head1 SERVICE MANAGEMENT UTILITIES

=head2 serviceControl()

Manage services - stop/start/restart/reload/graceful

Returns 1 for success, 0 if something went wrong, fatal exception on bad
arguments.

    serviceControl(
        NAME=>serviceName,
        ACTION=>start|stop|restart|reload|graceful
        [ BACKGROUND=>true|false (default is false) ]
    );

EXAMPLE:

    serviceControl( NAME=>'httpd-e-smith', ACTION=>'reload' );

NOTES:

The BACKGROUND parameter is optional and can be set to true if
start/stop/restart/etc. is to be done in the background (with
backgroundCommand()) rather than synchronously.

CONVENTIONS:

This command is the supported method for action scripts, blade handlers, etc.,
to start/stop/restart their services. Currently this is done via the rc7
symlinks, but this may change one day. Using this function gives us one
location to change this behaviour if desired, instead of hunting all over
every scrap of code. Please use it.

=cut

sub serviceControl
{
    my %params = @_;

    my $serviceName = $params{NAME};
    unless ( defined $serviceName )
    {
        die "serviceControl: NAME must be specified";
    }

    my $serviceAction = $params{ACTION};
    unless (defined $serviceAction)
    {
        die "serviceControl: ACTION must be specified";
    }

    if ( $serviceAction =~ /^(start|stop|restart|reload|graceful|adjust|svdisable)$/ )
    {
        my ($startScript) = glob("/etc/rc.d/rc7.d/S*$serviceName") ||'' ;
        my ($systemdScript) = "/usr/lib/systemd/system/$serviceName.service" ||'';

        unless ( -e $startScript or -e $systemdScript)
        {
            warn "serviceControl: startScript not found "
              . "for service $serviceName\n";
            return 0;
        }

        if (-e $systemdScript and ! -e $startScript){
            if ($serviceAction =~/^(start|stop|restart|reload)$/) {
                system('/usr/bin/systemctl',"$serviceAction","$serviceName.service") == '0'
                ||    warn "serviceControl: Couldn't " .
                "system( /usr/bin/systemctl $serviceAction $serviceName.service): $!\n";
            }
            else {
                die "serviceControl: systemd doesn't know : systemctl $serviceAction $serviceName.service";
            }
        }

        elsif (-e $startScript) {
            my  $background = $params{'BACKGROUND'} || 'false';

            if ( $background eq 'true' )
            {
            backgroundCommand( 0, $startScript, $serviceAction );
            }
            elsif ( $background eq 'false' )
            {
                unless ( system( $startScript, $serviceAction ) == 0 )
                {
                warn "serviceControl: "
                  . "Couldn't system($startScript, $serviceAction): $!\n";
                return 0;
                }
           }
           else
           {
            die "serviceControl: Unsupported BACKGROUND=>$background";
           }
        }
    }
    else
    {
        die "serviceControl: Unknown serviceAction $serviceAction";
    }
    return 1;
}

</syntaxhighlight>

=== Systemd Integration: Options and possibilities ===
This section is intended to open up a discussion concerning options and possibilities, in order to facilitate choosing the optimal SME approach to systemd.

Issues to solve :
* SME vs. upstream
* make unit files aware of service status in e-smith db configuration
* have our services boot in the right sequence
* journald vs rsyslogd
* plain file log vs special file format
* enabling /disabling /masking services

'''Table 1.         Load path when running in system mode (<code>--system</code>).'''      <ref>https://www.freedesktop.org/software/systemd/man/systemd.unit.html</ref>
{| class="wikitable"
!Path
!Description
|-
|<code>/etc/systemd/system.control</code>
| rowspan="2" |Persistent and transient configuration created using the dbus API
|-
|<code>/run/systemd/system.control</code>
|-
|<code>/run/systemd/transient</code>
|Dynamic configuration for transient units
|-
|<code>/run/systemd/generator.early</code>
|Generated units with high priority (see ''<code>early-dir</code>'' in systemd.generator(7))
|-
|<code>/etc/systemd/system</code>
|System units created by the administrator
|-
|<code>/run/systemd/system</code>
|Runtime units
|-
|<code>/run/systemd/generator</code>
|Generated units with medium priority (see ''<code>normal-dir</code>'' in systemd.generator(7))
|-
|<code>/usr/local/lib/systemd/system</code>
|System units installed by the administrator
|-
|<code>/usr/lib/systemd/system</code>
|System units installed by the distribution package manager
|-
|<code>/run/systemd/generator.late</code>
|Generated units with low priority (see ''<code>late-dir</code>'' in systemd.generator(7))
|}

==== Generators ====
There have been suggestions about using a generator, it is not clear how and why it would help.  This approach would be more complex. and according to the doc<ref>https://www.freedesktop.org/software/systemd/man/systemd.generator.html#</ref>: 
* Units written by generators are removed when the configuration is  reloaded. That means the lifetime of the generated units is closely bound to the reload cycles of '''systemd''' itself.
* Generators should only be used to generate unit files and symlinks to them, not any other kind of configuration. Due to the lifecycle logic mentioned above, generators are not a good fit to generate dynamic configuration for other services. If you need to generate dynamic configuration for other services, do so in normal services you order before the service in question.
systemctl daemon-reload has be run after each modification of a unit. Hence generated files by generators will be erased and generators rerun. <ref>https://www.freedesktop.org/software/systemd/man/systemctl.html#daemon-reload</ref>

==== Overriding the upstream vendor preset : templated unit files, or not? And where? ====
The reference is the example of a service unit provided by the upstream vendor. 
* Should we simply create a template and expand it over the unit.service in /lib/systemd/system/ 
* Or offer a different way to override upstream vendor settings?
Furthermore should we template our file to point to /lib/ or to /etc/? 

In other words, should we fight with admin space trying to overwrite changes in its dedicated space, or should we fight with upstream vendors and overwrite their files or find a way to override them?

Thus the questions arise:
* Where: /etc or /lib/
* What: use a template or not
* How: overwrite, or selective overriding
Looking at the options:

==== Create unit files in /etc/systemd/system/ or in /lib/systemd/system/? ====
:As a vendor we should work in /lib/systemd/system/, but as an admin helper we might want to play in /etc/systemd/system/ and rather offer a way for admin to use our template-custom or config db.

==== Template or not? ====
:The simplest way to override a service could be to simply template the file /lib/systemd/system/servicename.service and expand it every time a reconfiguration or a boot occurs.

:Going further, we could ensure the stability of the system by setting this in 

:/etc/systemd/system/servicename.service

===== unitname.d/file.conf versus overwrite uniname.service =====
:From reading and inspection of a few systems, a dot d folder could be created both in etc and lib.

:There are two methods of overriding vendor settings in unit files: 

::First, copying the unit file from     <code>/usr/lib/systemd/system</code> to   <code>/etc/systemd/system</code> and modifying the chosen settings. 

::Second, one can create a directory named <code>''<code>unit</code>''.d/</code> within <code>/etc/systemd/system</code> and place a drop-in file there <code>''<code>name</code>''.conf</code> that only changes the specific settings one is interested in. Note that multiple such drop-in files are read if present, processed in lexicographic order of their filename.

:The advantage of the first method is that one easily overrides the complete unit, the vendor unit is not parsed at all anymore. It has the disadvantage that improvements to the unit file by the vendor are not automatically incorporated on updates.

:The advantage of the second method is that one only overrides the settings one specifically wants, where updates to the unit by the vendor automatically apply. This has the disadvantage that some future updates by the vendor might be incompatible with the local changes.<ref>https://www.freedesktop.org/software/systemd/man/systemd.unit.html</ref>

===== Uninstalling/masking unwanted/conflicting services: firewalld example =====
:We can plan to uninstall firewalld for example, but some packages will reinstall as a requirement. It might even be started, which could conflict with masq.

=== Systemd current implementation ===
Previously we had sysvinit services and supervised services under Daemontool and Runit.

We are currently moving all sysvinit handled service to systemd.

For services supervised with Runit, we either move them to systemd with their own unit if one is provided, or we create one which will keep the service running under Runit

The idea is to stop to have the Bootstrap Console start services.

==== default target: sme-server.target ====
We use our own target.

==== system-preset ====
The use of system presets is the basis of our method of handling the systemd services under Koozali SME Server.

For direct post-install purposes we use an e-smith-base RPM own file :  /usr/lib/systemd/system-preset/50-Koozali.preset

This file contains a list of service we want to have enabled or disabled.

Another file will take precedence without hiding it: /etc/systemd/system-preset/49-koozali.preset. This file is templated, and uses the e-smith configuration db to list services that should be enabled or disabled based on admin changes.

It is important that this file is called 49-koozali.preset (k or K?) and not 50-Koozali.preset, so it does not hide 50-Koozali.preset content, but take precedence on it. Hence, anything not declared in 49-koozali.preset will take the state of what declare the 50 one. <!-- k or K? -->

Then we use an action script to default all we want to be in systemd: /etc/e-smith/events/actions/systemd-default<syntaxhighlight lang="bash">
#!/usr/bin/bash
/usr/bin/systemctl  enable sme-server.target
ln -fs sme-server.target /lib/systemd/system/default.target
/usr/bin/systemctl  preset-all
/usr/bin/systemctl  set-default sme-server.target

</syntaxhighlight>This will ensure that on every run, all services explicitly enabled or disabled in the configuration db are declared this way in systemd, and if they are not in the db they are controlled according to what is declared in other /lib/systemd/system-preset/* files.

Any services not explicitly declared there will be disabled (/lib/systemd/system-preset/99-default-disable.preset). So If you want a service to run you need to declare it at the very least with :<syntaxhighlight lang="bash">
db configuration set myservice service status enabled
expand-template /etc/systemd/system/preset/49-koozali.preset
/etc/e-smith/events/actions/systemd-default
systemcl start myservice.service
</syntaxhighlight>

Note you can also declare a service unit name with a service name with a different name. This is in beta for the moment, as it might conflict with some other script handling the services (/sbin/e-smith/service, bootstrap-console;  controlService perl function from /usr/share/perl5/vendor_perl/esmith/util.pm) <syntaxhighlight lang="bash">
db configuration set myservice service status enabled SystemdUnit service@my.service
expand-template /etc/systemd/system/preset/49-koozali.preset

</syntaxhighlight>

==== service-status ====
We run as ExecStartPre a call to a script preventing any unwanted launch of a disabled service. This is basic and just fails the service with a message at any attempt to start it. This deals with the case that it has been started manually, or has been enabled, and prevents an event from running to disable it before reboot (is this correct?)

Currently the script just fails, but we could in the future have a property in the db to make it just send a warning and let the service start.<syntaxhighlight lang="bash">
#! /bin/sh

SERVICE=$1
USAGE="Usage: service-status SERVICENAME"

#if no servicename is provided return usage
if [[ "${SERVICE}" == "" ]]
then
   echo ${USAGE} >&2
   exit 1
fi

TYPE=$(/sbin/e-smith/db configuration gettype "$SERVICE" || echo none)

if [[ "$TYPE" != 'service' ]]
then
    echo "$SERVICE is not a service"
    exit 9
fi

STATUS=$(/sbin/e-smith/db configuration getprop "$SERVICE" status || echo disabled)

if [[ "$STATUS" != 'enabled' ]]
then
    echo "$SERVICE will not start (service status not enabled)"
    exit 5
fi

exit 0

</syntaxhighlight>

==== services2adjust ====
Runit and Sysvinit were allowing some signals that are not handled anymore by systemd. We will have to replace those.

'''As an example <u>service masq adjust</u> needs to be replaced by <u>systemctl reload masq.service</u>.'''

for the following we could use  <code>kill --signal=</code> 
* sigusr1
* sigusr2
* sigterm
* sighup

On the other hand, systemd offers some interesting new solutions :
* start
* stop
* reload
* restart
* try-restart 
* reload-or-restart
* try-reload-or-restart

=== Service migration ===
* We will have all our service unit files in /usr/lib/systemd/system/
* They should all be required by sme-server.target in the [Install]
* For as long as possible we will avoid templating .service files and/or their modification in /usr/lib/systemd/system/servicename.service.d/50koozali.conf

===== Previous pure Syvinit service, with a provided systemd unit =====
If we are lucky we can simply use the ones provided as a replacement, we add a service.d/50koozali.conf for the service and alter it in the way we need.

===== Previous pure Syvinit service, without a provided systemd unit =====
Here is the example of masq : /lib/systemd/system/masq.service<syntaxhighlight lang="bash">
[Unit]
Description=masq, the Koozali SME Server firewall script
Before=network-pre.target
Wants=network-pre.target
Conflicts=iptables.service ip6tables.service ebtables.service ipset.service nftables.service firewalld.service

[Service]
Type=oneshot
ExecStartPre=/sbin/e-smith/service-status masq
ExecStart=/etc/rc.d/init.d/masq start
ExecStop=/etc/rc.d/init.d/masq stop
ExecReload=/etc/rc.d/init.d/masq adjust
RemainAfterExit=yes


[Install]
WantedBy=sme-server.target

</syntaxhighlight>example of network : /lib/systemd/system/networking.service<syntaxhighlight lang="bash">
[Unit]
Description= Network management for Koozali SME Server, using old sysvinit script
After=network-pre.target
Wants=network.target
Before=network-online.target wan.service
Conflicts=NetworkManager.service

[Service]
Type=oneshot
ExecStart=/etc/rc.d/init.d/network start
ExecStop=/etc/rc.d/init.d/network stop
ExecReload=/etc/rc.d/init.d/network restart
RemainAfterExit=yes

[Install]
WantedBy=sme-server.target
Alias=network.service

</syntaxhighlight>

===== Previous Runit service, with a provided systemd unit =====
If we are lucky we can simply use the ones provided as a replacement, we add a service.d/50koozali.conf for the service and alter it in the way we need.

As a last resort we could hide the whole file using the service.d/50koozali.conf  and simply call runit, see the next example.

===== Previous Runit service, without a provided systemd unit =====
example of wan : /lib/systemd/system/wan.service<syntaxhighlight lang="bash">
[Unit]
Description=WAN interface for Koozali SME Server
After=network-pre.target networking.service
Before=network-online.target

[Service]
Type=oneshot
ExecStartPre=/sbin/e-smith/service-status wan
ExecStart=/usr/bin/sv u /service/wan
ExecStop=/usr/bin/sv stop  /service/wan
ExecReload=/usr/bin/sv t /service/wan
RemainAfterExit=yes

[Install]
WantedBy=sme-server.target

</syntaxhighlight>

=== References ===
<references />
[[Category:SME10-Development]]
Templates used on this page:
Template:Ibox (view source) (protected)
Template:Warning box (view source) (protected)
Return to SME10 serviceControl.
Retrieved from "https://wiki.koozali.org/SME10_serviceControl"
View source for SME10 serviceControl

Navigation menu

Page actions

Page actions

Personal tools

Koozali SME Server

Recent activities

Koozali resources

Koozali SME Server wiki

Tools

Search
