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

daserver usage and systemd call is wrong

    XMLWordPrintable

    Details

    • Type: Regression
    • Status: Resolved
    • Priority: Not specified
    • Resolution: Fixed
    • Affects Version/s: 8.2.26
    • Fix Version/s: 8.2.34, 8.4.10
    • Component/s: Dali
    • Labels:
      None
    • Environment:
      All?

      Description

      NOTE: This is affecting more versions I believe (I checked 8.2.24, 8.2.22, and couple others).

      Starting daserver in daemon mode through either systemctl or manually (daserver --daemon something)  is NOT working.

      According to daserver usage:

       

      --daemon|-d <instanceName>      : run daemon as instance
      

      Yet the code parsing arguments doesn't seem to care (at least at one point) about <instanceName>.

      Now when starting daserver in interactive mode, this is not an issue.

      When starting daserver in daemon mode, adding the <instanceName> will cause the program to exit right away.

      The dali@mydali.service ExecStart is defined as such:

      ExecStart=/opt/HPCCSystems/bin/daserver --daemon mydali

      For reference:

      https://github.com/hpcc-systems/HPCC-Platform/blob/community_8.2.26-1/dali/server/daserver.cpp#L429

      When parsing arguments there, it just skips the --daemon argument, and no <instanceName> is collected/swallowed.

      So the next argument will be "mydali" and it will fall in https://github.com/hpcc-systems/HPCC-Platform/blob/community_8.2.26-1/dali/server/daserver.cpp#L437 and exit.

      Since daemon(1,0) is used, any standard output is redirected to /dev/null (correct me if I'm wrong). So it's impossible to notice that in say syslog or anywhere else at the moment.

       

       

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Michael-Gardner Michael Gardner
              Reporter:
              lpezet Luc
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: