[Help]Cannot start maldet

[greenhandzdl]

~ ❯ yay -R maldet                                                                                                                                 at 14:09:32
error: target not found: maldet
 -> exit status 1

~ ❯ yay -S maldet                                                                                                                                 at 14:09:36
AUR Explicit (1): maldet-1.6.5-1
:: PKGBUILD up to date, skipping download: maldet
  1 maldet                                   (Build Files Exist)
==> Packages to cleanBuild?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
  1 maldet                                   (Build Files Exist)
==> Diffs to show?
==> [N]one [A]ll [Ab]ort [I]nstalled [No]tInstalled or (1 2 3, 1-3, ^4)
==> 
==> Making package: maldet 1.6.5-1 (Sat 22 Apr 2023 02:09:45 PM CST)
==> Retrieving sources...
  -> Found 1.6.5.tar.gz
  -> Found maldet-update-signatures.service
  -> Found maldet-update-signatures.timer
==> Validating source files with sha256sums...
    1.6.5.tar.gz ... Passed
    maldet-update-signatures.service ... Passed
    maldet-update-signatures.timer ... Passed
:: (1/1) Parsing SRCINFO: maldet
==> Making package: maldet 1.6.5-1 (Sat 22 Apr 2023 02:09:46 PM CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found 1.6.5.tar.gz
  -> Found maldet-update-signatures.service
  -> Found maldet-update-signatures.timer
==> Validating source files with sha256sums...
    1.6.5.tar.gz ... Passed
    maldet-update-signatures.service ... Passed
    maldet-update-signatures.timer ... Passed
==> Removing existing $srcdir/ directory...
==> Extracting sources...
  -> Extracting 1.6.5.tar.gz with bsdtar
==> Starting prepare()...
==> Sources are ready.
 -> maldet-1.6.5-1 already made -- skipping build
==> Making package: maldet 1.6.5-1 (Sat 22 Apr 2023 02:09:47 PM CST)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> WARNING: Using existing $srcdir/ tree
==> Sources are ready.
loading packages...
resolving dependencies...
looking for conflicting packages...

Packages (1) maldet-1.6.5-1

Total Installed Size:  0.23 MiB

:: Proceed with installation? [Y/n] 
(1/1) checking keys in keyring                                                                 [########################################################] 100%
(1/1) checking package integrity                                                               [########################################################] 100%
(1/1) loading package files                                                                    [########################################################] 100%
(1/1) checking for file conflicts                                                              [########################################################] 100%
(1/1) checking available disk space                                                            [########################################################] 100%
:: Processing package changes...
(1/1) installing maldet                                                                        [########################################################] 100%

You are strongly advised to update signature version by executing this command:

    systemctl enable --now maldet-update-signatures.timer
    systemctl start maldet-update-signatures.service

Signatures must be updated at least once before running maldet.

:: Running post-transaction hooks...
(1/3) Reloading system manager configuration...
(2/3) Arming ConditionNeedsUpdate...
(3/3) Refreshing PackageKit...

~ ❯     systemctl enable --now maldet-update-signatures.timer                                                                             took 7s at 14:09:48

Created symlink /etc/systemd/system/timers.target.wants/maldet-update-signatures.timer → /usr/lib/systemd/system/maldet-update-signatures.timer.

~ ❯     systemctl start maldet-update-signatures.service                                                                                  took 7s at 14:10:04



~ ❯                                                                                                                                      took 16s at 14:10:32

~ ❯ sudo systemctl start maldet.service                                                                                                           at 14:10:32
Job for maldet.service failed because the service did not take the steps required by its unit configuration.
See "systemctl status maldet.service" and "journalctl -xeu maldet.service" for details.

~ ❯ sudo systemctl status maldet.service                                                                                                          at 14:10:46
× maldet.service - Linux Malware Detect monitoring - maldet
     Loaded: loaded (/usr/lib/systemd/system/maldet.service; enabled; preset: disabled)
     Active: failed (Result: protocol) since Sat 2023-04-22 14:10:46 CST; 9s ago
    Process: 13544 ExecStart=/usr/bin/maldet --monitor $default_monitor_mode (code=exited, status=0/SUCCESS)
        CPU: 48ms

Apr 22 14:10:46 archlinux systemd[1]: Starting Linux Malware Detect monitoring - maldet...
Apr 22 14:10:46 archlinux maldet[13544]: Linux Malware Detect v1.6.5
Apr 22 14:10:46 archlinux maldet[13544]:             (C) 2002-2023, R-fx Networks <proj@rfxn.com>
Apr 22 14:10:46 archlinux maldet[13544]:             (C) 2023, Ryan MacDonald <ryan@rfxn.com>
Apr 22 14:10:46 archlinux maldet[13544]: This program may be freely redistributed under the terms of the GNU GPL v2
Apr 22 14:10:46 archlinux maldet[13544]: maldet(13544): {mon} could not find monitor mode dependency 'ed' in PATH, please apt/yum/dnf install ed and try agai>
Apr 22 14:10:46 archlinux systemd[1]: maldet.service: Can't open PID file /var/lib/maldet/tmp/inotifywait.pid (yet?) after start: Bad file descriptor
Apr 22 14:10:46 archlinux systemd[1]: maldet.service: Failed with result 'protocol'.
Apr 22 14:10:46 archlinux systemd[1]: Failed to start Linux Malware Detect monitoring - maldet.

[waja]

How about reporting this against you distribution package? Looks like distribution specific issue in the first place.