ClamD サービスを開始できません。 [RHEL9]

ClamD サービスを開始できません。 [RHEL9]

私は現在これをフォローしていますガイドしかし、ClamAV自分のコンピュータに設定するとAlmaLinux 9.3ステップ11起動できず、clamd@service他のソースから多くの情報が見つからないため、他の人がこの問題に遭遇したかどうか疑問に思います。

[root@localhost tester]# sudo systemctl status clamd@service
× [email protected] - clamd scanner (service) daemon
     Loaded: loaded (/usr/lib/systemd/system/[email protected]; disabled; preset: disabled)
     Active: failed (Result: exit-code) since Thu 2023-12-28 12:08:15 GMT; 3min 26s ago
       Docs: man:clamd(8)
             man:clamd.conf(5)
             https://www.clamav.net/documents/
    Process: 6728 ExecStart=/usr/sbin/clamd -c /etc/clamd.d/service.conf (code=exited, status=1/FAILURE)
        CPU: 3ms

Dec 28 12:08:15 localhost.localdomain systemd[1]: [email protected]: Scheduled restart job, restart counter is at 5.
Dec 28 12:08:15 localhost.localdomain systemd[1]: Stopped clamd scanner (service) daemon.
Dec 28 12:08:15 localhost.localdomain systemd[1]: [email protected]: Start request repeated too quickly.
Dec 28 12:08:15 localhost.localdomain systemd[1]: [email protected]: Failed with result 'exit-code'.
Dec 28 12:08:15 localhost.localdomain systemd[1]: Failed to start clamd scanner (service) daemon.

提案された端末出力に基づいて、次のコマンドを実行しました。

$ journalctl -xeu [email protected]

░░ The process' exit code is 'exited' and its exit status is 1.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Dec 28 12:45:18 localhost.localdomain systemd[1]: Failed to start clamd scanner (service) daemon.
░░ Subject: A start job for unit [email protected] has failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A start job for unit [email protected] has finished with a failure.
░░
░░ The job identifier is 7444 and the job result is failed.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ Automatic restarting of the unit [email protected] has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Dec 28 12:45:18 localhost.localdomain systemd[1]: Stopped clamd scanner (service) daemon.
░░ Subject: A stop job for unit [email protected] has finished
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A stop job for unit [email protected] has finished.
░░
░░ The job identifier is 7568 and the job result is done.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Start request repeated too quickly.
Dec 28 12:45:18 localhost.localdomain systemd[1]: [email protected]: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ The unit [email protected] has entered the 'failed' state with result 'exit-code'.
Dec 28 12:45:18 localhost.localdomain systemd[1]: Failed to start clamd scanner (service) daemon.
░░ Subject: A start job for unit [email protected] has failed
░░ Defined-By: systemd
░░ Support: https://access.redhat.com/support
░░
░░ A start job for unit [email protected] has finished with a failure.
░░
░░ The job identifier is 7568 and the job result is failed.

答え1

コンテンツ/etc/clamd.d/scan.conf/etc/clamd.d/service.confファイルにコピーし、手順11で修正します。

それらが呼び出すsystemdユニットにはインスタンス名があり、@これは変数にユニットとして渡され、として参照されます%i。したがって、呼び出そうとすると、存在しないすべてのユニットファイルをsystemctl start clamd@service参照します。/etc/clamd.d/service.conf

デバイスが探しているプロファイルを作成したら起動する必要があります。

ちなみにユニットファイルは/usr/lib/systemd/system/[email protected]

関連情報