Frantisek Sumsal
f53d56f1a3
In a couple of recent CI runs I noticed TEST-36 failing due to a missed service exit notification and a subsequent fail of the `grep` command: ``` [ 257.112153] H systemd[1]: Started numa-test.service. [ 257.114343] H systemd[899]: numa-test.service: Failed to set NUMA memory policy: Invalid argument [ 257.118270] H systemd[899]: numa-test.service: Failed at step NUMA_POLICY spawning /bin/sleep: Invalid argument [ 257.126170] H systemd[1]: Bus private-bus-connection: changing state RUNNING → CLOSING [ 257.130290] H systemd[1]: numa-test.service: Failed to send unit change signal for numa-test.service: Connection reset by peer [ 257.131567] H systemd[1]: Received SIGCHLD from PID 899 ((sleep)). [ 257.132870] H systemd[1]: Got disconnect on private connection. [ 257.134299] H systemd[1]: systemd-journald.service: Got notification message from PID 498 (FDSTORE=1) [ 257.135611] H systemd[1]: systemd-journald.service: Added fd 38 (n/a) to fd store. [ 257.136999] H systemd[1]: systemd-journald.service: Received EPOLLHUP on stored fd 38 (stored), closing. [ 257.366996] H testsuite-36.sh[536]: + stopJournalctl [ 257.366996] H testsuite-36.sh[536]: + local unit=init.scope [ 257.366996] H testsuite-36.sh[536]: + echo 'Force journald to write all queued messages' [ 257.366996] H testsuite-36.sh[536]: Force journald to write all queued messages [ 257.366996] H testsuite-36.sh[536]: + journalctl --sync [ 257.488642] H systemd-journald[498]: Received client request to rotate journal. [ 257.520821] H testsuite-36.sh[536]: + journalctl -u init.scope --cursor-file=jounalCursorFile [ 257.981399] H testsuite-36.sh[536]: + pid1StopUnit numa-test.service [ 257.984533] H testsuite-36.sh[536]: + systemctl stop numa-test.service [ 258.173656] H systemd[1]: Bus private-bus-connection: changing state AUTHENTICATING → RUNNING [ 258.180710] H systemd[1]: numa-test.service: Trying to enqueue job numa-test.service/stop/replace [ 258.182424] H systemd[1]: Added job numa-test.service/stop to transaction. [ 258.185234] H systemd[1]: numa-test.service: Installed new job numa-test.service/stop as 738 [ 258.187017] H systemd[1]: numa-test.service: Enqueued job numa-test.service/stop as 738 [ 258.239930] H testsuite-36.sh[536]: + grep 'numa-test.service: Main process exited, code=exited, status=242/NUMA' journal.log ``` Let's mitigate this by checking the test service exit status directly instead of relying on the notification.
System and Service Manager
Details
Most documentation is available on systemd's web site.
Assorted, older, general information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Code Map for information about this repository's layout and content.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.