From 05aec1fdbffa8e6b99a4a09bd325ee9242668a9c Mon Sep 17 00:00:00 2001 From: Saikrishna Arcot Date: Wed, 10 Apr 2024 18:48:51 -0700 Subject: [PATCH] Manually start and stop rsyslogd For Bookworm, the init.d service file for rsyslogd is removed, and the only script to start and stop rsyslogd is the systemd service file. However, that can only be used if systemd is being used as the init manager, which isn't the case for our docker containers. As an alternative, manually start and stop rsyslogd ourselves. Signed-off-by: Saikrishna Arcot --- .azure-pipelines/build-template.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.azure-pipelines/build-template.yml b/.azure-pipelines/build-template.yml index 3e5a1417a..9ba2d9531 100644 --- a/.azure-pipelines/build-template.yml +++ b/.azure-pipelines/build-template.yml @@ -98,7 +98,7 @@ jobs: sudo mkdir -m 755 /var/run/sswsyncd sudo apt-get install -y rsyslog - sudo service rsyslog start + sudo rsyslogd cat /etc/apt/sources.list dpkg --list | grep libnl @@ -167,7 +167,8 @@ jobs: displayName: "Compile sonic sairedis with coverage enabled" - script: | sudo cp azsyslog.conf /etc/rsyslog.conf - sudo service rsyslog restart + sudo killall rsyslogd + sudo rsyslogd displayName: "Update rsyslog.conf" - ${{ if eq(parameters.run_unit_test, true) }}: - script: |