青龙面板[Qinglong] icon

青龙面板[Qinglong]

青龙面板计划任务节点.详细API请参考：https://qinglong.online/api/

Actions64

Overview

The node integrates with the Qinglong panel API to manage scripts and other resources programmatically. Specifically, for the "脚本管理" (Script Management) resource and the "停止脚本" (Stop Script) operation, it allows users to stop a running script by specifying its path, filename, and process ID. This is useful in automation workflows where you need to control script execution remotely, such as stopping a misbehaving or no longer needed script on a Qinglong-managed environment.

Practical examples:

  • Automatically stop a script that exceeds a certain runtime.
  • Integrate script stopping into larger automation flows to manage system resources.
  • Remotely halt scripts based on external triggers or conditions.

Properties

Name Meaning
脚本路径 The directory path where the target script resides.
文件名 The name of the script file to be stopped.
进程ID The process ID (PID) of the running script instance to stop.

Output

The node outputs JSON data under the json.result field containing the response from the Qinglong API after attempting to stop the script. This typically includes success status, error messages if any, or other relevant information returned by the API about the stop operation.

No binary data output is involved in this operation.

Dependencies

  • Requires an API key credential for authenticating with the Qinglong panel API.
  • The node depends on the Qinglong API being accessible and properly configured.
  • No additional external services are required beyond the Qinglong API.

Troubleshooting

  • Common issues:

    • Incorrect script path or filename may cause the stop operation to fail.
    • Providing an invalid or non-existent process ID will result in failure to stop the script.
    • Network or authentication errors if the API key is missing, expired, or incorrect.

  • Error messages:

    • If the operation is not implemented or unsupported, the node throws an error indicating the operation is not yet implemented.
    • API errors from Qinglong (e.g., unauthorized, not found) will be surfaced in the node's output.

  • Resolutions:

    • Verify the script path and filename exactly match those on the Qinglong server.
    • Confirm the process ID corresponds to a currently running script process.
    • Ensure the API key credential is valid and has necessary permissions.
    • Check network connectivity to the Qinglong API endpoint.

Links and References

Discussion