Uploaded image for project: 'HPCC'
  1. HPCC
  2. HPCC-23321

systemd startup issue with generic component name and [install] section

    XMLWordPrintable

Details

    • Bug
    • Status: Accepted
    • Major
    • Resolution: Unresolved
    • 7.6.18
    • None
    • Init system
    • None
    • Systemd enabled machines
    • Minor
    • Not applicable
    • na

    Description

      calls like `systemd start dafilesrv` are not working as ops expects and `systemd start dafilesrv@mydafilesrv.service` are returning an issue with the  [install] section missing.

       

      [root@System ~]# systemctl enable dafilesrv@mydafilesrv.service

      The unit files have no [Install] section. They are not meant to be enabled

      using systemctl.

      Possible reasons for having this kind of units are:

      1) A unit may be statically enabled by being symlinked from another unit's

         .wants/ or .requires/ directory.

      2) A unit's purpose may be to act as a helper for some other unit which has

         a requirement dependency on it.

      3) A unit may be started when needed via activation (socket, path, timer,

         D-Bus, udev, scripted systemctl call, ...).

      [root@System ~]# /opt/HPCCSystems/sbin/generate-hpccsystems-target.sh

      removing /etc/systemd/system/eclagent@myeclagent.service

      removing /etc/systemd/system/sasha@mysasha.service

      removing /etc/systemd/system/roxie@myroxie.service

      removing /etc/systemd/system/dali@mydali.service

      removing /etc/systemd/system/dfuserver@mydfuserver.service

      removing /etc/systemd/system/eclccserver@myeclccserver.service

      removing /etc/systemd/system/esp@myesp.service

      removing /etc/systemd/system/thor@mythor.service

      removing /etc/systemd/system/eclscheduler@myeclscheduler.service

      removing /etc/systemd/system/dafilesrv@mydafilesrv.service

      generating hpccsystems platform target from environment.xml

      [root@System ~]# systemctl enable dafilesrv@mydafilesrv.service

      The unit files have no [Install] section. They are not meant to be enabled

      using systemctl.

      Possible reasons for having this kind of units are:

      1) A unit may be statically enabled by being symlinked from another unit's

         .wants/ or .requires/ directory.

      2) A unit's purpose may be to act as a helper for some other unit which has

         a requirement dependency on it.

      3) A unit may be started when needed via activation (socket, path, timer,

         D-Bus, udev, scripted systemctl call, ...).

      Attachments

        Activity

          People

            Michael-Gardner Michael Gardner
            Michael-Gardner Michael Gardner
            Votes:
            0 Vote for this issue
            Watchers:
            8 Start watching this issue

            Dates

              Created:
              Updated: