Stopping & Starting HPCC V7 Cluster on Ubuntu 18.04

[amillar]

Hi There,

We have recently upgraded one of our HPCC Clusters to Version 7.4.8-1 running on Ubtunu 18.04.

With this being on Ubuntu 18.04 and HPCC V7 I just want to check if there is any differences with the commands to start / stop and check the status of the cluster.

I have always run sudo bash start-hpcc.sh status / stop / start

which runs :

#!/bin/bash
sudo /opt/HPCCSystems/sbin/hpcc-run.sh $1

This command does work but the output looks like this

192.168.20.35 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.36 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.37 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.39 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.40 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.41 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.42 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.43 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.44 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.45 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.46 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.47 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.48 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.49 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

192.168.20.50 hpccsystems-platform.target status :
hpccsystems-platform.target
â ââdafilesrv@mydafilesrv.service
â ââdali@mydali.service
â ââdfuserver@mydfuserver.service
â ââeclagent@myeclagent.service
â ââeclccserver@myeclccserver.service
â ââeclscheduler@myeclscheduler.service
â ââesp@myesp.service
â ââroxie@myroxie.service
â ââsasha@mysasha.service
â ââthor@mythor.service

Is this to be expected? On HPCC V6 and Ubuntu 16.04 it was nice and clear of what didn’t start.

e.g.

192.168.20.126 hpcc-init status :
mydafilesrv ( pid 1765 ) is running ...
192.168.20.132 hpcc-init status :
mydafilesrv ( pid 1707 ) is running ...
mydfuserver ( pid 1836 ) is running ...
myeclagent ( pid 2766 ) is running ...
myeclccserver ( pid 31624 ) is running ...
myesp ( pid 3065 ) is running ...
mysasha ( pid 3220 ) is running ...
mythor ( pid 7600 ) is running with 48 slave process(es) ...
192.168.20.133 hpcc-init status :
mydafilesrv ( pid 1710 ) is running ...
mydali ( pid 1839 ) is running ...
myeclscheduler ( pid 4018 ) is running ...

192.168.20.134 hpcc-init status :
mydafilesrv ( pid 1788 ) is running ...

192.168.20.135 hpcc-init status :
mydafilesrv ( pid 1663 ) is running ...

192.168.20.136 hpcc-init status :
mydafilesrv ( pid 1649 ) is running ...

192.168.20.137 hpcc-init status :
mydafilesrv ( pid 1664 ) is running ...

192.168.20.138 hpcc-init status :
mydafilesrv ( pid 1673 ) is running ...

192.168.20.139 hpcc-init status :
mydafilesrv ( pid 1666 ) is running ...

192.168.20.140 hpcc-init status :
mydafilesrv ( pid 1656 ) is running ...

192.168.20.141 hpcc-init status :
mydafilesrv ( pid 1660 ) is running ...

In addition to the commands to stop and start the cluster sometimes I have to stop and start certain components.

For example :

sudo service hpcc-init -c mythor stop / Start

is this still current on Ubuntu 18.04 & HPCC V7?

Also sometimes I need to stop the Dali server, on Version 6 and Ubuntu 16.04 I used to run :

sudo service mydafilesrv stop / start

should this now be :

Sudo systemctl start <service name>

Are there any other commands since V7 I should be aware of?

Thanks in advance

[mgardner]

Morning Amillar,

Most systems have moved from sysV to systemd. What you're seeing is our transition along with the platforms we build HPCCSystems Platform on to that new init system. If you want to revert to the old sysV style of output. You can start/stop and check status with the hpcc-init script. But the sysV scripts will have no knowledge of the status of processes running under systemd and vice versa, so it's recommended to stick to one or the other.

With the new systemd, 'status' is just showing which components have been setup and systemd is controlling. If you look in the new eclwatch, you should be able to easily tell which components are properly started or if there are any warnings.

sudo service hpcc-init -c mythor stop / Start

is this still current on Ubuntu 18.04 & HPCC V7?

It's recommended to stop using 'service' and start using 'systemctl'

sudo service mydafilesrv stop / start

should this now be :

Sudo systemctl start <service name>

Yes, `sudo systemctl start roxie@myroxie.service` is the recommended way to start/stop components.

An extra command that you might want to play with is `systemctl list-dependencies <service>`

We also have a generated target that you can regenerate after deploying a new environment.xml with the /opt/HPCCSystems/sbin/generate-hpccsystems-target.sh. It will list all your declared components on that local node. You can then do `systemctl list-dependencies hpccsystems-platform.target` and see a list of all running components, which is more like the old hpcc-init status that you're used to.

[amillar]

Hi Mgardner,

Thanks for getting back to me, this is really helpful and you have confirmed my suspicions that its part of a transition.

I also came across this blog which helped : https://hpccsystems.com/blog/systemd

I will be using systemctrl going forward to stop and start the platform and I will be keeping my eye out for new releases.

I will definitely look at this script /opt/HPCCSystems/sbin/generate-hpccsystems-target.sh

This command is another handy one to know as well systemctl list-dependencies hpccsystems-platform.target`

Thanks again for your help.

Best Regards

Antony