[systemd] Refusing to accept PID outside of service control group, acquired through unsafe symlink chain

Description

[Unit]
Description=apollo config service
After=network.target

[Service]
Type=forking
Restart=on-failure
PIDFile=/apollo/configservice/apollo-configservice/apollo-configservice.pid
# RemainAfterExit=true
ExecStart=/apollo/configservice/scripts/startup.sh
ExecStop= /apollo/configservice/scripts/shutdown.sh
[Install]
WantedBy=multi-user.target

Contributor guide

Tech stack

shelljava

Domain

backenddevops

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

2

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

mostly clear

Prerequisites

basic systemd knowledgeshell scripting

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

75

Research direction

Investigate the startup.sh script in the apollo configservice repository to understand how the PID file is created. Consider modifying the systemd unit to use 'Type=simple' or 'Type=forking' with proper cgroup handling, or ensuring the PID file is written within the service's cgroup. Check any existing discussions in the issue comments for potential solutions.