[Slackbuilds-users] crmsh not working

JCA 1.41421 at gmail.com
Thu Mar 7 16:30:45 UTC 2019

I am beginning to wonder if this is at all useable under Slackware. With
version 2.2.1 I am getting the following:

# crm
crm(live)# cluster
crm(live)cluster# init
ERROR: cluster.init: Error when loading script init: Failed to load yaml
module: No module named yaml

I installed PyYAML from Slackbuilds, and this error disappeared. But things
were not any better afterwards:

# crm cluster init --name FirstCluster --nodes "NodeOne NodeTwo"
INFO: Initialize a new cluster
INFO: Nodes: --name, FirstCluster, --nodes, NodeOne, NodeTwo
Traceback (most recent call last):
  File "/usr/sbin/crm", line 54, in <module>
    rc = main.run()
  File "/usr/lib64/python2.7/site-packages/crmsh/main.py", line 362, in run
    return main_input_loop(context, user_args)
  File "/usr/lib64/python2.7/site-packages/crmsh/main.py", line 244, in
    rc = handle_noninteractive_use(context, user_args)
  File "/usr/lib64/python2.7/site-packages/crmsh/main.py", line 200, in
    if context.run(' '.join(l)):
  File "/usr/lib64/python2.7/site-packages/crmsh/ui_context.py", line 75,
in run
    rv = self.execute_command() is not False
  File "/usr/lib64/python2.7/site-packages/crmsh/ui_context.py", line 245,
in execute_command
    rv = self.command_info.function(*arglist)
  File "/usr/lib64/python2.7/site-packages/crmsh/ui_cluster.py", line 110,
in do_init
    return scripts.run(script, script_args(args), script_printer())
  File "/usr/lib64/python2.7/site-packages/crmsh/scripts.py", line 2059, in
    opts = _make_options(params)
  File "/usr/lib64/python2.7/site-packages/crmsh/scripts.py", line 391, in
    opts = parallax.Options()
NameError: global name 'parallax' is not defined

This is getting more and more disappointing. With version 3.0.3 things are,
if anything, even more discouraging - it seems to assume the presence of an
infrastructure found in distributions such as Red Hat, Ubuntu and Debian,
but not in Slackware:

# crm cluster init --name ClusterOne --nodes "nodeone nodetwo"
! NTP is not configured to start at system boot.
! No watchdog device found. If SBD is used, the cluster will be unable to
start without a watchdog.
Do you want to continue anyway (y/n)? y
! Firewall: Could not open ports tcp=30865|5560|7630|21064, udp=
ERROR: cluster.init: Failed to start sshd.service

Just about every output line above represents what I described:
   1) The ntpd daemon is running in this system, and /etc/rc.d/rc.ntpd is
executable. Either it is trying to do something with the concourse of
systemd, or it is looking for SystemV init files.
   2) No clue about the watchdog warning.
   3) There are no iptables rules in this system - root can open any ports
it wants. Maybe it is looking for the firewalld daemon?
   4) sshd.service is how one would typically refer to the SSH daemon in
the Linux distributions above, which start it with incantations like
"service sshd start", which does not exist in Slackware. The SSH daemon was
already running in this system, anyway, and /etc/rc.d/rc.sshd is executable.

Anybody been able to get this (either version) to work at all under

On Wed, Mar 6, 2019 at 1:29 PM JCA <1.41421 at gmail.com> wrote:

> By the way, the crmsh version in Slackbuilds (2.2.1) is almost three years
> old. I used the Slackbuilds build script to build the latest stable release
> (3.0.3) as retrieved from the crmsh github repository; it builds correctly,
> and seems to run fine. Interestingly, it reports itself to be version
> 3.0.1, not 3.0.3. That seems to be something in the build framework as
> packaged by the crmsh people - nothing to do with the Slackbuilds build
> script.
> On Wed, Mar 6, 2019 at 7:40 AM JCA <1.41421 at gmail.com> wrote:
>> Thanks. After installing the lxml Python component, crm starts with no
>> problem.
>> On Tue, Mar 5, 2019 at 10:05 PM Jeremy Hansen <jebrhansen+SBo at gmail.com>
>> wrote:
>>> On Tue, Mar 5, 2019, 6:23 PM JCA <1.41421 at gmail.com> wrote:
>>>> I installed the crmsh package into two freshly installed Slackware 14.2
>>>> systems, fully patched. According to the info file for this package, it
>>>> does not have any explicit dependencies. I nevertheless installed
>>>> pacemaker, and all of its dependencies, for that's the context in which I
>>>> am going to use crmsh.
>>>> When I try to invoke the crm executable that is distributed with crmsh,
>>>> here is what I am getting:
>>>> # crm
>>>> Fatal error:
>>>>         No module named lxml
>>>>         No module named modules
>>>>     Failed to start crmsh! This is likely due to a broken
>>>>     installation or a missing dependency.
>>>>     If you are using a packaged version of crmsh, please try
>>>>     reinstalling the package. Also check your PYTHONPATH and
>>>>     make sure that the crmsh module is reachable.
>>>>     Please file an issue describing your installation at
>>>>     https://github.com/Clusterlabs/crmsh/issues/ .
>>>> PYTHONPATH is not set in my shell, and it is not found in any file in
>>>> /etc/profile.d. I tried setting it myself with
>>>> export PYTHONPATH=/usr/lib64/python2.7/site-packages/crmsh
>>>> and a few variations of the above, but it made no difference.
>>> Looks like there might be some undocumented dependencies somewhere.
>>> Based on your error message, I'm assuming you need
>>> https://slackbuilds.org/repository/14.2/python/lxml/ for the missing
>>> "lxml", but I'm not sure what you'd need for the missing "modules".
>>> Jeremy
>>>> _______________________________________________
>>> SlackBuilds-users mailing list
>>> SlackBuilds-users at slackbuilds.org
>>> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
>>> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
>>> FAQ - https://slackbuilds.org/faq/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20190307/fe3e6b0e/attachment-0001.html>

More information about the SlackBuilds-users mailing list