原因:命令在本地服务器上执行失败,退出代码为非零

Cause: Command execution failed on the local server with non-zero exit code

无法从目标服务器获取信息 原因:命令在本地服务器上执行失败,退出代码为非零。

  command: /usr/local/psa/bin/ipmanage --xml-info
exit code: 255
stdout: <ipinfo>
<ip name="193.160.214.57">
<state>0</state>
<type>shared</type>
<ip_address>193.160.214.57</ip_address>
<mask>255.255.255.255</mask>
<iface>venet0</iface>
<clients>0</clients>
<hostings>0</hostings>
<ftps>false</ftps>
<publicIp></publicIp>
</ip>
</ipinfo>

stderr: [2019-10-20 21:21:51.133] ERR [util_exec] proc_close() failed ['/usr/local/psa/admin/bin/f2bmng' '--reload'] with exit code [1]
PHP Fatal error: Uncaught PleskUtilException: f2bmng failed: 2019-10-20 21:21:51,115 fail2ban.jailreader [17670]: ERROR No file(s) found for glob /var/log/secure
2019-10-20 21:21:51,115 fail2ban [17670]: ERROR Failed during configuration: Have not found any log file for ssh jail
ERROR:__main__:Command '['/usr/bin/fail2ban-client', 'reload']' returned non-zero exit status 255 in /usr/local/psa/admin/plib/Service/Agent.php:210
Stack trace:
#0 /usr/local/psa/admin/plib/Ip/Ban/Manager.php(490): Service_Agent->execAndGetResponse('f2bmng', Array, '')
#1 /usr/local/psa/admin/plib/Ip/Ban/Manager.php(458): Ip_Ban_Manager->_callUtility('--reload')
#2 /usr/local/psa/admin/plib/Fail2Ban/EventListener.php(123): Ip_Ban_Manager->reload()
#3 [internal function]: Plesk\Fail2Ban\EventListener->applyChanges()
#4 {main}
thrown in /usr/local/psa/admin/plib/Service/Agent.php on line 210

That is a critical error, migration was stopped.

我不知道你的plesk是什么"wrong"(不太熟悉),但是fail2ban错误很简单:

ERROR No file(s) found for glob /var/log/secure 2019-10-20 21:21:51,115 fail2ban [17670]: ERROR Failed during configuration: Have not found any log file for ssh jail

您的 ssh 监狱似乎配置为监视 /var/log/secure,但实际上并不存在。要么您必须在 ssh 记录身份验证错误的地方指定正确的 logpath (/var/log/auth.log?); 或者如果它是您系统上的系统日志,您必须为此指定 backend = systemd

相关的 fail2ban jail.local 将是:

[ssh]
# backend = systemd
logpath = /var/log/auth.log

但您当然也可以在 plesk 设置中进行配置。

另请注意,您的监狱名为 ssh,fail2ban 的原始默认监狱通常为 sshd(但您的维护者确实可以使用此名称对其进行配置)。