Articles in this section

See more

Watchdog security scan fails in Plesk: Non-existent pathname: /usr/bin/lwp-request

Avatar
Pavel Rozental
Updated
Follow
Plesk Onyx for Linux kb: technical Plesk Obsidian for Linux

Applicable to:

  • Plesk Obsidian for Linux
  • Plesk Onyx for Linux

Symptoms

Watchdog security scan Plesk > Extensions > My Extensions > Watchdog > Open > Security > Start fails with error:

CONFIG_TEXT: Invalid SCRIPTWHITELIST configuration option: Non-existent pathname: /usr/bin/lwp-request

Cause

Binary file /usr/bin/lwp-request doesn't exist on the server. This file is part of "perl-libwww-perl" package that is not available in system repositories.

Resolution

  1. Connect to the server via SSH as a root user.

  2.  Create backup of rkhunter configuration file:

    # cp /usr/local/psa/etc/modules/watchdog/rkhunter.conf{,_orig}

  3. Comment SCRIPTWHITELIST string using below command:

    # sed -i 's@SCRIPTWHITELIST=/usr/bin/lwp-request@#SCRIPTWHITELIST=/usr/bin/lwp-request@g' /usr/local/psa/etc/modules/watchdog/rkhunter.conf

Comments

1 comment

Sort by Date Votes
  • Avatar
    Nicolas Guichard

    Hi,

    Thanks for the advice - however, it seems that each time there's a Plesk update, the rkhunter.conf file is replaced, and this manipulation has to be done again.

    Would you have an idea about how to ensure the fix remains stable despite Plesk updates ? Should we just create an empty lwp-request file in user/bin instead of uncommenting the line, what do you think ?

    Thanks a lot

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request

Related articles