Uploaded image for project: 'CFEngine Community'
  1. CFEngine Community
  2. CFE-2079

bootstrap fails on Debian Wheezy configured with systemd. systemctl command should use unit-name with ".service" appended?

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Unconfirmed
    • Priority: Medium
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Bootstrap
    • Labels:
      None

      Description

      I have just installed cfengine-community-3.7.0. When bootstrapping I get the following error. It does sort of work if i edit the default policy files, adding ".service" after the unit name in the calls to "systemctl". I still get some errors, but I believe that is from a default policy or something I found inside libpromises.so.3.0.6, which I haven't changed.

      On newer versions of systemd it seems to work with and without ".service", so adding this should not break the newer versions, but it should improve compatability with slightly older versions of systemd, like the one in wheezy.

      /---Error message

      root@server:/var/cfengine# cf-agent --bootstrap 10.0.0.133
      error: Finished command related to promiser '/bin/systemctl restart cfengine3' – an error occurred, returned 1
      notice: Q: ".../systemctl rest": Failed to issue method call: Unit name cfengine3 is not valid.
      R: This host assumes the role of policy server
      R: Updated local policy from policy server
      R: Failed to start the server
      R: Did not start the scheduler
      R: You are running a hard-coded failsafe. Please use the following command instead.
      "/var/cfengine/bin/cf-agent" -f /var/cfengine/inputs/update.cf
      notice: Q: ".../cf-agent" -f u": error: Finished command related to promiser '/bin/systemctl -q start cfengine3' – an error occurred, returned 1
      Q: ".../cf-agent" -f u": notice: Q: ".../systemctl -q s": Failed to open /dev/tty: No such device or address
      Q: ".../cf-agent" -f u": Q: ".../systemctl -q s": Failed to issue method call: Unit name cfengine3 is not valid.
      Q: ".../cf-agent" -f u": error: Method 'maintain_cfe_systemd' failed in some repairs
      error: Bootstrapping failed, cf-execd is not running
      root@server:/var/cfengine#

      ---End error message

      /---System information

      root@server:/# cat /etc/debian_version
      7.8
      root@server:/# dpkg -l grep systemd
      ii libpam-systemd:amd64 44-11+deb7u4 amd64 system and service manager - PAM module
      ii libsystemd-daemon0:amd64 44-11+deb7u4 amd64 systemd utility library
      ii libsystemd-id128-0:amd64 44-11+deb7u4 amd64 systemd 128 bit ID utility library
      ii libsystemd-journal0:amd64 44-11+deb7u4 amd64 systemd journal utility library
      ii libsystemd-login0:amd64 44-11+deb7u4 amd64 systemd login utility library
      ii systemd 44-11+deb7u4 amd64 system and service manager
      ii systemd-gui 44-11+deb7u4 amd64 system and service manager - GUI
      root@server:/#

      ---End system information

        Attachments

          Activity

            People

            • Assignee:
              a10040 Kristian Amlie
              Reporter:
              dstensnes Daniel Stensnes
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:

                Summary Panel