Uploaded image for project: 'Mender'
  1. Mender
  2. MEN-3945

During startup, Mender client terminates on SIGUSR1/SIGUSR2

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Rejected
    • Priority: (None)
    • Resolution: Won't Do
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Backlog:
      no
    • Days in progress:
      0

      Description

      If you do the following:

      for i in {1..10} ; do
      	echo "mender send-inventory"
      	/usr/bin/mender send-inventory
      	sleep 3
      done
      

      And then start the mender-client.service, you get something like this:

      Sep 10 06:37:40 localhost systemd[1]: mender-client-systemd-machine-id.service: Succeeded.
      Sep 10 06:37:50 raspberrypi3 mender-inventory[325]: mender send-inventory
      Sep 10 06:37:50 raspberrypi3 mender-inventory[325]: time="2020-09-10T06:37:50Z" level=error msg="failed to force updateCheck: could not find the PID of the mender daemon"
      Sep 10 06:37:53 raspberrypi3 mender-inventory[325]: mender send-inventory
      Sep 10 06:37:53 raspberrypi3 systemd[1]: mender-client.service: Main process exited, code=killed, status=12/USR2
      Sep 10 06:37:53 raspberrypi3 systemd[1]: mender-client.service: Failed with result 'signal'.
      

      Reason is probably that SIGUSR1/SIGUSR2 signals are fatal, until the Mender client actually registers signal handlers for these.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              oleorhagen Ole Petter Orhagen
              Reporter:
              mirzak Mirza Krak
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: