如何通过AWS IoT Job实现IoT设备中systemd服务的启停与重启？

Hey there! Since you’ve already got device reboot working via AWS IoT Jobs with the AWS IoT Device SDK for JavaScript, extending this to manage your systemd services (like sourcefileName.service) is really straightforward. Let’s walk through how to implement start/stop/restart actions step by step:

First, modify your existing job handling code to recognize new parameters in the job document that specify what action to take and which service to target. The job document you send from AWS IoT Core will need two key fields: action (either start, stop, or restart) and serviceName (your target service, e.g., sourcefileName.service).

Here’s how to extend your handler code:

const awsIot = require('aws-iot-device-sdk');
const { exec } = require('child_process');

// Initialize your device client (you likely already have this set up)
const device = awsIot.device({
  keyPath: 'private.pem.key',
  certPath: 'certificate.pem.crt',
  caPath: 'root-CA.crt',
  clientId: 'your-device-unique-id',
  host: 'your-iot-core-endpoint.amazonaws.com'
});

// Handle incoming IoT Jobs
device.on('job', (job) => {
  console.log(`Received job request: ${job.jobId}`);
  const jobDoc = job.document;

  // Validate required parameters exist in the job document
  if (!jobDoc.action || !jobDoc.serviceName) {
    // Report failure to AWS IoT Core if params are missing
    device.jobUpdate(job.jobId, 'FAILED', {
      statusDetails: { message: 'Missing required fields: action and serviceName are mandatory' }
    }, (err) => {
      if (err) console.error('Failed to send job status update:', err);
    });
    return;
  }

  const { action, serviceName } = jobDoc;
  // Validate the action is one of our allowed values
  const validActions = ['start', 'stop', 'restart'];
  if (!validActions.includes(action)) {
    device.jobUpdate(job.jobId, 'FAILED', {
      statusDetails: { message: `Invalid action: use one of ${validActions.join(', ')}` }
    }, (err) => {
      if (err) console.error('Failed to send job status update:', err);
    });
    return;
  }

  // Build the systemctl command (we use sudo since systemctl requires root privileges)
  const command = `sudo systemctl ${action} ${serviceName}`;

  // Execute the command on the device
  exec(command, (error, stdout, stderr) => {
    let jobStatus = 'SUCCEEDED';
    let statusMsg = `Successfully ${action}ed service ${serviceName}`;

    if (error) {
      jobStatus = 'FAILED';
      statusMsg = `Failed to ${action} ${serviceName}: ${stderr || error.message}`;
      console.error(statusMsg);
    } else if (stderr) {
      // Some systemctl commands output warnings to stderr even on success
      console.warn(`Command warnings: ${stderr}`);
    }

    // Send the final job status back to AWS IoT Core
    device.jobUpdate(job.jobId, jobStatus, {
      statusDetails: {
        message: statusMsg,
        stdout: stdout.trim(),
        stderr: stderr.trim()
      }
    }, (err) => {
      if (err) console.error('Failed to send job completion update:', err);
      else console.log(`Job ${job.jobId} marked as ${jobStatus}`);
    });
  });
});

When you create a new IoT Job in the AWS Console, use a job document that specifies the action and service name. For example:

{
  "action": "start",
  "serviceName": "sourcefileName.service"
}

Swap out "start" for "stop" or "restart" depending on the action you want to perform.

Since systemctl requires root access, the user running your Node.js script needs permission to execute those specific sudo systemctl commands without entering a password (otherwise the command will hang waiting for input).

To set this up:

1. On your device, run sudo visudo to edit the sudoers file (this is the safe way to modify it).
2. Add this line at the end (replace your-device-user with the actual user running your SDK script):

your-device-user ALL=(ALL) NOPASSWD: /bin/systemctl start sourcefileName.service, /bin/systemctl stop sourcefileName.service, /bin/systemctl restart sourcefileName.service

This restricts the user to only those three commands, which is more secure than granting full sudo access.

1. Deploy your updated Node.js script to the device and start it.
2. Create a new IoT Job in AWS IoT Core with your target job document.
3. Check the job status in the AWS Console—you should see it transition to SUCCEEDED if everything works.
4. Verify the service state on your device with systemctl status sourcefileName.service to confirm the action took effect.

• Error Handling: The code includes basic validation for missing parameters and invalid actions, but you can expand this to handle edge cases (like a non-existent service) if needed.
• Debugging: The job status update includes stdout and stderr, which is super helpful for troubleshooting if a command fails.
• Security: Avoid granting broader sudo permissions than necessary—least privilege is always best for IoT devices.

内容的提问来源于stack exchange，提问作者Marimuthu